Jul 27 11:19:02 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8371" x-info="http://www.rsyslog.com"] start
Jul 27 11:19:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 27 11:19:02 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 27 11:19:02 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 27 11:19:02 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 27 11:19:02 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 27 11:19:02 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 27 11:19:02 node-1 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 27 11:19:02 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=f41f2961-9461-4e69-95c6-09c4f4148bba nomdmonddf nomdmonisw
Jul 27 11:19:02 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 27 11:19:02 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 27 11:19:02 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 27 11:19:02 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 27 11:19:02 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 27 11:19:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 27 11:19:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 27 11:19:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 27 11:19:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Jul 27 11:19:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Jul 27 11:19:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Jul 27 11:19:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Jul 27 11:19:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Jul 27 11:19:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 27 11:19:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 27 11:19:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 27 11:19:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 27 11:19:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 27 11:19:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 27 11:19:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 27 11:19:02 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 27 11:19:02 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 27 11:19:02 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
Jul 27 11:19:02 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 27 11:19:02 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 27 11:19:02 node-1 kernel: [    0.000000] No AGP bridge found
Jul 27 11:19:02 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 27 11:19:02 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 27 11:19:02 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 27 11:19:02 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 27 11:19:02 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 27 11:19:02 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 27 11:19:02 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 27 11:19:02 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 27 11:19:02 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 27 11:19:02 node-1 kernel: [    0.000000]   2 disabled
Jul 27 11:19:02 node-1 kernel: [    0.000000]   3 disabled
Jul 27 11:19:02 node-1 kernel: [    0.000000]   4 disabled
Jul 27 11:19:02 node-1 kernel: [    0.000000]   5 disabled
Jul 27 11:19:02 node-1 kernel: [    0.000000]   6 disabled
Jul 27 11:19:02 node-1 kernel: [    0.000000]   7 disabled
Jul 27 11:19:02 node-1 kernel: [    0.000000]   8 disabled
Jul 27 11:19:02 node-1 kernel: [    0.000000]   9 disabled
Jul 27 11:19:02 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 27 11:19:02 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 27 11:19:02 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 27 11:19:02 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 27 11:19:02 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 27 11:19:02 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 27 11:19:02 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 27 11:19:02 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 27 11:19:02 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 27 11:19:02 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 27 11:19:02 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 27 11:19:02 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 27 11:19:02 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 27 11:19:02 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 27 11:19:02 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 27 11:19:02 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Jul 27 11:19:02 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 27 11:19:02 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 27 11:19:02 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 27 11:19:02 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 27 11:19:02 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 27 11:19:02 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 27 11:19:02 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 27 11:19:02 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 27 11:19:02 node-1 kernel: [    0.000000] Zone ranges:
Jul 27 11:19:02 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 27 11:19:02 node-1 kernel: [    0.000000] Early memory node ranges
Jul 27 11:19:02 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Jul 27 11:19:02 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 27 11:19:02 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 27 11:19:02 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 27 11:19:02 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Jul 27 11:19:02 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Jul 27 11:19:02 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 27 11:19:02 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 27 11:19:02 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 27 11:19:02 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 27 11:19:02 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 27 11:19:02 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 27 11:19:02 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 27 11:19:02 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 27 11:19:02 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 27 11:19:02 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 27 11:19:02 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 27 11:19:02 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 27 11:19:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 27 11:19:02 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 27 11:19:02 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 27 11:19:02 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 27 11:19:02 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 27 11:19:02 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 27 11:19:02 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 
Jul 27 11:19:02 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Jul 27 11:19:02 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 27 11:19:02 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=f41f2961-9461-4e69-95c6-09c4f4148bba nomdmonddf nomdmonisw
Jul 27 11:19:02 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 27 11:19:02 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 27 11:19:02 node-1 kernel: [    0.000000] Checking aperture...
Jul 27 11:19:02 node-1 kernel: [    0.000000] No AGP bridge found
Jul 27 11:19:02 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 27 11:19:02 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 27 11:19:02 node-1 kernel: [    0.000000] Memory: 32653456K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 27 11:19:02 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 27 11:19:02 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 27 11:19:02 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 27 11:19:02 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 27 11:19:02 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 27 11:19:02 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 27 11:19:02 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 27 11:19:02 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 27 11:19:02 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 27 11:19:02 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 27 11:19:02 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 27 11:19:02 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 27 11:19:02 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 27 11:19:02 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 27 11:19:02 node-1 kernel: [    0.004000] tsc: Detected 3492.112 MHz processor
Jul 27 11:19:02 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.22 BogoMIPS (lpj=13968448)
Jul 27 11:19:02 node-1 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Jul 27 11:19:02 node-1 kernel: [    0.000042] Security Framework initialized
Jul 27 11:19:02 node-1 kernel: [    0.000061] AppArmor: AppArmor initialized
Jul 27 11:19:02 node-1 kernel: [    0.000062] Yama: becoming mindful.
Jul 27 11:19:02 node-1 kernel: [    0.001461] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 27 11:19:02 node-1 kernel: [    0.006388] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 27 11:19:02 node-1 kernel: [    0.008315] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 27 11:19:02 node-1 kernel: [    0.008343] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 27 11:19:02 node-1 kernel: [    0.008635] Initializing cgroup subsys memory
Jul 27 11:19:02 node-1 kernel: [    0.008642] Initializing cgroup subsys devices
Jul 27 11:19:02 node-1 kernel: [    0.008644] Initializing cgroup subsys freezer
Jul 27 11:19:02 node-1 kernel: [    0.008646] Initializing cgroup subsys blkio
Jul 27 11:19:02 node-1 kernel: [    0.008647] Initializing cgroup subsys perf_event
Jul 27 11:19:02 node-1 kernel: [    0.008649] Initializing cgroup subsys hugetlb
Jul 27 11:19:02 node-1 kernel: [    0.008669] CPU: Physical Processor ID: 0
Jul 27 11:19:02 node-1 kernel: [    0.008670] CPU: Processor Core ID: 0
Jul 27 11:19:02 node-1 kernel: [    0.008674] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 27 11:19:02 node-1 kernel: [    0.008674] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 27 11:19:02 node-1 kernel: [    0.009368] mce: CPU supports 22 MCE banks
Jul 27 11:19:02 node-1 kernel: [    0.009395] CPU0: Thermal monitoring enabled (TM1)
Jul 27 11:19:02 node-1 kernel: [    0.009416] process: using mwait in idle threads
Jul 27 11:19:02 node-1 kernel: [    0.009419] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 27 11:19:02 node-1 kernel: [    0.009419] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 27 11:19:02 node-1 kernel: [    0.009419] tlb_flushall_shift: 6
Jul 27 11:19:02 node-1 kernel: [    0.009509] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 27 11:19:02 node-1 kernel: [    0.010235] ACPI: Core revision 20131115
Jul 27 11:19:02 node-1 kernel: [    0.022929] ACPI: All ACPI Tables successfully acquired
Jul 27 11:19:02 node-1 kernel: [    0.023093] ftrace: allocating 28617 entries in 112 pages
Jul 27 11:19:02 node-1 kernel: [    0.031880] dmar: Host address width 46
Jul 27 11:19:02 node-1 kernel: [    0.031883] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 27 11:19:02 node-1 kernel: [    0.031888] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 27 11:19:02 node-1 kernel: [    0.031890] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 27 11:19:02 node-1 kernel: [    0.031894] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 27 11:19:02 node-1 kernel: [    0.031896] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 27 11:19:02 node-1 kernel: [    0.031897] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 27 11:19:02 node-1 kernel: [    0.031898] dmar: ATSR flags: 0x0
Jul 27 11:19:02 node-1 kernel: [    0.031899] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 27 11:19:02 node-1 kernel: [    0.031900] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 27 11:19:02 node-1 kernel: [    0.032015] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 27 11:19:02 node-1 kernel: [    0.032017] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 27 11:19:02 node-1 kernel: [    0.032018] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 27 11:19:02 node-1 kernel: [    0.032019] HPET id 0 under DRHD base 0xc7ffc000
Jul 27 11:19:02 node-1 kernel: [    0.032020] Your BIOS is broken and requested that x2apic be disabled.
Jul 27 11:19:02 node-1 kernel: [    0.032020] This will slightly decrease performance.
Jul 27 11:19:02 node-1 kernel: [    0.032020] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 27 11:19:02 node-1 kernel: [    0.032451] Enabled IRQ remapping in xapic mode
Jul 27 11:19:02 node-1 kernel: [    0.032453] x2apic not enabled, IRQ remapping is in xapic mode
Jul 27 11:19:02 node-1 kernel: [    0.032456] Switched APIC routing to physical flat.
Jul 27 11:19:02 node-1 kernel: [    0.033034] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 27 11:19:02 node-1 kernel: [    0.072686] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 27 11:19:02 node-1 kernel: [    0.072692] TSC deadline timer enabled
Jul 27 11:19:02 node-1 kernel: [    0.072699] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 27 11:19:02 node-1 kernel: [    0.072706] ... version:                3
Jul 27 11:19:02 node-1 kernel: [    0.072707] ... bit width:              48
Jul 27 11:19:02 node-1 kernel: [    0.072708] ... generic registers:      4
Jul 27 11:19:02 node-1 kernel: [    0.072709] ... value mask:             0000ffffffffffff
Jul 27 11:19:02 node-1 kernel: [    0.072710] ... max period:             0000ffffffffffff
Jul 27 11:19:02 node-1 kernel: [    0.072711] ... fixed-purpose events:   3
Jul 27 11:19:02 node-1 kernel: [    0.072711] ... event mask:             000000070000000f
Jul 27 11:19:02 node-1 kernel: [    0.074140] x86: Booting SMP configuration:
Jul 27 11:19:02 node-1 kernel: [    0.088244] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 27 11:19:02 node-1 kernel: [    0.074142] .... node  #0, CPUs:        #1  #2  #3
Jul 27 11:19:02 node-1 kernel: [    0.116155] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 27 11:19:02 node-1 kernel: [    0.270308] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 27 11:19:02 node-1 kernel: [    0.325946] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 27 11:19:02 node-1 kernel: [    0.383008] x86: Booted up 2 nodes, 16 CPUs
Jul 27 11:19:02 node-1 kernel: [    0.383012] smpboot: Total of 16 processors activated (111759.50 BogoMIPS)
Jul 27 11:19:02 node-1 kernel: [    0.407572] devtmpfs: initialized
Jul 27 11:19:02 node-1 kernel: [    0.410684] EVM: security.selinux
Jul 27 11:19:02 node-1 kernel: [    0.410685] EVM: security.SMACK64
Jul 27 11:19:02 node-1 kernel: [    0.410686] EVM: security.ima
Jul 27 11:19:02 node-1 kernel: [    0.410687] EVM: security.capability
Jul 27 11:19:02 node-1 kernel: [    0.410737] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Jul 27 11:19:02 node-1 kernel: [    0.411415] pinctrl core: initialized pinctrl subsystem
Jul 27 11:19:02 node-1 kernel: [    0.411477] regulator-dummy: no parameters
Jul 27 11:19:02 node-1 kernel: [    0.411509] RTC time: 11:18:26, date: 07/27/16
Jul 27 11:19:02 node-1 kernel: [    0.411544] NET: Registered protocol family 16
Jul 27 11:19:02 node-1 kernel: [    0.411628] cpuidle: using governor ladder
Jul 27 11:19:02 node-1 kernel: [    0.411630] cpuidle: using governor menu
Jul 27 11:19:02 node-1 kernel: [    0.411664] ACPI: bus type PCI registered
Jul 27 11:19:02 node-1 kernel: [    0.411666] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 27 11:19:02 node-1 kernel: [    0.411713] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 27 11:19:02 node-1 kernel: [    0.411716] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 27 11:19:02 node-1 kernel: [    0.425460] PCI: Using configuration type 1 for base access
Jul 27 11:19:02 node-1 kernel: [    0.426462] bio: create slab <bio-0> at 0
Jul 27 11:19:02 node-1 kernel: [    0.426746] ACPI: Added _OSI(Module Device)
Jul 27 11:19:02 node-1 kernel: [    0.426747] ACPI: Added _OSI(Processor Device)
Jul 27 11:19:02 node-1 kernel: [    0.426748] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 27 11:19:02 node-1 kernel: [    0.426749] ACPI: Added _OSI(Processor Aggregator Device)
Jul 27 11:19:02 node-1 kernel: [    0.439449] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 27 11:19:02 node-1 kernel: [    0.450176] ACPI: Interpreter enabled
Jul 27 11:19:02 node-1 kernel: [    0.450181] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 27 11:19:02 node-1 kernel: [    0.450185] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 27 11:19:02 node-1 kernel: [    0.450188] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 27 11:19:02 node-1 kernel: [    0.450195] ACPI: (supports S0 S4 S5)
Jul 27 11:19:02 node-1 kernel: [    0.450196] ACPI: Using IOAPIC for interrupt routing
Jul 27 11:19:02 node-1 kernel: [    0.450239] HEST: Table parsing has been initialized.
Jul 27 11:19:02 node-1 kernel: [    0.450242] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 27 11:19:02 node-1 kernel: [    0.450796] ACPI: No dock devices found.
Jul 27 11:19:02 node-1 kernel: [    0.462426] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 27 11:19:02 node-1 kernel: [    0.462430] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 11:19:02 node-1 kernel: [    0.462434] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 27 11:19:02 node-1 kernel: [    0.462460] PCI host bridge to bus 0000:ff
Jul 27 11:19:02 node-1 kernel: [    0.462462] pci_bus 0000:ff: root bus resource [bus ff]
Jul 27 11:19:02 node-1 kernel: [    0.462470] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.462508] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 27 11:19:02 node-1 kernel: [    0.462539] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.462573] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.462602] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 27 11:19:02 node-1 kernel: [    0.462631] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 27 11:19:02 node-1 kernel: [    0.462662] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.462691] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.462720] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.462748] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.462775] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.462801] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.462829] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.462855] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.462882] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.462909] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.462938] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.462965] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.462992] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 27 11:19:02 node-1 kernel: [    0.463022] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463048] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 27 11:19:02 node-1 kernel: [    0.463073] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463099] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463130] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 27 11:19:02 node-1 kernel: [    0.463165] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463196] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463226] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463257] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463287] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463318] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463349] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463381] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463411] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463444] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463476] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463509] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463542] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463572] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463600] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463632] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463665] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463701] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463736] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463768] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463798] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463829] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463859] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463888] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463918] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463949] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.463980] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464009] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464038] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464069] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464098] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464128] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464159] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464216] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 27 11:19:02 node-1 kernel: [    0.464219] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 11:19:02 node-1 kernel: [    0.464221] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 27 11:19:02 node-1 kernel: [    0.464243] PCI host bridge to bus 0000:7f
Jul 27 11:19:02 node-1 kernel: [    0.464244] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 27 11:19:02 node-1 kernel: [    0.464249] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464277] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 27 11:19:02 node-1 kernel: [    0.464305] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464333] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464355] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 27 11:19:02 node-1 kernel: [    0.464379] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 27 11:19:02 node-1 kernel: [    0.464405] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464430] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464453] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464475] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464497] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464519] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464548] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464572] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464596] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464622] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464644] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464667] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464690] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 27 11:19:02 node-1 kernel: [    0.464714] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464736] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 27 11:19:02 node-1 kernel: [    0.464758] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464780] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464807] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 27 11:19:02 node-1 kernel: [    0.464841] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464867] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464893] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464920] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464945] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.464973] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465001] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465031] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465056] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465082] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465110] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465138] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465167] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465192] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465217] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465245] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465270] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465297] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465325] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465354] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465380] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465410] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465437] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465466] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465494] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465521] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465551] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465577] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465600] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465626] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465652] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465682] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.465709] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.466967] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 27 11:19:02 node-1 kernel: [    0.466970] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 11:19:02 node-1 kernel: [    0.468088] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 27 11:19:02 node-1 kernel: [    0.468601] PCI host bridge to bus 0000:00
Jul 27 11:19:02 node-1 kernel: [    0.468604] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 27 11:19:02 node-1 kernel: [    0.468605] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 27 11:19:02 node-1 kernel: [    0.468606] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 27 11:19:02 node-1 kernel: [    0.468608] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 27 11:19:02 node-1 kernel: [    0.468609] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 27 11:19:02 node-1 kernel: [    0.468611] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 27 11:19:02 node-1 kernel: [    0.468612] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 27 11:19:02 node-1 kernel: [    0.468618] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 27 11:19:02 node-1 kernel: [    0.468700] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 27 11:19:02 node-1 kernel: [    0.468731] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 27 11:19:02 node-1 kernel: [    0.468773] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 27 11:19:02 node-1 kernel: [    0.468792] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 27 11:19:02 node-1 kernel: [    0.468822] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 27 11:19:02 node-1 kernel: [    0.468861] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 27 11:19:02 node-1 kernel: [    0.468881] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 27 11:19:02 node-1 kernel: [    0.468910] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 27 11:19:02 node-1 kernel: [    0.468950] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 27 11:19:02 node-1 kernel: [    0.468968] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.469038] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.469115] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.469193] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 27 11:19:02 node-1 kernel: [    0.469198] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 27 11:19:02 node-1 kernel: [    0.469282] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 27 11:19:02 node-1 kernel: [    0.469427] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 27 11:19:02 node-1 kernel: [    0.469444] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 27 11:19:02 node-1 kernel: [    0.469522] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 27 11:19:02 node-1 kernel: [    0.469576] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 27 11:19:02 node-1 kernel: [    0.469598] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 27 11:19:02 node-1 kernel: [    0.469653] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 27 11:19:02 node-1 kernel: [    0.469697] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 27 11:19:02 node-1 kernel: [    0.469723] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 27 11:19:02 node-1 kernel: [    0.469778] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 27 11:19:02 node-1 kernel: [    0.469821] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 27 11:19:02 node-1 kernel: [    0.469845] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 27 11:19:02 node-1 kernel: [    0.469863] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 27 11:19:02 node-1 kernel: [    0.469940] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 27 11:19:02 node-1 kernel: [    0.469989] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 27 11:19:02 node-1 kernel: [    0.470015] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 27 11:19:02 node-1 kernel: [    0.470261] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 27 11:19:02 node-1 kernel: [    0.470267] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 27 11:19:02 node-1 kernel: [    0.470273] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 27 11:19:02 node-1 kernel: [    0.470279] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 27 11:19:02 node-1 kernel: [    0.470286] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 27 11:19:02 node-1 kernel: [    0.470316] pci 0000:01:00.0: supports D1 D2
Jul 27 11:19:02 node-1 kernel: [    0.476258] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 27 11:19:02 node-1 kernel: [    0.476264] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 27 11:19:02 node-1 kernel: [    0.476268] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 27 11:19:02 node-1 kernel: [    0.476529] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 27 11:19:02 node-1 kernel: [    0.476590] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 27 11:19:02 node-1 kernel: [    0.484255] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 27 11:19:02 node-1 kernel: [    0.484261] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 27 11:19:02 node-1 kernel: [    0.484265] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 11:19:02 node-1 kernel: [    0.484356] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 27 11:19:02 node-1 kernel: [    0.484424] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 27 11:19:02 node-1 kernel: [    0.484501] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 27 11:19:02 node-1 kernel: [    0.484545] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 27 11:19:02 node-1 kernel: [    0.484548] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 11:19:02 node-1 kernel: [    0.484550] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 11:19:02 node-1 kernel: [    0.484615] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 27 11:19:02 node-1 kernel: [    0.484738] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 27 11:19:02 node-1 kernel: [    0.484795] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 27 11:19:02 node-1 kernel: [    0.484798] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 11:19:02 node-1 kernel: [    0.484800] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 11:19:02 node-1 kernel: [    0.484849] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 27 11:19:02 node-1 kernel: [    0.484968] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 27 11:19:02 node-1 kernel: [    0.485008] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 27 11:19:02 node-1 kernel: [    0.485127] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 27 11:19:02 node-1 kernel: [    0.485165] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 27 11:19:02 node-1 kernel: [    0.485286] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 27 11:19:02 node-1 kernel: [    0.485324] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 27 11:19:02 node-1 kernel: [    0.485442] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 27 11:19:02 node-1 kernel: [    0.485485] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 27 11:19:02 node-1 kernel: [    0.485487] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 11:19:02 node-1 kernel: [    0.485489] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 11:19:02 node-1 kernel: [    0.485549] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 27 11:19:02 node-1 kernel: [    0.485631] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 27 11:19:02 node-1 kernel: [    0.485684] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 27 11:19:02 node-1 kernel: [    0.485724] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 27 11:19:02 node-1 kernel: [    0.485807] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 27 11:19:02 node-1 kernel: [    0.485914] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 27 11:19:02 node-1 kernel: [    0.485916] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 11:19:02 node-1 kernel: [    0.485918] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 27 11:19:02 node-1 kernel: [    0.485974] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 27 11:19:02 node-1 kernel: [    0.486028] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 27 11:19:02 node-1 kernel: [    0.486077] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 27 11:19:02 node-1 kernel: [    0.486289] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 27 11:19:02 node-1 kernel: [    0.486292] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 27 11:19:02 node-1 kernel: [    0.486355] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 27 11:19:02 node-1 kernel: [    0.486408] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 27 11:19:02 node-1 kernel: [    0.486457] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 27 11:19:02 node-1 kernel: [    0.486687] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 27 11:19:02 node-1 kernel: [    0.486691] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 27 11:19:02 node-1 kernel: [    0.486749] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 27 11:19:02 node-1 kernel: [    0.486812] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 27 11:19:02 node-1 kernel: [    0.486868] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 27 11:19:02 node-1 kernel: [    0.487088] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 27 11:19:02 node-1 kernel: [    0.487092] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 27 11:19:02 node-1 kernel: [    0.487265] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 27 11:19:02 node-1 kernel: [    0.487303] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 27 11:19:02 node-1 kernel: [    0.487379] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 27 11:19:02 node-1 kernel: [    0.487398] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 27 11:19:02 node-1 kernel: [    0.487411] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 27 11:19:02 node-1 kernel: [    0.487425] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 27 11:19:02 node-1 kernel: [    0.487474] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 27 11:19:02 node-1 kernel: [    0.492262] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 27 11:19:02 node-1 kernel: [    0.492271] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 27 11:19:02 node-1 kernel: [    0.492323] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 27 11:19:02 node-1 kernel: [    0.492975] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 27 11:19:02 node-1 kernel: [    0.492978] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 11:19:02 node-1 kernel: [    0.493098] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 27 11:19:02 node-1 kernel: [    0.493204] PCI host bridge to bus 0000:80
Jul 27 11:19:02 node-1 kernel: [    0.493206] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 27 11:19:02 node-1 kernel: [    0.493207] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 27 11:19:02 node-1 kernel: [    0.493209] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 27 11:19:02 node-1 kernel: [    0.493217] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.493279] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.493346] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 27 11:19:02 node-1 kernel: [    0.493407] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 27 11:19:02 node-1 kernel: [    0.493412] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 27 11:19:02 node-1 kernel: [    0.493482] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 27 11:19:02 node-1 kernel: [    0.493779] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 27 11:19:02 node-1 kernel: [    0.493810] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 27 11:19:02 node-1 kernel: [    0.493840] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 27 11:19:02 node-1 kernel: [    0.493869] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 27 11:19:02 node-1 kernel: [    0.493898] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 11:19:02 node-1 kernel: [    0.493927] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 11:19:02 node-1 kernel: [    0.493957] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 11:19:02 node-1 kernel: [    0.493986] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 11:19:02 node-1 kernel: [    0.494070] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 27 11:19:02 node-1 kernel: [    0.494074] ACPI: \_SB_.UNC1: notify handler is installed
Jul 27 11:19:02 node-1 kernel: [    0.494076] ACPI: \_SB_.UNC0: notify handler is installed
Jul 27 11:19:02 node-1 kernel: [    0.494090] ACPI: \_SB_.PCI0: notify handler is installed
Jul 27 11:19:02 node-1 kernel: [    0.494143] ACPI: \_SB_.PCI1: notify handler is installed
Jul 27 11:19:02 node-1 kernel: [    0.494222] Found 4 acpi root devices
Jul 27 11:19:02 node-1 kernel: [    0.494328] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 27 11:19:02 node-1 kernel: [    0.494330] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 27 11:19:02 node-1 kernel: [    0.494332] vgaarb: loaded
Jul 27 11:19:02 node-1 kernel: [    0.494333] vgaarb: bridge control possible 0000:0c:00.0
Jul 27 11:19:02 node-1 kernel: [    0.494449] SCSI subsystem initialized
Jul 27 11:19:02 node-1 kernel: [    0.494515] libata version 3.00 loaded.
Jul 27 11:19:02 node-1 kernel: [    0.494535] ACPI: bus type USB registered
Jul 27 11:19:02 node-1 kernel: [    0.494545] usbcore: registered new interface driver usbfs
Jul 27 11:19:02 node-1 kernel: [    0.494550] usbcore: registered new interface driver hub
Jul 27 11:19:02 node-1 kernel: [    0.494570] usbcore: registered new device driver usb
Jul 27 11:19:02 node-1 kernel: [    0.494726] PCI: Using ACPI for IRQ routing
Jul 27 11:19:02 node-1 kernel: [    0.498328] PCI: pci_cache_line_size set to 64 bytes
Jul 27 11:19:02 node-1 kernel: [    0.498538] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 27 11:19:02 node-1 kernel: [    0.498539] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Jul 27 11:19:02 node-1 kernel: [    0.498540] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 27 11:19:02 node-1 kernel: [    0.498604] NetLabel: Initializing
Jul 27 11:19:02 node-1 kernel: [    0.498606] NetLabel:  domain hash size = 128
Jul 27 11:19:02 node-1 kernel: [    0.498607] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 27 11:19:02 node-1 kernel: [    0.498616] NetLabel:  unlabeled traffic allowed by default
Jul 27 11:19:02 node-1 kernel: [    0.498671] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 27 11:19:02 node-1 kernel: [    0.498676] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 27 11:19:02 node-1 kernel: [    0.500732] Switched to clocksource hpet
Jul 27 11:19:02 node-1 kernel: [    0.504617] AppArmor: AppArmor Filesystem Enabled
Jul 27 11:19:02 node-1 kernel: [    0.504632] pnp: PnP ACPI init
Jul 27 11:19:02 node-1 kernel: [    0.504638] ACPI: bus type PNP registered
Jul 27 11:19:02 node-1 kernel: [    0.504761] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 27 11:19:02 node-1 kernel: [    0.504769] pnp 00:01: [dma 4]
Jul 27 11:19:02 node-1 kernel: [    0.504780] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 27 11:19:02 node-1 kernel: [    0.504807] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 27 11:19:02 node-1 kernel: [    0.504826] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 27 11:19:02 node-1 kernel: [    0.504844] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 27 11:19:02 node-1 kernel: [    0.504876] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 27 11:19:02 node-1 kernel: [    0.504928] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 27 11:19:02 node-1 kernel: [    0.504930] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 27 11:19:02 node-1 kernel: [    0.504932] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 27 11:19:02 node-1 kernel: [    0.504933] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 27 11:19:02 node-1 kernel: [    0.504935] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 27 11:19:02 node-1 kernel: [    0.504940] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 27 11:19:02 node-1 kernel: [    0.504942] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 27 11:19:02 node-1 kernel: [    0.504943] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 27 11:19:02 node-1 kernel: [    0.504945] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 27 11:19:02 node-1 kernel: [    0.504947] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 27 11:19:02 node-1 kernel: [    0.504948] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 27 11:19:02 node-1 kernel: [    0.504950] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 27 11:19:02 node-1 kernel: [    0.504951] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 27 11:19:02 node-1 kernel: [    0.504953] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 27 11:19:02 node-1 kernel: [    0.505036] pnp 00:07: [dma 0 disabled]
Jul 27 11:19:02 node-1 kernel: [    0.505064] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 27 11:19:02 node-1 kernel: [    0.505138] pnp 00:08: [dma 0 disabled]
Jul 27 11:19:02 node-1 kernel: [    0.505170] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 27 11:19:02 node-1 kernel: [    0.505221] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 27 11:19:02 node-1 kernel: [    0.505564] pnp: PnP ACPI: found 10 devices
Jul 27 11:19:02 node-1 kernel: [    0.505565] ACPI: bus type PNP unregistered
Jul 27 11:19:02 node-1 kernel: [    0.511825] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 27 11:19:02 node-1 kernel: [    0.511828] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 27 11:19:02 node-1 kernel: [    0.511831] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 27 11:19:02 node-1 kernel: [    0.511835] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 27 11:19:02 node-1 kernel: [    0.511837] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 11:19:02 node-1 kernel: [    0.511852] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 27 11:19:02 node-1 kernel: [    0.511880] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 27 11:19:02 node-1 kernel: [    0.511895] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 27 11:19:02 node-1 kernel: [    0.511924] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 27 11:19:02 node-1 kernel: [    0.511938] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 27 11:19:02 node-1 kernel: [    0.511970] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 27 11:19:02 node-1 kernel: [    0.511985] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 27 11:19:02 node-1 kernel: [    0.512013] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 27 11:19:02 node-1 kernel: [    0.512015] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 11:19:02 node-1 kernel: [    0.512030] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 11:19:02 node-1 kernel: [    0.512059] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 27 11:19:02 node-1 kernel: [    0.512061] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 11:19:02 node-1 kernel: [    0.512075] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 11:19:02 node-1 kernel: [    0.512104] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 27 11:19:02 node-1 kernel: [    0.512105] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 11:19:02 node-1 kernel: [    0.512108] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 11:19:02 node-1 kernel: [    0.512112] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 27 11:19:02 node-1 kernel: [    0.512114] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 27 11:19:02 node-1 kernel: [    0.512116] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 11:19:02 node-1 kernel: [    0.512120] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 27 11:19:02 node-1 kernel: [    0.512125] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 27 11:19:02 node-1 kernel: [    0.512133] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 27 11:19:02 node-1 kernel: [    0.512136] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 27 11:19:02 node-1 kernel: [    0.512142] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 27 11:19:02 node-1 kernel: [    0.512143] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 27 11:19:02 node-1 kernel: [    0.512144] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 27 11:19:02 node-1 kernel: [    0.512145] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 27 11:19:02 node-1 kernel: [    0.512146] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 27 11:19:02 node-1 kernel: [    0.512147] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 27 11:19:02 node-1 kernel: [    0.512148] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 27 11:19:02 node-1 kernel: [    0.512149] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 27 11:19:02 node-1 kernel: [    0.512149] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 27 11:19:02 node-1 kernel: [    0.512150] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 27 11:19:02 node-1 kernel: [    0.512151] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 27 11:19:02 node-1 kernel: [    0.512152] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 27 11:19:02 node-1 kernel: [    0.512153] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 27 11:19:02 node-1 kernel: [    0.512154] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 27 11:19:02 node-1 kernel: [    0.512155] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 27 11:19:02 node-1 kernel: [    0.512155] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 27 11:19:02 node-1 kernel: [    0.512156] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 27 11:19:02 node-1 kernel: [    0.512157] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 27 11:19:02 node-1 kernel: [    0.512158] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 27 11:19:02 node-1 kernel: [    0.512159] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 27 11:19:02 node-1 kernel: [    0.512160] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 27 11:19:02 node-1 kernel: [    0.512161] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 27 11:19:02 node-1 kernel: [    0.512163] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 27 11:19:02 node-1 kernel: [    0.512164] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 27 11:19:02 node-1 kernel: [    0.512203] NET: Registered protocol family 2
Jul 27 11:19:02 node-1 kernel: [    0.512473] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 27 11:19:02 node-1 kernel: [    0.512809] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 27 11:19:02 node-1 kernel: [    0.512953] TCP: Hash tables configured (established 262144 bind 65536)
Jul 27 11:19:02 node-1 kernel: [    0.512996] TCP: reno registered
Jul 27 11:19:02 node-1 kernel: [    0.513026] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 27 11:19:02 node-1 kernel: [    0.513119] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 27 11:19:02 node-1 kernel: [    0.513263] NET: Registered protocol family 1
Jul 27 11:19:02 node-1 kernel: [    0.552828] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 27 11:19:02 node-1 kernel: [    0.552841] PCI: CLS 64 bytes, default 64
Jul 27 11:19:02 node-1 kernel: [    0.552917] Trying to unpack rootfs image as initramfs...
Jul 27 11:19:02 node-1 kernel: [    0.772112] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 27 11:19:02 node-1 kernel: [    0.772156] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 27 11:19:02 node-1 kernel: [    0.772158] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Jul 27 11:19:02 node-1 kernel: [    0.772594] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 11:19:02 node-1 kernel: [    0.772601] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 11:19:02 node-1 kernel: [    0.772605] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 11:19:02 node-1 kernel: [    0.772611] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 11:19:02 node-1 kernel: [    0.772623] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 11:19:02 node-1 kernel: [    0.772640] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 11:19:02 node-1 kernel: [    0.772656] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 11:19:02 node-1 kernel: [    0.772671] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 11:19:02 node-1 kernel: [    0.772696] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 11:19:02 node-1 kernel: [    0.772705] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 11:19:02 node-1 kernel: [    0.772711] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 11:19:02 node-1 kernel: [    0.772717] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 11:19:02 node-1 kernel: [    0.772724] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 11:19:02 node-1 kernel: [    0.772733] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 11:19:02 node-1 kernel: [    0.772740] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 11:19:02 node-1 kernel: [    0.772747] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 11:19:02 node-1 kernel: [    0.772822] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 27 11:19:02 node-1 kernel: [    0.772825] Scanning for low memory corruption every 60 seconds
Jul 27 11:19:02 node-1 kernel: [    0.773207] Initialise system trusted keyring
Jul 27 11:19:02 node-1 kernel: [    0.773260] audit: initializing netlink socket (disabled)
Jul 27 11:19:02 node-1 kernel: [    0.773276] type=2000 audit(1469618306.728:1): initialized
Jul 27 11:19:02 node-1 kernel: [    0.791206] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 27 11:19:02 node-1 kernel: [    0.792735] zbud: loaded
Jul 27 11:19:02 node-1 kernel: [    0.792861] VFS: Disk quotas dquot_6.5.2
Jul 27 11:19:02 node-1 kernel: [    0.792897] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 27 11:19:02 node-1 kernel: [    0.793279] fuse init (API version 7.22)
Jul 27 11:19:02 node-1 kernel: [    0.793337] msgmni has been set to 32768
Jul 27 11:19:02 node-1 kernel: [    0.793388] Key type big_key registered
Jul 27 11:19:02 node-1 kernel: [    0.793933] Key type asymmetric registered
Jul 27 11:19:02 node-1 kernel: [    0.793935] Asymmetric key parser 'x509' registered
Jul 27 11:19:02 node-1 kernel: [    0.793957] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 27 11:19:02 node-1 kernel: [    0.794026] io scheduler noop registered
Jul 27 11:19:02 node-1 kernel: [    0.794028] io scheduler deadline registered (default)
Jul 27 11:19:02 node-1 kernel: [    0.794048] io scheduler cfq registered
Jul 27 11:19:02 node-1 kernel: [    0.794576] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    0.794760] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    0.794872] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    0.795004] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    0.795114] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    0.795206] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    0.795600] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 27 11:19:02 node-1 kernel: [    0.795625] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 27 11:19:02 node-1 kernel: [    0.795642] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 27 11:19:02 node-1 kernel: [    0.795659] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795661] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795664] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 27 11:19:02 node-1 kernel: [    0.795669] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795671] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795672] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795674] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795675] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795677] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795678] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795680] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795681] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795682] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795684] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795685] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795688] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 27 11:19:02 node-1 kernel: [    0.795693] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795695] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 27 11:19:02 node-1 kernel: [    0.795708] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795711] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 27 11:19:02 node-1 kernel: [    0.795721] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795722] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 27 11:19:02 node-1 kernel: [    0.795725] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 27 11:19:02 node-1 kernel: [    0.795763] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 27 11:19:02 node-1 kernel: [    0.795770] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 27 11:19:02 node-1 kernel: [    0.795774] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 27 11:19:02 node-1 kernel: [    0.795784] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 27 11:19:02 node-1 kernel: [    0.795825] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 27 11:19:02 node-1 kernel: [    0.795826] vesafb: scrolling: redraw
Jul 27 11:19:02 node-1 kernel: [    0.795828] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 27 11:19:02 node-1 kernel: [    0.816574] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 27 11:19:02 node-1 kernel: [    0.825087] Console: switching to colour frame buffer device 80x30
Jul 27 11:19:02 node-1 kernel: [    0.833763] fb0: VESA VGA frame buffer device
Jul 27 11:19:02 node-1 kernel: [    0.833961] intel_idle: MWAIT substates: 0x2120
Jul 27 11:19:02 node-1 kernel: [    0.833962] intel_idle: v0.4 model 0x3F
Jul 27 11:19:02 node-1 kernel: [    0.833962] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 27 11:19:02 node-1 kernel: [    0.834190] ipmi message handler version 39.2
Jul 27 11:19:02 node-1 kernel: [    0.834461] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 27 11:19:02 node-1 kernel: [    0.834895] ACPI: AC Adapter [P111] (on-line)
Jul 27 11:19:02 node-1 kernel: [    0.840132] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 27 11:19:02 node-1 kernel: [    0.851143] ACPI: Power Button [PWRB]
Jul 27 11:19:02 node-1 kernel: [    0.856904] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 27 11:19:02 node-1 kernel: [    0.868549] ACPI: Power Button [PWRF]
Jul 27 11:19:02 node-1 kernel: [    0.886240] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 27 11:19:02 node-1 kernel: [    0.897912] pstore: Registered erst as persistent store backend
Jul 27 11:19:02 node-1 kernel: [    0.904205] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 27 11:19:02 node-1 kernel: [    0.916142] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 27 11:19:02 node-1 kernel: [    0.942876] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 27 11:19:02 node-1 kernel: [    0.976129] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 27 11:19:02 node-1 kernel: [    0.990325] Linux agpgart interface v0.103
Jul 27 11:19:02 node-1 kernel: [    0.998029] brd: module loaded
Jul 27 11:19:02 node-1 kernel: [    1.005100] loop: module loaded
Jul 27 11:19:02 node-1 kernel: [    1.011887] libphy: Fixed MDIO Bus: probed
Jul 27 11:19:02 node-1 kernel: [    1.018451] tun: Universal TUN/TAP device driver, 1.6
Jul 27 11:19:02 node-1 kernel: [    1.025007] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 27 11:19:02 node-1 kernel: [    1.031611] PPP generic driver version 2.4.2
Jul 27 11:19:02 node-1 kernel: [    1.038076] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 27 11:19:02 node-1 kernel: [    1.044616] ehci-pci: EHCI PCI platform driver
Jul 27 11:19:02 node-1 kernel: [    1.051220] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 27 11:19:02 node-1 kernel: [    1.057707] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 27 11:19:02 node-1 kernel: [    1.070385] ehci-pci 0000:00:1a.0: debug port 2
Jul 27 11:19:02 node-1 kernel: [    1.080669] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 27 11:19:02 node-1 kernel: [    1.080689] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 27 11:19:02 node-1 kernel: [    1.096230] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 27 11:19:02 node-1 kernel: [    1.102355] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 27 11:19:02 node-1 kernel: [    1.108610] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 27 11:19:02 node-1 kernel: [    1.120661] usb usb1: Product: EHCI Host Controller
Jul 27 11:19:02 node-1 kernel: [    1.126792] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 27 11:19:02 node-1 kernel: [    1.132932] usb usb1: SerialNumber: 0000:00:1a.0
Jul 27 11:19:02 node-1 kernel: [    1.138984] hub 1-0:1.0: USB hub found
Jul 27 11:19:02 node-1 kernel: [    1.144866] hub 1-0:1.0: 2 ports detected
Jul 27 11:19:02 node-1 kernel: [    1.150725] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 27 11:19:02 node-1 kernel: [    1.156408] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 27 11:19:02 node-1 kernel: [    1.167482] ehci-pci 0000:00:1d.0: debug port 2
Jul 27 11:19:02 node-1 kernel: [    1.176868] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 27 11:19:02 node-1 kernel: [    1.176871] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 27 11:19:02 node-1 kernel: [    1.192149] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 27 11:19:02 node-1 kernel: [    1.197429] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 27 11:19:02 node-1 kernel: [    1.202777] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 27 11:19:02 node-1 kernel: [    1.213534] usb usb2: Product: EHCI Host Controller
Jul 27 11:19:02 node-1 kernel: [    1.219090] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 27 11:19:02 node-1 kernel: [    1.224684] usb usb2: SerialNumber: 0000:00:1d.0
Jul 27 11:19:02 node-1 kernel: [    1.230304] hub 2-0:1.0: USB hub found
Jul 27 11:19:02 node-1 kernel: [    1.235728] hub 2-0:1.0: 2 ports detected
Jul 27 11:19:02 node-1 kernel: [    1.241127] ehci-platform: EHCI generic platform driver
Jul 27 11:19:02 node-1 kernel: [    1.246434] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 27 11:19:02 node-1 kernel: [    1.251844] ohci-pci: OHCI PCI platform driver
Jul 27 11:19:02 node-1 kernel: [    1.257176] ohci-platform: OHCI generic platform driver
Jul 27 11:19:02 node-1 kernel: [    1.262435] uhci_hcd: USB Universal Host Controller Interface driver
Jul 27 11:19:02 node-1 kernel: [    1.267876] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 27 11:19:02 node-1 kernel: [    1.459928] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 27 11:19:02 node-1 kernel: [    1.767707] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 27 11:19:02 node-1 kernel: [    1.784026] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 27 11:19:02 node-1 kernel: [    1.789632] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 27 11:19:02 node-1 kernel: [    1.795418] hub 1-1:1.0: USB hub found
Jul 27 11:19:02 node-1 kernel: [    1.801012] hub 1-1:1.0: 6 ports detected
Jul 27 11:19:02 node-1 kernel: [    1.915561] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 27 11:19:02 node-1 kernel: [    2.306645] i8042: No controller found
Jul 27 11:19:02 node-1 kernel: [    2.312184] mousedev: PS/2 mouse device common for all mice
Jul 27 11:19:02 node-1 kernel: [    2.317924] rtc_cmos 00:02: RTC can wake from S4
Jul 27 11:19:02 node-1 kernel: [    2.320010] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 27 11:19:02 node-1 kernel: [    2.320011] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 27 11:19:02 node-1 kernel: [    2.320535] hub 2-1:1.0: USB hub found
Jul 27 11:19:02 node-1 kernel: [    2.320762] hub 2-1:1.0: 8 ports detected
Jul 27 11:19:02 node-1 kernel: [    2.346293] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 27 11:19:02 node-1 kernel: [    2.352122] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 27 11:19:02 node-1 kernel: [    2.363449] device-mapper: uevent: version 1.0.3
Jul 27 11:19:02 node-1 kernel: [    2.369174] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 27 11:19:02 node-1 kernel: [    2.380550] ledtrig-cpu: registered to indicate activity on CPUs
Jul 27 11:19:02 node-1 kernel: [    2.386521] TCP: cubic registered
Jul 27 11:19:02 node-1 kernel: [    2.392381] NET: Registered protocol family 10
Jul 27 11:19:02 node-1 kernel: [    2.398433] NET: Registered protocol family 17
Jul 27 11:19:02 node-1 kernel: [    2.404200] Key type dns_resolver registered
Jul 27 11:19:02 node-1 kernel: [    2.410306] Loading compiled-in X.509 certificates
Jul 27 11:19:02 node-1 kernel: [    2.416579] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 27 11:19:02 node-1 kernel: [    2.428227] registered taskstats version 1
Jul 27 11:19:02 node-1 kernel: [    2.436307] Key type trusted registered
Jul 27 11:19:02 node-1 kernel: [    2.443917] Key type encrypted registered
Jul 27 11:19:02 node-1 kernel: [    2.449412] AppArmor: AppArmor sha1 policy hashing enabled
Jul 27 11:19:02 node-1 kernel: [    2.454914] IMA: No TPM chip found, activating TPM-bypass!
Jul 27 11:19:02 node-1 kernel: [    2.461014] regulator-dummy: disabling
Jul 27 11:19:02 node-1 kernel: [    2.466495]   Magic number: 8:472:328
Jul 27 11:19:02 node-1 kernel: [    2.472212] rtc_cmos 00:02: setting system clock to 2016-07-27 11:18:28 UTC (1469618308)
Jul 27 11:19:02 node-1 kernel: [    2.484699] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 27 11:19:02 node-1 kernel: [    2.490360] EDD information not available.
Jul 27 11:19:02 node-1 kernel: [    2.495974] PM: Hibernation image not present or could not be loaded.
Jul 27 11:19:02 node-1 kernel: [    2.496839] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 27 11:19:02 node-1 kernel: [    2.508139] Write protecting the kernel read-only data: 12288k
Jul 27 11:19:02 node-1 kernel: [    2.514404] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 27 11:19:02 node-1 kernel: [    2.527345] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 27 11:19:02 node-1 kernel: [    2.558831] device-mapper: multipath: version 1.6.0 loaded
Jul 27 11:19:02 node-1 kernel: [    2.566782] systemd-udevd[215]: starting version 204
Jul 27 11:19:02 node-1 kernel: [    2.585158] md: linear personality registered for level -1
Jul 27 11:19:02 node-1 kernel: [    2.598973] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 27 11:19:02 node-1 kernel: [    2.606037] md: multipath personality registered for level -4
Jul 27 11:19:02 node-1 kernel: [    2.614020] md: raid0 personality registered for level 0
Jul 27 11:19:02 node-1 kernel: [    2.622455] md: raid1 personality registered for level 1
Jul 27 11:19:02 node-1 kernel: [    2.631563] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 27 11:19:02 node-1 kernel: [    2.637964] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 27 11:19:02 node-1 kernel: [    2.644303] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 27 11:19:02 node-1 kernel: [    2.645381] megasas: FW now in Ready state
Jul 27 11:19:02 node-1 kernel: [    2.645916] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.646068] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.646225] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.646324] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.646462] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.646586] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.646739] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.646865] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.647349] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.647498] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.647628] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.647810] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.647888] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.648037] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.648162] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.648242] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.648811] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 27 11:19:02 node-1 kernel: [    2.678298] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Jul 27 11:19:02 node-1 kernel: [    2.691723] 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
Jul 27 11:19:02 node-1 kernel: [    2.694948] raid6: sse2x1   11412 MB/s
Jul 27 11:19:02 node-1 kernel: [    2.712472] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 11:19:02 node-1 kernel: [    2.719406] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.719410] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.719414] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.719420] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.719460] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 11:19:02 node-1 kernel: [    2.741545] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Jul 27 11:19:02 node-1 kernel: [    2.754890] enic 0000:07: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
Jul 27 11:19:02 node-1 kernel: [    2.762899] raid6: sse2x2   14558 MB/s
Jul 27 11:19:02 node-1 kernel: [    2.775082] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 11:19:02 node-1 kernel: [    2.830774] raid6: sse2x4   10159 MB/s
Jul 27 11:19:02 node-1 kernel: [    2.902705] raid6: avx2x1   14950 MB/s
Jul 27 11:19:02 node-1 kernel: [    2.974650] raid6: avx2x2   18929 MB/s
Jul 27 11:19:02 node-1 kernel: [    3.046587] raid6: avx2x4   21329 MB/s
Jul 27 11:19:02 node-1 kernel: [    3.052772] raid6: using algorithm avx2x4 (21329 MB/s)
Jul 27 11:19:02 node-1 kernel: [    3.058887] raid6: using avx2x2 recovery algorithm
Jul 27 11:19:02 node-1 kernel: [    3.064881] Switched to clocksource tsc
Jul 27 11:19:02 node-1 kernel: [    3.064885] megasas:IOC Init cmd success
Jul 27 11:19:02 node-1 kernel: [    3.064947] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    3.064989] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    3.065029] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    3.065043] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    3.065134] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 11:19:02 node-1 kernel: [    3.073270] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Jul 27 11:19:02 node-1 kernel: [    3.073271] 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
Jul 27 11:19:02 node-1 kernel: [    3.073272] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 11:19:02 node-1 kernel: [    3.073334] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    3.073370] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    3.073407] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    3.073444] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    3.073525] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 11:19:02 node-1 kernel: [    3.079529] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 27 11:19:02 node-1 kernel: [    3.079530] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 27 11:19:02 node-1 kernel: [    3.079531] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 27 11:19:02 node-1 kernel: [    3.079531] usb 2-1.4: Manufacturer: Avocent
Jul 27 11:19:02 node-1 kernel: [    3.079532] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 27 11:19:02 node-1 kernel: [    3.082392] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Jul 27 11:19:02 node-1 kernel: [    3.082394] 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
Jul 27 11:19:02 node-1 kernel: [    3.082395] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 11:19:02 node-1 kernel: [    3.082461] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    3.082500] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    3.082541] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    3.082582] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 27 11:19:02 node-1 kernel: [    3.082677] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 11:19:02 node-1 kernel: [    3.086579] megasas: INIT adapter done
Jul 27 11:19:02 node-1 kernel: [    3.138062] xor: automatically using best checksumming function:
Jul 27 11:19:02 node-1 kernel: [    3.158529] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 27 11:19:02 node-1 kernel: [    3.158862] scsi0 : LSI SAS based MegaRAID driver
Jul 27 11:19:02 node-1 kernel: [    3.165926] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 27 11:19:02 node-1 kernel: [    3.177151] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 27 11:19:02 node-1 kernel: [    3.179534] hidraw: raw HID events driver (C) Jiri Kosina
Jul 27 11:19:02 node-1 kernel: [    3.181459] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 27 11:19:02 node-1 kernel: [    3.181490] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 27 11:19:02 node-1 kernel: [    3.181771] sd 0:2:0:0: [sda] Write Protect is off
Jul 27 11:19:02 node-1 kernel: [    3.181772] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 27 11:19:02 node-1 kernel: [    3.181841] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 27 11:19:02 node-1 kernel: [    3.186523]    avx       : 62776.000 MB/sec
Jul 27 11:19:02 node-1 kernel: [    3.205499]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 27 11:19:02 node-1 kernel: [    3.206685] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 27 11:19:02 node-1 kernel: [    3.315108] async_tx: api initialized (async)
Jul 27 11:19:02 node-1 kernel: [    3.317954] usbcore: registered new interface driver usbhid
Jul 27 11:19:02 node-1 kernel: [    3.317954] usbhid: USB HID core driver
Jul 27 11:19:02 node-1 kernel: [    3.340486] 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
Jul 27 11:19:02 node-1 kernel: [    3.353247] 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
Jul 27 11:19:02 node-1 kernel: [    3.366113] 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
Jul 27 11:19:02 node-1 kernel: [    3.378920] 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
Jul 27 11:19:02 node-1 kernel: [    3.379195] md: raid6 personality registered for level 6
Jul 27 11:19:02 node-1 kernel: [    3.379195] md: raid5 personality registered for level 5
Jul 27 11:19:02 node-1 kernel: [    3.379196] md: raid4 personality registered for level 4
Jul 27 11:19:02 node-1 kernel: [    3.407852] random: lvm urandom read with 35 bits of entropy available
Jul 27 11:19:02 node-1 kernel: [    3.418574] 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
Jul 27 11:19:02 node-1 kernel: [    3.431651] 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
Jul 27 11:19:02 node-1 kernel: [    3.446115] md: raid10 personality registered for level 10
Jul 27 11:19:02 node-1 kernel: [    3.501463] multipathd (370): /proc/370/oom_adj is deprecated, please use /proc/370/oom_score_adj instead.
Jul 27 11:19:02 node-1 kernel: [    3.587747] bio: create slab <bio-1> at 1
Jul 27 11:19:02 node-1 kernel: [    4.349711] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 11:19:02 node-1 kernel: [    4.991150] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 27 11:19:02 node-1 kernel: [    5.037384] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 27 11:19:02 node-1 kernel: [    5.059675] random: nonblocking pool is initialized
Jul 27 11:19:02 node-1 kernel: [    5.174011] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 27 11:19:02 node-1 kernel: [    5.209957] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 27 11:19:02 node-1 kernel: [    5.291243] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 11:19:02 node-1 kernel: [    5.491984] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 27 11:19:02 node-1 kernel: [    5.535076] XFS (dm-0): Mounting Filesystem
Jul 27 11:19:02 node-1 kernel: [    5.834344] XFS (dm-0): Ending clean mount
Jul 27 11:19:02 node-1 kernel: [    5.931732] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 11:19:02 node-1 kernel: [    5.971925] XFS (dm-1): Mounting Filesystem
Jul 27 11:19:02 node-1 kernel: [    6.108094] XFS (dm-1): Ending clean mount
Jul 27 11:19:02 node-1 kernel: [    7.967444] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 27 11:19:02 node-1 kernel: [    7.980974] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 27 11:19:02 node-1 kernel: [    8.148452] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 27 11:19:02 node-1 kernel: [    8.148458] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 27 11:19:02 node-1 kernel: [    8.148462] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 27 11:19:02 node-1 kernel: [    8.148466] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 27 11:19:02 node-1 kernel: [    8.191070] systemd-udevd[778]: starting version 204
Jul 27 11:19:02 node-1 kernel: [    8.384069] wmi: Mapper loaded
Jul 27 11:19:02 node-1 kernel: [    8.413780] power_meter ACPI000D:00: Found ACPI power meter.
Jul 27 11:19:02 node-1 kernel: [    8.413823] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 27 11:19:02 node-1 kernel: [    8.433527] IPMI System Interface driver.
Jul 27 11:19:02 node-1 kernel: [    8.433627] ipmi_si: probing via ACPI
Jul 27 11:19:02 node-1 kernel: [    8.433640] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 27 11:19:02 node-1 kernel: [    8.433642] ipmi_si: Adding ACPI-specified kcs state machine
Jul 27 11:19:02 node-1 kernel: [    8.433655] ipmi_si: probing via SMBIOS
Jul 27 11:19:02 node-1 kernel: [    8.433657] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 27 11:19:02 node-1 kernel: [    8.433658] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 27 11:19:02 node-1 kernel: [    8.433660] ipmi_si: probing via SPMI
Jul 27 11:19:02 node-1 kernel: [    8.433661] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 27 11:19:02 node-1 kernel: [    8.433662] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 27 11:19:02 node-1 kernel: [    8.433664] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 27 11:19:02 node-1 kernel: [    8.433788] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 27 11:19:02 node-1 kernel: [    8.434309] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 27 11:19:02 node-1 kernel: [    8.434315] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 27 11:19:02 node-1 kernel: [    8.434319] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 27 11:19:02 node-1 kernel: [    8.434321] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 27 11:19:02 node-1 kernel: [    8.434342] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 27 11:19:02 node-1 kernel: [    8.547075] systemd-udevd[805]: renamed network interface eth2 to enp8s0
Jul 27 11:19:02 node-1 kernel: [    8.566274] systemd-udevd[823]: renamed network interface eth0 to enp6s0
Jul 27 11:19:02 node-1 kernel: [    8.584508] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 27 11:19:02 node-1 kernel: [    8.584513] ipmi_si 00:09: IPMI kcs interface initialized
Jul 27 11:19:02 node-1 kernel: [    8.586267] systemd-udevd[824]: renamed network interface eth1 to enp7s0
Jul 27 11:19:02 node-1 kernel: [    8.618245] systemd-udevd[797]: renamed network interface eth3 to enp9s0
Jul 27 11:19:02 node-1 kernel: [    8.915028] type=1400 audit(1469618314.946:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1060 comm="apparmor_parser"
Jul 27 11:19:02 node-1 kernel: [    8.915177] type=1400 audit(1469618314.946:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1060 comm="apparmor_parser"
Jul 27 11:19:02 node-1 kernel: [    8.915303] type=1400 audit(1469618314.946:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1060 comm="apparmor_parser"
Jul 27 11:19:02 node-1 kernel: [    8.919366] type=1400 audit(1469618314.950:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1061 comm="apparmor_parser"
Jul 27 11:19:02 node-1 kernel: [    8.919504] type=1400 audit(1469618314.950:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1061 comm="apparmor_parser"
Jul 27 11:19:02 node-1 kernel: [    8.919625] type=1400 audit(1469618314.950:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1061 comm="apparmor_parser"
Jul 27 11:19:02 node-1 kernel: [    8.920933] type=1400 audit(1469618314.950:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1059 comm="apparmor_parser"
Jul 27 11:19:02 node-1 kernel: [    8.921172] type=1400 audit(1469618314.950:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1059 comm="apparmor_parser"
Jul 27 11:19:02 node-1 kernel: [    8.921221] type=1400 audit(1469618314.950:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1062 comm="apparmor_parser"
Jul 27 11:19:02 node-1 kernel: [    8.921289] type=1400 audit(1469618314.950:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1059 comm="apparmor_parser"
Jul 27 11:19:02 node-1 kernel: [    9.530843] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 27 11:19:02 node-1 kernel: [    9.538608] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 27 11:19:02 node-1 kernel: [    9.737486] enic 0000:06:00.0 enp6s0: Link UP
Jul 27 11:19:02 node-1 kernel: [    9.738606] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 27 11:19:02 node-1 kernel: [    9.738611] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 27 11:19:02 node-1 kernel: [   18.833978] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 27 11:19:02 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 27 11:19:03 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 27 11:19:03 node-1 kernel: [   37.399780] init: failsafe main process (8398) killed by TERM signal
Jul 27 11:19:04 node-1 dbus[8444]: [system] AppArmor D-Bus mediation is enabled
Jul 27 11:19:04 node-1 kernel: [   37.597086] audit_printk_skb: 30 callbacks suppressed
Jul 27 11:19:04 node-1 kernel: [   37.597088] type=1400 audit(1469618344.183:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8524 comm="apparmor_parser"
Jul 27 11:19:04 node-1 kernel: [   37.597093] type=1400 audit(1469618344.183:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8524 comm="apparmor_parser"
Jul 27 11:19:04 node-1 kernel: [   37.597096] type=1400 audit(1469618344.183:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8524 comm="apparmor_parser"
Jul 27 11:19:04 node-1 kernel: [   37.597331] type=1400 audit(1469618344.183:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8524 comm="apparmor_parser"
Jul 27 11:19:04 node-1 kernel: [   37.597333] type=1400 audit(1469618344.183:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8524 comm="apparmor_parser"
Jul 27 11:19:04 node-1 kernel: [   37.597448] type=1400 audit(1469618344.183:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8524 comm="apparmor_parser"
Jul 27 11:19:04 node-1 kernel: [   37.597549] type=1400 audit(1469618344.183:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8525 comm="apparmor_parser"
Jul 27 11:19:04 node-1 kernel: [   37.666495] type=1400 audit(1469618344.251:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8527 comm="apparmor_parser"
Jul 27 11:19:04 node-1 anacron[8594]: Anacron 2.3 started on 2016-07-27
Jul 27 11:19:04 node-1 anacron[8594]: Will run job `cron.daily' in 5 min.
Jul 27 11:19:04 node-1 anacron[8594]: Will run job `cron.weekly' in 10 min.
Jul 27 11:19:04 node-1 anacron[8594]: Will run job `cron.monthly' in 15 min.
Jul 27 11:19:04 node-1 anacron[8594]: Jobs will be executed sequentially
Jul 27 11:19:04 node-1 cron[8555]: (CRON) INFO (pidfile fd = 3)
Jul 27 11:19:04 node-1 cron[8614]: (CRON) STARTUP (fork ok)
Jul 27 11:19:04 node-1 multipathd: path checkers start up
Jul 27 11:19:04 node-1 cron[8614]: (CRON) INFO (Running @reboot jobs)
Jul 27 11:19:04 node-1 postfix/master[8735]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 27 11:19:08 node-1 puppet-agent[9050]: Reopening log files
Jul 27 11:19:08 node-1 puppet-agent[9050]: Could not request certificate: Connection refused - connect(2)
Jul 27 11:19:22 node-1 puppet-user[9309]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 27 11:19:22 node-1 puppet-user[9309]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 27 11:19:23 node-1 puppet-user[9309]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 27 11:19:23 node-1 puppet-user[9309]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 27 11:19:23 node-1 puppet-user[9309]: Finished catalog run in 1.11 seconds
Jul 27 11:19:24 node-1 multipathd: uevent trigger error
Jul 27 11:19:24 node-1 puppet-user[9734]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 27 11:19:24 node-1 puppet-user[9734]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Jul 27 11:19:25 node-1 puppet-user[9734]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 27 11:19:25 node-1 puppet-user[9734]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 27 11:19:25 node-1 puppet-user[9734]: (/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"]'
Jul 27 11:19:25 node-1 puppet-user[9734]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 27 11:19:25 node-1 puppet-user[9734]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 27 11:19:25 node-1 puppet-user[9734]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 27 11:19:25 node-1 puppet-user[9734]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 27 11:19:25 node-1 puppet-user[9734]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 27 11:19:25 node-1 puppet-user[9734]: Finished catalog run in 0.06 seconds
Jul 27 11:19:26 node-1 puppet-user[10194]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 27 11:19:26 node-1 puppet-user[10194]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 27 11:19:26 node-1 puppet-user[10194]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 27 11:19:26 node-1 puppet-user[10194]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 27 11:19:26 node-1 puppet-user[10194]: Finished catalog run in 0.03 seconds
Jul 27 11:19:28 node-1 puppet-user[10660]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 27 11:19:28 node-1 puppet-user[10660]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 27 11:19:28 node-1 puppet-user[10660]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 27 11:19:28 node-1 puppet-user[10660]: Finished catalog run in 0.04 seconds
Jul 27 11:19:29 node-1 puppet-user[11111]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 27 11:19:29 node-1 puppet-user[11111]: Compiled catalog for node-1.domain.tld in environment production in 0.18 seconds
Jul 27 11:19:29 node-1 puppet-user[11111]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 27 11:19:31 node-1 puppet-user[11111]: (/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
Jul 27 11:19:31 node-1 puppet-user[11111]: Finished catalog run in 1.96 seconds
Jul 27 11:19:32 node-1 kernel: [   66.244478] init: plymouth-upstart-bridge main process ended, respawning
Jul 27 11:19:32 node-1 puppet-user[11639]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 27 11:19:33 node-1 puppet-agent[9050]: Could not run: SIGTERM
Jul 27 11:19:33 node-1 puppet-user[11639]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Jul 27 11:19:33 node-1 kernel: [   66.521383] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 27 11:19:33 node-1 puppet-user[11639]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 27 11:19:33 node-1 ec2: 
Jul 27 11:19:33 node-1 ec2: #############################################################
Jul 27 11:19:33 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 27 11:19:33 node-1 ec2: 1024 bd:86:24:9f:ca:66:98:a0:b9:92:7b:25:32:7a:88:c0  root@node-1.domain.tld (DSA)
Jul 27 11:19:33 node-1 puppet-user[11639]: (/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
Jul 27 11:19:33 node-1 ec2: 256 f1:98:15:7d:43:97:e7:53:9c:75:c2:05:22:c1:7a:a9  root@node-1.domain.tld (ECDSA)
Jul 27 11:19:33 node-1 ec2: 256 be:c2:8c:de:cb:10:c7:95:89:f2:1e:0c:b1:62:fd:bb  root@node-1.domain.tld (ED25519)
Jul 27 11:19:33 node-1 ec2: 2048 c5:9b:5b:ef:e9:c5:31:4d:9d:3a:eb:db:dd:e3:82:3f  root@node-1.domain.tld (RSA)
Jul 27 11:19:33 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 27 11:19:33 node-1 ec2: #############################################################
Jul 27 11:19:33 node-1 puppet-user[11639]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 27 11:19:33 node-1 puppet-user[11639]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 27 11:19:33 node-1 puppet-user[11639]: Finished catalog run in 0.30 seconds
Jul 27 11:19:35 node-1 puppet-user[12301]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 27 11:19:35 node-1 puppet-user[12301]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Jul 27 11:19:35 node-1 puppet-user[12301]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 27 11:19:35 node-1 kernel: [   68.713599] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 27 11:19:35 node-1 kernel: [   68.713648] 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.
Jul 27 11:19:35 node-1 puppet-user[12301]: (/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'
Jul 27 11:19:35 node-1 puppet-user[12301]: Finished catalog run in 0.05 seconds
Jul 27 11:19:37 node-1 puppet-user[12767]: (Scope(Class[main])) MODULAR: sync_time
Jul 27 11:19:37 node-1 puppet-user[12767]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 27 11:19:37 node-1 ntpdate[13199]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 27 11:19:43 node-1 ntpdate[13199]: adjust time server 10.20.0.2 offset -0.268681 sec
Jul 27 11:19:43 node-1 puppet-user[12767]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 27 11:19:43 node-1 puppet-user[12767]: Finished catalog run in 6.18 seconds
Jul 27 11:19:48 node-1 puppet-user[13391]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 27 11:19:48 node-1 puppet-user[13391]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Jul 27 11:19:48 node-1 puppet-user[13391]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 27 11:19:48 node-1 puppet-user[13391]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Jul 27 11:19:48 node-1 puppet-user[13391]: Finished catalog run in 0.07 seconds
Jul 27 11:19:50 node-1 puppet-user[13853]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 27 11:19:51 node-1 puppet-user[13853]: Compiled catalog for node-1.domain.tld in environment production in 1.43 seconds
Jul 27 11:19:51 node-1 puppet-user[13853]: (/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
Jul 27 11:19:51 node-1 puppet-user[13853]: (/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
Jul 27 11:19:51 node-1 puppet-user[13853]: (/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
Jul 27 11:19:51 node-1 puppet-user[13853]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 27 11:19:52 node-1 puppet-user[13853]: (/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
Jul 27 11:19:52 node-1 puppet-user[13853]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 27 11:19:52 node-1 puppet-user[13853]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 27 11:19:52 node-1 puppet-user[13853]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 27 11:19:52 node-1 puppet-user[13853]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 27 11:19:52 node-1 puppet-user[13853]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 27 11:19:52 node-1 puppet-user[13853]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 27 11:19:52 node-1 puppet-user[13853]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 27 11:19:52 node-1 puppet-user[13853]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 27 11:19:52 node-1 puppet-user[13853]: (/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
Jul 27 11:19:52 node-1 puppet-user[13853]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 27 11:19:52 node-1 puppet-user[13853]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 27 11:20:01 node-1 CRON[14656]: (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")
Jul 27 11:20:06 node-1 puppet-user[13853]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 27 11:20:06 node-1 puppet-user[13853]: Finished catalog run in 14.60 seconds
Jul 27 11:20:08 node-1 puppet-user[14840]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 27 11:20:08 node-1 puppet-user[14840]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Jul 27 11:20:13 node-1 puppet-user[14840]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 27 11:20:21 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 11:20:21 node-1 nailgun-agent: I, [2016-07-27T11:20:21.706550 #14659]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 27 11:20:34 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 11:20:34 node-1 nailgun-agent: I, [2016-07-27T11:20:34.884728 #14659]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 27 11:20:44 node-1 puppet-user[14840]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 27 11:20:44 node-1 puppet-user[14840]: Finished catalog run in 35.31 seconds
Jul 27 11:20:45 node-1 puppet-user[17573]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 27 11:20:46 node-1 puppet-user[17573]: Compiled catalog for node-1.domain.tld in environment production in 0.54 seconds
Jul 27 11:20:46 node-1 puppet-user[17573]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 27 11:20:46 node-1 puppet-user[17573]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 27 11:20:46 node-1 puppet-user[17573]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 27 11:20:46 node-1 puppet-user[17573]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 27 11:20:46 node-1 puppet-user[17573]: Finished catalog run in 0.08 seconds
Jul 27 11:20:48 node-1 puppet-user[18035]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 27 11:20:49 node-1 puppet-user[18035]: Compiled catalog for node-1.domain.tld in environment production in 0.83 seconds
Jul 27 11:20:49 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 27 11:20:49 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 27 11:20:49 node-1 crontab[18475]: (root) LIST (root)
Jul 27 11:20:49 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 27 11:20:49 node-1 crontab[18476]: (root) REPLACE (root)
Jul 27 11:20:51 node-1 puppet-user[18035]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/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
Jul 27 11:20:53 node-1 puppet-user[18035]: (/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
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/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
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/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
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/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
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/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
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/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
Jul 27 11:20:53 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 27 11:20:53 node-1 puppet-user[18035]: (/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
Jul 27 11:20:54 node-1 puppet-user[18035]: (/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
Jul 27 11:20:54 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 27 11:20:54 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 27 11:20:54 node-1 puppet-user[18035]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 27 11:20:54 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8371" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 11:20:54 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 27 11:20:55 node-1 multipathd: uevent trigger error
<27>Jul 27 11:20:55 node-1 multipathd: uevent trigger error
<27>Jul 27 11:20:55 node-1 multipathd: uevent trigger error
<27>Jul 27 11:20:55 node-1 multipathd: uevent trigger error
<27>Jul 27 11:21:14 node-1 multipathd: uevent trigger error
<27>Jul 27 11:21:14 node-1 multipathd: uevent trigger error
<27>Jul 27 11:21:14 node-1 multipathd: uevent trigger error
<27>Jul 27 11:21:14 node-1 multipathd: uevent trigger error
<27>Jul 27 11:21:14 node-1 multipathd: uevent trigger error
<27>Jul 27 11:22:02 node-1 multipathd: uevent trigger error
<27>Jul 27 11:22:02 node-1 multipathd: uevent trigger error
<27>Jul 27 11:22:02 node-1 multipathd: uevent trigger error
<27>Jul 27 11:22:02 node-1 multipathd: uevent trigger error
<27>Jul 27 11:22:02 node-1 multipathd: uevent trigger error
<27>Jul 27 11:22:04 node-1 multipathd: uevent trigger error
<27>Jul 27 11:22:04 node-1 multipathd: uevent trigger error
<27>Jul 27 11:22:05 node-1 multipathd: uevent trigger error
<27>Jul 27 11:22:05 node-1 multipathd: uevent trigger error
<27>Jul 27 11:22:05 node-1 multipathd: uevent trigger error
<27>Jul 27 11:22:47 node-1 ntpdate[2075]: no servers can be used, exiting
<27>Jul 27 11:23:19 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:19 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:19 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:19 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:19 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:22 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:22 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:22 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:22 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:22 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:34 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:34 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:34 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:34 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:34 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:23:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:24:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:24:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:24:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:24:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:24:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:24:46 node-1 multipathd: uevent trigger error
<27>Jul 27 11:24:46 node-1 multipathd: uevent trigger error
<27>Jul 27 11:24:46 node-1 multipathd: uevent trigger error
<27>Jul 27 11:24:46 node-1 multipathd: uevent trigger error
<27>Jul 27 11:24:46 node-1 multipathd: uevent trigger error
<27>Jul 27 11:24:48 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 11:24:48 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 11:24:54 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 11:24:54 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 11:25:00 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 11:25:05 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 11:25:06 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 11:25:13 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:13 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:13 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:13 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:13 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:13 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:26 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:26 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:26 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:26 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:26 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:26 node-1 multipathd: uevent trigger error
<129>Jul 27 11:25:28 node-1 haproxy[22401]: 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>Jul 27 11:25:29 node-1 haproxy[22406]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:29 node-1 haproxy[22406]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:29 node-1 haproxy[22406]: proxy mysqld has no server available!
<27>Jul 27 11:25:31 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:31 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:31 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:31 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:31 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:34 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:34 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:34 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:35 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:35 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:35 node-1 multipathd: uevent trigger error
<129>Jul 27 11:25:37 node-1 haproxy[25168]: 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>Jul 27 11:25:37 node-1 haproxy[25168]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:38 node-1 haproxy[25172]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:38 node-1 haproxy[25172]: proxy mysqld has no server available!
<129>Jul 27 11:25:38 node-1 haproxy[25172]: 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>Jul 27 11:25:38 node-1 haproxy[25172]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:39 node-1 haproxy[25172]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:39 node-1 haproxy[25172]: proxy object-storage has no server available!
<27>Jul 27 11:25:40 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:40 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:40 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:40 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:40 node-1 multipathd: uevent trigger error
<129>Jul 27 11:25:42 node-1 haproxy[26564]: 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>Jul 27 11:25:43 node-1 haproxy[26568]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:43 node-1 haproxy[26568]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:43 node-1 haproxy[26568]: proxy neutron has no server available!
<129>Jul 27 11:25:43 node-1 haproxy[26568]: 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>Jul 27 11:25:43 node-1 haproxy[26568]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:43 node-1 haproxy[26568]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:43 node-1 haproxy[26568]: proxy mysqld has no server available!
<129>Jul 27 11:25:44 node-1 haproxy[26568]: 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>Jul 27 11:25:44 node-1 haproxy[26568]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:44 node-1 haproxy[26568]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:44 node-1 haproxy[26568]: proxy object-storage has no server available!
<27>Jul 27 11:25:45 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:45 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:45 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:45 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:45 node-1 multipathd: uevent trigger error
<129>Jul 27 11:25:48 node-1 haproxy[27958]: 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>Jul 27 11:25:48 node-1 haproxy[27958]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:48 node-1 haproxy[27958]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:48 node-1 haproxy[27958]: proxy keystone-1 has no server available!
<129>Jul 27 11:25:48 node-1 haproxy[27958]: 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>Jul 27 11:25:48 node-1 haproxy[27958]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:48 node-1 haproxy[27958]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:48 node-1 haproxy[27958]: proxy keystone-2 has no server available!
<129>Jul 27 11:25:49 node-1 haproxy[27962]: 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>Jul 27 11:25:49 node-1 haproxy[27962]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:49 node-1 haproxy[27962]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:49 node-1 haproxy[27962]: proxy neutron has no server available!
<129>Jul 27 11:25:49 node-1 haproxy[27962]: 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>Jul 27 11:25:49 node-1 haproxy[27962]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:49 node-1 haproxy[27962]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:49 node-1 haproxy[27962]: proxy mysqld has no server available!
<129>Jul 27 11:25:49 node-1 haproxy[27962]: 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>Jul 27 11:25:49 node-1 haproxy[27962]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:50 node-1 haproxy[27962]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:50 node-1 haproxy[27962]: proxy object-storage has no server available!
<27>Jul 27 11:25:51 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:51 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:51 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:51 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:51 node-1 multipathd: uevent trigger error
<129>Jul 27 11:25:53 node-1 haproxy[29299]: 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>Jul 27 11:25:53 node-1 haproxy[29299]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:53 node-1 haproxy[29299]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:53 node-1 haproxy[29299]: proxy keystone-1 has no server available!
<129>Jul 27 11:25:53 node-1 haproxy[29299]: 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>Jul 27 11:25:54 node-1 haproxy[29310]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:54 node-1 haproxy[29310]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:54 node-1 haproxy[29310]: proxy keystone-2 has no server available!
<129>Jul 27 11:25:54 node-1 haproxy[29310]: 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>Jul 27 11:25:54 node-1 haproxy[29310]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:54 node-1 haproxy[29310]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:54 node-1 haproxy[29310]: proxy neutron has no server available!
<129>Jul 27 11:25:54 node-1 haproxy[29310]: 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>Jul 27 11:25:54 node-1 haproxy[29310]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:54 node-1 haproxy[29310]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:54 node-1 haproxy[29310]: proxy mysqld has no server available!
<129>Jul 27 11:25:54 node-1 haproxy[29310]: 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>Jul 27 11:25:55 node-1 haproxy[29310]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:55 node-1 haproxy[29310]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:55 node-1 haproxy[29310]: proxy object-storage has no server available!
<129>Jul 27 11:25:55 node-1 haproxy[29310]: 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>Jul 27 11:25:55 node-1 haproxy[29310]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:55 node-1 haproxy[29310]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:55 node-1 haproxy[29310]: proxy aodh has no server available!
<27>Jul 27 11:25:57 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:57 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:57 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:57 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:57 node-1 multipathd: uevent trigger error
<27>Jul 27 11:25:57 node-1 multipathd: uevent trigger error
<129>Jul 27 11:25:59 node-1 haproxy[30686]: 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>Jul 27 11:25:59 node-1 haproxy[30686]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:59 node-1 haproxy[30686]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:59 node-1 haproxy[30686]: proxy keystone-1 has no server available!
<129>Jul 27 11:25:59 node-1 haproxy[30686]: 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>Jul 27 11:25:59 node-1 haproxy[30686]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:25:59 node-1 haproxy[30686]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:25:59 node-1 haproxy[30686]: proxy keystone-2 has no server available!
<129>Jul 27 11:25:59 node-1 haproxy[30686]: 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>Jul 27 11:25:59 node-1 haproxy[30686]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:00 node-1 haproxy[30690]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:00 node-1 haproxy[30690]: proxy neutron has no server available!
<129>Jul 27 11:26:00 node-1 haproxy[30690]: 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>Jul 27 11:26:00 node-1 haproxy[30690]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:00 node-1 haproxy[30690]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:00 node-1 haproxy[30690]: proxy mysqld has no server available!
<129>Jul 27 11:26:00 node-1 haproxy[30690]: 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>Jul 27 11:26:00 node-1 haproxy[30690]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:00 node-1 haproxy[30690]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:00 node-1 haproxy[30690]: proxy object-storage has no server available!
<129>Jul 27 11:26:00 node-1 haproxy[30690]: 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>Jul 27 11:26:00 node-1 haproxy[30690]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:00 node-1 haproxy[30690]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:00 node-1 haproxy[30690]: proxy aodh has no server available!
<129>Jul 27 11:26:01 node-1 haproxy[30690]: 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>Jul 27 11:26:01 node-1 haproxy[30690]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:01 node-1 haproxy[30690]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:01 node-1 haproxy[30690]: proxy ceilometer has no server available!
<27>Jul 27 11:26:02 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:02 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:02 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:02 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:02 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:02 node-1 multipathd: uevent trigger error
<129>Jul 27 11:26:04 node-1 haproxy[32057]: 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>Jul 27 11:26:04 node-1 haproxy[32057]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:05 node-1 haproxy[32063]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:05 node-1 haproxy[32063]: proxy keystone-1 has no server available!
<129>Jul 27 11:26:05 node-1 haproxy[32063]: 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>Jul 27 11:26:05 node-1 haproxy[32063]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:05 node-1 haproxy[32063]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:05 node-1 haproxy[32063]: proxy keystone-2 has no server available!
<129>Jul 27 11:26:05 node-1 haproxy[32063]: 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>Jul 27 11:26:05 node-1 haproxy[32063]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:05 node-1 haproxy[32063]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:05 node-1 haproxy[32063]: proxy neutron has no server available!
<129>Jul 27 11:26:05 node-1 haproxy[32063]: 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>Jul 27 11:26:05 node-1 haproxy[32063]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:05 node-1 haproxy[32063]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:05 node-1 haproxy[32063]: proxy mysqld has no server available!
<129>Jul 27 11:26:05 node-1 haproxy[32063]: 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>Jul 27 11:26:06 node-1 haproxy[32063]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:06 node-1 haproxy[32063]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:06 node-1 haproxy[32063]: proxy object-storage has no server available!
<129>Jul 27 11:26:06 node-1 haproxy[32063]: 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>Jul 27 11:26:06 node-1 haproxy[32063]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:06 node-1 haproxy[32063]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:06 node-1 haproxy[32063]: proxy aodh has no server available!
<129>Jul 27 11:26:06 node-1 haproxy[32063]: 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>Jul 27 11:26:06 node-1 haproxy[32063]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:06 node-1 haproxy[32063]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:06 node-1 haproxy[32063]: proxy ceilometer has no server available!
<27>Jul 27 11:26:07 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:07 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:07 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:07 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:07 node-1 multipathd: uevent trigger error
<129>Jul 27 11:26:10 node-1 haproxy[994]: 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>Jul 27 11:26:10 node-1 haproxy[994]: Server horizon/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:10 node-1 haproxy[994]: 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>Jul 27 11:26:10 node-1 haproxy[994]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:10 node-1 haproxy[994]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:10 node-1 haproxy[994]: proxy keystone-1 has no server available!
<129>Jul 27 11:26:10 node-1 haproxy[994]: 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>Jul 27 11:26:10 node-1 haproxy[994]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:10 node-1 haproxy[994]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:10 node-1 haproxy[994]: proxy keystone-2 has no server available!
<129>Jul 27 11:26:10 node-1 haproxy[994]: 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>Jul 27 11:26:10 node-1 haproxy[994]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:10 node-1 haproxy[994]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:10 node-1 haproxy[994]: proxy neutron has no server available!
<129>Jul 27 11:26:11 node-1 haproxy[998]: 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>Jul 27 11:26:11 node-1 haproxy[998]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:11 node-1 haproxy[998]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:11 node-1 haproxy[998]: proxy mysqld has no server available!
<129>Jul 27 11:26:11 node-1 haproxy[998]: 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>Jul 27 11:26:11 node-1 haproxy[998]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:11 node-1 haproxy[998]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:11 node-1 haproxy[998]: proxy object-storage has no server available!
<129>Jul 27 11:26:11 node-1 haproxy[998]: 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>Jul 27 11:26:11 node-1 haproxy[998]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:11 node-1 haproxy[998]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:11 node-1 haproxy[998]: proxy aodh has no server available!
<129>Jul 27 11:26:11 node-1 haproxy[998]: 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>Jul 27 11:26:11 node-1 haproxy[998]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:11 node-1 haproxy[998]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:11 node-1 haproxy[998]: proxy ceilometer has no server available!
<27>Jul 27 11:26:13 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:13 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:13 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:13 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:13 node-1 multipathd: uevent trigger error
<129>Jul 27 11:26:15 node-1 haproxy[2368]: 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>Jul 27 11:26:15 node-1 haproxy[2368]: Server horizon/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:15 node-1 haproxy[2368]: 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>Jul 27 11:26:16 node-1 haproxy[2385]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:16 node-1 haproxy[2385]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:16 node-1 haproxy[2385]: proxy keystone-1 has no server available!
<129>Jul 27 11:26:16 node-1 haproxy[2385]: 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>Jul 27 11:26:16 node-1 haproxy[2385]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:16 node-1 haproxy[2385]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:16 node-1 haproxy[2385]: proxy keystone-2 has no server available!
<129>Jul 27 11:26:16 node-1 haproxy[2385]: 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>Jul 27 11:26:16 node-1 haproxy[2385]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:16 node-1 haproxy[2385]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:16 node-1 haproxy[2385]: proxy glance-api has no server available!
<129>Jul 27 11:26:16 node-1 haproxy[2385]: 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>Jul 27 11:26:16 node-1 haproxy[2385]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:16 node-1 haproxy[2385]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:16 node-1 haproxy[2385]: proxy glance-glare has no server available!
<129>Jul 27 11:26:16 node-1 haproxy[2385]: 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>Jul 27 11:26:16 node-1 haproxy[2385]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:16 node-1 haproxy[2385]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:16 node-1 haproxy[2385]: proxy neutron has no server available!
<129>Jul 27 11:26:16 node-1 haproxy[2385]: 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>Jul 27 11:26:16 node-1 haproxy[2385]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:17 node-1 haproxy[2385]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:17 node-1 haproxy[2385]: proxy glance-registry has no server available!
<129>Jul 27 11:26:17 node-1 haproxy[2385]: 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>Jul 27 11:26:17 node-1 haproxy[2385]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:17 node-1 haproxy[2385]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:17 node-1 haproxy[2385]: proxy mysqld has no server available!
<129>Jul 27 11:26:17 node-1 haproxy[2385]: 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>Jul 27 11:26:17 node-1 haproxy[2385]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:17 node-1 haproxy[2385]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:17 node-1 haproxy[2385]: proxy object-storage has no server available!
<129>Jul 27 11:26:17 node-1 haproxy[2385]: 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>Jul 27 11:26:17 node-1 haproxy[2385]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:17 node-1 haproxy[2385]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:17 node-1 haproxy[2385]: proxy aodh has no server available!
<129>Jul 27 11:26:17 node-1 haproxy[2385]: 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>Jul 27 11:26:17 node-1 haproxy[2385]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:17 node-1 haproxy[2385]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:17 node-1 haproxy[2385]: proxy ceilometer has no server available!
<27>Jul 27 11:26:18 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:18 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:18 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:18 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:18 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:18 node-1 multipathd: uevent trigger error
<129>Jul 27 11:26:21 node-1 haproxy[3797]: 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>Jul 27 11:26:21 node-1 haproxy[3797]: Server horizon/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:21 node-1 haproxy[3797]: 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>Jul 27 11:26:21 node-1 haproxy[3797]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:21 node-1 haproxy[3797]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:21 node-1 haproxy[3797]: proxy keystone-1 has no server available!
<129>Jul 27 11:26:22 node-1 haproxy[3801]: 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>Jul 27 11:26:22 node-1 haproxy[3801]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:22 node-1 haproxy[3801]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:22 node-1 haproxy[3801]: proxy keystone-2 has no server available!
<129>Jul 27 11:26:22 node-1 haproxy[3801]: 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>Jul 27 11:26:22 node-1 haproxy[3801]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:22 node-1 haproxy[3801]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:22 node-1 haproxy[3801]: proxy nova-api has no server available!
<129>Jul 27 11:26:22 node-1 haproxy[3801]: 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>Jul 27 11:26:22 node-1 haproxy[3801]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:22 node-1 haproxy[3801]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:22 node-1 haproxy[3801]: proxy nova-metadata-api has no server available!
<129>Jul 27 11:26:22 node-1 haproxy[3801]: 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>Jul 27 11:26:22 node-1 haproxy[3801]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:22 node-1 haproxy[3801]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:22 node-1 haproxy[3801]: proxy glance-api has no server available!
<129>Jul 27 11:26:22 node-1 haproxy[3801]: 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>Jul 27 11:26:22 node-1 haproxy[3801]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:22 node-1 haproxy[3801]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:22 node-1 haproxy[3801]: proxy glance-glare has no server available!
<129>Jul 27 11:26:22 node-1 haproxy[3801]: 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>Jul 27 11:26:22 node-1 haproxy[3801]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:22 node-1 haproxy[3801]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:22 node-1 haproxy[3801]: proxy neutron has no server available!
<129>Jul 27 11:26:22 node-1 haproxy[3801]: 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>Jul 27 11:26:22 node-1 haproxy[3801]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:22 node-1 haproxy[3801]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:22 node-1 haproxy[3801]: proxy glance-registry has no server available!
<129>Jul 27 11:26:23 node-1 haproxy[3801]: 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>Jul 27 11:26:23 node-1 haproxy[3801]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:23 node-1 haproxy[3801]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:23 node-1 haproxy[3801]: proxy mysqld has no server available!
<129>Jul 27 11:26:23 node-1 haproxy[3801]: 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>Jul 27 11:26:23 node-1 haproxy[3801]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:23 node-1 haproxy[3801]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:23 node-1 haproxy[3801]: proxy object-storage has no server available!
<129>Jul 27 11:26:23 node-1 haproxy[3801]: 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>Jul 27 11:26:23 node-1 haproxy[3801]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:23 node-1 haproxy[3801]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:23 node-1 haproxy[3801]: proxy aodh has no server available!
<129>Jul 27 11:26:23 node-1 haproxy[3801]: 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>Jul 27 11:26:23 node-1 haproxy[3801]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:23 node-1 haproxy[3801]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:23 node-1 haproxy[3801]: proxy ceilometer has no server available!
<129>Jul 27 11:26:23 node-1 haproxy[3801]: 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>Jul 27 11:26:23 node-1 haproxy[3801]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:23 node-1 haproxy[3801]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:23 node-1 haproxy[3801]: proxy nova-novncproxy has no server available!
<27>Jul 27 11:26:25 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:25 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:25 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:25 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:25 node-1 multipathd: uevent trigger error
<129>Jul 27 11:26:27 node-1 haproxy[5247]: 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>Jul 27 11:26:27 node-1 haproxy[5247]: Server horizon/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:27 node-1 haproxy[5247]: 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>Jul 27 11:26:27 node-1 haproxy[5247]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:27 node-1 haproxy[5247]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:27 node-1 haproxy[5247]: proxy keystone-1 has no server available!
<129>Jul 27 11:26:27 node-1 haproxy[5247]: 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>Jul 27 11:26:27 node-1 haproxy[5247]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:27 node-1 haproxy[5247]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:27 node-1 haproxy[5247]: proxy keystone-2 has no server available!
<129>Jul 27 11:26:27 node-1 haproxy[5247]: 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>Jul 27 11:26:27 node-1 haproxy[5247]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:27 node-1 haproxy[5247]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:27 node-1 haproxy[5247]: proxy nova-api has no server available!
<129>Jul 27 11:26:27 node-1 haproxy[5247]: 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>Jul 27 11:26:27 node-1 haproxy[5247]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:27 node-1 haproxy[5247]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:27 node-1 haproxy[5247]: proxy nova-metadata-api has no server available!
<129>Jul 27 11:26:28 node-1 haproxy[5256]: 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>Jul 27 11:26:28 node-1 haproxy[5256]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:28 node-1 haproxy[5256]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:28 node-1 haproxy[5256]: proxy cinder-api has no server available!
<129>Jul 27 11:26:28 node-1 haproxy[5256]: 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>Jul 27 11:26:28 node-1 haproxy[5256]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:28 node-1 haproxy[5256]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:28 node-1 haproxy[5256]: proxy glance-api has no server available!
<129>Jul 27 11:26:28 node-1 haproxy[5256]: 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>Jul 27 11:26:28 node-1 haproxy[5256]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:28 node-1 haproxy[5256]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:28 node-1 haproxy[5256]: proxy glance-glare has no server available!
<129>Jul 27 11:26:28 node-1 haproxy[5256]: 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>Jul 27 11:26:28 node-1 haproxy[5256]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:28 node-1 haproxy[5256]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:28 node-1 haproxy[5256]: proxy neutron has no server available!
<129>Jul 27 11:26:28 node-1 haproxy[5256]: 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>Jul 27 11:26:28 node-1 haproxy[5256]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:28 node-1 haproxy[5256]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:28 node-1 haproxy[5256]: proxy glance-registry has no server available!
<129>Jul 27 11:26:28 node-1 haproxy[5256]: 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>Jul 27 11:26:28 node-1 haproxy[5256]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:28 node-1 haproxy[5256]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:28 node-1 haproxy[5256]: proxy mysqld has no server available!
<129>Jul 27 11:26:28 node-1 haproxy[5256]: 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>Jul 27 11:26:28 node-1 haproxy[5256]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:28 node-1 haproxy[5256]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:28 node-1 haproxy[5256]: proxy object-storage has no server available!
<129>Jul 27 11:26:28 node-1 haproxy[5256]: 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>Jul 27 11:26:29 node-1 haproxy[5256]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:29 node-1 haproxy[5256]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:29 node-1 haproxy[5256]: proxy aodh has no server available!
<129>Jul 27 11:26:29 node-1 haproxy[5256]: 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>Jul 27 11:26:29 node-1 haproxy[5256]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:29 node-1 haproxy[5256]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:29 node-1 haproxy[5256]: proxy ceilometer has no server available!
<129>Jul 27 11:26:29 node-1 haproxy[5256]: 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>Jul 27 11:26:29 node-1 haproxy[5256]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:29 node-1 haproxy[5256]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:29 node-1 haproxy[5256]: proxy nova-novncproxy has no server available!
<27>Jul 27 11:26:30 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:30 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:30 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:30 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:30 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:30 node-1 multipathd: uevent trigger error
<129>Jul 27 11:26:33 node-1 haproxy[6646]: 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>Jul 27 11:26:33 node-1 haproxy[6646]: Server horizon/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:33 node-1 haproxy[6646]: 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>Jul 27 11:26:33 node-1 haproxy[6646]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:33 node-1 haproxy[6646]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:33 node-1 haproxy[6646]: proxy keystone-1 has no server available!
<129>Jul 27 11:26:33 node-1 haproxy[6646]: 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>Jul 27 11:26:33 node-1 haproxy[6646]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:33 node-1 haproxy[6646]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:33 node-1 haproxy[6646]: proxy keystone-2 has no server available!
<129>Jul 27 11:26:33 node-1 haproxy[6646]: 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>Jul 27 11:26:33 node-1 haproxy[6646]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:33 node-1 haproxy[6646]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:33 node-1 haproxy[6646]: proxy nova-api has no server available!
<129>Jul 27 11:26:33 node-1 haproxy[6646]: 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>Jul 27 11:26:33 node-1 haproxy[6646]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:33 node-1 haproxy[6646]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:33 node-1 haproxy[6646]: proxy nova-metadata-api has no server available!
<129>Jul 27 11:26:33 node-1 haproxy[6646]: 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>Jul 27 11:26:33 node-1 haproxy[6646]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:33 node-1 haproxy[6646]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:33 node-1 haproxy[6646]: proxy cinder-api has no server available!
<129>Jul 27 11:26:34 node-1 haproxy[6650]: 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>Jul 27 11:26:34 node-1 haproxy[6650]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:34 node-1 haproxy[6650]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:34 node-1 haproxy[6650]: proxy glance-api has no server available!
<129>Jul 27 11:26:34 node-1 haproxy[6650]: 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>Jul 27 11:26:34 node-1 haproxy[6650]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:34 node-1 haproxy[6650]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:34 node-1 haproxy[6650]: proxy glance-glare has no server available!
<129>Jul 27 11:26:34 node-1 haproxy[6650]: 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>Jul 27 11:26:34 node-1 haproxy[6650]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:34 node-1 haproxy[6650]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:34 node-1 haproxy[6650]: proxy neutron has no server available!
<129>Jul 27 11:26:34 node-1 haproxy[6650]: 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>Jul 27 11:26:34 node-1 haproxy[6650]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:34 node-1 haproxy[6650]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:34 node-1 haproxy[6650]: proxy glance-registry has no server available!
<129>Jul 27 11:26:34 node-1 haproxy[6650]: 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>Jul 27 11:26:34 node-1 haproxy[6650]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:34 node-1 haproxy[6650]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:34 node-1 haproxy[6650]: proxy mysqld has no server available!
<129>Jul 27 11:26:34 node-1 haproxy[6650]: 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>Jul 27 11:26:34 node-1 haproxy[6650]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:34 node-1 haproxy[6650]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:34 node-1 haproxy[6650]: proxy object-storage has no server available!
<129>Jul 27 11:26:34 node-1 haproxy[6650]: 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>Jul 27 11:26:34 node-1 haproxy[6650]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:34 node-1 haproxy[6650]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:34 node-1 haproxy[6650]: proxy aodh has no server available!
<129>Jul 27 11:26:34 node-1 haproxy[6650]: 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>Jul 27 11:26:34 node-1 haproxy[6650]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:34 node-1 haproxy[6650]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:34 node-1 haproxy[6650]: proxy ceilometer has no server available!
<129>Jul 27 11:26:34 node-1 haproxy[6650]: 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>Jul 27 11:26:34 node-1 haproxy[6650]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:34 node-1 haproxy[6650]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:34 node-1 haproxy[6650]: proxy heat-api has no server available!
<129>Jul 27 11:26:35 node-1 haproxy[6650]: 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>Jul 27 11:26:35 node-1 haproxy[6650]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:35 node-1 haproxy[6650]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:35 node-1 haproxy[6650]: proxy heat-api-cfn has no server available!
<129>Jul 27 11:26:35 node-1 haproxy[6650]: 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>Jul 27 11:26:35 node-1 haproxy[6650]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:35 node-1 haproxy[6650]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:35 node-1 haproxy[6650]: proxy heat-api-cloudwatch has no server available!
<129>Jul 27 11:26:35 node-1 haproxy[6650]: 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>Jul 27 11:26:35 node-1 haproxy[6650]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:26:35 node-1 haproxy[6650]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 11:26:35 node-1 haproxy[6650]: proxy nova-novncproxy has no server available!
<27>Jul 27 11:26:36 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:36 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:36 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:36 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:36 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:36 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:36 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:40 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:40 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:40 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:40 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:40 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:40 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:40 node-1 multipathd: uevent trigger error
<27>Jul 27 11:26:50 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 27 11:27:14 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>Jul 27 11:27:16 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 27 11:27:38 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 11:27:44 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 11:28:03 node-1 multipathd: uevent trigger error
<27>Jul 27 11:28:03 node-1 multipathd: uevent trigger error
<27>Jul 27 11:28:03 node-1 multipathd: uevent trigger error
<27>Jul 27 11:28:03 node-1 multipathd: uevent trigger error
<27>Jul 27 11:28:03 node-1 multipathd: uevent trigger error
<27>Jul 27 11:28:03 node-1 multipathd: uevent trigger error
<27>Jul 27 11:29:53 node-1 multipathd: uevent trigger error
<27>Jul 27 11:29:53 node-1 multipathd: uevent trigger error
<27>Jul 27 11:29:53 node-1 multipathd: uevent trigger error
<27>Jul 27 11:29:53 node-1 multipathd: uevent trigger error
<27>Jul 27 11:29:53 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:00 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:00 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:00 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:00 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:00 node-1 multipathd: uevent trigger error
<43>Jul 27 11:30:14 node-1 apache2_error [Wed Jul 27 11:30:13.394389 2016] [mpm_event:notice] [pid 12764:tid 140489589589888] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 27 11:30:14 node-1 apache2_error [Wed Jul 27 11:30:13.394497 2016] [core:notice] [pid 12764:tid 140489589589888] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 11:30:22 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:22 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:22 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:22 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:22 node-1 multipathd: uevent trigger error
<43>Jul 27 11:30:24 node-1 apache2_error [Wed Jul 27 11:30:16.500908 2016] [mpm_event:notice] [pid 12764:tid 140489589589888] AH00491: caught SIGTERM, shutting down
<43>Jul 27 11:30:24 node-1 apache2_error [Wed Jul 27 11:30:17.590091 2016] [mpm_worker:notice] [pid 13260:tid 140284514961280] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 27 11:30:24 node-1 apache2_error [Wed Jul 27 11:30:17.590152 2016] [core:notice] [pid 13260:tid 140284514961280] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 11:30:25 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:25 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:25 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:25 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:25 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:28 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:28 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:28 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:28 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:28 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:28 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:30:40 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 11:31:14 node-1 multipathd: uevent trigger error
<27>Jul 27 11:31:14 node-1 multipathd: uevent trigger error
<27>Jul 27 11:31:14 node-1 multipathd: uevent trigger error
<27>Jul 27 11:31:14 node-1 multipathd: uevent trigger error
<27>Jul 27 11:31:14 node-1 multipathd: uevent trigger error
<43>Jul 27 11:31:14 node-1 apache2_error [Wed Jul 27 11:31:11.182133 2016] [mpm_worker:notice] [pid 13260:tid 140284514961280] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 11:31:14 node-1 apache2_error [Wed Jul 27 11:31:11.190167 2016] [mpm_worker:warn] [pid 13260:tid 140284514961280] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 11:31:14 node-1 apache2_error [Wed Jul 27 11:31:11.191023 2016] [mpm_worker:notice] [pid 13260:tid 140284514961280] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 27 11:31:14 node-1 apache2_error [Wed Jul 27 11:31:11.191037 2016] [core:notice] [pid 13260:tid 140284514961280] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 11:31:19 node-1 multipathd: uevent trigger error
<27>Jul 27 11:31:19 node-1 multipathd: uevent trigger error
<27>Jul 27 11:31:19 node-1 multipathd: uevent trigger error
<27>Jul 27 11:31:19 node-1 multipathd: uevent trigger error
<27>Jul 27 11:31:19 node-1 multipathd: uevent trigger error
<27>Jul 27 11:31:19 node-1 multipathd: uevent trigger error
<27>Jul 27 11:31:19 node-1 multipathd: uevent trigger error
<43>Jul 27 11:32:34 node-1 apache2_error [Wed Jul 27 11:32:27.645960 2016] [mpm_worker:notice] [pid 13260:tid 140284514961280] AH00295: caught SIGTERM, shutting down
<43>Jul 27 11:32:34 node-1 apache2_error [Wed Jul 27 11:32:28.387161 2016] [mpm_worker:notice] [pid 4066:tid 140222429190016] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 11:32:34 node-1 apache2_error [Wed Jul 27 11:32:28.387189 2016] [core:notice] [pid 4066:tid 140222429190016] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 27 11:33:15 node-1 apache2_error [Wed Jul 27 11:33:12.675852 2016] [mpm_worker:notice] [pid 4066:tid 140222429190016] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 11:33:15 node-1 apache2_error [Wed Jul 27 11:33:12.683202 2016] [mpm_worker:warn] [pid 4066:tid 140222429190016] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 11:33:15 node-1 apache2_error [Wed Jul 27 11:33:12.690073 2016] [mpm_worker:notice] [pid 4066:tid 140222429190016] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 11:33:15 node-1 apache2_error [Wed Jul 27 11:33:12.690107 2016] [core:notice] [pid 4066:tid 140222429190016] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 11:33:42 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 11:34:32 node-1 multipathd: uevent trigger error
<27>Jul 27 11:34:32 node-1 multipathd: uevent trigger error
<27>Jul 27 11:34:32 node-1 multipathd: uevent trigger error
<27>Jul 27 11:34:32 node-1 multipathd: uevent trigger error
<27>Jul 27 11:34:32 node-1 multipathd: uevent trigger error
<27>Jul 27 11:34:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:34:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:34:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:34:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:34:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:34:37 node-1 multipathd: uevent trigger error
<27>Jul 27 11:34:53 node-1 multipathd: uevent trigger error
<27>Jul 27 11:34:53 node-1 multipathd: uevent trigger error
<27>Jul 27 11:34:53 node-1 multipathd: uevent trigger error
<27>Jul 27 11:34:53 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:15 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:15 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:15 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:15 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:15 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:15 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:19 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:19 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:19 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:20 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:20 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:20 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:33 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:33 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:33 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:33 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:33 node-1 multipathd: uevent trigger error
<27>Jul 27 11:35:33 node-1 multipathd: uevent trigger error
<27>Jul 27 11:36:32 node-1 multipathd: uevent trigger error
<27>Jul 27 11:36:32 node-1 multipathd: uevent trigger error
<27>Jul 27 11:36:32 node-1 multipathd: uevent trigger error
<27>Jul 27 11:36:32 node-1 multipathd: uevent trigger error
<27>Jul 27 11:36:32 node-1 multipathd: uevent trigger error
<27>Jul 27 11:36:44 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 11:37:48 node-1 multipathd: uevent trigger error
<27>Jul 27 11:37:48 node-1 multipathd: uevent trigger error
<27>Jul 27 11:37:48 node-1 multipathd: uevent trigger error
<27>Jul 27 11:37:48 node-1 multipathd: uevent trigger error
<27>Jul 27 11:37:48 node-1 multipathd: uevent trigger error
<27>Jul 27 11:37:48 node-1 multipathd: uevent trigger error
<27>Jul 27 11:38:46 node-1 multipathd: uevent trigger error
<27>Jul 27 11:38:46 node-1 multipathd: uevent trigger error
<27>Jul 27 11:38:46 node-1 multipathd: uevent trigger error
<27>Jul 27 11:38:46 node-1 multipathd: uevent trigger error
<27>Jul 27 11:38:46 node-1 multipathd: uevent trigger error
<27>Jul 27 11:38:52 node-1 multipathd: uevent trigger error
<27>Jul 27 11:38:52 node-1 multipathd: uevent trigger error
<27>Jul 27 11:38:52 node-1 multipathd: uevent trigger error
<27>Jul 27 11:38:52 node-1 multipathd: uevent trigger error
<27>Jul 27 11:38:52 node-1 multipathd: uevent trigger error
<27>Jul 27 11:38:52 node-1 multipathd: uevent trigger error
<27>Jul 27 11:39:16 node-1 multipathd: uevent trigger error
<27>Jul 27 11:39:16 node-1 multipathd: uevent trigger error
<27>Jul 27 11:39:16 node-1 multipathd: uevent trigger error
<27>Jul 27 11:39:16 node-1 multipathd: uevent trigger error
<27>Jul 27 11:39:16 node-1 multipathd: uevent trigger error
<27>Jul 27 11:39:16 node-1 multipathd: uevent trigger error
<27>Jul 27 11:39:46 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 11:41:43 node-1 multipathd: uevent trigger error
<27>Jul 27 11:41:43 node-1 multipathd: uevent trigger error
<27>Jul 27 11:41:43 node-1 multipathd: uevent trigger error
<27>Jul 27 11:41:43 node-1 multipathd: uevent trigger error
<27>Jul 27 11:41:43 node-1 multipathd: uevent trigger error
<27>Jul 27 11:41:43 node-1 multipathd: uevent trigger error
<27>Jul 27 11:41:58 node-1 multipathd: uevent trigger error
<27>Jul 27 11:41:58 node-1 multipathd: uevent trigger error
<27>Jul 27 11:41:58 node-1 multipathd: uevent trigger error
<27>Jul 27 11:41:58 node-1 multipathd: uevent trigger error
<27>Jul 27 11:41:58 node-1 multipathd: uevent trigger error
<27>Jul 27 11:41:58 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:04 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:04 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:04 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:04 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:04 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:04 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:04 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:45 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:45 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:45 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:45 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:45 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:48 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 11:42:50 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:50 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:50 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:50 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:50 node-1 multipathd: uevent trigger error
<27>Jul 27 11:42:50 node-1 multipathd: uevent trigger error
<27>Jul 27 11:43:15 node-1 multipathd: uevent trigger error
<27>Jul 27 11:43:15 node-1 multipathd: uevent trigger error
<27>Jul 27 11:43:15 node-1 multipathd: uevent trigger error
<27>Jul 27 11:43:15 node-1 multipathd: uevent trigger error
<27>Jul 27 11:43:15 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:01 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:01 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:01 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:01 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:01 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:08 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Jul 27 11:44:08 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Jul 27 11:44:08 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Jul 27 11:44:09 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Jul 27 11:44:09 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Jul 27 11:44:10 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:10 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:10 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:10 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:10 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:23 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:23 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:23 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:23 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:23 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:38 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:38 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:38 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:38 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:38 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:38 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:38 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:38 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:57 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:57 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:57 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:57 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:57 node-1 multipathd: uevent trigger error
<27>Jul 27 11:44:57 node-1 multipathd: uevent trigger error
<27>Jul 27 11:45:49 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 11:47:20 node-1 multipathd: uevent trigger error
<27>Jul 27 11:47:20 node-1 multipathd: uevent trigger error
<27>Jul 27 11:47:20 node-1 multipathd: uevent trigger error
<27>Jul 27 11:47:20 node-1 multipathd: uevent trigger error
<27>Jul 27 11:47:20 node-1 multipathd: uevent trigger error
<27>Jul 27 11:47:35 node-1 multipathd: uevent trigger error
<27>Jul 27 11:47:35 node-1 multipathd: uevent trigger error
<27>Jul 27 11:47:35 node-1 multipathd: uevent trigger error
<27>Jul 27 11:47:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:47:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:47:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:47:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:47:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:47:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:47:43 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Jul 27 11:48:50 node-1 multipathd: uevent trigger error
<27>Jul 27 11:48:50 node-1 multipathd: uevent trigger error
<27>Jul 27 11:48:50 node-1 multipathd: uevent trigger error
<27>Jul 27 11:48:50 node-1 multipathd: uevent trigger error
<27>Jul 27 11:48:50 node-1 multipathd: uevent trigger error
<27>Jul 27 11:48:51 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 11:49:00 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:00 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:00 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:00 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:00 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:49 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:49 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:49 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:49 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:49 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:54 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:54 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:54 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:54 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:54 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:58 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:58 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:58 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:58 node-1 multipathd: uevent trigger error
<27>Jul 27 11:49:58 node-1 multipathd: uevent trigger error
<27>Jul 27 11:50:11 node-1 multipathd: uevent trigger error
<27>Jul 27 11:50:11 node-1 multipathd: uevent trigger error
<27>Jul 27 11:50:11 node-1 multipathd: uevent trigger error
<27>Jul 27 11:50:11 node-1 multipathd: uevent trigger error
<27>Jul 27 11:50:11 node-1 multipathd: uevent trigger error
<27>Jul 27 11:50:17 node-1 multipathd: uevent trigger error
<27>Jul 27 11:50:17 node-1 multipathd: uevent trigger error
<27>Jul 27 11:50:17 node-1 multipathd: uevent trigger error
<27>Jul 27 11:50:17 node-1 multipathd: uevent trigger error
<27>Jul 27 11:50:17 node-1 multipathd: uevent trigger error
<27>Jul 27 11:50:17 node-1 multipathd: uevent trigger error
<27>Jul 27 11:50:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:50:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:50:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:50:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:50:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:51:47 node-1 multipathd: uevent trigger error
<27>Jul 27 11:51:47 node-1 multipathd: uevent trigger error
<27>Jul 27 11:51:47 node-1 multipathd: uevent trigger error
<27>Jul 27 11:51:47 node-1 multipathd: uevent trigger error
<27>Jul 27 11:51:47 node-1 multipathd: uevent trigger error
<27>Jul 27 11:51:47 node-1 multipathd: uevent trigger error
<27>Jul 27 11:51:52 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 11:52:03 node-1 multipathd: uevent trigger error
<27>Jul 27 11:52:03 node-1 multipathd: uevent trigger error
<27>Jul 27 11:52:03 node-1 multipathd: uevent trigger error
<27>Jul 27 11:52:03 node-1 multipathd: uevent trigger error
<27>Jul 27 11:52:03 node-1 multipathd: uevent trigger error
<11>Jul 27 11:52:16 node-1 liberasurecode[70959]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:16 node-1 liberasurecode[70959]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:16 node-1 liberasurecode[70959]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:16 node-1 liberasurecode[70959]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:16 node-1 liberasurecode[70983]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:16 node-1 liberasurecode[70983]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:16 node-1 liberasurecode[70983]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:16 node-1 liberasurecode[70983]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:19 node-1 liberasurecode[71397]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:19 node-1 liberasurecode[71397]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:19 node-1 liberasurecode[71397]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:19 node-1 liberasurecode[71397]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:24 node-1 liberasurecode[72212]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:24 node-1 liberasurecode[72212]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:24 node-1 liberasurecode[72212]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:24 node-1 liberasurecode[72212]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:24 node-1 liberasurecode[72252]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:24 node-1 liberasurecode[72252]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:24 node-1 liberasurecode[72252]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:24 node-1 liberasurecode[72252]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:24 node-1 liberasurecode[72301]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:24 node-1 liberasurecode[72301]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:24 node-1 liberasurecode[72301]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:24 node-1 liberasurecode[72301]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:25 node-1 liberasurecode[72364]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:25 node-1 liberasurecode[72364]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:25 node-1 liberasurecode[72364]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:25 node-1 liberasurecode[72364]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:25 node-1 liberasurecode[72378]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:25 node-1 liberasurecode[72378]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:25 node-1 liberasurecode[72378]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:25 node-1 liberasurecode[72378]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:25 node-1 liberasurecode[72390]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:25 node-1 liberasurecode[72390]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:25 node-1 liberasurecode[72390]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:25 node-1 liberasurecode[72390]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:25 node-1 liberasurecode[72402]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:25 node-1 liberasurecode[72402]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:25 node-1 liberasurecode[72402]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:25 node-1 liberasurecode[72402]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:33 node-1 liberasurecode[73931]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:33 node-1 liberasurecode[73931]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:33 node-1 liberasurecode[73931]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:52:33 node-1 liberasurecode[73931]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 27 11:52:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:52:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:52:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:52:42 node-1 multipathd: uevent trigger error
<43>Jul 27 11:53:36 node-1 apache2_error [Wed Jul 27 11:53:28.932058 2016] [mpm_worker:notice] [pid 4066:tid 140222429190016] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 11:53:36 node-1 apache2_error [Wed Jul 27 11:53:29.317689 2016] [mpm_worker:warn] [pid 4066:tid 140222429190016] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 11:53:36 node-1 apache2_error [Wed Jul 27 11:53:29.324471 2016] [mpm_worker:notice] [pid 4066:tid 140222429190016] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 11:53:36 node-1 apache2_error [Wed Jul 27 11:53:29.324513 2016] [core:notice] [pid 4066:tid 140222429190016] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 27 11:54:06 node-1 apache2_error [Wed Jul 27 11:54:06.529615 2016] [mpm_worker:notice] [pid 4066:tid 140222429190016] AH00297: SIGUSR1 received.  Doing graceful restart
<27>Jul 27 11:54:10 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:11 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:11 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:11 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:11 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:11 node-1 multipathd: uevent trigger error
<43>Jul 27 11:54:16 node-1 apache2_error [Wed Jul 27 11:54:06.912888 2016] [mpm_worker:warn] [pid 4066:tid 140222429190016] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 11:54:16 node-1 apache2_error [Wed Jul 27 11:54:06.923614 2016] [mpm_worker:notice] [pid 4066:tid 140222429190016] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 11:54:16 node-1 apache2_error [Wed Jul 27 11:54:06.923651 2016] [core:notice] [pid 4066:tid 140222429190016] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 11:54:17 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:17 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:17 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:17 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:17 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:24 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:24 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:24 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:24 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:24 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:24 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:24 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:33 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:33 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:33 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:33 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:33 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:49 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:49 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:49 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:49 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:49 node-1 multipathd: uevent trigger error
<27>Jul 27 11:54:54 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<11>Jul 27 11:55:01 node-1 liberasurecode[102107]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:55:01 node-1 liberasurecode[102107]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:55:01 node-1 liberasurecode[102107]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 11:55:01 node-1 liberasurecode[102107]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 27 11:55:11 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:19 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 27 11:55:27 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:27 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:27 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:27 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:27 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:32 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:32 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:32 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:32 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:32 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:32 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:42 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:48 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:48 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:48 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:48 node-1 multipathd: uevent trigger error
<27>Jul 27 11:55:48 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:01 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:01 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:01 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:01 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:01 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:01 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:06 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:06 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:06 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:06 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:21 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:21 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:21 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:21 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:21 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:24 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 11:56:34 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:34 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:34 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:34 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:34 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:34 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:34 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:39 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:39 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:39 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:39 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:44 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:44 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:44 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:44 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:44 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:49 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:49 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:49 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:49 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:49 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:49 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:54 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:54 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:54 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:54 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:54 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:58 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:58 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:58 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:58 node-1 multipathd: uevent trigger error
<27>Jul 27 11:56:58 node-1 multipathd: uevent trigger error
<27>Jul 27 11:58:35 node-1 multipathd: uevent trigger error
<27>Jul 27 11:58:35 node-1 multipathd: uevent trigger error
<27>Jul 27 11:58:35 node-1 multipathd: uevent trigger error
<27>Jul 27 11:58:35 node-1 multipathd: uevent trigger error
<27>Jul 27 11:58:35 node-1 multipathd: uevent trigger error
<27>Jul 27 11:58:44 node-1 multipathd: uevent trigger error
<27>Jul 27 11:58:44 node-1 multipathd: uevent trigger error
<27>Jul 27 11:58:44 node-1 multipathd: uevent trigger error
<27>Jul 27 11:58:44 node-1 multipathd: uevent trigger error
<27>Jul 27 11:58:44 node-1 multipathd: uevent trigger error
<27>Jul 27 11:58:44 node-1 multipathd: uevent trigger error
<27>Jul 27 11:58:55 node-1 multipathd: uevent trigger error
<27>Jul 27 11:58:55 node-1 multipathd: uevent trigger error
<27>Jul 27 11:58:55 node-1 multipathd: uevent trigger error
<27>Jul 27 11:58:55 node-1 multipathd: uevent trigger error
<27>Jul 27 11:58:55 node-1 multipathd: uevent trigger error
<129>Jul 27 11:59:04 node-1 haproxy[145970]: 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>Jul 27 11:59:05 node-1 haproxy[145970]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 11:59:44 node-1 haproxy[145970]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 27 11:59:50 node-1 multipathd: uevent trigger error
<27>Jul 27 11:59:50 node-1 multipathd: uevent trigger error
<27>Jul 27 11:59:50 node-1 multipathd: uevent trigger error
<27>Jul 27 11:59:50 node-1 multipathd: uevent trigger error
<27>Jul 27 11:59:50 node-1 multipathd: uevent trigger error
<27>Jul 27 11:59:56 node-1 multipathd: uevent trigger error
<27>Jul 27 11:59:56 node-1 multipathd: uevent trigger error
<27>Jul 27 11:59:56 node-1 multipathd: uevent trigger error
<27>Jul 27 11:59:56 node-1 multipathd: uevent trigger error
<27>Jul 27 11:59:56 node-1 multipathd: uevent trigger error
<27>Jul 27 12:00:01 node-1 multipathd: uevent trigger error
<27>Jul 27 12:00:01 node-1 multipathd: uevent trigger error
<27>Jul 27 12:00:01 node-1 multipathd: uevent trigger error
<27>Jul 27 12:00:01 node-1 multipathd: uevent trigger error
<27>Jul 27 12:00:01 node-1 multipathd: uevent trigger error
<27>Jul 27 12:00:01 node-1 multipathd: uevent trigger error
<11>Jul 27 12:00:02 node-1 liberasurecode[163669]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 12:00:02 node-1 liberasurecode[163669]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 12:00:02 node-1 liberasurecode[163669]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 12:00:02 node-1 liberasurecode[163669]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 27 12:00:12 node-1 multipathd: uevent trigger error
<27>Jul 27 12:00:12 node-1 multipathd: uevent trigger error
<27>Jul 27 12:00:12 node-1 multipathd: uevent trigger error
<27>Jul 27 12:00:12 node-1 multipathd: uevent trigger error
<27>Jul 27 12:00:12 node-1 multipathd: uevent trigger error
