Nov 14 05:56:40 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8387" x-info="http://www.rsyslog.com"] start
Nov 14 05:56:40 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Nov 14 05:56:40 node-1 rsyslogd: rsyslogd's groupid changed to 104
Nov 14 05:56:40 node-1 rsyslogd: rsyslogd's userid changed to 101
Nov 14 05:56:40 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Nov 14 05:56:40 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Nov 14 05:56:40 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Nov 14 05:56:40 node-1 kernel: [    0.000000] Linux version 3.13.0-101-generic (buildd@lgw01-40) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #148-Ubuntu SMP Thu Oct 20 22:08:32 UTC 2016 (Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39)
Nov 14 05:56:40 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-101-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=b64b3ab2-fcc3-4e27-ab13-6d9974dcf43e nomdmonddf nomdmonisw
Nov 14 05:56:40 node-1 kernel: [    0.000000] KERNEL supported cpus:
Nov 14 05:56:40 node-1 kernel: [    0.000000]   Intel GenuineIntel
Nov 14 05:56:40 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Nov 14 05:56:40 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Nov 14 05:56:40 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Nov 14 05:56:40 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Nov 14 05:56:40 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Nov 14 05:56:40 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Nov 14 05:56:40 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Nov 14 05:56:40 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Nov 14 05:56:40 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Nov 14 05:56:40 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Nov 14 05:56:40 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Nov 14 05:56:40 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Nov 14 05:56:40 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Nov 14 05:56:40 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Nov 14 05:56:40 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Nov 14 05:56:40 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Nov 14 05:56:40 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov 14 05:56:40 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Nov 14 05:56:40 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Nov 14 05:56:40 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Nov 14 05:56:40 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
Nov 14 05:56:40 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov 14 05:56:40 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Nov 14 05:56:40 node-1 kernel: [    0.000000] No AGP bridge found
Nov 14 05:56:40 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Nov 14 05:56:40 node-1 kernel: [    0.000000] MTRR default type: write-back
Nov 14 05:56:40 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Nov 14 05:56:40 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Nov 14 05:56:40 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Nov 14 05:56:40 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Nov 14 05:56:40 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Nov 14 05:56:40 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Nov 14 05:56:40 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Nov 14 05:56:40 node-1 kernel: [    0.000000]   2 disabled
Nov 14 05:56:40 node-1 kernel: [    0.000000]   3 disabled
Nov 14 05:56:40 node-1 kernel: [    0.000000]   4 disabled
Nov 14 05:56:40 node-1 kernel: [    0.000000]   5 disabled
Nov 14 05:56:40 node-1 kernel: [    0.000000]   6 disabled
Nov 14 05:56:40 node-1 kernel: [    0.000000]   7 disabled
Nov 14 05:56:40 node-1 kernel: [    0.000000]   8 disabled
Nov 14 05:56:40 node-1 kernel: [    0.000000]   9 disabled
Nov 14 05:56:40 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Nov 14 05:56:40 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Nov 14 05:56:40 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Nov 14 05:56:40 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Nov 14 05:56:40 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Nov 14 05:56:40 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Nov 14 05:56:40 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Nov 14 05:56:40 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Nov 14 05:56:40 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Nov 14 05:56:40 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Nov 14 05:56:40 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Nov 14 05:56:40 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Nov 14 05:56:40 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Nov 14 05:56:40 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Nov 14 05:56:40 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Nov 14 05:56:40 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Nov 14 05:56:40 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Nov 14 05:56:40 node-1 kernel: [    0.000000] BRK [0x01fe6000, 0x01fe6fff] PGTABLE
Nov 14 05:56:40 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Nov 14 05:56:40 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Nov 14 05:56:40 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Nov 14 05:56:40 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Nov 14 05:56:40 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Nov 14 05:56:40 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Nov 14 05:56:40 node-1 kernel: [    0.000000] Zone ranges:
Nov 14 05:56:40 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] Movable zone start for each node
Nov 14 05:56:40 node-1 kernel: [    0.000000] Early memory node ranges
Nov 14 05:56:40 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Nov 14 05:56:40 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Nov 14 05:56:40 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Nov 14 05:56:40 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Nov 14 05:56:40 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Nov 14 05:56:40 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Nov 14 05:56:40 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Nov 14 05:56:40 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Nov 14 05:56:40 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Nov 14 05:56:40 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Nov 14 05:56:40 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Nov 14 05:56:40 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Nov 14 05:56:40 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Nov 14 05:56:40 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Nov 14 05:56:40 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Nov 14 05:56:40 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Nov 14 05:56:40 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Nov 14 05:56:40 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Nov 14 05:56:40 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Nov 14 05:56:40 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Nov 14 05:56:40 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Nov 14 05:56:40 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Nov 14 05:56:40 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Nov 14 05:56:40 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Nov 14 05:56:40 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 
Nov 14 05:56:40 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Nov 14 05:56:40 node-1 kernel: [    0.000000] Policy zone: Normal
Nov 14 05:56:40 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-101-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=b64b3ab2-fcc3-4e27-ab13-6d9974dcf43e nomdmonddf nomdmonisw
Nov 14 05:56:40 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Nov 14 05:56:40 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Nov 14 05:56:40 node-1 kernel: [    0.000000] Checking aperture...
Nov 14 05:56:40 node-1 kernel: [    0.000000] No AGP bridge found
Nov 14 05:56:40 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Nov 14 05:56:40 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Nov 14 05:56:40 node-1 kernel: [    0.000000] Memory: 32653448K/33280636K available (7429K kernel code, 1147K rwdata, 3420K rodata, 1340K init, 1448K bss, 627188K reserved)
Nov 14 05:56:40 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Nov 14 05:56:40 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Nov 14 05:56:40 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Nov 14 05:56:40 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Nov 14 05:56:40 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Nov 14 05:56:40 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Nov 14 05:56:40 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Nov 14 05:56:40 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Nov 14 05:56:40 node-1 kernel: [    0.000000] console [tty0] enabled
Nov 14 05:56:40 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Nov 14 05:56:40 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Nov 14 05:56:40 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Nov 14 05:56:40 node-1 kernel: [    0.000000] hpet clockevent registered
Nov 14 05:56:40 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Nov 14 05:56:40 node-1 kernel: [    0.004000] tsc: Detected 3491.598 MHz processor
Nov 14 05:56:40 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.19 BogoMIPS (lpj=13966392)
Nov 14 05:56:40 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Nov 14 05:56:40 node-1 kernel: [    0.000045] Security Framework initialized
Nov 14 05:56:40 node-1 kernel: [    0.000063] AppArmor: AppArmor initialized
Nov 14 05:56:40 node-1 kernel: [    0.000064] Yama: becoming mindful.
Nov 14 05:56:40 node-1 kernel: [    0.001471] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Nov 14 05:56:40 node-1 kernel: [    0.006432] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Nov 14 05:56:40 node-1 kernel: [    0.008364] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov 14 05:56:40 node-1 kernel: [    0.008392] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov 14 05:56:40 node-1 kernel: [    0.008684] Initializing cgroup subsys memory
Nov 14 05:56:40 node-1 kernel: [    0.008693] Initializing cgroup subsys devices
Nov 14 05:56:40 node-1 kernel: [    0.008695] Initializing cgroup subsys freezer
Nov 14 05:56:40 node-1 kernel: [    0.008696] Initializing cgroup subsys blkio
Nov 14 05:56:40 node-1 kernel: [    0.008698] Initializing cgroup subsys perf_event
Nov 14 05:56:40 node-1 kernel: [    0.008700] Initializing cgroup subsys hugetlb
Nov 14 05:56:40 node-1 kernel: [    0.008719] CPU: Physical Processor ID: 0
Nov 14 05:56:40 node-1 kernel: [    0.008720] CPU: Processor Core ID: 0
Nov 14 05:56:40 node-1 kernel: [    0.008724] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Nov 14 05:56:40 node-1 kernel: [    0.008724] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Nov 14 05:56:40 node-1 kernel: [    0.009418] mce: CPU supports 22 MCE banks
Nov 14 05:56:40 node-1 kernel: [    0.009446] CPU0: Thermal monitoring enabled (TM1)
Nov 14 05:56:40 node-1 kernel: [    0.009466] process: using mwait in idle threads
Nov 14 05:56:40 node-1 kernel: [    0.009469] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Nov 14 05:56:40 node-1 kernel: [    0.009469] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Nov 14 05:56:40 node-1 kernel: [    0.009469] tlb_flushall_shift: 6
Nov 14 05:56:40 node-1 kernel: [    0.009557] Freeing SMP alternatives memory: 32K (ffffffff81e6f000 - ffffffff81e77000)
Nov 14 05:56:40 node-1 kernel: [    0.010300] ACPI: Core revision 20131115
Nov 14 05:56:40 node-1 kernel: [    0.023009] ACPI: All ACPI Tables successfully acquired
Nov 14 05:56:40 node-1 kernel: [    0.023184] ftrace: allocating 28664 entries in 112 pages
Nov 14 05:56:40 node-1 kernel: [    0.031982] dmar: Host address width 46
Nov 14 05:56:40 node-1 kernel: [    0.031984] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Nov 14 05:56:40 node-1 kernel: [    0.031990] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov 14 05:56:40 node-1 kernel: [    0.031992] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Nov 14 05:56:40 node-1 kernel: [    0.031995] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov 14 05:56:40 node-1 kernel: [    0.031997] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Nov 14 05:56:40 node-1 kernel: [    0.031998] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Nov 14 05:56:40 node-1 kernel: [    0.031999] dmar: ATSR flags: 0x0
Nov 14 05:56:40 node-1 kernel: [    0.032000] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Nov 14 05:56:40 node-1 kernel: [    0.032002] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Nov 14 05:56:40 node-1 kernel: [    0.032117] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Nov 14 05:56:40 node-1 kernel: [    0.032119] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Nov 14 05:56:40 node-1 kernel: [    0.032120] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Nov 14 05:56:40 node-1 kernel: [    0.032121] HPET id 0 under DRHD base 0xc7ffc000
Nov 14 05:56:40 node-1 kernel: [    0.032122] Your BIOS is broken and requested that x2apic be disabled.
Nov 14 05:56:40 node-1 kernel: [    0.032122] This will slightly decrease performance.
Nov 14 05:56:40 node-1 kernel: [    0.032122] Use 'intremap=no_x2apic_optout' to override BIOS request.
Nov 14 05:56:40 node-1 kernel: [    0.032555] Enabled IRQ remapping in xapic mode
Nov 14 05:56:40 node-1 kernel: [    0.032556] x2apic not enabled, IRQ remapping is in xapic mode
Nov 14 05:56:40 node-1 kernel: [    0.032560] Switched APIC routing to physical flat.
Nov 14 05:56:40 node-1 kernel: [    0.033147] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov 14 05:56:40 node-1 kernel: [    0.072793] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Nov 14 05:56:40 node-1 kernel: [    0.072799] TSC deadline timer enabled
Nov 14 05:56:40 node-1 kernel: [    0.072806] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Nov 14 05:56:40 node-1 kernel: [    0.072812] ... version:                3
Nov 14 05:56:40 node-1 kernel: [    0.072813] ... bit width:              48
Nov 14 05:56:40 node-1 kernel: [    0.072814] ... generic registers:      4
Nov 14 05:56:40 node-1 kernel: [    0.072815] ... value mask:             0000ffffffffffff
Nov 14 05:56:40 node-1 kernel: [    0.072816] ... max period:             0000ffffffffffff
Nov 14 05:56:40 node-1 kernel: [    0.072817] ... fixed-purpose events:   3
Nov 14 05:56:40 node-1 kernel: [    0.072818] ... event mask:             000000070000000f
Nov 14 05:56:40 node-1 kernel: [    0.074256] x86: Booting SMP configuration:
Nov 14 05:56:40 node-1 kernel: [    0.088458] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Nov 14 05:56:40 node-1 kernel: [    0.074258] .... node  #0, CPUs:        #1  #2  #3
Nov 14 05:56:40 node-1 kernel: [    0.116364] .... node  #1, CPUs:    #4  #5  #6  #7
Nov 14 05:56:40 node-1 kernel: [    0.270478] .... node  #0, CPUs:    #8  #9 #10 #11
Nov 14 05:56:40 node-1 kernel: [    0.326098] .... node  #1, CPUs:   #12 #13 #14 #15
Nov 14 05:56:40 node-1 kernel: [    0.383149] x86: Booted up 2 nodes, 16 CPUs
Nov 14 05:56:40 node-1 kernel: [    0.383152] smpboot: Total of 16 processors activated (111743.62 BogoMIPS)
Nov 14 05:56:40 node-1 kernel: [    0.407988] devtmpfs: initialized
Nov 14 05:56:40 node-1 kernel: [    0.410302] EVM: security.selinux
Nov 14 05:56:40 node-1 kernel: [    0.410303] EVM: security.SMACK64
Nov 14 05:56:40 node-1 kernel: [    0.410304] EVM: security.ima
Nov 14 05:56:40 node-1 kernel: [    0.410305] EVM: security.capability
Nov 14 05:56:40 node-1 kernel: [    0.410355] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Nov 14 05:56:40 node-1 kernel: [    0.411004] pinctrl core: initialized pinctrl subsystem
Nov 14 05:56:40 node-1 kernel: [    0.411066] regulator-dummy: no parameters
Nov 14 05:56:40 node-1 kernel: [    0.411098] RTC time:  5:56:03, date: 11/14/16
Nov 14 05:56:40 node-1 kernel: [    0.411131] NET: Registered protocol family 16
Nov 14 05:56:40 node-1 kernel: [    0.411214] cpuidle: using governor ladder
Nov 14 05:56:40 node-1 kernel: [    0.411216] cpuidle: using governor menu
Nov 14 05:56:40 node-1 kernel: [    0.411250] ACPI: bus type PCI registered
Nov 14 05:56:40 node-1 kernel: [    0.411252] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov 14 05:56:40 node-1 kernel: [    0.411296] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Nov 14 05:56:40 node-1 kernel: [    0.411299] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Nov 14 05:56:40 node-1 kernel: [    0.425051] PCI: Using configuration type 1 for base access
Nov 14 05:56:40 node-1 kernel: [    0.426040] bio: create slab <bio-0> at 0
Nov 14 05:56:40 node-1 kernel: [    0.426321] ACPI: Added _OSI(Module Device)
Nov 14 05:56:40 node-1 kernel: [    0.426322] ACPI: Added _OSI(Processor Device)
Nov 14 05:56:40 node-1 kernel: [    0.426324] ACPI: Added _OSI(3.0 _SCP Extensions)
Nov 14 05:56:40 node-1 kernel: [    0.426325] ACPI: Added _OSI(Processor Aggregator Device)
Nov 14 05:56:40 node-1 kernel: [    0.438991] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Nov 14 05:56:40 node-1 kernel: [    0.449624] ACPI: Interpreter enabled
Nov 14 05:56:40 node-1 kernel: [    0.449629] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Nov 14 05:56:40 node-1 kernel: [    0.449633] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Nov 14 05:56:40 node-1 kernel: [    0.449636] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Nov 14 05:56:40 node-1 kernel: [    0.449643] ACPI: (supports S0 S4 S5)
Nov 14 05:56:40 node-1 kernel: [    0.449644] ACPI: Using IOAPIC for interrupt routing
Nov 14 05:56:40 node-1 kernel: [    0.449689] HEST: Table parsing has been initialized.
Nov 14 05:56:40 node-1 kernel: [    0.449691] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov 14 05:56:40 node-1 kernel: [    0.450252] ACPI: No dock devices found.
Nov 14 05:56:40 node-1 kernel: [    0.462026] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Nov 14 05:56:40 node-1 kernel: [    0.462031] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 14 05:56:40 node-1 kernel: [    0.462034] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov 14 05:56:40 node-1 kernel: [    0.462061] PCI host bridge to bus 0000:ff
Nov 14 05:56:40 node-1 kernel: [    0.462063] pci_bus 0000:ff: root bus resource [bus ff]
Nov 14 05:56:40 node-1 kernel: [    0.462071] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462109] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Nov 14 05:56:40 node-1 kernel: [    0.462139] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462173] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462203] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Nov 14 05:56:40 node-1 kernel: [    0.462233] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Nov 14 05:56:40 node-1 kernel: [    0.462264] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462293] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462324] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462352] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462379] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462405] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462433] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462459] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462486] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462512] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462541] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462568] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462595] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Nov 14 05:56:40 node-1 kernel: [    0.462623] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462649] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Nov 14 05:56:40 node-1 kernel: [    0.462675] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462701] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462731] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Nov 14 05:56:40 node-1 kernel: [    0.462766] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462797] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462827] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462858] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462889] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462919] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462950] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.462983] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463014] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463048] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463081] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463113] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463147] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463177] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463205] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463236] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463270] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463310] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463345] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463379] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Nov 14 05:56:40 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Nov 14 05:56:40 node-1 kernel: [    0.463410] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463438] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463468] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463500] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463532] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463564] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463596] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463626] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463654] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463683] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463713] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463744] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463780] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463839] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Nov 14 05:56:40 node-1 kernel: [    0.463842] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 14 05:56:40 node-1 kernel: [    0.463845] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov 14 05:56:40 node-1 kernel: [    0.463863] PCI host bridge to bus 0000:7f
Nov 14 05:56:40 node-1 kernel: [    0.463865] pci_bus 0000:7f: root bus resource [bus 7f]
Nov 14 05:56:40 node-1 kernel: [    0.463870] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463898] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Nov 14 05:56:40 node-1 kernel: [    0.463927] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463957] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.463979] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Nov 14 05:56:40 node-1 kernel: [    0.464004] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Nov 14 05:56:40 node-1 kernel: [    0.464031] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464057] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464082] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464105] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464128] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464150] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464176] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464201] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464227] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464254] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464276] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464299] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464322] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Nov 14 05:56:40 node-1 kernel: [    0.464345] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464367] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Nov 14 05:56:40 node-1 kernel: [    0.464389] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464412] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464438] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Nov 14 05:56:40 node-1 kernel: [    0.464472] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464499] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464525] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464553] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464578] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464606] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464633] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464661] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464688] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464716] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464745] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464773] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464802] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464829] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464854] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464883] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464908] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464938] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464969] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.464997] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.465024] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.465051] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.465077] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.465104] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.465131] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.465158] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.465188] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.465212] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.465234] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.465259] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.465284] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.465311] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.465338] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.466594] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Nov 14 05:56:40 node-1 kernel: [    0.466598] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 14 05:56:40 node-1 kernel: [    0.467718] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov 14 05:56:40 node-1 kernel: [    0.468233] PCI host bridge to bus 0000:00
Nov 14 05:56:40 node-1 kernel: [    0.468235] pci_bus 0000:00: root bus resource [bus 00-7e]
Nov 14 05:56:40 node-1 kernel: [    0.468237] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Nov 14 05:56:40 node-1 kernel: [    0.468238] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Nov 14 05:56:40 node-1 kernel: [    0.468239] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Nov 14 05:56:40 node-1 kernel: [    0.468241] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Nov 14 05:56:40 node-1 kernel: [    0.468242] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Nov 14 05:56:40 node-1 kernel: [    0.468244] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Nov 14 05:56:40 node-1 kernel: [    0.468249] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Nov 14 05:56:40 node-1 kernel: [    0.468331] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Nov 14 05:56:40 node-1 kernel: [    0.468362] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Nov 14 05:56:40 node-1 kernel: [    0.468403] pci 0000:00:01.0: System wakeup disabled by ACPI
Nov 14 05:56:40 node-1 kernel: [    0.468422] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Nov 14 05:56:40 node-1 kernel: [    0.468451] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Nov 14 05:56:40 node-1 kernel: [    0.468492] pci 0000:00:02.0: System wakeup disabled by ACPI
Nov 14 05:56:40 node-1 kernel: [    0.468510] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Nov 14 05:56:40 node-1 kernel: [    0.468540] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Nov 14 05:56:40 node-1 kernel: [    0.468580] pci 0000:00:03.0: System wakeup disabled by ACPI
Nov 14 05:56:40 node-1 kernel: [    0.468596] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.468667] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.468744] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.468819] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Nov 14 05:56:40 node-1 kernel: [    0.468824] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Nov 14 05:56:40 node-1 kernel: [    0.468909] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Nov 14 05:56:40 node-1 kernel: [    0.469057] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Nov 14 05:56:40 node-1 kernel: [    0.469075] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Nov 14 05:56:40 node-1 kernel: [    0.469152] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Nov 14 05:56:40 node-1 kernel: [    0.469205] pci 0000:00:1a.0: System wakeup disabled by ACPI
Nov 14 05:56:40 node-1 kernel: [    0.469227] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Nov 14 05:56:40 node-1 kernel: [    0.469282] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Nov 14 05:56:40 node-1 kernel: [    0.469326] pci 0000:00:1c.0: System wakeup disabled by ACPI
Nov 14 05:56:40 node-1 kernel: [    0.469352] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Nov 14 05:56:40 node-1 kernel: [    0.469408] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Nov 14 05:56:40 node-1 kernel: [    0.469451] pci 0000:00:1c.7: System wakeup disabled by ACPI
Nov 14 05:56:40 node-1 kernel: [    0.469475] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Nov 14 05:56:40 node-1 kernel: [    0.469493] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Nov 14 05:56:40 node-1 kernel: [    0.469570] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Nov 14 05:56:40 node-1 kernel: [    0.469620] pci 0000:00:1d.0: System wakeup disabled by ACPI
Nov 14 05:56:40 node-1 kernel: [    0.469646] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Nov 14 05:56:40 node-1 kernel: [    0.469895] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Nov 14 05:56:40 node-1 kernel: [    0.469901] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Nov 14 05:56:40 node-1 kernel: [    0.469907] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Nov 14 05:56:40 node-1 kernel: [    0.469913] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Nov 14 05:56:40 node-1 kernel: [    0.469920] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Nov 14 05:56:40 node-1 kernel: [    0.469950] pci 0000:01:00.0: supports D1 D2
Nov 14 05:56:40 node-1 kernel: [    0.479781] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 14 05:56:40 node-1 kernel: [    0.479787] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov 14 05:56:40 node-1 kernel: [    0.479792] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov 14 05:56:40 node-1 kernel: [    0.480052] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Nov 14 05:56:40 node-1 kernel: [    0.480112] pci 0000:02:00.0: PME# supported from D0 D3hot
Nov 14 05:56:40 node-1 kernel: [    0.491775] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov 14 05:56:40 node-1 kernel: [    0.491782] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov 14 05:56:40 node-1 kernel: [    0.491786] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 14 05:56:40 node-1 kernel: [    0.491870] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Nov 14 05:56:40 node-1 kernel: [    0.491951] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Nov 14 05:56:40 node-1 kernel: [    0.492032] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Nov 14 05:56:40 node-1 kernel: [    0.492076] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov 14 05:56:40 node-1 kernel: [    0.492080] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov 14 05:56:40 node-1 kernel: [    0.492082] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 14 05:56:40 node-1 kernel: [    0.492134] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Nov 14 05:56:40 node-1 kernel: [    0.492276] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Nov 14 05:56:40 node-1 kernel: [    0.492329] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov 14 05:56:40 node-1 kernel: [    0.492332] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov 14 05:56:40 node-1 kernel: [    0.492334] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 14 05:56:40 node-1 kernel: [    0.492383] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Nov 14 05:56:40 node-1 kernel: [    0.492505] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Nov 14 05:56:40 node-1 kernel: [    0.492545] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Nov 14 05:56:40 node-1 kernel: [    0.492664] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Nov 14 05:56:40 node-1 kernel: [    0.492700] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Nov 14 05:56:40 node-1 kernel: [    0.492820] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Nov 14 05:56:40 node-1 kernel: [    0.492855] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Nov 14 05:56:40 node-1 kernel: [    0.492976] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Nov 14 05:56:40 node-1 kernel: [    0.493017] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov 14 05:56:40 node-1 kernel: [    0.493019] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov 14 05:56:40 node-1 kernel: [    0.493021] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 14 05:56:40 node-1 kernel: [    0.493081] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Nov 14 05:56:40 node-1 kernel: [    0.493143] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Nov 14 05:56:40 node-1 kernel: [    0.493220] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Nov 14 05:56:40 node-1 kernel: [    0.493262] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Nov 14 05:56:40 node-1 kernel: [    0.493341] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Nov 14 05:56:40 node-1 kernel: [    0.493448] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov 14 05:56:40 node-1 kernel: [    0.493451] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov 14 05:56:40 node-1 kernel: [    0.493453] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov 14 05:56:40 node-1 kernel: [    0.493509] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Nov 14 05:56:40 node-1 kernel: [    0.493563] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Nov 14 05:56:40 node-1 kernel: [    0.493611] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Nov 14 05:56:40 node-1 kernel: [    0.493823] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov 14 05:56:40 node-1 kernel: [    0.493827] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov 14 05:56:40 node-1 kernel: [    0.493888] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Nov 14 05:56:40 node-1 kernel: [    0.493941] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Nov 14 05:56:40 node-1 kernel: [    0.493992] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Nov 14 05:56:40 node-1 kernel: [    0.494211] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov 14 05:56:40 node-1 kernel: [    0.494215] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov 14 05:56:40 node-1 kernel: [    0.494274] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Nov 14 05:56:40 node-1 kernel: [    0.494337] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Nov 14 05:56:40 node-1 kernel: [    0.494390] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Nov 14 05:56:40 node-1 kernel: [    0.494613] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov 14 05:56:40 node-1 kernel: [    0.494617] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov 14 05:56:40 node-1 kernel: [    0.494791] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov 14 05:56:40 node-1 kernel: [    0.494829] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov 14 05:56:40 node-1 kernel: [    0.494906] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Nov 14 05:56:40 node-1 kernel: [    0.494925] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Nov 14 05:56:40 node-1 kernel: [    0.494938] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Nov 14 05:56:40 node-1 kernel: [    0.494951] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Nov 14 05:56:40 node-1 kernel: [    0.495001] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Nov 14 05:56:40 node-1 kernel: [    0.499790] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov 14 05:56:40 node-1 kernel: [    0.499795] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov 14 05:56:40 node-1 kernel: [    0.499827] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Nov 14 05:56:40 node-1 kernel: [    0.500315] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Nov 14 05:56:40 node-1 kernel: [    0.500318] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 14 05:56:40 node-1 kernel: [    0.500439] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov 14 05:56:40 node-1 kernel: [    0.500548] PCI host bridge to bus 0000:80
Nov 14 05:56:40 node-1 kernel: [    0.500550] pci_bus 0000:80: root bus resource [bus 80-fe]
Nov 14 05:56:40 node-1 kernel: [    0.500552] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Nov 14 05:56:40 node-1 kernel: [    0.500553] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Nov 14 05:56:40 node-1 kernel: [    0.500561] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.500624] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.500691] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Nov 14 05:56:40 node-1 kernel: [    0.500752] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Nov 14 05:56:40 node-1 kernel: [    0.500758] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Nov 14 05:56:40 node-1 kernel: [    0.500831] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Nov 14 05:56:40 node-1 kernel: [    0.501129] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov 14 05:56:40 node-1 kernel: [    0.501160] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov 14 05:56:40 node-1 kernel: [    0.501190] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Nov 14 05:56:40 node-1 kernel: [    0.501219] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Nov 14 05:56:40 node-1 kernel: [    0.501249] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 14 05:56:40 node-1 kernel: [    0.501278] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 14 05:56:40 node-1 kernel: [    0.501308] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 14 05:56:40 node-1 kernel: [    0.501338] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 14 05:56:40 node-1 kernel: [    0.501423] ACPI: Enabled 3 GPEs in block 00 to 3F
Nov 14 05:56:40 node-1 kernel: [    0.501427] ACPI: \_SB_.UNC1: notify handler is installed
Nov 14 05:56:40 node-1 kernel: [    0.501428] ACPI: \_SB_.UNC0: notify handler is installed
Nov 14 05:56:40 node-1 kernel: [    0.501443] ACPI: \_SB_.PCI0: notify handler is installed
Nov 14 05:56:40 node-1 kernel: [    0.501496] ACPI: \_SB_.PCI1: notify handler is installed
Nov 14 05:56:40 node-1 kernel: [    0.501576] Found 4 acpi root devices
Nov 14 05:56:40 node-1 kernel: [    0.501682] vgaarb: setting as boot device: PCI:0000:0c:00.0
Nov 14 05:56:40 node-1 kernel: [    0.501685] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Nov 14 05:56:40 node-1 kernel: [    0.501686] vgaarb: loaded
Nov 14 05:56:40 node-1 kernel: [    0.501687] vgaarb: bridge control possible 0000:0c:00.0
Nov 14 05:56:40 node-1 kernel: [    0.501802] SCSI subsystem initialized
Nov 14 05:56:40 node-1 kernel: [    0.501865] libata version 3.00 loaded.
Nov 14 05:56:40 node-1 kernel: [    0.501880] ACPI: bus type USB registered
Nov 14 05:56:40 node-1 kernel: [    0.501890] usbcore: registered new interface driver usbfs
Nov 14 05:56:40 node-1 kernel: [    0.501895] usbcore: registered new interface driver hub
Nov 14 05:56:40 node-1 kernel: [    0.501919] usbcore: registered new device driver usb
Nov 14 05:56:40 node-1 kernel: [    0.502089] PCI: Using ACPI for IRQ routing
Nov 14 05:56:40 node-1 kernel: [    0.505708] PCI: pci_cache_line_size set to 64 bytes
Nov 14 05:56:40 node-1 kernel: [    0.505911] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Nov 14 05:56:40 node-1 kernel: [    0.505912] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Nov 14 05:56:40 node-1 kernel: [    0.505913] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Nov 14 05:56:40 node-1 kernel: [    0.505978] NetLabel: Initializing
Nov 14 05:56:40 node-1 kernel: [    0.505980] NetLabel:  domain hash size = 128
Nov 14 05:56:40 node-1 kernel: [    0.505980] NetLabel:  protocols = UNLABELED CIPSOv4
Nov 14 05:56:40 node-1 kernel: [    0.505990] NetLabel:  unlabeled traffic allowed by default
Nov 14 05:56:40 node-1 kernel: [    0.506059] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Nov 14 05:56:40 node-1 kernel: [    0.506063] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Nov 14 05:56:40 node-1 kernel: [    0.508132] Switched to clocksource hpet
Nov 14 05:56:40 node-1 kernel: [    0.512521] AppArmor: AppArmor Filesystem Enabled
Nov 14 05:56:40 node-1 kernel: [    0.512559] pnp: PnP ACPI init
Nov 14 05:56:40 node-1 kernel: [    0.512571] ACPI: bus type PNP registered
Nov 14 05:56:40 node-1 kernel: [    0.512748] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Nov 14 05:56:40 node-1 kernel: [    0.512760] pnp 00:01: [dma 4]
Nov 14 05:56:40 node-1 kernel: [    0.512778] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Nov 14 05:56:40 node-1 kernel: [    0.512813] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov 14 05:56:40 node-1 kernel: [    0.512837] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Nov 14 05:56:40 node-1 kernel: [    0.512859] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Nov 14 05:56:40 node-1 kernel: [    0.512907] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Nov 14 05:56:40 node-1 kernel: [    0.513022] system 00:06: [io  0x0500-0x057f] has been reserved
Nov 14 05:56:40 node-1 kernel: [    0.513025] system 00:06: [io  0x0400-0x047f] could not be reserved
Nov 14 05:56:40 node-1 kernel: [    0.513027] system 00:06: [io  0x0580-0x059f] has been reserved
Nov 14 05:56:40 node-1 kernel: [    0.513028] system 00:06: [io  0x0600-0x061f] has been reserved
Nov 14 05:56:40 node-1 kernel: [    0.513030] system 00:06: [io  0x0880-0x0883] has been reserved
Nov 14 05:56:40 node-1 kernel: [    0.513031] system 00:06: [io  0x0800-0x081f] has been reserved
Nov 14 05:56:40 node-1 kernel: [    0.513035] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Nov 14 05:56:40 node-1 kernel: [    0.513037] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Nov 14 05:56:40 node-1 kernel: [    0.513038] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Nov 14 05:56:40 node-1 kernel: [    0.513040] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Nov 14 05:56:40 node-1 kernel: [    0.513041] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Nov 14 05:56:40 node-1 kernel: [    0.513043] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Nov 14 05:56:40 node-1 kernel: [    0.513044] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Nov 14 05:56:40 node-1 kernel: [    0.513047] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 14 05:56:40 node-1 kernel: [    0.513148] pnp 00:07: [dma 0 disabled]
Nov 14 05:56:40 node-1 kernel: [    0.513181] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 14 05:56:40 node-1 kernel: [    0.513263] pnp 00:08: [dma 0 disabled]
Nov 14 05:56:40 node-1 kernel: [    0.513299] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 14 05:56:40 node-1 kernel: [    0.513357] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Nov 14 05:56:40 node-1 kernel: [    0.513800] pnp: PnP ACPI: found 10 devices
Nov 14 05:56:40 node-1 kernel: [    0.513802] ACPI: bus type PNP unregistered
Nov 14 05:56:40 node-1 kernel: [    0.519800] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 14 05:56:40 node-1 kernel: [    0.519805] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov 14 05:56:40 node-1 kernel: [    0.519808] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov 14 05:56:40 node-1 kernel: [    0.519813] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov 14 05:56:40 node-1 kernel: [    0.519815] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov 14 05:56:40 node-1 kernel: [    0.519830] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov 14 05:56:40 node-1 kernel: [    0.519859] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov 14 05:56:40 node-1 kernel: [    0.519874] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov 14 05:56:40 node-1 kernel: [    0.519903] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov 14 05:56:40 node-1 kernel: [    0.519918] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov 14 05:56:40 node-1 kernel: [    0.519947] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov 14 05:56:40 node-1 kernel: [    0.519961] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov 14 05:56:40 node-1 kernel: [    0.519990] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov 14 05:56:40 node-1 kernel: [    0.519992] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov 14 05:56:40 node-1 kernel: [    0.520007] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 14 05:56:40 node-1 kernel: [    0.520040] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov 14 05:56:40 node-1 kernel: [    0.520042] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov 14 05:56:40 node-1 kernel: [    0.520057] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 14 05:56:40 node-1 kernel: [    0.520086] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov 14 05:56:40 node-1 kernel: [    0.520088] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov 14 05:56:40 node-1 kernel: [    0.520091] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 14 05:56:40 node-1 kernel: [    0.520095] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov 14 05:56:40 node-1 kernel: [    0.520097] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov 14 05:56:40 node-1 kernel: [    0.520100] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 14 05:56:40 node-1 kernel: [    0.520109] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov 14 05:56:40 node-1 kernel: [    0.520115] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov 14 05:56:40 node-1 kernel: [    0.520123] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov 14 05:56:40 node-1 kernel: [    0.520127] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov 14 05:56:40 node-1 kernel: [    0.520134] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Nov 14 05:56:40 node-1 kernel: [    0.520135] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Nov 14 05:56:40 node-1 kernel: [    0.520136] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Nov 14 05:56:40 node-1 kernel: [    0.520137] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Nov 14 05:56:40 node-1 kernel: [    0.520138] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Nov 14 05:56:40 node-1 kernel: [    0.520139] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Nov 14 05:56:40 node-1 kernel: [    0.520140] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Nov 14 05:56:40 node-1 kernel: [    0.520141] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Nov 14 05:56:40 node-1 kernel: [    0.520142] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Nov 14 05:56:40 node-1 kernel: [    0.520143] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov 14 05:56:40 node-1 kernel: [    0.520144] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Nov 14 05:56:40 node-1 kernel: [    0.520145] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov 14 05:56:40 node-1 kernel: [    0.520146] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Nov 14 05:56:40 node-1 kernel: [    0.520147] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov 14 05:56:40 node-1 kernel: [    0.520148] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Nov 14 05:56:40 node-1 kernel: [    0.520149] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov 14 05:56:40 node-1 kernel: [    0.520150] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Nov 14 05:56:40 node-1 kernel: [    0.520151] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Nov 14 05:56:40 node-1 kernel: [    0.520153] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Nov 14 05:56:40 node-1 kernel: [    0.520154] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Nov 14 05:56:40 node-1 kernel: [    0.520155] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Nov 14 05:56:40 node-1 kernel: [    0.520156] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Nov 14 05:56:40 node-1 kernel: [    0.520159] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Nov 14 05:56:40 node-1 kernel: [    0.520160] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Nov 14 05:56:40 node-1 kernel: [    0.520200] NET: Registered protocol family 2
Nov 14 05:56:40 node-1 kernel: [    0.520497] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Nov 14 05:56:40 node-1 kernel: [    0.520879] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Nov 14 05:56:40 node-1 kernel: [    0.521048] TCP: Hash tables configured (established 262144 bind 65536)
Nov 14 05:56:40 node-1 kernel: [    0.521093] TCP: reno registered
Nov 14 05:56:40 node-1 kernel: [    0.521124] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Nov 14 05:56:40 node-1 kernel: [    0.521233] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Nov 14 05:56:40 node-1 kernel: [    0.521390] NET: Registered protocol family 1
Nov 14 05:56:40 node-1 kernel: [    0.556221] pci 0000:0c:00.0: Video device with shadowed ROM
Nov 14 05:56:40 node-1 kernel: [    0.556235] PCI: CLS 64 bytes, default 64
Nov 14 05:56:40 node-1 kernel: [    0.556320] Trying to unpack rootfs image as initramfs...
Nov 14 05:56:40 node-1 kernel: [    0.779437] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Nov 14 05:56:40 node-1 kernel: [    0.779476] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Nov 14 05:56:40 node-1 kernel: [    0.779479] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Nov 14 05:56:40 node-1 kernel: [    0.779907] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Nov 14 05:56:40 node-1 kernel: [    0.779916] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Nov 14 05:56:40 node-1 kernel: [    0.779924] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Nov 14 05:56:40 node-1 kernel: [    0.779932] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Nov 14 05:56:40 node-1 kernel: [    0.779942] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Nov 14 05:56:40 node-1 kernel: [    0.779949] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Nov 14 05:56:40 node-1 kernel: [    0.779954] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Nov 14 05:56:40 node-1 kernel: [    0.779960] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Nov 14 05:56:40 node-1 kernel: [    0.779967] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Nov 14 05:56:40 node-1 kernel: [    0.779974] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Nov 14 05:56:40 node-1 kernel: [    0.779984] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Nov 14 05:56:40 node-1 kernel: [    0.779991] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Nov 14 05:56:40 node-1 kernel: [    0.779998] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Nov 14 05:56:40 node-1 kernel: [    0.780004] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Nov 14 05:56:40 node-1 kernel: [    0.780010] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Nov 14 05:56:40 node-1 kernel: [    0.780016] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Nov 14 05:56:40 node-1 kernel: [    0.780064] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Nov 14 05:56:40 node-1 kernel: [    0.780067] Scanning for low memory corruption every 60 seconds
Nov 14 05:56:40 node-1 kernel: [    0.780367] Initialise system trusted keyring
Nov 14 05:56:40 node-1 kernel: [    0.780419] audit: initializing netlink socket (disabled)
Nov 14 05:56:40 node-1 kernel: [    0.780430] type=2000 audit(1479102963.732:1): initialized
Nov 14 05:56:40 node-1 kernel: [    0.798200] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov 14 05:56:40 node-1 kernel: [    0.799651] zbud: loaded
Nov 14 05:56:40 node-1 kernel: [    0.799768] VFS: Disk quotas dquot_6.5.2
Nov 14 05:56:40 node-1 kernel: [    0.799806] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Nov 14 05:56:40 node-1 kernel: [    0.800186] fuse init (API version 7.22)
Nov 14 05:56:40 node-1 kernel: [    0.800237] msgmni has been set to 32768
Nov 14 05:56:40 node-1 kernel: [    0.800280] Key type big_key registered
Nov 14 05:56:40 node-1 kernel: [    0.800755] Key type asymmetric registered
Nov 14 05:56:40 node-1 kernel: [    0.800757] Asymmetric key parser 'x509' registered
Nov 14 05:56:40 node-1 kernel: [    0.800779] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov 14 05:56:40 node-1 kernel: [    0.800850] io scheduler noop registered
Nov 14 05:56:40 node-1 kernel: [    0.800852] io scheduler deadline registered (default)
Nov 14 05:56:40 node-1 kernel: [    0.800869] io scheduler cfq registered
Nov 14 05:56:40 node-1 kernel: [    0.801277] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    0.801412] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    0.801531] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    0.801647] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    0.801765] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    0.801869] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    0.802256] aer 0000:00:01.0:pcie02: service driver aer loaded
Nov 14 05:56:40 node-1 kernel: [    0.802282] aer 0000:00:02.0:pcie02: service driver aer loaded
Nov 14 05:56:40 node-1 kernel: [    0.802299] aer 0000:00:03.0:pcie02: service driver aer loaded
Nov 14 05:56:40 node-1 kernel: [    0.802311] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802314] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802316] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Nov 14 05:56:40 node-1 kernel: [    0.802322] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802323] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802325] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802327] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802329] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802330] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802332] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802334] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802335] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802336] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802338] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802340] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802342] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Nov 14 05:56:40 node-1 kernel: [    0.802354] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802357] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Nov 14 05:56:40 node-1 kernel: [    0.802368] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802372] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Nov 14 05:56:40 node-1 kernel: [    0.802383] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802385] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Nov 14 05:56:40 node-1 kernel: [    0.802388] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Nov 14 05:56:40 node-1 kernel: [    0.802418] ioapic: probe of 0000:00:05.4 failed with error -22
Nov 14 05:56:40 node-1 kernel: [    0.802423] ioapic: probe of 0000:80:05.4 failed with error -22
Nov 14 05:56:40 node-1 kernel: [    0.802427] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov 14 05:56:40 node-1 kernel: [    0.802436] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov 14 05:56:40 node-1 kernel: [    0.802472] vesafb: mode is 640x480x32, linelength=2560, pages=0
Nov 14 05:56:40 node-1 kernel: [    0.802473] vesafb: scrolling: redraw
Nov 14 05:56:40 node-1 kernel: [    0.802475] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Nov 14 05:56:40 node-1 kernel: [    0.823231] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Nov 14 05:56:40 node-1 kernel: [    0.831737] Console: switching to colour frame buffer device 80x30
Nov 14 05:56:40 node-1 kernel: [    0.840416] fb0: VESA VGA frame buffer device
Nov 14 05:56:40 node-1 kernel: [    0.840610] intel_idle: MWAIT substates: 0x2120
Nov 14 05:56:40 node-1 kernel: [    0.840611] intel_idle: v0.4 model 0x3F
Nov 14 05:56:40 node-1 kernel: [    0.840611] intel_idle: lapic_timer_reliable_states 0xffffffff
Nov 14 05:56:40 node-1 kernel: [    0.840845] ipmi message handler version 39.2
Nov 14 05:56:40 node-1 kernel: [    0.841116] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Nov 14 05:56:40 node-1 kernel: [    0.841546] ACPI: AC Adapter [P111] (on-line)
Nov 14 05:56:40 node-1 kernel: [    0.846802] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Nov 14 05:56:40 node-1 kernel: [    0.857824] ACPI: Power Button [PWRB]
Nov 14 05:56:40 node-1 kernel: [    0.863586] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Nov 14 05:56:40 node-1 kernel: [    0.875203] ACPI: Power Button [PWRF]
Nov 14 05:56:40 node-1 kernel: [    0.901679] ERST: Error Record Serialization Table (ERST) support is initialized.
Nov 14 05:56:40 node-1 kernel: [    0.913373] pstore: Registered erst as persistent store backend
Nov 14 05:56:40 node-1 kernel: [    0.919581] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Nov 14 05:56:40 node-1 kernel: [    0.931525] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Nov 14 05:56:40 node-1 kernel: [    0.958272] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Nov 14 05:56:40 node-1 kernel: [    0.991573] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Nov 14 05:56:40 node-1 kernel: [    1.005618] Linux agpgart interface v0.103
Nov 14 05:56:40 node-1 kernel: [    1.013261] brd: module loaded
Nov 14 05:56:40 node-1 kernel: [    1.020311] loop: module loaded
Nov 14 05:56:40 node-1 kernel: [    1.027024] libphy: Fixed MDIO Bus: probed
Nov 14 05:56:40 node-1 kernel: [    1.033518] tun: Universal TUN/TAP device driver, 1.6
Nov 14 05:56:40 node-1 kernel: [    1.039989] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov 14 05:56:40 node-1 kernel: [    1.046517] PPP generic driver version 2.4.2
Nov 14 05:56:40 node-1 kernel: [    1.052890] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov 14 05:56:40 node-1 kernel: [    1.059322] ehci-pci: EHCI PCI platform driver
Nov 14 05:56:40 node-1 kernel: [    1.065842] ehci-pci 0000:00:1a.0: EHCI Host Controller
Nov 14 05:56:40 node-1 kernel: [    1.072243] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Nov 14 05:56:40 node-1 kernel: [    1.084793] ehci-pci 0000:00:1a.0: debug port 2
Nov 14 05:56:40 node-1 kernel: [    1.095024] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Nov 14 05:56:40 node-1 kernel: [    1.095043] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Nov 14 05:56:40 node-1 kernel: [    1.111610] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Nov 14 05:56:40 node-1 kernel: [    1.117674] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov 14 05:56:40 node-1 kernel: [    1.123831] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 14 05:56:40 node-1 kernel: [    1.135715] usb usb1: Product: EHCI Host Controller
Nov 14 05:56:40 node-1 kernel: [    1.141721] usb usb1: Manufacturer: Linux 3.13.0-101-generic ehci_hcd
Nov 14 05:56:40 node-1 kernel: [    1.147756] usb usb1: SerialNumber: 0000:00:1a.0
Nov 14 05:56:40 node-1 kernel: [    1.153709] hub 1-0:1.0: USB hub found
Nov 14 05:56:40 node-1 kernel: [    1.159467] hub 1-0:1.0: 2 ports detected
Nov 14 05:56:40 node-1 kernel: [    1.165285] ehci-pci 0000:00:1d.0: EHCI Host Controller
Nov 14 05:56:40 node-1 kernel: [    1.170921] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Nov 14 05:56:40 node-1 kernel: [    1.181884] ehci-pci 0000:00:1d.0: debug port 2
Nov 14 05:56:40 node-1 kernel: [    1.191164] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Nov 14 05:56:40 node-1 kernel: [    1.191167] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Nov 14 05:56:40 node-1 kernel: [    1.207529] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Nov 14 05:56:40 node-1 kernel: [    1.212736] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Nov 14 05:56:40 node-1 kernel: [    1.218030] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 14 05:56:40 node-1 kernel: [    1.228592] usb usb2: Product: EHCI Host Controller
Nov 14 05:56:40 node-1 kernel: [    1.234056] usb usb2: Manufacturer: Linux 3.13.0-101-generic ehci_hcd
Nov 14 05:56:40 node-1 kernel: [    1.239608] usb usb2: SerialNumber: 0000:00:1d.0
Nov 14 05:56:40 node-1 kernel: [    1.245162] hub 2-0:1.0: USB hub found
Nov 14 05:56:40 node-1 kernel: [    1.250523] hub 2-0:1.0: 2 ports detected
Nov 14 05:56:40 node-1 kernel: [    1.255825] ehci-platform: EHCI generic platform driver
Nov 14 05:56:40 node-1 kernel: [    1.261061] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Nov 14 05:56:40 node-1 kernel: [    1.266388] ohci-pci: OHCI PCI platform driver
Nov 14 05:56:40 node-1 kernel: [    1.271688] ohci-platform: OHCI generic platform driver
Nov 14 05:56:40 node-1 kernel: [    1.276888] uhci_hcd: USB Universal Host Controller Interface driver
Nov 14 05:56:40 node-1 kernel: [    1.282225] i8042: PNP: No PS/2 controller found. Probing ports directly.
Nov 14 05:56:40 node-1 kernel: [    1.479296] usb 1-1: new high-speed USB device number 2 using ehci-pci
Nov 14 05:56:40 node-1 kernel: [    1.639563] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Nov 14 05:56:40 node-1 kernel: [    1.645107] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 14 05:56:40 node-1 kernel: [    1.650831] hub 1-1:1.0: USB hub found
Nov 14 05:56:40 node-1 kernel: [    1.656299] hub 1-1:1.0: 6 ports detected
Nov 14 05:56:40 node-1 kernel: [    1.771049] usb 2-1: new high-speed USB device number 2 using ehci-pci
Nov 14 05:56:40 node-1 kernel: [    2.039224] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Nov 14 05:56:40 node-1 kernel: [    2.044647] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 14 05:56:40 node-1 kernel: [    2.050365] hub 2-1:1.0: USB hub found
Nov 14 05:56:40 node-1 kernel: [    2.055960] hub 2-1:1.0: 8 ports detected
Nov 14 05:56:40 node-1 kernel: [    2.323023] i8042: No controller found
Nov 14 05:56:40 node-1 kernel: [    2.328374] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Nov 14 05:56:40 node-1 kernel: [    2.329697] mousedev: PS/2 mouse device common for all mice
Nov 14 05:56:40 node-1 kernel: [    2.331574] rtc_cmos 00:02: RTC can wake from S4
Nov 14 05:56:40 node-1 kernel: [    2.333088] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Nov 14 05:56:40 node-1 kernel: [    2.333650] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov 14 05:56:40 node-1 kernel: [    2.334439] device-mapper: uevent: version 1.0.3
Nov 14 05:56:40 node-1 kernel: [    2.334656] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Nov 14 05:56:40 node-1 kernel: [    2.335652] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Nov 14 05:56:40 node-1 kernel: [    2.335800] ledtrig-cpu: registered to indicate activity on CPUs
Nov 14 05:56:40 node-1 kernel: [    2.337551] TCP: cubic registered
Nov 14 05:56:40 node-1 kernel: [    2.338837] NET: Registered protocol family 10
Nov 14 05:56:40 node-1 kernel: [    2.341476] NET: Registered protocol family 17
Nov 14 05:56:40 node-1 kernel: [    2.341613] Key type dns_resolver registered
Nov 14 05:56:40 node-1 kernel: [    2.348309] Loading compiled-in X.509 certificates
Nov 14 05:56:40 node-1 kernel: [    2.350143] Loaded X.509 cert 'Magrathea: Glacier signing key: a646945ba0946c9505627a9179bb3ba9458a96b7'
Nov 14 05:56:40 node-1 kernel: [    2.350556] registered taskstats version 1
Nov 14 05:56:40 node-1 kernel: [    2.390141] Key type trusted registered
Nov 14 05:56:40 node-1 kernel: [    2.411008] Key type encrypted registered
Nov 14 05:56:40 node-1 kernel: [    2.411064] AppArmor: AppArmor sha1 policy hashing enabled
Nov 14 05:56:40 node-1 kernel: [    2.411079] IMA: No TPM chip found, activating TPM-bypass!
Nov 14 05:56:40 node-1 kernel: [    2.419440] regulator-dummy: disabling
Nov 14 05:56:40 node-1 kernel: [    2.420172]   Magic number: 8:501:921
Nov 14 05:56:40 node-1 kernel: [    2.420479] clockevents clockevent14: hash matches
Nov 14 05:56:40 node-1 kernel: [    2.421362] acpi device:ef: hash matches
Nov 14 05:56:40 node-1 kernel: [    2.477663] rtc_cmos 00:02: setting system clock to 2016-11-14 05:56:05 UTC (1479102965)
Nov 14 05:56:40 node-1 kernel: [    2.490256] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Nov 14 05:56:40 node-1 kernel: [    2.495942] EDD information not available.
Nov 14 05:56:40 node-1 kernel: [    2.501582] PM: Hibernation image not present or could not be loaded.
Nov 14 05:56:40 node-1 kernel: [    2.502454] Freeing unused kernel memory: 1340K (ffffffff81d20000 - ffffffff81e6f000)
Nov 14 05:56:40 node-1 kernel: [    2.513901] Write protecting the kernel read-only data: 12288k
Nov 14 05:56:40 node-1 kernel: [    2.520273] Freeing unused kernel memory: 752K (ffff880001744000 - ffff880001800000)
Nov 14 05:56:40 node-1 kernel: [    2.533076] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Nov 14 05:56:40 node-1 kernel: [    2.535256] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Nov 14 05:56:40 node-1 kernel: [    2.535257] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 14 05:56:40 node-1 kernel: [    2.535257] usb 2-1.4: Product: Cisco USB Composite Device-0
Nov 14 05:56:40 node-1 kernel: [    2.535258] usb 2-1.4: Manufacturer: Avocent
Nov 14 05:56:40 node-1 kernel: [    2.535259] usb 2-1.4: SerialNumber: 20111102-00000001
Nov 14 05:56:40 node-1 kernel: [    2.602454] device-mapper: multipath: version 1.6.0 loaded
Nov 14 05:56:40 node-1 kernel: [    2.610509] systemd-udevd[219]: starting version 204
Nov 14 05:56:40 node-1 kernel: [    2.635129] md: linear personality registered for level -1
Nov 14 05:56:40 node-1 kernel: [    2.649888] md: multipath personality registered for level -4
Nov 14 05:56:40 node-1 kernel: [    2.658103] md: raid0 personality registered for level 0
Nov 14 05:56:40 node-1 kernel: [    2.666621] md: raid1 personality registered for level 1
Nov 14 05:56:40 node-1 kernel: [    2.675187] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Nov 14 05:56:40 node-1 kernel: [    2.681657] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Nov 14 05:56:40 node-1 kernel: [    2.688203] hidraw: raw HID events driver (C) Jiri Kosina
Nov 14 05:56:40 node-1 kernel: [    2.691308] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Nov 14 05:56:40 node-1 kernel: [    2.692695] megasas: FW now in Ready state
Nov 14 05:56:40 node-1 kernel: [    2.693209] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.693368] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.693507] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.693626] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.693775] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.693939] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.694063] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.694227] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.694719] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.694889] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.694985] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.695038] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.695246] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.695364] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.695498] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.695590] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.696282] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Nov 14 05:56:40 node-1 kernel: [    2.699687] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Nov 14 05:56:40 node-1 kernel: [    2.699688] 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
Nov 14 05:56:40 node-1 kernel: [    2.699691] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov 14 05:56:40 node-1 kernel: [    2.700037] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.700202] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.700332] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.700495] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.700693] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.716235] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Nov 14 05:56:40 node-1 kernel: [    2.716237] 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
Nov 14 05:56:40 node-1 kernel: [    2.716237] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Nov 14 05:56:40 node-1 kernel: [    2.716450] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.716556] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.716685] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.716844] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.716990] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.717070] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.717397] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.735368] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Nov 14 05:56:40 node-1 kernel: [    2.735372] 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
Nov 14 05:56:40 node-1 kernel: [    2.735386] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov 14 05:56:40 node-1 kernel: [    2.735566] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.735628] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.735758] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.735943] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.736214] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.742296] raid6: sse2x1   10433 MB/s
Nov 14 05:56:40 node-1 kernel: [    2.752848] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Nov 14 05:56:40 node-1 kernel: [    2.752869] 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
Nov 14 05:56:40 node-1 kernel: [    2.752883] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov 14 05:56:40 node-1 kernel: [    2.753084] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.753244] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.753321] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.753443] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.753781] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov 14 05:56:40 node-1 kernel: [    2.810278] raid6: sse2x2   13586 MB/s
Nov 14 05:56:40 node-1 kernel: [    2.878203] raid6: sse2x4   16018 MB/s
Nov 14 05:56:40 node-1 kernel: [    2.935049] usbcore: registered new interface driver usbhid
Nov 14 05:56:40 node-1 kernel: [    2.941557] usbhid: USB HID core driver
Nov 14 05:56:40 node-1 kernel: [    2.946095] raid6: avx2x1   19634 MB/s
Nov 14 05:56:40 node-1 kernel: [    2.955237] 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
Nov 14 05:56:40 node-1 kernel: [    2.968282] 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
Nov 14 05:56:40 node-1 kernel: [    2.981441] 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
Nov 14 05:56:40 node-1 kernel: [    2.994544] 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
Nov 14 05:56:40 node-1 kernel: [    3.007983] 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
Nov 14 05:56:40 node-1 kernel: [    3.014198] raid6: avx2x2    3953 MB/s
Nov 14 05:56:40 node-1 kernel: [    3.028340] 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
Nov 14 05:56:40 node-1 kernel: [    3.038007] megasas:IOC Init cmd success
Nov 14 05:56:40 node-1 kernel: [    3.061961] megasas: INIT adapter done
Nov 14 05:56:40 node-1 kernel: [    3.081932] raid6: avx2x4   16828 MB/s
Nov 14 05:56:40 node-1 kernel: [    3.088480] raid6: using algorithm avx2x1 (19634 MB/s)
Nov 14 05:56:40 node-1 kernel: [    3.095106] raid6: using avx2x2 recovery algorithm
Nov 14 05:56:40 node-1 kernel: [    3.102461] xor: automatically using best checksumming function:
Nov 14 05:56:40 node-1 kernel: [    3.145876]    avx       : 35702.000 MB/sec
Nov 14 05:56:40 node-1 kernel: [    3.152979] async_tx: api initialized (async)
Nov 14 05:56:40 node-1 kernel: [    3.163486] md: raid6 personality registered for level 6
Nov 14 05:56:40 node-1 kernel: [    3.169682] md: raid5 personality registered for level 5
Nov 14 05:56:40 node-1 kernel: [    3.169914] megaraid_sas 0000:01:00.0: Controller type: iMR
Nov 14 05:56:40 node-1 kernel: [    3.170245] scsi0 : LSI SAS based MegaRAID driver
Nov 14 05:56:40 node-1 kernel: [    3.177483] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov 14 05:56:40 node-1 kernel: [    3.192806] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov 14 05:56:40 node-1 kernel: [    3.198305] sd 0:2:0:0: Attached scsi generic sg0 type 0
Nov 14 05:56:40 node-1 kernel: [    3.198566] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Nov 14 05:56:40 node-1 kernel: [    3.199041] sd 0:2:0:0: [sda] Write Protect is off
Nov 14 05:56:40 node-1 kernel: [    3.199042] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Nov 14 05:56:40 node-1 kernel: [    3.199132] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Nov 14 05:56:40 node-1 kernel: [    3.230879]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Nov 14 05:56:40 node-1 kernel: [    3.233384] sd 0:2:0:0: [sda] Attached SCSI disk
Nov 14 05:56:40 node-1 kernel: [    3.263022] md: raid4 personality registered for level 4
Nov 14 05:56:40 node-1 kernel: [    3.272360] md: raid10 personality registered for level 10
Nov 14 05:56:40 node-1 kernel: [    3.322729] multipathd (359): /proc/359/oom_adj is deprecated, please use /proc/359/oom_score_adj instead.
Nov 14 05:56:40 node-1 kernel: [    3.405923] random: lvm urandom read with 29 bits of entropy available
Nov 14 05:56:40 node-1 kernel: [    3.473735] Switched to clocksource tsc
Nov 14 05:56:40 node-1 kernel: [    3.522749] bio: create slab <bio-1> at 1
Nov 14 05:56:40 node-1 kernel: [    4.183268] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Nov 14 05:56:40 node-1 kernel: [    4.725409] init: plymouth-upstart-bridge main process (549) terminated with status 1
Nov 14 05:56:40 node-1 kernel: [    4.738071] init: plymouth-upstart-bridge main process ended, respawning
Nov 14 05:56:40 node-1 kernel: [    4.869658] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Nov 14 05:56:40 node-1 kernel: [    4.907427] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Nov 14 05:56:40 node-1 kernel: [    5.022623] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Nov 14 05:56:40 node-1 kernel: [    5.052538] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Nov 14 05:56:40 node-1 kernel: [    5.163852] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Nov 14 05:56:40 node-1 kernel: [    5.192422] random: nonblocking pool is initialized
Nov 14 05:56:40 node-1 kernel: [    5.352861] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Nov 14 05:56:40 node-1 kernel: [    5.392770] XFS (dm-0): Mounting Filesystem
Nov 14 05:56:40 node-1 kernel: [    5.665110] XFS (dm-0): Ending clean mount
Nov 14 05:56:40 node-1 kernel: [    5.744670] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Nov 14 05:56:40 node-1 kernel: [    5.775720] XFS (dm-1): Mounting Filesystem
Nov 14 05:56:40 node-1 kernel: [    5.870320] XFS (dm-1): Ending clean mount
Nov 14 05:56:40 node-1 kernel: [    7.949576] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov 14 05:56:40 node-1 kernel: [    7.963759] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov 14 05:56:40 node-1 kernel: [    8.142915] systemd-udevd[776]: starting version 204
Nov 14 05:56:40 node-1 kernel: [    8.363895] IPMI System Interface driver.
Nov 14 05:56:40 node-1 kernel: [    8.363935] ipmi_si: probing via ACPI
Nov 14 05:56:40 node-1 kernel: [    8.363946] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Nov 14 05:56:40 node-1 kernel: [    8.363947] ipmi_si: Adding ACPI-specified kcs state machine
Nov 14 05:56:40 node-1 kernel: [    8.363955] ipmi_si: probing via SMBIOS
Nov 14 05:56:40 node-1 kernel: [    8.363956] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Nov 14 05:56:40 node-1 kernel: [    8.363957] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Nov 14 05:56:40 node-1 kernel: [    8.363958] ipmi_si: probing via SPMI
Nov 14 05:56:40 node-1 kernel: [    8.363959] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Nov 14 05:56:40 node-1 kernel: [    8.363960] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Nov 14 05:56:40 node-1 kernel: [    8.363961] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Nov 14 05:56:40 node-1 kernel: [    8.382020] wmi: Mapper loaded
Nov 14 05:56:40 node-1 kernel: [    8.388895] power_meter ACPI000D:00: Found ACPI power meter.
Nov 14 05:56:40 node-1 kernel: [    8.388916] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Nov 14 05:56:40 node-1 kernel: [    8.398249] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Nov 14 05:56:40 node-1 kernel: [    8.398256] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 14 05:56:40 node-1 kernel: [    8.398259] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Nov 14 05:56:40 node-1 kernel: [    8.398262] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 14 05:56:40 node-1 kernel: [    8.398322] lpc_ich: Resource conflict(s) found affecting gpio_ich
Nov 14 05:56:40 node-1 kernel: [    8.409416] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Nov 14 05:56:40 node-1 kernel: [    8.474782] systemd-udevd[797]: renamed network interface eth1 to enp7s0
Nov 14 05:56:40 node-1 kernel: [    8.506584] systemd-udevd[796]: renamed network interface eth0 to enp6s0
Nov 14 05:56:40 node-1 kernel: [    8.514164] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Nov 14 05:56:40 node-1 kernel: [    8.514172] ipmi_si 00:09: IPMI kcs interface initialized
Nov 14 05:56:40 node-1 kernel: [    8.545701] systemd-udevd[799]: renamed network interface eth2 to enp8s0
Nov 14 05:56:40 node-1 kernel: [    8.571398] systemd-udevd[812]: renamed network interface eth3 to enp9s0
Nov 14 05:56:40 node-1 kernel: [    8.850817] type=1400 audit(1479102971.926:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1050 comm="apparmor_parser"
Nov 14 05:56:40 node-1 kernel: [    8.850977] type=1400 audit(1479102971.926:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1050 comm="apparmor_parser"
Nov 14 05:56:40 node-1 kernel: [    8.851103] type=1400 audit(1479102971.926:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1050 comm="apparmor_parser"
Nov 14 05:56:40 node-1 kernel: [    8.851441] type=1400 audit(1479102971.926:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1048 comm="apparmor_parser"
Nov 14 05:56:40 node-1 kernel: [    8.851585] type=1400 audit(1479102971.926:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1048 comm="apparmor_parser"
Nov 14 05:56:40 node-1 kernel: [    8.851714] type=1400 audit(1479102971.926:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1048 comm="apparmor_parser"
Nov 14 05:56:40 node-1 kernel: [    8.867376] type=1400 audit(1479102971.942:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1053 comm="apparmor_parser"
Nov 14 05:56:40 node-1 kernel: [    8.867519] type=1400 audit(1479102971.942:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1053 comm="apparmor_parser"
Nov 14 05:56:40 node-1 kernel: [    8.867641] type=1400 audit(1479102971.942:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1053 comm="apparmor_parser"
Nov 14 05:56:40 node-1 kernel: [    8.882976] type=1400 audit(1479102971.958:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1055 comm="apparmor_parser"
Nov 14 05:56:40 node-1 kernel: [    9.540923] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov 14 05:56:40 node-1 kernel: [    9.542760] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov 14 05:56:40 node-1 kernel: [    9.748814] enic 0000:06:00.0 enp6s0: Link UP
Nov 14 05:56:40 node-1 kernel: [    9.749236] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Nov 14 05:56:40 node-1 kernel: [    9.749246] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Nov 14 05:56:40 node-1 kernel: [   18.689960] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Nov 14 05:56:41 node-1 failsafe: Failsafe of 120 seconds reached.
Nov 14 05:56:41 node-1 kernel: [   37.710394] init: failsafe main process (8414) killed by TERM signal
Nov 14 05:56:42 node-1 dbus[8447]: [system] AppArmor D-Bus mediation is enabled
Nov 14 05:56:42 node-1 kernel: [   37.965720] audit_printk_skb: 30 callbacks suppressed
Nov 14 05:56:42 node-1 kernel: [   37.965723] type=1400 audit(1479103002.240:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8540 comm="apparmor_parser"
Nov 14 05:56:42 node-1 kernel: [   37.965997] type=1400 audit(1479103002.240:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8539 comm="apparmor_parser"
Nov 14 05:56:42 node-1 kernel: [   37.966002] type=1400 audit(1479103002.240:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8539 comm="apparmor_parser"
Nov 14 05:56:42 node-1 kernel: [   37.966005] type=1400 audit(1479103002.240:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8539 comm="apparmor_parser"
Nov 14 05:56:42 node-1 kernel: [   37.966244] type=1400 audit(1479103002.240:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8539 comm="apparmor_parser"
Nov 14 05:56:42 node-1 kernel: [   37.966246] type=1400 audit(1479103002.240:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8539 comm="apparmor_parser"
Nov 14 05:56:42 node-1 kernel: [   37.966361] type=1400 audit(1479103002.240:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8539 comm="apparmor_parser"
Nov 14 05:56:42 node-1 kernel: [   38.034146] type=1400 audit(1479103002.308:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8542 comm="apparmor_parser"
Nov 14 05:56:42 node-1 anacron[8609]: Anacron 2.3 started on 2016-11-14
Nov 14 05:56:42 node-1 cron[8572]: (CRON) INFO (pidfile fd = 3)
Nov 14 05:56:42 node-1 cron[8613]: (CRON) STARTUP (fork ok)
Nov 14 05:56:42 node-1 anacron[8609]: Will run job `cron.daily' in 5 min.
Nov 14 05:56:42 node-1 anacron[8609]: Will run job `cron.weekly' in 10 min.
Nov 14 05:56:42 node-1 anacron[8609]: Will run job `cron.monthly' in 15 min.
Nov 14 05:56:42 node-1 anacron[8609]: Jobs will be executed sequentially
Nov 14 05:56:42 node-1 cron[8613]: (CRON) INFO (Running @reboot jobs)
Nov 14 05:56:42 node-1 multipathd: path checkers start up
Nov 14 05:56:42 node-1 postfix/master[8751]: daemon started -- version 2.11.0, configuration /etc/postfix
Nov 14 05:56:45 node-1 puppet-agent[8936]: Reopening log files
Nov 14 05:56:46 node-1 puppet-agent[8936]: Could not request certificate: Connection refused - connect(2)
Nov 14 05:57:00 node-1 puppet-user[9149]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Nov 14 05:57:00 node-1 puppet-user[9149]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Nov 14 05:57:01 node-1 CRON[9702]: (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")
Nov 14 05:57:02 node-1 puppet-user[9149]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Nov 14 05:57:02 node-1 puppet-user[9149]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Nov 14 05:57:02 node-1 puppet-user[9149]: Finished catalog run in 1.66 seconds
Nov 14 05:57:03 node-1 multipathd: uevent trigger error
Nov 14 05:57:03 node-1 puppet-user[9790]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov 14 05:57:04 node-1 puppet-user[9790]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Nov 14 05:57:04 node-1 puppet-user[9790]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Nov 14 05:57:04 node-1 puppet-user[9790]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Nov 14 05:57:04 node-1 puppet-user[9790]: (/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"]'
Nov 14 05:57:04 node-1 puppet-user[9790]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Nov 14 05:57:04 node-1 puppet-user[9790]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Nov 14 05:57:04 node-1 puppet-user[9790]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Nov 14 05:57:04 node-1 puppet-user[9790]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Nov 14 05:57:04 node-1 puppet-user[9790]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Nov 14 05:57:04 node-1 puppet-user[9790]: Finished catalog run in 0.05 seconds
Nov 14 05:57:05 node-1 puppet-user[10250]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Nov 14 05:57:05 node-1 puppet-user[10250]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Nov 14 05:57:05 node-1 puppet-user[10250]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Nov 14 05:57:05 node-1 puppet-user[10250]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Nov 14 05:57:05 node-1 puppet-user[10250]: Finished catalog run in 0.03 seconds
Nov 14 05:57:07 node-1 puppet-user[10716]: (Scope(Class[main])) MODULAR: configuration_symlink
Nov 14 05:57:07 node-1 puppet-user[10716]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Nov 14 05:57:07 node-1 puppet-user[10716]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Nov 14 05:57:07 node-1 puppet-user[10716]: Finished catalog run in 0.03 seconds
Nov 14 05:57:08 node-1 puppet-user[11162]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Nov 14 05:57:08 node-1 puppet-user[11162]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Nov 14 05:57:08 node-1 puppet-user[11162]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Nov 14 05:57:11 node-1 puppet-user[11162]: (/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
Nov 14 05:57:11 node-1 puppet-user[11162]: Finished catalog run in 2.49 seconds
Nov 14 05:57:12 node-1 kernel: [   68.084314] init: plymouth-upstart-bridge main process ended, respawning
Nov 14 05:57:12 node-1 puppet-user[11715]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Nov 14 05:57:12 node-1 puppet-agent[8936]: Could not run: SIGTERM
Nov 14 05:57:12 node-1 kernel: [   68.339718] ip_tables: (C) 2000-2006 Netfilter Core Team
Nov 14 05:57:12 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Nov 14 05:57:12 node-1 nailgun-agent: D, [2016-11-14T05:57:01.667002 #9705] DEBUG -- : Sleep for 11 seconds before sending request
Nov 14 05:57:12 node-1 nailgun-agent: I, [2016-11-14T05:57:12.722384 #9705]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov 14 05:57:12 node-1 puppet-user[11715]: Compiled catalog for node-1.domain.tld in environment production in 0.22 seconds
Nov 14 05:57:12 node-1 ec2: 
Nov 14 05:57:12 node-1 ec2: #############################################################
Nov 14 05:57:12 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Nov 14 05:57:12 node-1 ec2: 1024 1b:19:7c:ff:c2:97:8d:62:c1:9d:a2:3e:d4:c9:b9:79  root@node-1.domain.tld (DSA)
Nov 14 05:57:12 node-1 ec2: 256 f9:bb:f9:a1:fd:b6:6b:ca:3d:83:a0:55:9a:7c:11:e5  root@node-1.domain.tld (ECDSA)
Nov 14 05:57:12 node-1 ec2: 256 fd:5f:c4:54:f4:e2:b3:0d:4d:d9:ec:06:a5:b7:c9:00  root@node-1.domain.tld (ED25519)
Nov 14 05:57:12 node-1 ec2: 2048 c8:de:e6:b4:7b:71:d8:6f:58:03:98:d3:3f:95:94:12  root@node-1.domain.tld (RSA)
Nov 14 05:57:12 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Nov 14 05:57:12 node-1 ec2: #############################################################
Nov 14 05:57:12 node-1 puppet-user[11715]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Nov 14 05:57:12 node-1 puppet-user[11715]: (/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
Nov 14 05:57:12 node-1 puppet-user[11715]: (/Stage[main]/Apt/File[preferences]/ensure) created
Nov 14 05:57:13 node-1 puppet-user[11715]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Nov 14 05:57:13 node-1 puppet-user[11715]: Finished catalog run in 0.23 seconds
Nov 14 05:57:13 node-1 nailgun-agent: D, [2016-11-14T05:57:13.403320 #9705] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Nov 14 05:57:14 node-1 puppet-user[12507]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Nov 14 05:57:14 node-1 puppet-user[12507]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Nov 14 05:57:14 node-1 puppet-user[12507]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Nov 14 05:57:14 node-1 kernel: [   70.654701] nr_pdflush_threads exported in /proc is scheduled for removal
Nov 14 05:57:14 node-1 kernel: [   70.654752] 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.
Nov 14 05:57:14 node-1 puppet-user[12507]: (/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'
Nov 14 05:57:14 node-1 puppet-user[12507]: Finished catalog run in 0.05 seconds
Nov 14 05:57:16 node-1 puppet-user[12968]: (Scope(Class[main])) MODULAR: sync_time
Nov 14 05:57:16 node-1 puppet-user[12968]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Nov 14 05:57:16 node-1 ntpdate[13392]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Nov 14 05:57:22 node-1 ntpdate[13392]: step time server 10.20.0.2 offset -0.582350 sec
Nov 14 05:57:22 node-1 puppet-user[12968]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Nov 14 05:57:22 node-1 puppet-user[12968]: Finished catalog run in 5.58 seconds
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.911435 #9705] DEBUG -- : Trying to find block devices
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.911556 #9705] DEBUG -- : Found block device: sda
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.911609 #9705] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.911644 #9705] DEBUG -- : Trying to get list of physical devices
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.911812 #9705] DEBUG -- : Getting udev properties for device: sda
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.913874 #9705] 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
Nov 14 05:57:24 node-1 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86841", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.913901 #9705] DEBUG -- : Trying to find out if device sda is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.913960 #9705] DEBUG -- : Device sda removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.913992 #9705] DEBUG -- : Device sda seems to be appropriate
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.914436 #9705] DEBUG -- : Getting udev properties for device: dm-0
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.916029 #9705] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-BLJlB58p0J8hgOc5xnZtmMM98yp6sW53ebafXmxXvtkV987QTyktlpjfpfjnphwB /dev/disk/by-uuid/e95f9881-555b-4523-afb0-2ddeb92175da /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-BLJlB58p0J8hgOc5xnZtmMM98yp6sW53ebafXmxXvtkV987QTyktlpjfpfjnphwB", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"e95f9881-555b-4523-afb0-2ddeb92175da", "ID_FS_UUID_ENC"=>"e95f9881-555b-4523-afb0-2ddeb92175da", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77094", "nomdmonddf"=>"1", "nomd
Nov 14 05:57:24 node-1 nailgun-agent: monisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.916072 #9705] DEBUG -- : Trying to find out if device dm-0 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.916105 #9705] DEBUG -- : Device dm-0 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.916120 #9705] DEBUG -- : Device dm-0 seems to be appropriate
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.916136 #9705] DEBUG -- : Getting udev properties for device: dm-1
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.917788 #9705] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-lyaCrg5eU7m6u04tbS9ZvDBstDWLx1w1dM7t6ohxPiWoFvKsk3R6C3nSHc7gDkdp /dev/disk/by-uuid/08e54475-3138-4de8-bc82-08df84caeed0 /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-lyaCrg5eU7m6u04tbS9ZvDBstDWLx1w1dM7t6ohxPiWoFvKsk3R6C3nSHc7gDkdp", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"08e54475-3138-4de8-bc82-08df84caeed0", "ID_FS_UUID_ENC"=>"08e54475-3138-4de8-bc82-08df84caeed0", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97
Nov 14 05:57:24 node-1 nailgun-agent: 638", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.917815 #9705] DEBUG -- : Trying to find out if device dm-1 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.917846 #9705] DEBUG -- : Device dm-1 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.917860 #9705] DEBUG -- : Device dm-1 seems to be appropriate
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.917876 #9705] DEBUG -- : Getting udev properties for device: dm-2
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.919457 #9705] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-WcZJ1AZCtgMO4KgH7WU9P6jGecCO5L9ud6vnh130NgrCwIcKR3S6ZWiDkQ0NT4Pd /dev/disk/by-uuid/b77bbdcc-b65d-482c-adf3-f1ba733ad219 /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-WcZJ1AZCtgMO4KgH7WU9P6jGecCO5L9ud6vnh130NgrCwIcKR3S6ZWiDkQ0NT4Pd", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b77bbdcc-b65d-482c-adf3-f1ba733ad219", "ID_FS_UUID_ENC"=>"b77bbdcc-b65d-482c-adf3-f1ba733ad219", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"8893", "nomdmondd
Nov 14 05:57:24 node-1 nailgun-agent: f"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.919496 #9705] DEBUG -- : Trying to find out if device dm-2 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.919528 #9705] DEBUG -- : Device dm-2 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.919543 #9705] DEBUG -- : Device dm-2 seems to be appropriate
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.919577 #9705] DEBUG -- : Getting udev properties for device: dm-3
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.921200 #9705] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-Azb2OCKIZet5YHGZvq03X4bctoiw1Zo8eaLY5JQ2gRUydfbDBXOnItmCNUNWjffb /dev/disk/by-uuid/bc3513a4-592c-4ac6-8391-012e8be130e3 /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-Azb2OCKIZet5YHGZvq03X4bctoiw1Zo8eaLY5JQ2gRUydfbDBXOnItmCNUNWjffb", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"bc3513a4-592c-4ac6-8391-012e8be130e3", "ID_FS_UUID_ENC"=>"bc3513a4-592c-4ac6-8391-012e8be130e3", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2561", "nomdmonddf"=>"1", "
Nov 14 05:57:24 node-1 nailgun-agent: nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.921239 #9705] DEBUG -- : Trying to find out if device dm-3 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.921272 #9705] DEBUG -- : Device dm-3 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.921287 #9705] DEBUG -- : Device dm-3 seems to be appropriate
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.921319 #9705] DEBUG -- : Getting udev properties for device: dm-4
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.922918 #9705] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-BqhxifqMxWRD73gcPksiCv8mUQgw1x0j4cMYUz7e91ebGPOG45YGG3ViJ85JVVjK /dev/disk/by-uuid/b64b3ab2-fcc3-4e27-ab13-6d9974dcf43e /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-BqhxifqMxWRD73gcPksiCv8mUQgw1x0j4cMYUz7e91ebGPOG45YGG3ViJ85JVVjK", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b64b3ab2-fcc3-4e27-ab13-6d9974dcf43e", "ID_FS_UUID_ENC"=>"b64b3ab2-fcc3-4e27-ab13-6d9974dcf43e", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"9821", "nomdmonddf"=>"1", "nomdm
Nov 14 05:57:24 node-1 nailgun-agent: onisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.922960 #9705] DEBUG -- : Trying to find out if device dm-4 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.922992 #9705] DEBUG -- : Device dm-4 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.923019 #9705] DEBUG -- : Device dm-4 seems to be appropriate
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.923034 #9705] DEBUG -- : Getting udev properties for device: dm-5
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.924658 #9705] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-BqhxifqMxWRD73gcPksiCv8mUQgw1x0jACk0OJ5djoiKkmZYjcQk6XVPA9vvPj20 /dev/disk/by-uuid/8f79f832-1ea4-4eb6-b848-d50ae5425698 /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-BqhxifqMxWRD73gcPksiCv8mUQgw1x0jACk0OJ5djoiKkmZYjcQk6XVPA9vvPj20", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"8f79f832-1ea4-4eb6-b848-d50ae5425698", "ID_FS_UUID_ENC"=>"8f79f832-1ea4-4eb6-b848-d50ae5425698", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"10307", "nomdmonddf"=>"1", "nomdmonisw"
Nov 14 05:57:24 node-1 nailgun-agent: =>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.924697 #9705] DEBUG -- : Trying to find out if device dm-5 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.924767 #9705] DEBUG -- : Device dm-5 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.924783 #9705] DEBUG -- : Device dm-5 seems to be appropriate
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.924799 #9705] DEBUG -- : Getting udev properties for device: ram0
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.926258 #9705] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45814", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.926284 #9705] DEBUG -- : Trying to find out if device ram0 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.926346 #9705] DEBUG -- : Device ram0 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.926367 #9705] DEBUG -- : Getting udev properties for device: ram1
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.927874 #9705] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45993", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.927900 #9705] DEBUG -- : Trying to find out if device ram1 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.927950 #9705] DEBUG -- : Device ram1 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.927974 #9705] DEBUG -- : Getting udev properties for device: ram2
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.929513 #9705] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47687", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.929540 #9705] DEBUG -- : Trying to find out if device ram2 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.929619 #9705] DEBUG -- : Device ram2 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.929641 #9705] DEBUG -- : Getting udev properties for device: ram3
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.931120 #9705] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48428", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.931154 #9705] DEBUG -- : Trying to find out if device ram3 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.931198 #9705] DEBUG -- : Device ram3 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.931238 #9705] DEBUG -- : Getting udev properties for device: ram4
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.932784 #9705] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48816", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.932810 #9705] DEBUG -- : Trying to find out if device ram4 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.932850 #9705] DEBUG -- : Device ram4 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.932873 #9705] DEBUG -- : Getting udev properties for device: ram5
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.934474 #9705] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49129", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.934520 #9705] DEBUG -- : Trying to find out if device ram5 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.934555 #9705] DEBUG -- : Device ram5 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.934591 #9705] DEBUG -- : Getting udev properties for device: ram6
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.936313 #9705] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49485", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.936339 #9705] DEBUG -- : Trying to find out if device ram6 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.936371 #9705] DEBUG -- : Device ram6 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.936401 #9705] DEBUG -- : Getting udev properties for device: ram7
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.937770 #9705] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49924", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.937803 #9705] DEBUG -- : Trying to find out if device ram7 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.937842 #9705] DEBUG -- : Device ram7 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.937874 #9705] DEBUG -- : Getting udev properties for device: ram8
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.939358 #9705] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50216", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.939384 #9705] DEBUG -- : Trying to find out if device ram8 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.939448 #9705] DEBUG -- : Device ram8 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.939470 #9705] DEBUG -- : Getting udev properties for device: ram9
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.940931 #9705] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50664", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.940957 #9705] DEBUG -- : Trying to find out if device ram9 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.940991 #9705] DEBUG -- : Device ram9 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.941023 #9705] DEBUG -- : Getting udev properties for device: loop0
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.942426 #9705] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43915", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.942468 #9705] DEBUG -- : Trying to find out if device loop0 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.942502 #9705] DEBUG -- : Device loop0 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.942522 #9705] DEBUG -- : Getting udev properties for device: loop1
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.943906 #9705] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44427", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.943950 #9705] DEBUG -- : Trying to find out if device loop1 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.943983 #9705] DEBUG -- : Device loop1 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.944021 #9705] DEBUG -- : Getting udev properties for device: loop2
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.945475 #9705] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44653", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.945509 #9705] DEBUG -- : Trying to find out if device loop2 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.945557 #9705] DEBUG -- : Device loop2 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.945579 #9705] DEBUG -- : Getting udev properties for device: loop3
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.947085 #9705] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45003", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.951244 #9705] DEBUG -- : Trying to find out if device loop3 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.951283 #9705] DEBUG -- : Device loop3 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.951304 #9705] DEBUG -- : Getting udev properties for device: loop4
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.953018 #9705] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45136", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.953064 #9705] DEBUG -- : Trying to find out if device loop4 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.953101 #9705] DEBUG -- : Device loop4 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.953121 #9705] DEBUG -- : Getting udev properties for device: loop5
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.954500 #9705] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45328", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.954526 #9705] DEBUG -- : Trying to find out if device loop5 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.954596 #9705] DEBUG -- : Device loop5 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.954617 #9705] DEBUG -- : Getting udev properties for device: loop6
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.956011 #9705] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45476", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.956037 #9705] DEBUG -- : Trying to find out if device loop6 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.956069 #9705] DEBUG -- : Device loop6 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.956123 #9705] DEBUG -- : Getting udev properties for device: loop7
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.957624 #9705] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45646", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.957651 #9705] DEBUG -- : Trying to find out if device loop7 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.957682 #9705] DEBUG -- : Device loop7 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.957703 #9705] DEBUG -- : Getting udev properties for device: ram10
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.959073 #9705] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"46193", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.959098 #9705] DEBUG -- : Trying to find out if device ram10 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.959131 #9705] DEBUG -- : Device ram10 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.959151 #9705] DEBUG -- : Getting udev properties for device: ram11
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.960574 #9705] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"46477", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.960600 #9705] DEBUG -- : Trying to find out if device ram11 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.960634 #9705] DEBUG -- : Device ram11 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.960655 #9705] DEBUG -- : Getting udev properties for device: ram12
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.962125 #9705] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"46680", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.962151 #9705] DEBUG -- : Trying to find out if device ram12 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.962191 #9705] DEBUG -- : Device ram12 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.962211 #9705] DEBUG -- : Getting udev properties for device: ram13
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.963568 #9705] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"46856", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.963596 #9705] DEBUG -- : Trying to find out if device ram13 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.963629 #9705] DEBUG -- : Device ram13 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.963650 #9705] DEBUG -- : Getting udev properties for device: ram14
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.965038 #9705] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47059", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.965064 #9705] DEBUG -- : Trying to find out if device ram14 is removable or not
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.965101 #9705] DEBUG -- : Device ram14 removable parameter: "0"
Nov 14 05:57:24 node-1 nailgun-agent: D, [2016-11-14T05:57:24.965121 #9705] DEBUG -- : Getting udev properties for device: ram15
Nov 14 05:57:24 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.966728 #9705] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47330", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.966754 #9705] DEBUG -- : Trying to find out if device ram15 is removable or not
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.966799 #9705] DEBUG -- : Device ram15 removable parameter: "0"
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.966835 #9705] 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"}]
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.966861 #9705] DEBUG -- : Block device seems to be physical data storage: sda
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.966895 #9705] DEBUG -- : Found block device: dm-0
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.966909 #9705] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.966922 #9705] DEBUG -- : Found block device: dm-1
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.966932 #9705] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.966993 #9705] DEBUG -- : Found block device: dm-2
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967005 #9705] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967014 #9705] DEBUG -- : Found block device: dm-3
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967024 #9705] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967033 #9705] DEBUG -- : Found block device: dm-4
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967044 #9705] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967053 #9705] DEBUG -- : Found block device: dm-5
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967062 #9705] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967121 #9705] DEBUG -- : Found block device: ram0
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967131 #9705] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967142 #9705] DEBUG -- : Found block device: ram1
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967153 #9705] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967163 #9705] DEBUG -- : Found block device: ram2
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967173 #9705] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967181 #9705] DEBUG -- : Found block device: ram3
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967191 #9705] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967253 #9705] DEBUG -- : Found block device: ram4
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967264 #9705] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967274 #9705] DEBUG -- : Found block device: ram5
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967286 #9705] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967295 #9705] DEBUG -- : Found block device: ram6
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967304 #9705] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967312 #9705] DEBUG -- : Found block device: ram7
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967321 #9705] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967330 #9705] DEBUG -- : Found block device: ram8
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967378 #9705] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967388 #9705] DEBUG -- : Found block device: ram9
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967398 #9705] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967407 #9705] DEBUG -- : Found block device: loop0
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967417 #9705] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967425 #9705] DEBUG -- : Found block device: loop1
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967435 #9705] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967444 #9705] DEBUG -- : Found block device: loop2
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967494 #9705] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967504 #9705] DEBUG -- : Found block device: loop3
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967514 #9705] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967523 #9705] DEBUG -- : Found block device: loop4
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967532 #9705] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967540 #9705] DEBUG -- : Found block device: loop5
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967549 #9705] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967558 #9705] DEBUG -- : Found block device: loop6
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967568 #9705] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967602 #9705] DEBUG -- : Found block device: loop7
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967612 #9705] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967621 #9705] DEBUG -- : Found block device: ram10
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967631 #9705] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967639 #9705] DEBUG -- : Found block device: ram11
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967650 #9705] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967658 #9705] DEBUG -- : Found block device: ram12
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967668 #9705] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967678 #9705] DEBUG -- : Found block device: ram13
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967710 #9705] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967718 #9705] DEBUG -- : Found block device: ram14
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967727 #9705] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967736 #9705] DEBUG -- : Found block device: ram15
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967745 #9705] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:24.967771 #9705] 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}]
Nov 14 05:57:25 node-1 nailgun-agent: D, [2016-11-14T05:57:25.069214 #9705] DEBUG -- : Response: status: 200 body: {"id": 1}
Nov 14 05:57:25 node-1 nailgun-agent: I, [2016-11-14T05:57:25.069409 #9705]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Nov 14 05:57:27 node-1 puppet-user[13777]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov 14 05:57:27 node-1 puppet-user[13777]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Nov 14 05:57:27 node-1 puppet-user[13777]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Nov 14 05:57:27 node-1 puppet-user[13777]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Nov 14 05:57:27 node-1 puppet-user[13777]: Finished catalog run in 0.08 seconds
Nov 14 05:57:28 node-1 puppet-user[14234]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Nov 14 05:57:29 node-1 puppet-user[14234]: Compiled catalog for node-1.domain.tld in environment production in 0.48 seconds
Nov 14 05:57:29 node-1 puppet-user[14234]: (/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
Nov 14 05:57:29 node-1 puppet-user[14234]: (/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
Nov 14 05:57:29 node-1 puppet-user[14234]: (/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
Nov 14 05:57:29 node-1 puppet-user[14234]: (/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
Nov 14 05:57:29 node-1 puppet-user[14234]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Nov 14 05:57:29 node-1 puppet-user[14234]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Nov 14 05:57:29 node-1 puppet-user[14234]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Nov 14 05:57:29 node-1 puppet-user[14234]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Nov 14 05:57:29 node-1 puppet-user[14234]: (/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
Nov 14 05:57:29 node-1 puppet-user[14234]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Nov 14 05:57:30 node-1 puppet-user[14234]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Nov 14 05:57:30 node-1 puppet-user[14234]: Finished catalog run in 1.04 seconds
Nov 14 05:57:31 node-1 puppet-user[14744]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Nov 14 05:57:32 node-1 puppet-user[14744]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Nov 14 05:57:36 node-1 puppet-user[14744]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Nov 14 05:58:01 node-1 CRON[17478]: (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")
Nov 14 05:58:02 node-1 puppet-user[14744]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Nov 14 05:58:02 node-1 puppet-user[14744]: Finished catalog run in 30.56 seconds
Nov 14 05:58:04 node-1 puppet-user[17567]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Nov 14 05:58:05 node-1 puppet-user[17567]: Compiled catalog for node-1.domain.tld in environment production in 0.58 seconds
Nov 14 05:58:05 node-1 puppet-user[17567]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Nov 14 05:58:05 node-1 puppet-user[17567]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Nov 14 05:58:05 node-1 puppet-user[17567]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Nov 14 05:58:05 node-1 puppet-user[17567]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Nov 14 05:58:05 node-1 puppet-user[17567]: Finished catalog run in 0.07 seconds
Nov 14 05:58:07 node-1 puppet-user[18029]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Nov 14 05:58:08 node-1 puppet-user[18029]: Compiled catalog for node-1.domain.tld in environment production in 0.88 seconds
Nov 14 05:58:08 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Nov 14 05:58:08 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Nov 14 05:58:08 node-1 crontab[18479]: (root) LIST (root)
Nov 14 05:58:08 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Nov 14 05:58:08 node-1 crontab[18480]: (root) REPLACE (root)
Nov 14 05:58:09 node-1 puppet-user[18029]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Nov 14 05:58:10 node-1 puppet-user[18029]: (/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
Nov 14 05:58:10 node-1 puppet-user[18029]: (/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
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Nov 14 05:58:10 node-1 puppet-user[18029]: (/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
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Nov 14 05:58:10 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Nov 14 05:58:11 node-1 puppet-user[18029]: (/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
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Nov 14 05:58:11 node-1 puppet-user[18029]: (/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
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Nov 14 05:58:11 node-1 puppet-user[18029]: (/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
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Nov 14 05:58:11 node-1 puppet-user[18029]: (/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
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Nov 14 05:58:11 node-1 puppet-user[18029]: (/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
Nov 14 05:58:11 node-1 puppet-user[18029]: (/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
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Nov 14 05:58:11 node-1 puppet-user[18029]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Nov 14 05:58:11 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8387" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 14 05:58:11 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Nov 14 05:58:13 node-1 multipathd: uevent trigger error
<27>Nov 14 05:58:13 node-1 multipathd: uevent trigger error
<27>Nov 14 05:58:13 node-1 multipathd: uevent trigger error
<27>Nov 14 05:58:13 node-1 multipathd: uevent trigger error
<27>Nov 14 05:58:13 node-1 multipathd: uevent trigger error
<27>Nov 14 05:58:26 node-1 multipathd: uevent trigger error
<27>Nov 14 05:58:26 node-1 multipathd: uevent trigger error
<27>Nov 14 05:58:26 node-1 multipathd: uevent trigger error
<27>Nov 14 05:58:26 node-1 multipathd: uevent trigger error
<27>Nov 14 05:58:26 node-1 multipathd: uevent trigger error
<27>Nov 14 05:59:15 node-1 multipathd: uevent trigger error
<27>Nov 14 05:59:15 node-1 multipathd: uevent trigger error
<27>Nov 14 05:59:15 node-1 multipathd: uevent trigger error
<27>Nov 14 05:59:15 node-1 multipathd: uevent trigger error
<27>Nov 14 05:59:15 node-1 multipathd: uevent trigger error
<27>Nov 14 05:59:15 node-1 multipathd: uevent trigger error
<27>Nov 14 05:59:15 node-1 multipathd: uevent trigger error
<27>Nov 14 05:59:18 node-1 multipathd: uevent trigger error
<27>Nov 14 05:59:18 node-1 multipathd: uevent trigger error
<27>Nov 14 05:59:18 node-1 multipathd: uevent trigger error
<27>Nov 14 05:59:18 node-1 multipathd: uevent trigger error
<27>Nov 14 05:59:18 node-1 multipathd: uevent trigger error
<27>Nov 14 05:59:18 node-1 multipathd: uevent trigger error
<27>Nov 14 05:59:57 node-1 ntpdate[1856]: no servers can be used, exiting
<27>Nov 14 06:00:29 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:29 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:29 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:29 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:29 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:29 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:32 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:32 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:32 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:32 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:32 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:45 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:45 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:45 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:45 node-1 multipathd: uevent trigger error
<27>Nov 14 06:00:45 node-1 multipathd: uevent trigger error
<27>Nov 14 06:01:40 node-1 multipathd: uevent trigger error
<27>Nov 14 06:01:40 node-1 multipathd: uevent trigger error
<27>Nov 14 06:01:40 node-1 multipathd: uevent trigger error
<27>Nov 14 06:01:40 node-1 multipathd: uevent trigger error
<27>Nov 14 06:01:40 node-1 multipathd: uevent trigger error
<27>Nov 14 06:01:40 node-1 multipathd: uevent trigger error
<27>Nov 14 06:01:40 node-1 multipathd: uevent trigger error
<27>Nov 14 06:01:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:01:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:01:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:01:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:01:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:01:51 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 14 06:01:51 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 14 06:01:57 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 14 06:01:57 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 14 06:02:02 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 14 06:02:08 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 14 06:02:08 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 14 06:02:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:25 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:25 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:25 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:25 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:25 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:25 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:38 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:38 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:38 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:38 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:38 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:38 node-1 multipathd: uevent trigger error
<129>Nov 14 06:02:40 node-1 haproxy[23507]: 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>Nov 14 06:02:41 node-1 haproxy[23511]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:02:41 node-1 haproxy[23511]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:02:41 node-1 haproxy[23511]: proxy mysqld has no server available!
<27>Nov 14 06:02:43 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:43 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:43 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:43 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:43 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:47 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:47 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:47 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:47 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:47 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:47 node-1 multipathd: uevent trigger error
<129>Nov 14 06:02:49 node-1 haproxy[26088]: 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>Nov 14 06:02:50 node-1 haproxy[26092]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:02:50 node-1 haproxy[26092]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:02:50 node-1 haproxy[26092]: proxy mysqld has no server available!
<129>Nov 14 06:02:50 node-1 haproxy[26092]: 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>Nov 14 06:02:51 node-1 haproxy[26092]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:02:51 node-1 haproxy[26092]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:02:51 node-1 haproxy[26092]: proxy object-storage has no server available!
<27>Nov 14 06:02:52 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:52 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:52 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:52 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:52 node-1 multipathd: uevent trigger error
<129>Nov 14 06:02:55 node-1 haproxy[27415]: 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>Nov 14 06:02:55 node-1 haproxy[27415]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:02:55 node-1 haproxy[27415]: 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>Nov 14 06:02:55 node-1 haproxy[27415]: proxy neutron has no server available!
<129>Nov 14 06:02:55 node-1 haproxy[27415]: 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>Nov 14 06:02:55 node-1 haproxy[27415]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:02:56 node-1 haproxy[27419]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:02:56 node-1 haproxy[27419]: proxy mysqld has no server available!
<129>Nov 14 06:02:56 node-1 haproxy[27419]: 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>Nov 14 06:02:56 node-1 haproxy[27419]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:02:56 node-1 haproxy[27419]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:02:56 node-1 haproxy[27419]: proxy object-storage has no server available!
<27>Nov 14 06:02:58 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:58 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:58 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:58 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:58 node-1 multipathd: uevent trigger error
<27>Nov 14 06:02:58 node-1 multipathd: uevent trigger error
<129>Nov 14 06:03:00 node-1 haproxy[28844]: 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>Nov 14 06:03:00 node-1 haproxy[28844]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:00 node-1 haproxy[28844]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:00 node-1 haproxy[28844]: proxy keystone-1 has no server available!
<129>Nov 14 06:03:00 node-1 haproxy[28844]: 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>Nov 14 06:03:00 node-1 haproxy[28844]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:01 node-1 haproxy[28853]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:01 node-1 haproxy[28853]: proxy keystone-2 has no server available!
<129>Nov 14 06:03:01 node-1 haproxy[28853]: 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>Nov 14 06:03:01 node-1 haproxy[28853]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:01 node-1 haproxy[28853]: 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>Nov 14 06:03:01 node-1 haproxy[28853]: proxy neutron has no server available!
<129>Nov 14 06:03:01 node-1 haproxy[28853]: 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>Nov 14 06:03:01 node-1 haproxy[28853]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:01 node-1 haproxy[28853]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:01 node-1 haproxy[28853]: proxy mysqld has no server available!
<129>Nov 14 06:03:02 node-1 haproxy[28853]: 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>Nov 14 06:03:02 node-1 haproxy[28853]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:02 node-1 haproxy[28853]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:02 node-1 haproxy[28853]: proxy object-storage has no server available!
<27>Nov 14 06:03:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:03 node-1 multipathd: uevent trigger error
<129>Nov 14 06:03:05 node-1 haproxy[30248]: 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>Nov 14 06:03:05 node-1 haproxy[30248]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:05 node-1 haproxy[30248]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:05 node-1 haproxy[30248]: proxy keystone-1 has no server available!
<129>Nov 14 06:03:06 node-1 haproxy[30252]: 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>Nov 14 06:03:06 node-1 haproxy[30252]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:06 node-1 haproxy[30252]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:06 node-1 haproxy[30252]: proxy keystone-2 has no server available!
<129>Nov 14 06:03:06 node-1 haproxy[30252]: 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>Nov 14 06:03:06 node-1 haproxy[30252]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:06 node-1 haproxy[30252]: 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>Nov 14 06:03:06 node-1 haproxy[30252]: proxy neutron has no server available!
<129>Nov 14 06:03:06 node-1 haproxy[30252]: 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>Nov 14 06:03:06 node-1 haproxy[30252]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:06 node-1 haproxy[30252]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:06 node-1 haproxy[30252]: proxy mysqld has no server available!
<129>Nov 14 06:03:07 node-1 haproxy[30252]: 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>Nov 14 06:03:07 node-1 haproxy[30252]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:07 node-1 haproxy[30252]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:07 node-1 haproxy[30252]: proxy object-storage has no server available!
<129>Nov 14 06:03:07 node-1 haproxy[30252]: 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>Nov 14 06:03:07 node-1 haproxy[30252]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:07 node-1 haproxy[30252]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:07 node-1 haproxy[30252]: proxy aodh has no server available!
<27>Nov 14 06:03:08 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:09 node-1 multipathd: uevent trigger error
<129>Nov 14 06:03:11 node-1 haproxy[31580]: 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>Nov 14 06:03:11 node-1 haproxy[31580]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:11 node-1 haproxy[31580]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:11 node-1 haproxy[31580]: proxy keystone-1 has no server available!
<129>Nov 14 06:03:11 node-1 haproxy[31580]: 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>Nov 14 06:03:11 node-1 haproxy[31580]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:11 node-1 haproxy[31580]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:11 node-1 haproxy[31580]: proxy keystone-2 has no server available!
<129>Nov 14 06:03:11 node-1 haproxy[31580]: 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>Nov 14 06:03:11 node-1 haproxy[31580]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:11 node-1 haproxy[31580]: 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>Nov 14 06:03:11 node-1 haproxy[31580]: proxy neutron has no server available!
<129>Nov 14 06:03:12 node-1 haproxy[31584]: 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>Nov 14 06:03:12 node-1 haproxy[31584]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:12 node-1 haproxy[31584]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:12 node-1 haproxy[31584]: proxy mysqld has no server available!
<129>Nov 14 06:03:12 node-1 haproxy[31584]: 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>Nov 14 06:03:12 node-1 haproxy[31584]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:12 node-1 haproxy[31584]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:12 node-1 haproxy[31584]: proxy object-storage has no server available!
<129>Nov 14 06:03:12 node-1 haproxy[31584]: 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>Nov 14 06:03:12 node-1 haproxy[31584]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:12 node-1 haproxy[31584]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:12 node-1 haproxy[31584]: proxy aodh has no server available!
<129>Nov 14 06:03:12 node-1 haproxy[31584]: 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>Nov 14 06:03:13 node-1 haproxy[31584]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:13 node-1 haproxy[31584]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:13 node-1 haproxy[31584]: proxy ceilometer has no server available!
<27>Nov 14 06:03:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:14 node-1 multipathd: uevent trigger error
<129>Nov 14 06:03:16 node-1 haproxy[503]: 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>Nov 14 06:03:16 node-1 haproxy[503]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:17 node-1 haproxy[507]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:17 node-1 haproxy[507]: proxy keystone-1 has no server available!
<129>Nov 14 06:03:17 node-1 haproxy[507]: 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>Nov 14 06:03:17 node-1 haproxy[507]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:17 node-1 haproxy[507]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:17 node-1 haproxy[507]: proxy keystone-2 has no server available!
<129>Nov 14 06:03:17 node-1 haproxy[507]: 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>Nov 14 06:03:17 node-1 haproxy[507]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:17 node-1 haproxy[507]: 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>Nov 14 06:03:17 node-1 haproxy[507]: proxy neutron has no server available!
<129>Nov 14 06:03:17 node-1 haproxy[507]: 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>Nov 14 06:03:17 node-1 haproxy[507]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:17 node-1 haproxy[507]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:17 node-1 haproxy[507]: proxy mysqld has no server available!
<129>Nov 14 06:03:18 node-1 haproxy[507]: 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>Nov 14 06:03:18 node-1 haproxy[507]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:18 node-1 haproxy[507]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:18 node-1 haproxy[507]: proxy object-storage has no server available!
<129>Nov 14 06:03:18 node-1 haproxy[507]: 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>Nov 14 06:03:18 node-1 haproxy[507]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:18 node-1 haproxy[507]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:18 node-1 haproxy[507]: proxy aodh has no server available!
<129>Nov 14 06:03:18 node-1 haproxy[507]: 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>Nov 14 06:03:18 node-1 haproxy[507]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:18 node-1 haproxy[507]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:18 node-1 haproxy[507]: proxy ceilometer has no server available!
<27>Nov 14 06:03:19 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:19 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:19 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:19 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:20 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:20 node-1 multipathd: uevent trigger error
<129>Nov 14 06:03:22 node-1 haproxy[1980]: 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>Nov 14 06:03:22 node-1 haproxy[1980]: 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>Nov 14 06:03:22 node-1 haproxy[1980]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:22 node-1 haproxy[1980]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:22 node-1 haproxy[1980]: proxy keystone-1 has no server available!
<129>Nov 14 06:03:22 node-1 haproxy[1980]: 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>Nov 14 06:03:22 node-1 haproxy[1980]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:22 node-1 haproxy[1980]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:22 node-1 haproxy[1980]: proxy keystone-2 has no server available!
<129>Nov 14 06:03:22 node-1 haproxy[1980]: 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>Nov 14 06:03:23 node-1 haproxy[1984]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:23 node-1 haproxy[1984]: 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>Nov 14 06:03:23 node-1 haproxy[1984]: proxy neutron has no server available!
<129>Nov 14 06:03:23 node-1 haproxy[1984]: 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>Nov 14 06:03:23 node-1 haproxy[1984]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:23 node-1 haproxy[1984]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:23 node-1 haproxy[1984]: proxy mysqld has no server available!
<129>Nov 14 06:03:23 node-1 haproxy[1984]: 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>Nov 14 06:03:23 node-1 haproxy[1984]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:23 node-1 haproxy[1984]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:23 node-1 haproxy[1984]: proxy object-storage has no server available!
<129>Nov 14 06:03:23 node-1 haproxy[1984]: 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>Nov 14 06:03:23 node-1 haproxy[1984]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:23 node-1 haproxy[1984]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:23 node-1 haproxy[1984]: proxy aodh has no server available!
<129>Nov 14 06:03:23 node-1 haproxy[1984]: 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>Nov 14 06:03:24 node-1 haproxy[1984]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:24 node-1 haproxy[1984]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:24 node-1 haproxy[1984]: proxy ceilometer has no server available!
<27>Nov 14 06:03:25 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:25 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:25 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:25 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:25 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:25 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:25 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:25 node-1 multipathd: uevent trigger error
<129>Nov 14 06:03:27 node-1 haproxy[3382]: 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>Nov 14 06:03:27 node-1 haproxy[3382]: 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>Nov 14 06:03:27 node-1 haproxy[3382]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:27 node-1 haproxy[3382]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:27 node-1 haproxy[3382]: proxy keystone-1 has no server available!
<129>Nov 14 06:03:28 node-1 haproxy[3386]: 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>Nov 14 06:03:28 node-1 haproxy[3386]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:28 node-1 haproxy[3386]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:28 node-1 haproxy[3386]: proxy keystone-2 has no server available!
<129>Nov 14 06:03:28 node-1 haproxy[3386]: 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>Nov 14 06:03:28 node-1 haproxy[3386]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:28 node-1 haproxy[3386]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:28 node-1 haproxy[3386]: proxy glance-api has no server available!
<129>Nov 14 06:03:28 node-1 haproxy[3386]: 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>Nov 14 06:03:28 node-1 haproxy[3386]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:28 node-1 haproxy[3386]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:28 node-1 haproxy[3386]: proxy glance-glare has no server available!
<129>Nov 14 06:03:28 node-1 haproxy[3386]: 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>Nov 14 06:03:28 node-1 haproxy[3386]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:28 node-1 haproxy[3386]: 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>Nov 14 06:03:28 node-1 haproxy[3386]: proxy neutron has no server available!
<129>Nov 14 06:03:28 node-1 haproxy[3386]: 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>Nov 14 06:03:28 node-1 haproxy[3386]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:28 node-1 haproxy[3386]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:28 node-1 haproxy[3386]: proxy glance-registry has no server available!
<129>Nov 14 06:03:28 node-1 haproxy[3386]: 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>Nov 14 06:03:29 node-1 haproxy[3386]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:29 node-1 haproxy[3386]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:29 node-1 haproxy[3386]: proxy mysqld has no server available!
<129>Nov 14 06:03:29 node-1 haproxy[3386]: 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>Nov 14 06:03:29 node-1 haproxy[3386]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:29 node-1 haproxy[3386]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:29 node-1 haproxy[3386]: proxy object-storage has no server available!
<129>Nov 14 06:03:29 node-1 haproxy[3386]: 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>Nov 14 06:03:29 node-1 haproxy[3386]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:29 node-1 haproxy[3386]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:29 node-1 haproxy[3386]: proxy aodh has no server available!
<129>Nov 14 06:03:29 node-1 haproxy[3386]: 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>Nov 14 06:03:29 node-1 haproxy[3386]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:29 node-1 haproxy[3386]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:29 node-1 haproxy[3386]: proxy ceilometer has no server available!
<27>Nov 14 06:03:30 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:30 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:30 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:30 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:30 node-1 multipathd: uevent trigger error
<129>Nov 14 06:03:33 node-1 haproxy[4957]: 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>Nov 14 06:03:33 node-1 haproxy[4957]: 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>Nov 14 06:03:33 node-1 haproxy[4957]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:33 node-1 haproxy[4957]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:33 node-1 haproxy[4957]: proxy keystone-1 has no server available!
<129>Nov 14 06:03:33 node-1 haproxy[4957]: 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>Nov 14 06:03:33 node-1 haproxy[4957]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:33 node-1 haproxy[4957]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:33 node-1 haproxy[4957]: proxy keystone-2 has no server available!
<129>Nov 14 06:03:33 node-1 haproxy[4957]: 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>Nov 14 06:03:33 node-1 haproxy[4957]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:33 node-1 haproxy[4957]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:33 node-1 haproxy[4957]: proxy nova-api has no server available!
<129>Nov 14 06:03:34 node-1 haproxy[4961]: 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>Nov 14 06:03:34 node-1 haproxy[4961]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:34 node-1 haproxy[4961]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:34 node-1 haproxy[4961]: proxy nova-metadata-api has no server available!
<129>Nov 14 06:03:34 node-1 haproxy[4961]: 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>Nov 14 06:03:34 node-1 haproxy[4961]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:34 node-1 haproxy[4961]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:34 node-1 haproxy[4961]: proxy glance-api has no server available!
<129>Nov 14 06:03:34 node-1 haproxy[4961]: 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>Nov 14 06:03:34 node-1 haproxy[4961]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:34 node-1 haproxy[4961]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:34 node-1 haproxy[4961]: proxy glance-glare has no server available!
<129>Nov 14 06:03:34 node-1 haproxy[4961]: 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>Nov 14 06:03:34 node-1 haproxy[4961]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:34 node-1 haproxy[4961]: 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>Nov 14 06:03:34 node-1 haproxy[4961]: proxy neutron has no server available!
<129>Nov 14 06:03:34 node-1 haproxy[4961]: 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>Nov 14 06:03:34 node-1 haproxy[4961]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:34 node-1 haproxy[4961]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:34 node-1 haproxy[4961]: proxy glance-registry has no server available!
<129>Nov 14 06:03:34 node-1 haproxy[4961]: 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>Nov 14 06:03:34 node-1 haproxy[4961]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:34 node-1 haproxy[4961]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:34 node-1 haproxy[4961]: proxy mysqld has no server available!
<129>Nov 14 06:03:34 node-1 haproxy[4961]: 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>Nov 14 06:03:34 node-1 haproxy[4961]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:34 node-1 haproxy[4961]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:34 node-1 haproxy[4961]: proxy object-storage has no server available!
<129>Nov 14 06:03:35 node-1 haproxy[4961]: 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>Nov 14 06:03:35 node-1 haproxy[4961]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:35 node-1 haproxy[4961]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:35 node-1 haproxy[4961]: proxy aodh has no server available!
<129>Nov 14 06:03:35 node-1 haproxy[4961]: 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>Nov 14 06:03:35 node-1 haproxy[4961]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:35 node-1 haproxy[4961]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:35 node-1 haproxy[4961]: proxy ceilometer has no server available!
<129>Nov 14 06:03:35 node-1 haproxy[4961]: 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>Nov 14 06:03:35 node-1 haproxy[4961]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:35 node-1 haproxy[4961]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:35 node-1 haproxy[4961]: proxy nova-novncproxy has no server available!
<27>Nov 14 06:03:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:36 node-1 multipathd: uevent trigger error
<129>Nov 14 06:03:38 node-1 haproxy[6291]: 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>Nov 14 06:03:38 node-1 haproxy[6291]: 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>Nov 14 06:03:38 node-1 haproxy[6291]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:39 node-1 haproxy[6295]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:39 node-1 haproxy[6295]: proxy keystone-1 has no server available!
<129>Nov 14 06:03:39 node-1 haproxy[6295]: 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>Nov 14 06:03:39 node-1 haproxy[6295]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:39 node-1 haproxy[6295]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:39 node-1 haproxy[6295]: proxy keystone-2 has no server available!
<129>Nov 14 06:03:39 node-1 haproxy[6295]: 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>Nov 14 06:03:39 node-1 haproxy[6295]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:39 node-1 haproxy[6295]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:39 node-1 haproxy[6295]: proxy nova-api has no server available!
<129>Nov 14 06:03:39 node-1 haproxy[6295]: 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>Nov 14 06:03:39 node-1 haproxy[6295]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:39 node-1 haproxy[6295]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:39 node-1 haproxy[6295]: proxy nova-metadata-api has no server available!
<129>Nov 14 06:03:39 node-1 haproxy[6295]: 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>Nov 14 06:03:39 node-1 haproxy[6295]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:39 node-1 haproxy[6295]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:39 node-1 haproxy[6295]: proxy cinder-api has no server available!
<129>Nov 14 06:03:39 node-1 haproxy[6295]: 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>Nov 14 06:03:39 node-1 haproxy[6295]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:39 node-1 haproxy[6295]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:39 node-1 haproxy[6295]: proxy glance-api has no server available!
<129>Nov 14 06:03:39 node-1 haproxy[6295]: 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>Nov 14 06:03:39 node-1 haproxy[6295]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:39 node-1 haproxy[6295]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:39 node-1 haproxy[6295]: proxy glance-glare has no server available!
<129>Nov 14 06:03:39 node-1 haproxy[6295]: 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>Nov 14 06:03:39 node-1 haproxy[6295]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:39 node-1 haproxy[6295]: 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>Nov 14 06:03:39 node-1 haproxy[6295]: proxy neutron has no server available!
<129>Nov 14 06:03:40 node-1 haproxy[6295]: 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>Nov 14 06:03:40 node-1 haproxy[6295]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:40 node-1 haproxy[6295]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:40 node-1 haproxy[6295]: proxy glance-registry has no server available!
<129>Nov 14 06:03:40 node-1 haproxy[6295]: 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>Nov 14 06:03:40 node-1 haproxy[6295]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:40 node-1 haproxy[6295]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:40 node-1 haproxy[6295]: proxy mysqld has no server available!
<129>Nov 14 06:03:40 node-1 haproxy[6295]: 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>Nov 14 06:03:40 node-1 haproxy[6295]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:40 node-1 haproxy[6295]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:40 node-1 haproxy[6295]: proxy object-storage has no server available!
<129>Nov 14 06:03:40 node-1 haproxy[6295]: 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>Nov 14 06:03:40 node-1 haproxy[6295]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:40 node-1 haproxy[6295]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:40 node-1 haproxy[6295]: proxy aodh has no server available!
<129>Nov 14 06:03:40 node-1 haproxy[6295]: 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>Nov 14 06:03:40 node-1 haproxy[6295]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:40 node-1 haproxy[6295]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:40 node-1 haproxy[6295]: proxy ceilometer has no server available!
<129>Nov 14 06:03:40 node-1 haproxy[6295]: 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>Nov 14 06:03:40 node-1 haproxy[6295]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:40 node-1 haproxy[6295]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:40 node-1 haproxy[6295]: proxy nova-novncproxy has no server available!
<27>Nov 14 06:03:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:42 node-1 multipathd: uevent trigger error
<129>Nov 14 06:03:44 node-1 haproxy[7706]: 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>Nov 14 06:03:44 node-1 haproxy[7706]: 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>Nov 14 06:03:44 node-1 haproxy[7706]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:44 node-1 haproxy[7706]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:44 node-1 haproxy[7706]: proxy keystone-1 has no server available!
<129>Nov 14 06:03:44 node-1 haproxy[7706]: 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>Nov 14 06:03:44 node-1 haproxy[7706]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:44 node-1 haproxy[7706]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:44 node-1 haproxy[7706]: proxy keystone-2 has no server available!
<129>Nov 14 06:03:44 node-1 haproxy[7706]: 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>Nov 14 06:03:44 node-1 haproxy[7706]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:44 node-1 haproxy[7706]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:44 node-1 haproxy[7706]: proxy nova-api has no server available!
<129>Nov 14 06:03:45 node-1 haproxy[7710]: 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>Nov 14 06:03:45 node-1 haproxy[7710]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:45 node-1 haproxy[7710]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:45 node-1 haproxy[7710]: proxy nova-metadata-api has no server available!
<129>Nov 14 06:03:45 node-1 haproxy[7710]: 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>Nov 14 06:03:45 node-1 haproxy[7710]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:45 node-1 haproxy[7710]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:45 node-1 haproxy[7710]: proxy cinder-api has no server available!
<129>Nov 14 06:03:45 node-1 haproxy[7710]: 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>Nov 14 06:03:45 node-1 haproxy[7710]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:45 node-1 haproxy[7710]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:45 node-1 haproxy[7710]: proxy glance-api has no server available!
<129>Nov 14 06:03:45 node-1 haproxy[7710]: 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>Nov 14 06:03:45 node-1 haproxy[7710]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:45 node-1 haproxy[7710]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:45 node-1 haproxy[7710]: proxy glance-glare has no server available!
<129>Nov 14 06:03:45 node-1 haproxy[7710]: 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>Nov 14 06:03:45 node-1 haproxy[7710]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:45 node-1 haproxy[7710]: 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>Nov 14 06:03:45 node-1 haproxy[7710]: proxy neutron has no server available!
<129>Nov 14 06:03:45 node-1 haproxy[7710]: 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>Nov 14 06:03:45 node-1 haproxy[7710]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:45 node-1 haproxy[7710]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:45 node-1 haproxy[7710]: proxy glance-registry has no server available!
<129>Nov 14 06:03:45 node-1 haproxy[7710]: 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>Nov 14 06:03:45 node-1 haproxy[7710]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:45 node-1 haproxy[7710]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:45 node-1 haproxy[7710]: proxy mysqld has no server available!
<129>Nov 14 06:03:45 node-1 haproxy[7710]: 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>Nov 14 06:03:45 node-1 haproxy[7710]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:45 node-1 haproxy[7710]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:45 node-1 haproxy[7710]: proxy object-storage has no server available!
<129>Nov 14 06:03:45 node-1 haproxy[7710]: 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>Nov 14 06:03:45 node-1 haproxy[7710]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:45 node-1 haproxy[7710]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:45 node-1 haproxy[7710]: proxy aodh has no server available!
<129>Nov 14 06:03:46 node-1 haproxy[7710]: 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>Nov 14 06:03:46 node-1 haproxy[7710]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:46 node-1 haproxy[7710]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:46 node-1 haproxy[7710]: proxy ceilometer has no server available!
<129>Nov 14 06:03:46 node-1 haproxy[7710]: 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>Nov 14 06:03:46 node-1 haproxy[7710]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:46 node-1 haproxy[7710]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:46 node-1 haproxy[7710]: proxy heat-api has no server available!
<129>Nov 14 06:03:46 node-1 haproxy[7710]: 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>Nov 14 06:03:46 node-1 haproxy[7710]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:46 node-1 haproxy[7710]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:46 node-1 haproxy[7710]: proxy heat-api-cfn has no server available!
<129>Nov 14 06:03:46 node-1 haproxy[7710]: 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>Nov 14 06:03:46 node-1 haproxy[7710]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:46 node-1 haproxy[7710]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:46 node-1 haproxy[7710]: proxy heat-api-cloudwatch has no server available!
<129>Nov 14 06:03:46 node-1 haproxy[7710]: 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>Nov 14 06:03:46 node-1 haproxy[7710]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:03:46 node-1 haproxy[7710]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:03:46 node-1 haproxy[7710]: proxy nova-novncproxy has no server available!
<27>Nov 14 06:03:47 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:47 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:47 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:47 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:47 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:51 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:51 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:51 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:51 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:51 node-1 multipathd: uevent trigger error
<27>Nov 14 06:03:58 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Nov 14 06:04:22 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>Nov 14 06:04:24 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Nov 14 06:04:51 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 14 06:04:55 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 14 06:05:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:05:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:05:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:05:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:05:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:05:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:05:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:07:34 node-1 multipathd: uevent trigger error
<27>Nov 14 06:07:34 node-1 multipathd: uevent trigger error
<27>Nov 14 06:07:34 node-1 multipathd: uevent trigger error
<27>Nov 14 06:07:34 node-1 multipathd: uevent trigger error
<27>Nov 14 06:07:34 node-1 multipathd: uevent trigger error
<27>Nov 14 06:07:40 node-1 multipathd: uevent trigger error
<27>Nov 14 06:07:40 node-1 multipathd: uevent trigger error
<27>Nov 14 06:07:40 node-1 multipathd: uevent trigger error
<27>Nov 14 06:07:40 node-1 multipathd: uevent trigger error
<27>Nov 14 06:07:40 node-1 multipathd: uevent trigger error
<43>Nov 14 06:07:52 node-1 apache2_error [Mon Nov 14 06:07:50.901769 2016] [mpm_event:notice] [pid 15762:tid 140058772379520] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov 14 06:07:52 node-1 apache2_error [Mon Nov 14 06:07:50.901888 2016] [core:notice] [pid 15762:tid 140058772379520] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 14 06:07:53 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 14 06:07:58 node-1 multipathd: uevent trigger error
<27>Nov 14 06:07:58 node-1 multipathd: uevent trigger error
<27>Nov 14 06:07:58 node-1 multipathd: uevent trigger error
<27>Nov 14 06:07:58 node-1 multipathd: uevent trigger error
<27>Nov 14 06:07:58 node-1 multipathd: uevent trigger error
<43>Nov 14 06:08:02 node-1 apache2_error [Mon Nov 14 06:07:53.878899 2016] [mpm_event:notice] [pid 15762:tid 140058772379520] AH00491: caught SIGTERM, shutting down
<43>Nov 14 06:08:02 node-1 apache2_error [Mon Nov 14 06:07:54.973147 2016] [mpm_worker:notice] [pid 17331:tid 139967257524096] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov 14 06:08:02 node-1 apache2_error [Mon Nov 14 06:07:54.973182 2016] [core:notice] [pid 17331:tid 139967257524096] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 14 06:08:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:08:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:08:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:08:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:08:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:08:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:08:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:08:06 node-1 multipathd: uevent trigger error
<27>Nov 14 06:08:06 node-1 multipathd: uevent trigger error
<27>Nov 14 06:08:06 node-1 multipathd: uevent trigger error
<27>Nov 14 06:08:06 node-1 multipathd: uevent trigger error
<27>Nov 14 06:08:06 node-1 multipathd: uevent trigger error
<43>Nov 14 06:09:12 node-1 apache2_error [Mon Nov 14 06:09:08.665544 2016] [mpm_worker:notice] [pid 17331:tid 139967257524096] AH00295: caught SIGTERM, shutting down
<43>Nov 14 06:09:12 node-1 apache2_error [Mon Nov 14 06:09:09.412562 2016] [mpm_worker:notice] [pid 30684:tid 140053462763392] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 14 06:09:12 node-1 apache2_error [Mon Nov 14 06:09:09.412587 2016] [core:notice] [pid 30684:tid 140053462763392] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov 14 06:10:02 node-1 apache2_error [Mon Nov 14 06:09:53.405824 2016] [mpm_worker:notice] [pid 30684:tid 140053462763392] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 14 06:10:02 node-1 apache2_error [Mon Nov 14 06:09:53.598909 2016] [mpm_worker:warn] [pid 30684:tid 140053462763392] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 14 06:10:02 node-1 apache2_error [Mon Nov 14 06:09:53.602104 2016] [mpm_worker:notice] [pid 30684:tid 140053462763392] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 14 06:10:02 node-1 apache2_error [Mon Nov 14 06:09:53.602121 2016] [core:notice] [pid 30684:tid 140053462763392] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 14 06:10:38 node-1 multipathd: uevent trigger error
<27>Nov 14 06:10:38 node-1 multipathd: uevent trigger error
<27>Nov 14 06:10:38 node-1 multipathd: uevent trigger error
<27>Nov 14 06:10:38 node-1 multipathd: uevent trigger error
<27>Nov 14 06:10:38 node-1 multipathd: uevent trigger error
<27>Nov 14 06:10:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:10:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:10:43 node-1 multipathd: uevent trigger error
<27>Nov 14 06:10:43 node-1 multipathd: uevent trigger error
<27>Nov 14 06:10:43 node-1 multipathd: uevent trigger error
<27>Nov 14 06:10:55 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 14 06:10:58 node-1 multipathd: uevent trigger error
<27>Nov 14 06:10:58 node-1 multipathd: uevent trigger error
<27>Nov 14 06:10:58 node-1 multipathd: uevent trigger error
<27>Nov 14 06:10:58 node-1 multipathd: uevent trigger error
<27>Nov 14 06:10:58 node-1 multipathd: uevent trigger error
<27>Nov 14 06:10:58 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:17 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:17 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:17 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:17 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:17 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:17 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:21 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:21 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:21 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:21 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:21 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:11:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:12:23 node-1 multipathd: uevent trigger error
<27>Nov 14 06:12:23 node-1 multipathd: uevent trigger error
<27>Nov 14 06:12:23 node-1 multipathd: uevent trigger error
<27>Nov 14 06:12:23 node-1 multipathd: uevent trigger error
<27>Nov 14 06:12:23 node-1 multipathd: uevent trigger error
<27>Nov 14 06:13:31 node-1 multipathd: uevent trigger error
<27>Nov 14 06:13:31 node-1 multipathd: uevent trigger error
<27>Nov 14 06:13:31 node-1 multipathd: uevent trigger error
<27>Nov 14 06:13:31 node-1 multipathd: uevent trigger error
<27>Nov 14 06:13:31 node-1 multipathd: uevent trigger error
<27>Nov 14 06:13:31 node-1 multipathd: uevent trigger error
<27>Nov 14 06:13:56 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 14 06:14:26 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:26 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:26 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:26 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:26 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:26 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:26 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:54 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:54 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:54 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:54 node-1 multipathd: uevent trigger error
<27>Nov 14 06:14:54 node-1 multipathd: uevent trigger error
<27>Nov 14 06:16:58 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 14 06:17:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:17:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:17:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:17:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:17:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:17:29 node-1 multipathd: uevent trigger error
<27>Nov 14 06:17:29 node-1 multipathd: uevent trigger error
<27>Nov 14 06:17:29 node-1 multipathd: uevent trigger error
<27>Nov 14 06:17:29 node-1 multipathd: uevent trigger error
<27>Nov 14 06:17:29 node-1 multipathd: uevent trigger error
<27>Nov 14 06:17:34 node-1 multipathd: uevent trigger error
<27>Nov 14 06:17:34 node-1 multipathd: uevent trigger error
<27>Nov 14 06:17:34 node-1 multipathd: uevent trigger error
<27>Nov 14 06:17:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:17:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:17:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:21 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:21 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:21 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:21 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:21 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:41 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:41 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:41 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:41 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:41 node-1 multipathd: uevent trigger error
<27>Nov 14 06:18:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:27 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:27 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:27 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:27 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:27 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:27 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:33 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Nov 14 06:19:33 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Nov 14 06:19:33 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Nov 14 06:19:34 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Nov 14 06:19:34 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Nov 14 06:19:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:19:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:20:00 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 14 06:20:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:20:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:20:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:20:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:20:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:20:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:20:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:20:20 node-1 multipathd: uevent trigger error
<27>Nov 14 06:20:20 node-1 multipathd: uevent trigger error
<27>Nov 14 06:20:20 node-1 multipathd: uevent trigger error
<27>Nov 14 06:20:20 node-1 multipathd: uevent trigger error
<27>Nov 14 06:20:20 node-1 multipathd: uevent trigger error
<27>Nov 14 06:20:20 node-1 multipathd: uevent trigger error
<27>Nov 14 06:22:37 node-1 multipathd: uevent trigger error
<27>Nov 14 06:22:37 node-1 multipathd: uevent trigger error
<27>Nov 14 06:22:37 node-1 multipathd: uevent trigger error
<27>Nov 14 06:22:37 node-1 multipathd: uevent trigger error
<27>Nov 14 06:22:37 node-1 multipathd: uevent trigger error
<27>Nov 14 06:22:49 node-1 multipathd: uevent trigger error
<27>Nov 14 06:22:49 node-1 multipathd: uevent trigger error
<27>Nov 14 06:22:49 node-1 multipathd: uevent trigger error
<27>Nov 14 06:23:01 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 14 06:23:02 node-1 multipathd: uevent trigger error
<27>Nov 14 06:23:02 node-1 multipathd: uevent trigger error
<27>Nov 14 06:23:02 node-1 multipathd: uevent trigger error
<27>Nov 14 06:23:02 node-1 multipathd: uevent trigger error
<27>Nov 14 06:23:02 node-1 multipathd: uevent trigger error
<27>Nov 14 06:23:02 node-1 multipathd: uevent trigger error
<27>Nov 14 06:23:02 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Nov 14 06:23:54 node-1 multipathd: uevent trigger error
<27>Nov 14 06:23:54 node-1 multipathd: uevent trigger error
<27>Nov 14 06:23:54 node-1 multipathd: uevent trigger error
<27>Nov 14 06:23:54 node-1 multipathd: uevent trigger error
<27>Nov 14 06:23:54 node-1 multipathd: uevent trigger error
<27>Nov 14 06:23:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:23:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:23:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:23:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:23:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:38 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:38 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:38 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:38 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:38 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:47 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:47 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:47 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:47 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:47 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:47 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:24:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:25:05 node-1 multipathd: uevent trigger error
<27>Nov 14 06:25:05 node-1 multipathd: uevent trigger error
<27>Nov 14 06:25:05 node-1 multipathd: uevent trigger error
<27>Nov 14 06:25:05 node-1 multipathd: uevent trigger error
<27>Nov 14 06:25:05 node-1 multipathd: uevent trigger error
<27>Nov 14 06:25:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:25:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:25:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:25:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:25:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:26:02 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 14 06:26:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:26:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:26:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:26:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:26:42 node-1 multipathd: uevent trigger error
<27>Nov 14 06:26:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:26:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:26:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:26:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:26:59 node-1 multipathd: uevent trigger error
<11>Nov 14 06:27:11 node-1 liberasurecode[77700]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:11 node-1 liberasurecode[77700]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:11 node-1 liberasurecode[77700]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:11 node-1 liberasurecode[77700]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:11 node-1 liberasurecode[77729]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:11 node-1 liberasurecode[77729]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:11 node-1 liberasurecode[77729]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:11 node-1 liberasurecode[77729]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:13 node-1 liberasurecode[78188]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:13 node-1 liberasurecode[78188]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:13 node-1 liberasurecode[78188]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:13 node-1 liberasurecode[78188]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:17 node-1 liberasurecode[78771]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:17 node-1 liberasurecode[78771]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:17 node-1 liberasurecode[78771]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:17 node-1 liberasurecode[78771]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:17 node-1 liberasurecode[78807]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:17 node-1 liberasurecode[78807]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:17 node-1 liberasurecode[78807]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:17 node-1 liberasurecode[78807]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78850]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78850]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78850]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78850]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78920]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78920]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78920]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78920]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78932]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78932]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78932]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78932]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78947]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78947]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78947]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78947]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78963]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78963]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78963]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:18 node-1 liberasurecode[78963]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:27 node-1 liberasurecode[81024]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:27 node-1 liberasurecode[81024]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:27 node-1 liberasurecode[81024]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:27:27 node-1 liberasurecode[81024]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov 14 06:27:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:27:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:27:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:27:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:27:35 node-1 multipathd: uevent trigger error
<27>Nov 14 06:27:35 node-1 multipathd: uevent trigger error
<43>Nov 14 06:28:24 node-1 apache2_error [Mon Nov 14 06:28:21.140854 2016] [mpm_worker:notice] [pid 30684:tid 140053462763392] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 14 06:28:24 node-1 apache2_error [Mon Nov 14 06:28:21.524230 2016] [mpm_worker:warn] [pid 30684:tid 140053462763392] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 14 06:28:24 node-1 apache2_error [Mon Nov 14 06:28:21.528834 2016] [mpm_worker:notice] [pid 30684:tid 140053462763392] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 14 06:28:24 node-1 apache2_error [Mon Nov 14 06:28:21.528856 2016] [core:notice] [pid 30684:tid 140053462763392] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 14 06:29:02 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:02 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:02 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:02 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:02 node-1 multipathd: uevent trigger error
<43>Nov 14 06:29:04 node-1 apache2_error [Mon Nov 14 06:28:58.246779 2016] [mpm_worker:notice] [pid 30684:tid 140053462763392] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 14 06:29:04 node-1 apache2_error [Mon Nov 14 06:28:58.440424 2016] [mpm_worker:warn] [pid 30684:tid 140053462763392] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 14 06:29:04 node-1 apache2_error [Mon Nov 14 06:28:58.446726 2016] [mpm_worker:notice] [pid 30684:tid 140053462763392] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 14 06:29:04 node-1 apache2_error [Mon Nov 14 06:28:58.446768 2016] [core:notice] [pid 30684:tid 140053462763392] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 14 06:29:04 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 14 06:29:10 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:10 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:10 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:10 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:10 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:48 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:48 node-1 multipathd: uevent trigger error
<43>Nov 14 06:29:54 node-1 apache2_error [Mon Nov 14 06:29:44.460203 2016] [mpm_worker:notice] [pid 30684:tid 140053462763392] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 14 06:29:54 node-1 apache2_error [Mon Nov 14 06:29:44.655457 2016] [mpm_worker:warn] [pid 30684:tid 140053462763392] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 14 06:29:54 node-1 apache2_error [Mon Nov 14 06:29:44.661837 2016] [mpm_worker:notice] [pid 30684:tid 140053462763392] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 14 06:29:54 node-1 apache2_error [Mon Nov 14 06:29:44.661861 2016] [core:notice] [pid 30684:tid 140053462763392] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 14 06:29:54 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:55 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:55 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:55 node-1 multipathd: uevent trigger error
<27>Nov 14 06:29:55 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:00 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:00 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:00 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:00 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:00 node-1 multipathd: uevent trigger error
<11>Nov 14 06:30:01 node-1 liberasurecode[108459]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:30:01 node-1 liberasurecode[108459]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:30:01 node-1 liberasurecode[108459]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:30:01 node-1 liberasurecode[108459]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov 14 06:30:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:23 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:23 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:23 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:23 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:23 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:23 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:43 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:49 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Nov 14 06:30:58 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:30:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:03 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:12 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:12 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:12 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:12 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:12 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:18 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:18 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:18 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:18 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:31 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:31 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:31 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:31 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:31 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:31 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:50 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:50 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:50 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:50 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:50 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:54 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:54 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:54 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:54 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:55 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:31:59 node-1 multipathd: uevent trigger error
<27>Nov 14 06:32:04 node-1 multipathd: uevent trigger error
<27>Nov 14 06:32:04 node-1 multipathd: uevent trigger error
<27>Nov 14 06:32:04 node-1 multipathd: uevent trigger error
<27>Nov 14 06:32:04 node-1 multipathd: uevent trigger error
<27>Nov 14 06:32:04 node-1 multipathd: uevent trigger error
<27>Nov 14 06:32:04 node-1 multipathd: uevent trigger error
<27>Nov 14 06:32:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:32:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:32:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:32:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:32:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:32:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:32:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:32:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:32:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:32:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:34:01 node-1 multipathd: uevent trigger error
<27>Nov 14 06:34:01 node-1 multipathd: uevent trigger error
<27>Nov 14 06:34:01 node-1 multipathd: uevent trigger error
<27>Nov 14 06:34:01 node-1 multipathd: uevent trigger error
<27>Nov 14 06:34:01 node-1 multipathd: uevent trigger error
<27>Nov 14 06:34:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:34:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:34:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:34:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:34:09 node-1 multipathd: uevent trigger error
<27>Nov 14 06:34:20 node-1 multipathd: uevent trigger error
<27>Nov 14 06:34:20 node-1 multipathd: uevent trigger error
<27>Nov 14 06:34:20 node-1 multipathd: uevent trigger error
<27>Nov 14 06:34:20 node-1 multipathd: uevent trigger error
<129>Nov 14 06:34:30 node-1 haproxy[158304]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 14 06:34:30 node-1 haproxy[158304]: 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>Nov 14 06:35:00 node-1 haproxy[158304]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 14 06:35:00 node-1 haproxy[158304]: proxy neutron has no server available!
<11>Nov 14 06:35:01 node-1 liberasurecode[167962]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:35:01 node-1 liberasurecode[167962]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:35:01 node-1 liberasurecode[167962]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 14 06:35:01 node-1 liberasurecode[167962]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov 14 06:35:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:14 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:15 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:20 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:20 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:20 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:20 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:20 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:24 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:24 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:24 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:24 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:25 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:25 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:25 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:36 node-1 multipathd: uevent trigger error
<27>Nov 14 06:35:36 node-1 multipathd: uevent trigger error
