Jul 24 00:10:01 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8371" x-info="http://www.rsyslog.com"] start
Jul 24 00:10:01 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 24 00:10:01 node-2 rsyslogd: rsyslogd's groupid changed to 104
Jul 24 00:10:01 node-2 rsyslogd: rsyslogd's userid changed to 101
Jul 24 00:10:01 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 24 00:10:01 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 24 00:10:01 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 24 00:10:01 node-2 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 24 00:10:01 node-2 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=38e643b0-844a-44d7-a2fb-e9cb9ee42094 nomdmonddf nomdmonisw
Jul 24 00:10:01 node-2 kernel: [    0.000000] KERNEL supported cpus:
Jul 24 00:10:01 node-2 kernel: [    0.000000]   Intel GenuineIntel
Jul 24 00:10:01 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Jul 24 00:10:01 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Jul 24 00:10:01 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 24 00:10:01 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 24 00:10:01 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 24 00:10:01 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 24 00:10:01 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Jul 24 00:10:01 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Jul 24 00:10:01 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Jul 24 00:10:01 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Jul 24 00:10:01 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Jul 24 00:10:01 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 24 00:10:01 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 24 00:10:01 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 24 00:10:01 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 24 00:10:01 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 24 00:10:01 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 24 00:10:01 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 24 00:10:01 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 24 00:10:01 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 24 00:10:01 node-2 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 24 00:10:01 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 24 00:10:01 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 24 00:10:01 node-2 kernel: [    0.000000] No AGP bridge found
Jul 24 00:10:01 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 24 00:10:01 node-2 kernel: [    0.000000] MTRR default type: write-back
Jul 24 00:10:01 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 24 00:10:01 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Jul 24 00:10:01 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 24 00:10:01 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 24 00:10:01 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 24 00:10:01 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 24 00:10:01 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 24 00:10:01 node-2 kernel: [    0.000000]   2 disabled
Jul 24 00:10:01 node-2 kernel: [    0.000000]   3 disabled
Jul 24 00:10:01 node-2 kernel: [    0.000000]   4 disabled
Jul 24 00:10:01 node-2 kernel: [    0.000000]   5 disabled
Jul 24 00:10:01 node-2 kernel: [    0.000000]   6 disabled
Jul 24 00:10:01 node-2 kernel: [    0.000000]   7 disabled
Jul 24 00:10:01 node-2 kernel: [    0.000000]   8 disabled
Jul 24 00:10:01 node-2 kernel: [    0.000000]   9 disabled
Jul 24 00:10:01 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 24 00:10:01 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 24 00:10:01 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 24 00:10:01 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 24 00:10:01 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 24 00:10:01 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Jul 24 00:10:01 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 24 00:10:01 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 24 00:10:01 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 24 00:10:01 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 24 00:10:01 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 24 00:10:01 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 24 00:10:01 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 24 00:10:01 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 24 00:10:01 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 24 00:10:01 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Jul 24 00:10:01 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 24 00:10:01 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 24 00:10:01 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 24 00:10:01 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 24 00:10:01 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 24 00:10:01 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 24 00:10:01 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 24 00:10:01 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 24 00:10:01 node-2 kernel: [    0.000000] Zone ranges:
Jul 24 00:10:01 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] Movable zone start for each node
Jul 24 00:10:01 node-2 kernel: [    0.000000] Early memory node ranges
Jul 24 00:10:01 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] On node 0 totalpages: 4125855
Jul 24 00:10:01 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 24 00:10:01 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 24 00:10:01 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 24 00:10:01 node-2 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Jul 24 00:10:01 node-2 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Jul 24 00:10:01 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 24 00:10:01 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 24 00:10:01 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 24 00:10:01 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 24 00:10:01 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 24 00:10:01 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 24 00:10:01 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 24 00:10:01 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 24 00:10:01 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 24 00:10:01 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 24 00:10:01 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 24 00:10:01 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 24 00:10:01 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 24 00:10:01 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 24 00:10:01 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 24 00:10:01 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 24 00:10:01 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 24 00:10:01 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 24 00:10:01 node-2 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 24 00:10:01 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Jul 24 00:10:01 node-2 kernel: [    0.000000] Policy zone: Normal
Jul 24 00:10:01 node-2 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=38e643b0-844a-44d7-a2fb-e9cb9ee42094 nomdmonddf nomdmonisw
Jul 24 00:10:01 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 24 00:10:01 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 24 00:10:01 node-2 kernel: [    0.000000] Checking aperture...
Jul 24 00:10:01 node-2 kernel: [    0.000000] No AGP bridge found
Jul 24 00:10:01 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 24 00:10:01 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 24 00:10:01 node-2 kernel: [    0.000000] Memory: 32653460K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Jul 24 00:10:01 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 24 00:10:01 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 24 00:10:01 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 24 00:10:01 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 24 00:10:01 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 24 00:10:01 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 24 00:10:01 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 24 00:10:01 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 24 00:10:01 node-2 kernel: [    0.000000] console [tty0] enabled
Jul 24 00:10:01 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 24 00:10:01 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 24 00:10:01 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 24 00:10:01 node-2 kernel: [    0.000000] hpet clockevent registered
Jul 24 00:10:01 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 24 00:10:01 node-2 kernel: [    0.004000] tsc: Detected 3492.246 MHz processor
Jul 24 00:10:01 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.49 BogoMIPS (lpj=13968984)
Jul 24 00:10:01 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 24 00:10:01 node-2 kernel: [    0.000042] Security Framework initialized
Jul 24 00:10:01 node-2 kernel: [    0.000061] AppArmor: AppArmor initialized
Jul 24 00:10:01 node-2 kernel: [    0.000063] Yama: becoming mindful.
Jul 24 00:10:01 node-2 kernel: [    0.001451] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 24 00:10:01 node-2 kernel: [    0.006367] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 24 00:10:01 node-2 kernel: [    0.008295] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 24 00:10:01 node-2 kernel: [    0.008323] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 24 00:10:01 node-2 kernel: [    0.008614] Initializing cgroup subsys memory
Jul 24 00:10:01 node-2 kernel: [    0.008622] Initializing cgroup subsys devices
Jul 24 00:10:01 node-2 kernel: [    0.008624] Initializing cgroup subsys freezer
Jul 24 00:10:01 node-2 kernel: [    0.008626] Initializing cgroup subsys blkio
Jul 24 00:10:01 node-2 kernel: [    0.008627] Initializing cgroup subsys perf_event
Jul 24 00:10:01 node-2 kernel: [    0.008629] Initializing cgroup subsys hugetlb
Jul 24 00:10:01 node-2 kernel: [    0.008648] CPU: Physical Processor ID: 0
Jul 24 00:10:01 node-2 kernel: [    0.008650] CPU: Processor Core ID: 0
Jul 24 00:10:01 node-2 kernel: [    0.008654] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 24 00:10:01 node-2 kernel: [    0.008654] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 24 00:10:01 node-2 kernel: [    0.009348] mce: CPU supports 22 MCE banks
Jul 24 00:10:01 node-2 kernel: [    0.009375] CPU0: Thermal monitoring enabled (TM1)
Jul 24 00:10:01 node-2 kernel: [    0.009396] process: using mwait in idle threads
Jul 24 00:10:01 node-2 kernel: [    0.009399] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 24 00:10:01 node-2 kernel: [    0.009399] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 24 00:10:01 node-2 kernel: [    0.009399] tlb_flushall_shift: 6
Jul 24 00:10:01 node-2 kernel: [    0.009488] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 24 00:10:01 node-2 kernel: [    0.010214] ACPI: Core revision 20131115
Jul 24 00:10:01 node-2 kernel: [    0.022902] ACPI: All ACPI Tables successfully acquired
Jul 24 00:10:01 node-2 kernel: [    0.023066] ftrace: allocating 28617 entries in 112 pages
Jul 24 00:10:01 node-2 kernel: [    0.031878] dmar: Host address width 46
Jul 24 00:10:01 node-2 kernel: [    0.031880] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 24 00:10:01 node-2 kernel: [    0.031886] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 24 00:10:01 node-2 kernel: [    0.031888] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 24 00:10:01 node-2 kernel: [    0.031892] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 24 00:10:01 node-2 kernel: [    0.031893] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 24 00:10:01 node-2 kernel: [    0.031895] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 24 00:10:01 node-2 kernel: [    0.031896] dmar: ATSR flags: 0x0
Jul 24 00:10:01 node-2 kernel: [    0.031897] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 24 00:10:01 node-2 kernel: [    0.031898] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 24 00:10:01 node-2 kernel: [    0.032014] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 24 00:10:01 node-2 kernel: [    0.032015] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 24 00:10:01 node-2 kernel: [    0.032016] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 24 00:10:01 node-2 kernel: [    0.032017] HPET id 0 under DRHD base 0xc7ffc000
Jul 24 00:10:01 node-2 kernel: [    0.032018] Your BIOS is broken and requested that x2apic be disabled.
Jul 24 00:10:01 node-2 kernel: [    0.032018] This will slightly decrease performance.
Jul 24 00:10:01 node-2 kernel: [    0.032018] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 24 00:10:01 node-2 kernel: [    0.032449] Enabled IRQ remapping in xapic mode
Jul 24 00:10:01 node-2 kernel: [    0.032451] x2apic not enabled, IRQ remapping is in xapic mode
Jul 24 00:10:01 node-2 kernel: [    0.032454] Switched APIC routing to physical flat.
Jul 24 00:10:01 node-2 kernel: [    0.033079] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 24 00:10:01 node-2 kernel: [    0.072732] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 24 00:10:01 node-2 kernel: [    0.072738] TSC deadline timer enabled
Jul 24 00:10:01 node-2 kernel: [    0.072745] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 24 00:10:01 node-2 kernel: [    0.072751] ... version:                3
Jul 24 00:10:01 node-2 kernel: [    0.072752] ... bit width:              48
Jul 24 00:10:01 node-2 kernel: [    0.072753] ... generic registers:      4
Jul 24 00:10:01 node-2 kernel: [    0.072753] ... value mask:             0000ffffffffffff
Jul 24 00:10:01 node-2 kernel: [    0.072755] ... max period:             0000ffffffffffff
Jul 24 00:10:01 node-2 kernel: [    0.072755] ... fixed-purpose events:   3
Jul 24 00:10:01 node-2 kernel: [    0.072756] ... event mask:             000000070000000f
Jul 24 00:10:01 node-2 kernel: [    0.074176] x86: Booting SMP configuration:
Jul 24 00:10:01 node-2 kernel: [    0.088284] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 24 00:10:01 node-2 kernel: [    0.074178] .... node  #0, CPUs:        #1  #2  #3
Jul 24 00:10:01 node-2 kernel: [    0.116198] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 24 00:10:01 node-2 kernel: [    0.270362] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 24 00:10:01 node-2 kernel: [    0.325978] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 24 00:10:01 node-2 kernel: [    0.383035] x86: Booted up 2 nodes, 16 CPUs
Jul 24 00:10:01 node-2 kernel: [    0.383039] smpboot: Total of 16 processors activated (111783.95 BogoMIPS)
Jul 24 00:10:01 node-2 kernel: [    0.407552] devtmpfs: initialized
Jul 24 00:10:01 node-2 kernel: [    0.410672] EVM: security.selinux
Jul 24 00:10:01 node-2 kernel: [    0.410674] EVM: security.SMACK64
Jul 24 00:10:01 node-2 kernel: [    0.410675] EVM: security.ima
Jul 24 00:10:01 node-2 kernel: [    0.410676] EVM: security.capability
Jul 24 00:10:01 node-2 kernel: [    0.410727] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Jul 24 00:10:01 node-2 kernel: [    0.411399] pinctrl core: initialized pinctrl subsystem
Jul 24 00:10:01 node-2 kernel: [    0.411461] regulator-dummy: no parameters
Jul 24 00:10:01 node-2 kernel: [    0.411493] RTC time:  0:09:21, date: 07/24/16
Jul 24 00:10:01 node-2 kernel: [    0.411527] NET: Registered protocol family 16
Jul 24 00:10:01 node-2 kernel: [    0.411611] cpuidle: using governor ladder
Jul 24 00:10:01 node-2 kernel: [    0.411613] cpuidle: using governor menu
Jul 24 00:10:01 node-2 kernel: [    0.411646] ACPI: bus type PCI registered
Jul 24 00:10:01 node-2 kernel: [    0.411648] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 24 00:10:01 node-2 kernel: [    0.411693] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 24 00:10:01 node-2 kernel: [    0.411696] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 24 00:10:01 node-2 kernel: [    0.425429] PCI: Using configuration type 1 for base access
Jul 24 00:10:01 node-2 kernel: [    0.426432] bio: create slab <bio-0> at 0
Jul 24 00:10:01 node-2 kernel: [    0.426702] ACPI: Added _OSI(Module Device)
Jul 24 00:10:01 node-2 kernel: [    0.426704] ACPI: Added _OSI(Processor Device)
Jul 24 00:10:01 node-2 kernel: [    0.426705] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 24 00:10:01 node-2 kernel: [    0.426706] ACPI: Added _OSI(Processor Aggregator Device)
Jul 24 00:10:01 node-2 kernel: [    0.439326] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 24 00:10:01 node-2 kernel: [    0.450842] ACPI: Interpreter enabled
Jul 24 00:10:01 node-2 kernel: [    0.450848] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 24 00:10:01 node-2 kernel: [    0.450852] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 24 00:10:01 node-2 kernel: [    0.450855] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 24 00:10:01 node-2 kernel: [    0.450861] ACPI: (supports S0 S4 S5)
Jul 24 00:10:01 node-2 kernel: [    0.450862] ACPI: Using IOAPIC for interrupt routing
Jul 24 00:10:01 node-2 kernel: [    0.450903] HEST: Table parsing has been initialized.
Jul 24 00:10:01 node-2 kernel: [    0.450906] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 24 00:10:01 node-2 kernel: [    0.451456] ACPI: No dock devices found.
Jul 24 00:10:01 node-2 kernel: [    0.463110] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 24 00:10:01 node-2 kernel: [    0.463115] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 00:10:01 node-2 kernel: [    0.463118] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 24 00:10:01 node-2 kernel: [    0.463145] PCI host bridge to bus 0000:ff
Jul 24 00:10:01 node-2 kernel: [    0.463147] pci_bus 0000:ff: root bus resource [bus ff]
Jul 24 00:10:01 node-2 kernel: [    0.463155] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463193] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 24 00:10:01 node-2 kernel: [    0.463223] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463258] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463287] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 24 00:10:01 node-2 kernel: [    0.463316] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 24 00:10:01 node-2 kernel: [    0.463347] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463376] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463405] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463435] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463461] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463488] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463516] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463542] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463569] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463596] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463624] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463651] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463678] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 24 00:10:01 node-2 kernel: [    0.463706] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463732] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 24 00:10:01 node-2 kernel: [    0.463758] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463785] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463816] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 24 00:10:01 node-2 kernel: [    0.463850] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463881] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463911] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463942] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.463973] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464004] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464035] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464067] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464098] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464132] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464166] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464199] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464233] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464264] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464293] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464326] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464360] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464399] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464434] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464467] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464497] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464527] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464557] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464588] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464620] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464651] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464682] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 24 00:10:01 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 24 00:10:01 node-2 kernel: [    0.464711] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464740] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464769] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464798] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464829] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464860] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464917] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 24 00:10:01 node-2 kernel: [    0.464919] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 00:10:01 node-2 kernel: [    0.464922] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 24 00:10:01 node-2 kernel: [    0.464940] PCI host bridge to bus 0000:7f
Jul 24 00:10:01 node-2 kernel: [    0.464941] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 24 00:10:01 node-2 kernel: [    0.464946] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.464973] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 24 00:10:01 node-2 kernel: [    0.465001] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465030] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465051] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 24 00:10:01 node-2 kernel: [    0.465076] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 24 00:10:01 node-2 kernel: [    0.465101] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465128] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465156] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465182] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465206] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465231] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465258] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465282] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465307] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465333] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465354] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465377] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465400] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 24 00:10:01 node-2 kernel: [    0.465424] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465446] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 24 00:10:01 node-2 kernel: [    0.465468] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465490] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465517] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 24 00:10:01 node-2 kernel: [    0.465551] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465577] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465606] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465632] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465657] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465683] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465708] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465736] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465761] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465787] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465815] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465843] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465873] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465897] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465921] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465950] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.465975] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.466001] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.466029] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.466056] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.466083] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.466107] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.466133] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.466160] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.466186] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.466213] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.466241] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.466267] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.466289] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.466314] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.466340] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.466371] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.466397] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.467656] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 24 00:10:01 node-2 kernel: [    0.467659] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 00:10:01 node-2 kernel: [    0.468787] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 24 00:10:01 node-2 kernel: [    0.469302] PCI host bridge to bus 0000:00
Jul 24 00:10:01 node-2 kernel: [    0.469304] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 24 00:10:01 node-2 kernel: [    0.469306] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 24 00:10:01 node-2 kernel: [    0.469307] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 24 00:10:01 node-2 kernel: [    0.469308] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 24 00:10:01 node-2 kernel: [    0.469310] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 24 00:10:01 node-2 kernel: [    0.469311] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 24 00:10:01 node-2 kernel: [    0.469313] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 24 00:10:01 node-2 kernel: [    0.469318] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 24 00:10:01 node-2 kernel: [    0.469402] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 24 00:10:01 node-2 kernel: [    0.469433] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 24 00:10:01 node-2 kernel: [    0.469474] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 24 00:10:01 node-2 kernel: [    0.469494] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 24 00:10:01 node-2 kernel: [    0.469523] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 24 00:10:01 node-2 kernel: [    0.469564] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 24 00:10:01 node-2 kernel: [    0.469583] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 24 00:10:01 node-2 kernel: [    0.469613] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 24 00:10:01 node-2 kernel: [    0.469655] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 24 00:10:01 node-2 kernel: [    0.469673] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.469743] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.469820] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.469898] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 24 00:10:01 node-2 kernel: [    0.469903] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 24 00:10:01 node-2 kernel: [    0.469988] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 24 00:10:01 node-2 kernel: [    0.470137] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 24 00:10:01 node-2 kernel: [    0.470155] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 24 00:10:01 node-2 kernel: [    0.470233] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 24 00:10:01 node-2 kernel: [    0.470286] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 24 00:10:01 node-2 kernel: [    0.470309] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 24 00:10:01 node-2 kernel: [    0.470364] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 24 00:10:01 node-2 kernel: [    0.470408] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 24 00:10:01 node-2 kernel: [    0.470436] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 24 00:10:01 node-2 kernel: [    0.470493] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 24 00:10:01 node-2 kernel: [    0.470535] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 24 00:10:01 node-2 kernel: [    0.470560] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 24 00:10:01 node-2 kernel: [    0.470578] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 24 00:10:01 node-2 kernel: [    0.470656] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 24 00:10:01 node-2 kernel: [    0.470706] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 24 00:10:01 node-2 kernel: [    0.470733] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 24 00:10:01 node-2 kernel: [    0.470982] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 24 00:10:01 node-2 kernel: [    0.470988] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 24 00:10:01 node-2 kernel: [    0.470994] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 24 00:10:01 node-2 kernel: [    0.470999] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 24 00:10:01 node-2 kernel: [    0.471007] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 24 00:10:01 node-2 kernel: [    0.471037] pci 0000:01:00.0: supports D1 D2
Jul 24 00:10:01 node-2 kernel: [    0.477163] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 24 00:10:01 node-2 kernel: [    0.477169] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 24 00:10:01 node-2 kernel: [    0.477174] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 24 00:10:01 node-2 kernel: [    0.477434] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 24 00:10:01 node-2 kernel: [    0.477494] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 24 00:10:01 node-2 kernel: [    0.485160] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 24 00:10:01 node-2 kernel: [    0.485167] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 24 00:10:01 node-2 kernel: [    0.485171] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 00:10:01 node-2 kernel: [    0.485255] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 24 00:10:01 node-2 kernel: [    0.485327] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 24 00:10:01 node-2 kernel: [    0.485427] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 24 00:10:01 node-2 kernel: [    0.485472] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 24 00:10:01 node-2 kernel: [    0.485476] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 00:10:01 node-2 kernel: [    0.485477] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 00:10:01 node-2 kernel: [    0.485530] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 24 00:10:01 node-2 kernel: [    0.485668] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 24 00:10:01 node-2 kernel: [    0.485722] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 24 00:10:01 node-2 kernel: [    0.485725] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 00:10:01 node-2 kernel: [    0.485727] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 00:10:01 node-2 kernel: [    0.485776] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 24 00:10:01 node-2 kernel: [    0.485895] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 24 00:10:01 node-2 kernel: [    0.485935] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 24 00:10:01 node-2 kernel: [    0.486057] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 24 00:10:01 node-2 kernel: [    0.486095] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 24 00:10:01 node-2 kernel: [    0.486214] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 24 00:10:01 node-2 kernel: [    0.486252] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 24 00:10:01 node-2 kernel: [    0.486371] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 24 00:10:01 node-2 kernel: [    0.486415] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 24 00:10:01 node-2 kernel: [    0.486418] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 00:10:01 node-2 kernel: [    0.486420] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 00:10:01 node-2 kernel: [    0.486478] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 24 00:10:01 node-2 kernel: [    0.486541] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 24 00:10:01 node-2 kernel: [    0.486593] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 24 00:10:01 node-2 kernel: [    0.486634] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 24 00:10:01 node-2 kernel: [    0.486740] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 24 00:10:01 node-2 kernel: [    0.486847] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 24 00:10:01 node-2 kernel: [    0.486849] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 00:10:01 node-2 kernel: [    0.486851] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 24 00:10:01 node-2 kernel: [    0.486908] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 24 00:10:01 node-2 kernel: [    0.486962] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 24 00:10:01 node-2 kernel: [    0.487013] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 24 00:10:01 node-2 kernel: [    0.487226] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 24 00:10:01 node-2 kernel: [    0.487230] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 24 00:10:01 node-2 kernel: [    0.487291] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 24 00:10:01 node-2 kernel: [    0.487344] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 24 00:10:01 node-2 kernel: [    0.487393] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 24 00:10:01 node-2 kernel: [    0.487604] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 24 00:10:01 node-2 kernel: [    0.487607] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 24 00:10:01 node-2 kernel: [    0.487695] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 24 00:10:01 node-2 kernel: [    0.487762] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 24 00:10:01 node-2 kernel: [    0.487812] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 24 00:10:01 node-2 kernel: [    0.488034] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 24 00:10:01 node-2 kernel: [    0.488038] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 24 00:10:01 node-2 kernel: [    0.488215] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 24 00:10:01 node-2 kernel: [    0.488253] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 24 00:10:01 node-2 kernel: [    0.488328] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 24 00:10:01 node-2 kernel: [    0.488347] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 24 00:10:01 node-2 kernel: [    0.488360] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 24 00:10:01 node-2 kernel: [    0.488373] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 24 00:10:01 node-2 kernel: [    0.488423] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 24 00:10:01 node-2 kernel: [    0.493167] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 24 00:10:01 node-2 kernel: [    0.493177] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 24 00:10:01 node-2 kernel: [    0.493229] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 24 00:10:01 node-2 kernel: [    0.493975] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 24 00:10:01 node-2 kernel: [    0.493978] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 00:10:01 node-2 kernel: [    0.494102] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 24 00:10:01 node-2 kernel: [    0.494207] PCI host bridge to bus 0000:80
Jul 24 00:10:01 node-2 kernel: [    0.494209] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 24 00:10:01 node-2 kernel: [    0.494211] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 24 00:10:01 node-2 kernel: [    0.494212] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 24 00:10:01 node-2 kernel: [    0.494220] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.494282] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.494350] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 24 00:10:01 node-2 kernel: [    0.494410] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 24 00:10:01 node-2 kernel: [    0.494416] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 24 00:10:01 node-2 kernel: [    0.494488] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 24 00:10:01 node-2 kernel: [    0.494787] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 24 00:10:01 node-2 kernel: [    0.494819] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 24 00:10:01 node-2 kernel: [    0.494848] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 24 00:10:01 node-2 kernel: [    0.494877] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 24 00:10:01 node-2 kernel: [    0.494906] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 00:10:01 node-2 kernel: [    0.494936] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 00:10:01 node-2 kernel: [    0.494966] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 00:10:01 node-2 kernel: [    0.494996] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 00:10:01 node-2 kernel: [    0.495080] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 24 00:10:01 node-2 kernel: [    0.495084] ACPI: \_SB_.UNC1: notify handler is installed
Jul 24 00:10:01 node-2 kernel: [    0.495086] ACPI: \_SB_.UNC0: notify handler is installed
Jul 24 00:10:01 node-2 kernel: [    0.495100] ACPI: \_SB_.PCI0: notify handler is installed
Jul 24 00:10:01 node-2 kernel: [    0.495153] ACPI: \_SB_.PCI1: notify handler is installed
Jul 24 00:10:01 node-2 kernel: [    0.495232] Found 4 acpi root devices
Jul 24 00:10:01 node-2 kernel: [    0.495361] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 24 00:10:01 node-2 kernel: [    0.495363] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 24 00:10:01 node-2 kernel: [    0.495364] vgaarb: loaded
Jul 24 00:10:01 node-2 kernel: [    0.495365] vgaarb: bridge control possible 0000:0c:00.0
Jul 24 00:10:01 node-2 kernel: [    0.495475] SCSI subsystem initialized
Jul 24 00:10:01 node-2 kernel: [    0.495537] libata version 3.00 loaded.
Jul 24 00:10:01 node-2 kernel: [    0.495554] ACPI: bus type USB registered
Jul 24 00:10:01 node-2 kernel: [    0.495564] usbcore: registered new interface driver usbfs
Jul 24 00:10:01 node-2 kernel: [    0.495569] usbcore: registered new interface driver hub
Jul 24 00:10:01 node-2 kernel: [    0.495605] usbcore: registered new device driver usb
Jul 24 00:10:01 node-2 kernel: [    0.495763] PCI: Using ACPI for IRQ routing
Jul 24 00:10:01 node-2 kernel: [    0.499376] PCI: pci_cache_line_size set to 64 bytes
Jul 24 00:10:01 node-2 kernel: [    0.499582] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 24 00:10:01 node-2 kernel: [    0.499583] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Jul 24 00:10:01 node-2 kernel: [    0.499584] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 24 00:10:01 node-2 kernel: [    0.499648] NetLabel: Initializing
Jul 24 00:10:01 node-2 kernel: [    0.499650] NetLabel:  domain hash size = 128
Jul 24 00:10:01 node-2 kernel: [    0.499650] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 24 00:10:01 node-2 kernel: [    0.499660] NetLabel:  unlabeled traffic allowed by default
Jul 24 00:10:01 node-2 kernel: [    0.499715] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 24 00:10:01 node-2 kernel: [    0.499719] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 24 00:10:01 node-2 kernel: [    0.501787] Switched to clocksource hpet
Jul 24 00:10:01 node-2 kernel: [    0.506230] AppArmor: AppArmor Filesystem Enabled
Jul 24 00:10:01 node-2 kernel: [    0.506268] pnp: PnP ACPI init
Jul 24 00:10:01 node-2 kernel: [    0.506281] ACPI: bus type PNP registered
Jul 24 00:10:01 node-2 kernel: [    0.506455] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 24 00:10:01 node-2 kernel: [    0.506467] pnp 00:01: [dma 4]
Jul 24 00:10:01 node-2 kernel: [    0.506485] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 24 00:10:01 node-2 kernel: [    0.506519] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 24 00:10:01 node-2 kernel: [    0.506544] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 24 00:10:01 node-2 kernel: [    0.506565] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 24 00:10:01 node-2 kernel: [    0.506611] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 24 00:10:01 node-2 kernel: [    0.506723] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 24 00:10:01 node-2 kernel: [    0.506726] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 24 00:10:01 node-2 kernel: [    0.506728] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 24 00:10:01 node-2 kernel: [    0.506729] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 24 00:10:01 node-2 kernel: [    0.506731] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 24 00:10:01 node-2 kernel: [    0.506732] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 24 00:10:01 node-2 kernel: [    0.506736] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 24 00:10:01 node-2 kernel: [    0.506737] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 24 00:10:01 node-2 kernel: [    0.506739] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 24 00:10:01 node-2 kernel: [    0.506741] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 24 00:10:01 node-2 kernel: [    0.506742] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 24 00:10:01 node-2 kernel: [    0.506743] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 24 00:10:01 node-2 kernel: [    0.506745] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 24 00:10:01 node-2 kernel: [    0.506747] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 24 00:10:01 node-2 kernel: [    0.506848] pnp 00:07: [dma 0 disabled]
Jul 24 00:10:01 node-2 kernel: [    0.506880] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 24 00:10:01 node-2 kernel: [    0.506961] pnp 00:08: [dma 0 disabled]
Jul 24 00:10:01 node-2 kernel: [    0.506997] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 24 00:10:01 node-2 kernel: [    0.507056] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 24 00:10:01 node-2 kernel: [    0.507500] pnp: PnP ACPI: found 10 devices
Jul 24 00:10:01 node-2 kernel: [    0.507502] ACPI: bus type PNP unregistered
Jul 24 00:10:01 node-2 kernel: [    0.513524] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 24 00:10:01 node-2 kernel: [    0.513528] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 24 00:10:01 node-2 kernel: [    0.513531] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 24 00:10:01 node-2 kernel: [    0.513536] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 24 00:10:01 node-2 kernel: [    0.513538] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 00:10:01 node-2 kernel: [    0.513553] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 24 00:10:01 node-2 kernel: [    0.513582] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 24 00:10:01 node-2 kernel: [    0.513597] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 24 00:10:01 node-2 kernel: [    0.513641] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 24 00:10:01 node-2 kernel: [    0.513655] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 24 00:10:01 node-2 kernel: [    0.513684] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 24 00:10:01 node-2 kernel: [    0.513698] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 24 00:10:01 node-2 kernel: [    0.513727] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 24 00:10:01 node-2 kernel: [    0.513729] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 00:10:01 node-2 kernel: [    0.513744] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 00:10:01 node-2 kernel: [    0.513776] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 24 00:10:01 node-2 kernel: [    0.513778] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 00:10:01 node-2 kernel: [    0.513793] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 00:10:01 node-2 kernel: [    0.513822] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 24 00:10:01 node-2 kernel: [    0.513824] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 00:10:01 node-2 kernel: [    0.513827] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 00:10:01 node-2 kernel: [    0.513831] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 24 00:10:01 node-2 kernel: [    0.513833] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 24 00:10:01 node-2 kernel: [    0.513836] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 00:10:01 node-2 kernel: [    0.513840] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 24 00:10:01 node-2 kernel: [    0.513846] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 24 00:10:01 node-2 kernel: [    0.513855] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 24 00:10:01 node-2 kernel: [    0.513859] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 24 00:10:01 node-2 kernel: [    0.513866] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 24 00:10:01 node-2 kernel: [    0.513867] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 24 00:10:01 node-2 kernel: [    0.513868] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 24 00:10:01 node-2 kernel: [    0.513869] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 24 00:10:01 node-2 kernel: [    0.513869] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 24 00:10:01 node-2 kernel: [    0.513870] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 24 00:10:01 node-2 kernel: [    0.513871] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 24 00:10:01 node-2 kernel: [    0.513872] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 24 00:10:01 node-2 kernel: [    0.513873] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 24 00:10:01 node-2 kernel: [    0.513874] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 24 00:10:01 node-2 kernel: [    0.513875] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 24 00:10:01 node-2 kernel: [    0.513876] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 24 00:10:01 node-2 kernel: [    0.513877] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 24 00:10:01 node-2 kernel: [    0.513878] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 24 00:10:01 node-2 kernel: [    0.513879] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 24 00:10:01 node-2 kernel: [    0.513880] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 24 00:10:01 node-2 kernel: [    0.513881] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 24 00:10:01 node-2 kernel: [    0.513882] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 24 00:10:01 node-2 kernel: [    0.513883] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 24 00:10:01 node-2 kernel: [    0.513885] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 24 00:10:01 node-2 kernel: [    0.513886] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 24 00:10:01 node-2 kernel: [    0.513887] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 24 00:10:01 node-2 kernel: [    0.513889] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 24 00:10:01 node-2 kernel: [    0.513890] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 24 00:10:01 node-2 kernel: [    0.513932] NET: Registered protocol family 2
Jul 24 00:10:01 node-2 kernel: [    0.514230] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 24 00:10:01 node-2 kernel: [    0.514603] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 24 00:10:01 node-2 kernel: [    0.514768] TCP: Hash tables configured (established 262144 bind 65536)
Jul 24 00:10:01 node-2 kernel: [    0.514810] TCP: reno registered
Jul 24 00:10:01 node-2 kernel: [    0.514850] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 24 00:10:01 node-2 kernel: [    0.514956] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 24 00:10:01 node-2 kernel: [    0.515116] NET: Registered protocol family 1
Jul 24 00:10:01 node-2 kernel: [    0.553876] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 24 00:10:01 node-2 kernel: [    0.553890] PCI: CLS 64 bytes, default 64
Jul 24 00:10:01 node-2 kernel: [    0.553972] Trying to unpack rootfs image as initramfs...
Jul 24 00:10:01 node-2 kernel: [    0.775322] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Jul 24 00:10:01 node-2 kernel: [    0.775377] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 24 00:10:01 node-2 kernel: [    0.775387] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Jul 24 00:10:01 node-2 kernel: [    0.775806] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 00:10:01 node-2 kernel: [    0.775812] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 00:10:01 node-2 kernel: [    0.775819] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 00:10:01 node-2 kernel: [    0.775826] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 00:10:01 node-2 kernel: [    0.775837] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 00:10:01 node-2 kernel: [    0.775850] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 00:10:01 node-2 kernel: [    0.775865] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 00:10:01 node-2 kernel: [    0.775879] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 00:10:01 node-2 kernel: [    0.775891] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 00:10:01 node-2 kernel: [    0.775899] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 00:10:01 node-2 kernel: [    0.775905] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 00:10:01 node-2 kernel: [    0.775911] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 00:10:01 node-2 kernel: [    0.775920] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 00:10:01 node-2 kernel: [    0.775932] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 00:10:01 node-2 kernel: [    0.775944] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 00:10:01 node-2 kernel: [    0.775956] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 00:10:01 node-2 kernel: [    0.776026] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 24 00:10:01 node-2 kernel: [    0.776030] Scanning for low memory corruption every 60 seconds
Jul 24 00:10:01 node-2 kernel: [    0.776312] Initialise system trusted keyring
Jul 24 00:10:01 node-2 kernel: [    0.776354] audit: initializing netlink socket (disabled)
Jul 24 00:10:01 node-2 kernel: [    0.776361] type=2000 audit(1469318960.728:1): initialized
Jul 24 00:10:01 node-2 kernel: [    0.794178] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 24 00:10:01 node-2 kernel: [    0.795642] zbud: loaded
Jul 24 00:10:01 node-2 kernel: [    0.795754] VFS: Disk quotas dquot_6.5.2
Jul 24 00:10:01 node-2 kernel: [    0.795795] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 24 00:10:01 node-2 kernel: [    0.796170] fuse init (API version 7.22)
Jul 24 00:10:01 node-2 kernel: [    0.796232] msgmni has been set to 32768
Jul 24 00:10:01 node-2 kernel: [    0.796289] Key type big_key registered
Jul 24 00:10:01 node-2 kernel: [    0.796820] Key type asymmetric registered
Jul 24 00:10:01 node-2 kernel: [    0.796822] Asymmetric key parser 'x509' registered
Jul 24 00:10:01 node-2 kernel: [    0.796845] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 24 00:10:01 node-2 kernel: [    0.796906] io scheduler noop registered
Jul 24 00:10:01 node-2 kernel: [    0.796908] io scheduler deadline registered (default)
Jul 24 00:10:01 node-2 kernel: [    0.796928] io scheduler cfq registered
Jul 24 00:10:01 node-2 kernel: [    0.797221] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    0.797315] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    0.797405] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    0.797492] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    0.797600] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    0.797666] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    0.797922] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 24 00:10:01 node-2 kernel: [    0.797943] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 24 00:10:01 node-2 kernel: [    0.797957] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 24 00:10:01 node-2 kernel: [    0.797963] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.797966] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.797968] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 24 00:10:01 node-2 kernel: [    0.797972] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.797973] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.797975] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.797976] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.797977] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.797979] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.797981] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.797982] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.797983] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.797985] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.797986] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.797988] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.797990] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 24 00:10:01 node-2 kernel: [    0.797993] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.797996] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 24 00:10:01 node-2 kernel: [    0.798005] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.798008] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 24 00:10:01 node-2 kernel: [    0.798017] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.798019] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 24 00:10:01 node-2 kernel: [    0.798022] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 24 00:10:01 node-2 kernel: [    0.798034] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 24 00:10:01 node-2 kernel: [    0.798119] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 24 00:10:01 node-2 kernel: [    0.798124] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 24 00:10:01 node-2 kernel: [    0.798132] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 24 00:10:01 node-2 kernel: [    0.798168] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 24 00:10:01 node-2 kernel: [    0.798170] vesafb: scrolling: redraw
Jul 24 00:10:01 node-2 kernel: [    0.798171] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 24 00:10:01 node-2 kernel: [    0.817772] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 24 00:10:01 node-2 kernel: [    0.826297] Console: switching to colour frame buffer device 80x30
Jul 24 00:10:01 node-2 kernel: [    0.835102] fb0: VESA VGA frame buffer device
Jul 24 00:10:01 node-2 kernel: [    0.835301] intel_idle: MWAIT substates: 0x2120
Jul 24 00:10:01 node-2 kernel: [    0.835302] intel_idle: v0.4 model 0x3F
Jul 24 00:10:01 node-2 kernel: [    0.835302] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 24 00:10:01 node-2 kernel: [    0.835536] ipmi message handler version 39.2
Jul 24 00:10:01 node-2 kernel: [    0.835797] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 24 00:10:01 node-2 kernel: [    0.836230] ACPI: AC Adapter [P111] (on-line)
Jul 24 00:10:01 node-2 kernel: [    0.841521] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 24 00:10:01 node-2 kernel: [    0.852556] ACPI: Power Button [PWRB]
Jul 24 00:10:01 node-2 kernel: [    0.858328] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 24 00:10:01 node-2 kernel: [    0.869989] ACPI: Power Button [PWRF]
Jul 24 00:10:01 node-2 kernel: [    0.891324] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 24 00:10:01 node-2 kernel: [    0.903143] pstore: Registered erst as persistent store backend
Jul 24 00:10:01 node-2 kernel: [    0.909420] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 24 00:10:01 node-2 kernel: [    0.921523] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 24 00:10:01 node-2 kernel: [    0.948337] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 24 00:10:01 node-2 kernel: [    0.981782] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 24 00:10:01 node-2 kernel: [    0.996025] Linux agpgart interface v0.103
Jul 24 00:10:01 node-2 kernel: [    1.003766] brd: module loaded
Jul 24 00:10:01 node-2 kernel: [    1.010863] loop: module loaded
Jul 24 00:10:01 node-2 kernel: [    1.017651] libphy: Fixed MDIO Bus: probed
Jul 24 00:10:01 node-2 kernel: [    1.024190] tun: Universal TUN/TAP device driver, 1.6
Jul 24 00:10:01 node-2 kernel: [    1.030723] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 24 00:10:01 node-2 kernel: [    1.037304] PPP generic driver version 2.4.2
Jul 24 00:10:01 node-2 kernel: [    1.043744] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 24 00:10:01 node-2 kernel: [    1.050270] ehci-pci: EHCI PCI platform driver
Jul 24 00:10:01 node-2 kernel: [    1.056839] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 24 00:10:01 node-2 kernel: [    1.063317] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 24 00:10:01 node-2 kernel: [    1.076018] ehci-pci 0000:00:1a.0: debug port 2
Jul 24 00:10:01 node-2 kernel: [    1.086288] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 24 00:10:01 node-2 kernel: [    1.086306] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 24 00:10:01 node-2 kernel: [    1.101271] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 24 00:10:01 node-2 kernel: [    1.107419] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 24 00:10:01 node-2 kernel: [    1.113660] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 24 00:10:01 node-2 kernel: [    1.125694] usb usb1: Product: EHCI Host Controller
Jul 24 00:10:01 node-2 kernel: [    1.131787] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 24 00:10:01 node-2 kernel: [    1.137901] usb usb1: SerialNumber: 0000:00:1a.0
Jul 24 00:10:01 node-2 kernel: [    1.143905] hub 1-0:1.0: USB hub found
Jul 24 00:10:01 node-2 kernel: [    1.149702] hub 1-0:1.0: 2 ports detected
Jul 24 00:10:01 node-2 kernel: [    1.155505] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 24 00:10:01 node-2 kernel: [    1.161122] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 24 00:10:01 node-2 kernel: [    1.172065] ehci-pci 0000:00:1d.0: debug port 2
Jul 24 00:10:01 node-2 kernel: [    1.181361] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 24 00:10:01 node-2 kernel: [    1.181364] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 24 00:10:01 node-2 kernel: [    1.197190] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 24 00:10:01 node-2 kernel: [    1.202401] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 24 00:10:01 node-2 kernel: [    1.207751] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 24 00:10:01 node-2 kernel: [    1.218437] usb usb2: Product: EHCI Host Controller
Jul 24 00:10:01 node-2 kernel: [    1.223930] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 24 00:10:01 node-2 kernel: [    1.229502] usb usb2: SerialNumber: 0000:00:1d.0
Jul 24 00:10:01 node-2 kernel: [    1.235024] hub 2-0:1.0: USB hub found
Jul 24 00:10:01 node-2 kernel: [    1.240369] hub 2-0:1.0: 2 ports detected
Jul 24 00:10:01 node-2 kernel: [    1.245665] ehci-platform: EHCI generic platform driver
Jul 24 00:10:01 node-2 kernel: [    1.250892] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 24 00:10:01 node-2 kernel: [    1.256201] ohci-pci: OHCI PCI platform driver
Jul 24 00:10:01 node-2 kernel: [    1.261486] ohci-platform: OHCI generic platform driver
Jul 24 00:10:01 node-2 kernel: [    1.266672] uhci_hcd: USB Universal Host Controller Interface driver
Jul 24 00:10:01 node-2 kernel: [    1.272006] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 24 00:10:01 node-2 kernel: [    1.464971] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 24 00:10:01 node-2 kernel: [    1.633186] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 24 00:10:01 node-2 kernel: [    1.638700] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 24 00:10:01 node-2 kernel: [    1.644456] hub 1-1:1.0: USB hub found
Jul 24 00:10:01 node-2 kernel: [    1.649923] hub 1-1:1.0: 6 ports detected
Jul 24 00:10:01 node-2 kernel: [    1.764707] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 24 00:10:01 node-2 kernel: [    1.796677] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 24 00:10:01 node-2 kernel: [    2.032847] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 24 00:10:01 node-2 kernel: [    2.038385] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 24 00:10:01 node-2 kernel: [    2.044239] hub 2-1:1.0: USB hub found
Jul 24 00:10:01 node-2 kernel: [    2.049958] hub 2-1:1.0: 8 ports detected
Jul 24 00:10:01 node-2 kernel: [    2.313962] i8042: No controller found
Jul 24 00:10:01 node-2 kernel: [    2.319375] mousedev: PS/2 mouse device common for all mice
Jul 24 00:10:01 node-2 kernel: [    2.324876] rtc_cmos 00:02: RTC can wake from S4
Jul 24 00:10:01 node-2 kernel: [    2.328298] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 24 00:10:01 node-2 kernel: [    2.336102] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 24 00:10:01 node-2 kernel: [    2.341748] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 24 00:10:01 node-2 kernel: [    2.353031] device-mapper: uevent: version 1.0.3
Jul 24 00:10:01 node-2 kernel: [    2.358697] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 24 00:10:01 node-2 kernel: [    2.370020] ledtrig-cpu: registered to indicate activity on CPUs
Jul 24 00:10:01 node-2 kernel: [    2.375978] TCP: cubic registered
Jul 24 00:10:01 node-2 kernel: [    2.381908] NET: Registered protocol family 10
Jul 24 00:10:01 node-2 kernel: [    2.387926] NET: Registered protocol family 17
Jul 24 00:10:01 node-2 kernel: [    2.393643] Key type dns_resolver registered
Jul 24 00:10:01 node-2 kernel: [    2.399636] Loading compiled-in X.509 certificates
Jul 24 00:10:01 node-2 kernel: [    2.405837] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 24 00:10:01 node-2 kernel: [    2.417280] registered taskstats version 1
Jul 24 00:10:01 node-2 kernel: [    2.425283] Key type trusted registered
Jul 24 00:10:01 node-2 kernel: [    2.432830] Key type encrypted registered
Jul 24 00:10:01 node-2 kernel: [    2.438325] AppArmor: AppArmor sha1 policy hashing enabled
Jul 24 00:10:01 node-2 kernel: [    2.443842] IMA: No TPM chip found, activating TPM-bypass!
Jul 24 00:10:01 node-2 kernel: [    2.450014] regulator-dummy: disabling
Jul 24 00:10:01 node-2 kernel: [    2.455610]   Magic number: 8:422:153
Jul 24 00:10:01 node-2 kernel: [    2.460674] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 24 00:10:01 node-2 kernel: [    2.460675] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 24 00:10:01 node-2 kernel: [    2.460675] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 24 00:10:01 node-2 kernel: [    2.460676] usb 2-1.4: Manufacturer: Avocent
Jul 24 00:10:01 node-2 kernel: [    2.460676] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 24 00:10:01 node-2 kernel: [    2.494342] bdi 1:5: hash matches
Jul 24 00:10:01 node-2 kernel: [    2.499845] pci 0000:7f:13.4: hash matches
Jul 24 00:10:01 node-2 kernel: [    2.505342] acpi device:20: hash matches
Jul 24 00:10:01 node-2 kernel: [    2.510689] GHES GHES.0: hash matches
Jul 24 00:10:01 node-2 kernel: [    2.516026] rtc_cmos 00:02: setting system clock to 2016-07-24 00:09:23 UTC (1469318963)
Jul 24 00:10:01 node-2 kernel: [    2.528006] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 24 00:10:01 node-2 kernel: [    2.533440] EDD information not available.
Jul 24 00:10:01 node-2 kernel: [    2.538726] PM: Hibernation image not present or could not be loaded.
Jul 24 00:10:01 node-2 kernel: [    2.539604] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 24 00:10:01 node-2 kernel: [    2.550212] Write protecting the kernel read-only data: 12288k
Jul 24 00:10:01 node-2 kernel: [    2.556204] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 24 00:10:01 node-2 kernel: [    2.568709] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 24 00:10:01 node-2 kernel: [    2.600852] device-mapper: multipath: version 1.6.0 loaded
Jul 24 00:10:01 node-2 kernel: [    2.608588] systemd-udevd[218]: starting version 204
Jul 24 00:10:01 node-2 kernel: [    2.631872] md: linear personality registered for level -1
Jul 24 00:10:01 node-2 kernel: [    2.646308] md: multipath personality registered for level -4
Jul 24 00:10:01 node-2 kernel: [    2.654269] md: raid0 personality registered for level 0
Jul 24 00:10:01 node-2 kernel: [    2.662421] md: raid1 personality registered for level 1
Jul 24 00:10:01 node-2 kernel: [    2.671567] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 24 00:10:01 node-2 kernel: [    2.677756] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 24 00:10:01 node-2 kernel: [    2.683939] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 24 00:10:01 node-2 kernel: [    2.684924] megasas: FW now in Ready state
Jul 24 00:10:01 node-2 kernel: [    2.685073] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.685111] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.685155] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.685196] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.685243] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.685288] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.685338] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.685387] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.685422] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.685467] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.685503] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.685550] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.685600] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.685638] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.685673] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.685711] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.685908] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 24 00:10:01 node-2 kernel: [    2.708590] hidraw: raw HID events driver (C) Jiri Kosina
Jul 24 00:10:01 node-2 kernel: [    2.716567] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Jul 24 00:10:01 node-2 kernel: [    2.729578] 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 24 00:10:01 node-2 kernel: [    2.735950] raid6: sse2x1    5983 MB/s
Jul 24 00:10:01 node-2 kernel: [    2.749907] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 00:10:01 node-2 kernel: [    2.756758] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.756762] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.756766] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.756770] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.756808] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.770945] usbcore: registered new interface driver usbhid
Jul 24 00:10:01 node-2 kernel: [    2.777500] usbhid: USB HID core driver
Jul 24 00:10:01 node-2 kernel: [    2.780187] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Jul 24 00:10:01 node-2 kernel: [    2.780189] 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 24 00:10:01 node-2 kernel: [    2.780206] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 00:10:01 node-2 kernel: [    2.780283] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.780316] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.780357] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.780419] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.780534] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 00:10:01 node-2 kernel: [    2.804067] raid6: sse2x2    7308 MB/s
Jul 24 00:10:01 node-2 kernel: [    2.871786] raid6: sse2x4    6359 MB/s
Jul 24 00:10:01 node-2 kernel: [    2.943724] raid6: avx2x1   14933 MB/s
Jul 24 00:10:01 node-2 kernel: [    3.015657] raid6: avx2x2   18867 MB/s
Jul 24 00:10:01 node-2 kernel: [    3.087596] raid6: avx2x4   21263 MB/s
Jul 24 00:10:01 node-2 kernel: [    3.093438] raid6: using algorithm avx2x4 (21263 MB/s)
Jul 24 00:10:01 node-2 kernel: [    3.099290] raid6: using avx2x2 recovery algorithm
Jul 24 00:10:01 node-2 kernel: [    3.105060] Switched to clocksource tsc
Jul 24 00:10:01 node-2 kernel: [    3.105061] megasas:IOC Init cmd success
Jul 24 00:10:01 node-2 kernel: [    3.115883] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Jul 24 00:10:01 node-2 kernel: [    3.115885] 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 24 00:10:01 node-2 kernel: [    3.115898] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 00:10:01 node-2 kernel: [    3.116311] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    3.116530] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    3.116608] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    3.116798] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    3.117269] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 00:10:01 node-2 kernel: [    3.127861] megasas: INIT adapter done
Jul 24 00:10:01 node-2 kernel: [    3.132460] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Jul 24 00:10:01 node-2 kernel: [    3.132461] 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 24 00:10:01 node-2 kernel: [    3.132464] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 00:10:01 node-2 kernel: [    3.132888] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    3.132977] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    3.133116] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    3.133287] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 24 00:10:01 node-2 kernel: [    3.133606] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 00:10:01 node-2 kernel: [    3.199974] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 24 00:10:01 node-2 kernel: [    3.201531] scsi0 : LSI SAS based MegaRAID driver
Jul 24 00:10:01 node-2 kernel: [    3.209330] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 24 00:10:01 node-2 kernel: [    3.222800] xor: automatically using best checksumming function:
Jul 24 00:10:01 node-2 kernel: [    3.228534] 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 24 00:10:01 node-2 kernel: [    3.237730] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 24 00:10:01 node-2 kernel: [    3.241836] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 24 00:10:01 node-2 kernel: [    3.242134] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 24 00:10:01 node-2 kernel: [    3.242173] sd 0:2:0:0: [sda] Write Protect is off
Jul 24 00:10:01 node-2 kernel: [    3.242174] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 24 00:10:01 node-2 kernel: [    3.242265] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 24 00:10:01 node-2 kernel: [    3.259488]    avx       : 36458.000 MB/sec
Jul 24 00:10:01 node-2 kernel: [    3.275144]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 24 00:10:01 node-2 kernel: [    3.277028] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 24 00:10:01 node-2 kernel: [    3.312301] 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 24 00:10:01 node-2 kernel: [    3.325734] async_tx: api initialized (async)
Jul 24 00:10:01 node-2 kernel: [    3.325760] 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 24 00:10:01 node-2 kernel: [    3.325837] 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 24 00:10:01 node-2 kernel: [    3.325898] 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 24 00:10:01 node-2 kernel: [    3.326022] 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 24 00:10:01 node-2 kernel: [    3.392142] md: raid6 personality registered for level 6
Jul 24 00:10:01 node-2 kernel: [    3.399384] md: raid5 personality registered for level 5
Jul 24 00:10:01 node-2 kernel: [    3.406478] md: raid4 personality registered for level 4
Jul 24 00:10:01 node-2 kernel: [    3.416392] md: raid10 personality registered for level 10
Jul 24 00:10:01 node-2 kernel: [    3.463783] random: lvm urandom read with 28 bits of entropy available
Jul 24 00:10:01 node-2 kernel: [    3.478856] multipathd (367): /proc/367/oom_adj is deprecated, please use /proc/367/oom_score_adj instead.
Jul 24 00:10:01 node-2 kernel: [    3.575456] bio: create slab <bio-1> at 1
Jul 24 00:10:01 node-2 kernel: [    4.422121] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 00:10:01 node-2 kernel: [    5.040821] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 24 00:10:01 node-2 kernel: [    5.060900] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 24 00:10:01 node-2 kernel: [    5.187760] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 24 00:10:01 node-2 kernel: [    5.223752] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 24 00:10:01 node-2 kernel: [    5.304791] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 00:10:01 node-2 kernel: [    5.348181] random: nonblocking pool is initialized
Jul 24 00:10:01 node-2 kernel: [    5.486436] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 24 00:10:01 node-2 kernel: [    5.520880] XFS (dm-0): Mounting Filesystem
Jul 24 00:10:01 node-2 kernel: [    5.752510] XFS (dm-0): Ending clean mount
Jul 24 00:10:01 node-2 kernel: [    5.801856] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 00:10:01 node-2 kernel: [    5.867913] XFS (dm-1): Mounting Filesystem
Jul 24 00:10:01 node-2 kernel: [    6.002031] XFS (dm-1): Ending clean mount
Jul 24 00:10:01 node-2 kernel: [    8.090828] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 24 00:10:01 node-2 kernel: [    8.110522] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 24 00:10:01 node-2 kernel: [    8.284383] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 24 00:10:01 node-2 kernel: [    8.284388] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 24 00:10:01 node-2 kernel: [    8.284393] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 24 00:10:01 node-2 kernel: [    8.284397] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 24 00:10:01 node-2 kernel: [    8.334660] systemd-udevd[777]: starting version 204
Jul 24 00:10:01 node-2 kernel: [    8.514514] power_meter ACPI000D:00: Found ACPI power meter.
Jul 24 00:10:01 node-2 kernel: [    8.514541] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 24 00:10:01 node-2 kernel: [    8.533400] wmi: Mapper loaded
Jul 24 00:10:01 node-2 kernel: [    8.545598] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 24 00:10:01 node-2 kernel: [    8.545603] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 24 00:10:01 node-2 kernel: [    8.545606] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 24 00:10:01 node-2 kernel: [    8.545607] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 24 00:10:01 node-2 kernel: [    8.545623] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 24 00:10:01 node-2 kernel: [    8.548032] IPMI System Interface driver.
Jul 24 00:10:01 node-2 kernel: [    8.548070] ipmi_si: probing via ACPI
Jul 24 00:10:01 node-2 kernel: [    8.548091] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 24 00:10:01 node-2 kernel: [    8.548092] ipmi_si: Adding ACPI-specified kcs state machine
Jul 24 00:10:01 node-2 kernel: [    8.548112] ipmi_si: probing via SMBIOS
Jul 24 00:10:01 node-2 kernel: [    8.548114] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 24 00:10:01 node-2 kernel: [    8.548115] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 24 00:10:01 node-2 kernel: [    8.548117] ipmi_si: probing via SPMI
Jul 24 00:10:01 node-2 kernel: [    8.548118] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 24 00:10:01 node-2 kernel: [    8.548119] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 24 00:10:01 node-2 kernel: [    8.548121] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 24 00:10:01 node-2 kernel: [    8.560042] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 24 00:10:01 node-2 kernel: [    8.603377] systemd-udevd[819]: renamed network interface eth0 to enp6s0
Jul 24 00:10:01 node-2 kernel: [    8.627411] systemd-udevd[803]: renamed network interface eth1 to enp7s0
Jul 24 00:10:01 node-2 kernel: [    8.651278] systemd-udevd[827]: renamed network interface eth2 to enp8s0
Jul 24 00:10:01 node-2 kernel: [    8.687204] systemd-udevd[796]: renamed network interface eth3 to enp9s0
Jul 24 00:10:01 node-2 kernel: [    8.694403] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 24 00:10:01 node-2 kernel: [    8.694411] ipmi_si 00:09: IPMI kcs interface initialized
Jul 24 00:10:01 node-2 kernel: [    8.993942] type=1400 audit(1469318969.976:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1039 comm="apparmor_parser"
Jul 24 00:10:01 node-2 kernel: [    8.994086] type=1400 audit(1469318969.976:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1039 comm="apparmor_parser"
Jul 24 00:10:01 node-2 kernel: [    8.994207] type=1400 audit(1469318969.976:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1039 comm="apparmor_parser"
Jul 24 00:10:01 node-2 kernel: [    8.998757] type=1400 audit(1469318969.984:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1038 comm="apparmor_parser"
Jul 24 00:10:01 node-2 kernel: [    8.998878] type=1400 audit(1469318969.984:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1038 comm="apparmor_parser"
Jul 24 00:10:01 node-2 kernel: [    8.998991] type=1400 audit(1469318969.984:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1038 comm="apparmor_parser"
Jul 24 00:10:01 node-2 kernel: [    9.000677] type=1400 audit(1469318969.984:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1040 comm="apparmor_parser"
Jul 24 00:10:01 node-2 kernel: [    9.000818] type=1400 audit(1469318969.984:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1040 comm="apparmor_parser"
Jul 24 00:10:01 node-2 kernel: [    9.000938] type=1400 audit(1469318969.984:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1040 comm="apparmor_parser"
Jul 24 00:10:01 node-2 kernel: [    9.011022] type=1400 audit(1469318969.996:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1037 comm="apparmor_parser"
Jul 24 00:10:01 node-2 kernel: [    9.634360] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 24 00:10:01 node-2 kernel: [    9.635052] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 24 00:10:01 node-2 kernel: [    9.833848] enic 0000:06:00.0 enp6s0: Link UP
Jul 24 00:10:01 node-2 kernel: [    9.834978] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 24 00:10:01 node-2 kernel: [    9.834984] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 24 00:10:01 node-2 kernel: [   18.859539] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 24 00:10:02 node-2 failsafe: Failsafe of 120 seconds reached.
Jul 24 00:10:02 node-2 kernel: [   42.067086] init: failsafe main process (8398) killed by TERM signal
Jul 24 00:10:03 node-2 dbus[8478]: [system] AppArmor D-Bus mediation is enabled
Jul 24 00:10:03 node-2 kernel: [   42.241053] audit_printk_skb: 30 callbacks suppressed
Jul 24 00:10:03 node-2 kernel: [   42.241054] type=1400 audit(1469319003.143:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8524 comm="apparmor_parser"
Jul 24 00:10:03 node-2 kernel: [   42.241327] type=1400 audit(1469319003.143:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8523 comm="apparmor_parser"
Jul 24 00:10:03 node-2 kernel: [   42.241331] type=1400 audit(1469319003.143:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8523 comm="apparmor_parser"
Jul 24 00:10:03 node-2 kernel: [   42.241334] type=1400 audit(1469319003.143:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8523 comm="apparmor_parser"
Jul 24 00:10:03 node-2 kernel: [   42.241565] type=1400 audit(1469319003.147:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8523 comm="apparmor_parser"
Jul 24 00:10:03 node-2 kernel: [   42.241566] type=1400 audit(1469319003.147:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8523 comm="apparmor_parser"
Jul 24 00:10:03 node-2 kernel: [   42.241696] type=1400 audit(1469319003.147:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8523 comm="apparmor_parser"
Jul 24 00:10:03 node-2 kernel: [   42.348035] type=1400 audit(1469319003.251:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8526 comm="apparmor_parser"
Jul 24 00:10:03 node-2 cron[8557]: (CRON) INFO (pidfile fd = 3)
Jul 24 00:10:03 node-2 anacron[8574]: Anacron 2.3 started on 2016-07-24
Jul 24 00:10:03 node-2 cron[8597]: (CRON) STARTUP (fork ok)
Jul 24 00:10:03 node-2 anacron[8574]: Will run job `cron.daily' in 5 min.
Jul 24 00:10:03 node-2 anacron[8574]: Will run job `cron.weekly' in 10 min.
Jul 24 00:10:03 node-2 anacron[8574]: Will run job `cron.monthly' in 15 min.
Jul 24 00:10:03 node-2 anacron[8574]: Jobs will be executed sequentially
Jul 24 00:10:03 node-2 multipathd: path checkers start up
Jul 24 00:10:03 node-2 cron[8597]: (CRON) INFO (Running @reboot jobs)
Jul 24 00:10:03 node-2 postfix/master[8736]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 24 00:10:07 node-2 puppet-agent[8920]: Reopening log files
Jul 24 00:10:08 node-2 puppet-agent[8920]: Could not request certificate: Connection refused - connect(2)
Jul 24 00:10:18 node-2 puppet-user[8999]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 24 00:10:18 node-2 puppet-user[8999]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 24 00:10:19 node-2 puppet-user[8999]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 24 00:10:19 node-2 puppet-user[8999]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 24 00:10:19 node-2 puppet-user[8999]: Finished catalog run in 0.66 seconds
Jul 24 00:10:20 node-2 multipathd: uevent trigger error
Jul 24 00:10:21 node-2 puppet-user[9424]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 24 00:10:21 node-2 puppet-user[9424]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Jul 24 00:10:21 node-2 puppet-user[9424]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 24 00:10:21 node-2 puppet-user[9424]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 24 00:10:21 node-2 puppet-user[9424]: (/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 24 00:10:21 node-2 puppet-user[9424]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 24 00:10:21 node-2 puppet-user[9424]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 24 00:10:21 node-2 puppet-user[9424]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 24 00:10:21 node-2 puppet-user[9424]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 24 00:10:21 node-2 puppet-user[9424]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 24 00:10:21 node-2 puppet-user[9424]: Finished catalog run in 0.07 seconds
Jul 24 00:10:22 node-2 puppet-user[10014]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 24 00:10:22 node-2 puppet-user[10014]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Jul 24 00:10:22 node-2 puppet-user[10014]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 24 00:10:22 node-2 puppet-user[10014]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 24 00:10:22 node-2 puppet-user[10014]: Finished catalog run in 0.03 seconds
Jul 24 00:10:24 node-2 puppet-user[10485]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 24 00:10:24 node-2 puppet-user[10485]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 24 00:10:24 node-2 puppet-user[10485]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 24 00:10:24 node-2 puppet-user[10485]: Finished catalog run in 0.04 seconds
Jul 24 00:10:25 node-2 puppet-user[10940]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 24 00:10:25 node-2 puppet-user[10940]: Compiled catalog for node-2.domain.tld in environment production in 0.19 seconds
Jul 24 00:10:25 node-2 puppet-user[10940]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 24 00:10:26 node-2 puppet-user[10940]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Jul 24 00:10:26 node-2 puppet-user[10940]: Finished catalog run in 0.43 seconds
Jul 24 00:10:27 node-2 puppet-user[11422]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 24 00:10:27 node-2 puppet-user[11422]: Compiled catalog for node-2.domain.tld in environment production in 0.21 seconds
Jul 24 00:10:27 node-2 puppet-user[11422]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 24 00:10:27 node-2 puppet-user[11422]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 24 00:10:27 node-2 puppet-user[11422]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Jul 24 00:10:27 node-2 puppet-user[11422]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 24 00:10:27 node-2 puppet-user[11422]: Finished catalog run in 0.23 seconds
Jul 24 00:10:29 node-2 puppet-user[11899]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 24 00:10:29 node-2 puppet-user[11899]: Compiled catalog for node-2.domain.tld in environment production in 0.15 seconds
Jul 24 00:10:29 node-2 puppet-user[11899]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 24 00:10:29 node-2 kernel: [   68.521894] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 24 00:10:29 node-2 kernel: [   68.521942] 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 24 00:10:29 node-2 puppet-user[11899]: (/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 24 00:10:29 node-2 puppet-user[11899]: Finished catalog run in 0.05 seconds
Jul 24 00:10:31 node-2 puppet-user[12375]: (Scope(Class[main])) MODULAR: sync_time
Jul 24 00:10:31 node-2 puppet-user[12375]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 24 00:10:31 node-2 ntpdate[12790]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 24 00:10:37 node-2 ntpdate[12790]: adjust time server 10.20.0.2 offset 0.049747 sec
Jul 24 00:10:37 node-2 puppet-user[12375]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 24 00:10:37 node-2 puppet-user[12375]: Finished catalog run in 6.16 seconds
Jul 24 00:10:44 node-2 puppet-user[13167]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 24 00:10:44 node-2 puppet-user[13167]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Jul 24 00:10:44 node-2 puppet-user[13167]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 24 00:10:44 node-2 puppet-user[13167]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Jul 24 00:10:44 node-2 puppet-user[13167]: Finished catalog run in 0.06 seconds
Jul 24 00:10:45 node-2 puppet-user[13624]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 24 00:10:47 node-2 kernel: [   86.318498] init: plymouth-upstart-bridge main process ended, respawning
Jul 24 00:10:47 node-2 puppet-user[13624]: Compiled catalog for node-2.domain.tld in environment production in 1.56 seconds
Jul 24 00:10:47 node-2 puppet-agent[8920]: Could not run: SIGTERM
Jul 24 00:10:47 node-2 puppet-user[13624]: (/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 24 00:10:47 node-2 kernel: [   86.600637] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 24 00:10:47 node-2 puppet-user[13624]: (/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 24 00:10:47 node-2 puppet-user[13624]: (/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 24 00:10:47 node-2 ec2: 
Jul 24 00:10:47 node-2 ec2: #############################################################
Jul 24 00:10:47 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 24 00:10:47 node-2 ec2: 1024 99:c7:30:44:a8:73:9b:df:5d:56:dc:f1:b8:e4:d3:55  root@node-2.domain.tld (DSA)
Jul 24 00:10:47 node-2 ec2: 256 ed:7c:c6:f5:ac:e7:6e:92:94:3b:74:46:5d:e6:fa:43  root@node-2.domain.tld (ECDSA)
Jul 24 00:10:47 node-2 ec2: 256 c0:de:e8:63:dc:91:dc:db:68:c2:50:b0:0d:37:7c:05  root@node-2.domain.tld (ED25519)
Jul 24 00:10:47 node-2 ec2: 2048 7f:87:70:5d:0c:7a:4e:d6:b8:69:c8:c3:b3:68:75:87  root@node-2.domain.tld (RSA)
Jul 24 00:10:47 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 24 00:10:47 node-2 ec2: #############################################################
Jul 24 00:10:47 node-2 puppet-user[13624]: (/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 24 00:10:47 node-2 puppet-user[13624]: (/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 24 00:10:47 node-2 puppet-user[13624]: (/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 24 00:10:47 node-2 puppet-user[13624]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 24 00:10:47 node-2 puppet-user[13624]: (/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 24 00:10:47 node-2 puppet-user[13624]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 24 00:10:47 node-2 puppet-user[13624]: (/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 24 00:10:47 node-2 puppet-user[13624]: (/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 24 00:10:47 node-2 puppet-user[13624]: (/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 24 00:10:47 node-2 puppet-user[13624]: (/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 24 00:10:47 node-2 puppet-user[13624]: (/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 24 00:10:47 node-2 puppet-user[13624]: (/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 24 00:10:47 node-2 puppet-user[13624]: (/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 24 00:11:01 node-2 CRON[14728]: (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 24 00:11:05 node-2 puppet-user[13624]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 24 00:11:05 node-2 puppet-user[13624]: Finished catalog run in 18.20 seconds
Jul 24 00:11:07 node-2 puppet-user[14867]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 24 00:11:08 node-2 puppet-user[14867]: Compiled catalog for node-2.domain.tld in environment production in 0.14 seconds
Jul 24 00:11:12 node-2 puppet-user[14867]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 24 00:11:25 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 00:11:25 node-2 nailgun-agent: I, [2016-07-24T00:11:25.674280 #14731]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 24 00:11:38 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 00:11:39 node-2 nailgun-agent: I, [2016-07-24T00:11:39.019122 #14731]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 24 00:11:43 node-2 puppet-user[14867]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 24 00:11:43 node-2 puppet-user[14867]: Finished catalog run in 34.85 seconds
Jul 24 00:11:45 node-2 puppet-user[17628]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 24 00:11:45 node-2 puppet-user[17628]: Compiled catalog for node-2.domain.tld in environment production in 0.56 seconds
Jul 24 00:11:45 node-2 puppet-user[17628]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 24 00:11:45 node-2 puppet-user[17628]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 24 00:11:45 node-2 puppet-user[17628]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 24 00:11:45 node-2 puppet-user[17628]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 24 00:11:45 node-2 puppet-user[17628]: Finished catalog run in 0.12 seconds
Jul 24 00:11:47 node-2 puppet-user[18099]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 24 00:11:48 node-2 puppet-user[18099]: Compiled catalog for node-2.domain.tld in environment production in 0.90 seconds
Jul 24 00:11:48 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 24 00:11:49 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 24 00:11:49 node-2 crontab[18544]: (root) LIST (root)
Jul 24 00:11:49 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 24 00:11:49 node-2 crontab[18545]: (root) REPLACE (root)
Jul 24 00:11:51 node-2 puppet-user[18099]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 24 00:11:52 node-2 puppet-user[18099]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/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 24 00:11:53 node-2 puppet-user[18099]: (/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 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/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 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/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 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/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 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/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 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/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 24 00:11:53 node-2 puppet-user[18099]: (/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 24 00:11:53 node-2 puppet-user[18099]: (/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 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/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 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/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 24 00:11:53 node-2 puppet-user[18099]: (/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 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 24 00:11:53 node-2 puppet-user[18099]: (/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 24 00:11:53 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8371" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 00:11:53 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 24 00:11:55 node-2 multipathd: uevent trigger error
<27>Jul 24 00:11:55 node-2 multipathd: uevent trigger error
<27>Jul 24 00:11:55 node-2 multipathd: uevent trigger error
<27>Jul 24 00:11:55 node-2 multipathd: uevent trigger error
<27>Jul 24 00:11:55 node-2 multipathd: uevent trigger error
<27>Jul 24 00:11:55 node-2 multipathd: uevent trigger error
<27>Jul 24 00:12:15 node-2 multipathd: uevent trigger error
<27>Jul 24 00:12:15 node-2 multipathd: uevent trigger error
<27>Jul 24 00:12:15 node-2 multipathd: uevent trigger error
<27>Jul 24 00:12:15 node-2 multipathd: uevent trigger error
<27>Jul 24 00:12:15 node-2 multipathd: uevent trigger error
<27>Jul 24 00:12:17 node-2 multipathd: uevent trigger error
<27>Jul 24 00:12:17 node-2 multipathd: uevent trigger error
<27>Jul 24 00:12:17 node-2 multipathd: uevent trigger error
<27>Jul 24 00:12:17 node-2 multipathd: uevent trigger error
<27>Jul 24 00:12:17 node-2 multipathd: uevent trigger error
<27>Jul 24 00:12:19 node-2 multipathd: uevent trigger error
<27>Jul 24 00:12:19 node-2 multipathd: uevent trigger error
<27>Jul 24 00:12:19 node-2 multipathd: uevent trigger error
<27>Jul 24 00:12:19 node-2 multipathd: uevent trigger error
<27>Jul 24 00:12:20 node-2 multipathd: uevent trigger error
<27>Jul 24 00:12:20 node-2 multipathd: uevent trigger error
<27>Jul 24 00:13:19 node-2 ntpdate[29837]: no servers can be used, exiting
<27>Jul 24 00:13:19 node-2 ntpdate[30053]: no servers can be used, exiting
<27>Jul 24 00:13:19 node-2 ntpdate[30283]: no servers can be used, exiting
<27>Jul 24 00:13:51 node-2 multipathd: uevent trigger error
<27>Jul 24 00:13:51 node-2 multipathd: uevent trigger error
<27>Jul 24 00:13:51 node-2 multipathd: uevent trigger error
<27>Jul 24 00:13:51 node-2 multipathd: uevent trigger error
<27>Jul 24 00:13:51 node-2 multipathd: uevent trigger error
<27>Jul 24 00:13:51 node-2 multipathd: uevent trigger error
<27>Jul 24 00:13:54 node-2 multipathd: uevent trigger error
<27>Jul 24 00:13:54 node-2 multipathd: uevent trigger error
<27>Jul 24 00:13:54 node-2 multipathd: uevent trigger error
<27>Jul 24 00:13:54 node-2 multipathd: uevent trigger error
<27>Jul 24 00:13:54 node-2 multipathd: uevent trigger error
<27>Jul 24 00:13:54 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:07 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:07 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:07 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:07 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:07 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:10 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:10 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:10 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:10 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:10 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:10 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:16 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:16 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:16 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:16 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:16 node-2 multipathd: uevent trigger error
<43>Jul 24 00:14:33 node-2 apache2_error [Sun Jul 24 00:14:28.761746 2016] [mpm_event:notice] [pid 7040:tid 140612679681920] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 00:14:33 node-2 apache2_error [Sun Jul 24 00:14:28.761833 2016] [core:notice] [pid 7040:tid 140612679681920] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 24 00:14:33 node-2 apache2_error [Sun Jul 24 00:14:31.758812 2016] [mpm_event:notice] [pid 7040:tid 140612679681920] AH00491: caught SIGTERM, shutting down
<43>Jul 24 00:14:33 node-2 apache2_error [Sun Jul 24 00:14:32.876002 2016] [mpm_worker:notice] [pid 7532:tid 140045394401152] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 00:14:33 node-2 apache2_error [Sun Jul 24 00:14:32.876102 2016] [core:notice] [pid 7532:tid 140045394401152] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 00:14:36 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:37 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:37 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:37 node-2 multipathd: uevent trigger error
<27>Jul 24 00:14:37 node-2 multipathd: uevent trigger error
<27>Jul 24 00:15:12 node-2 multipathd: uevent trigger error
<27>Jul 24 00:15:12 node-2 multipathd: uevent trigger error
<27>Jul 24 00:15:12 node-2 multipathd: uevent trigger error
<27>Jul 24 00:15:12 node-2 multipathd: uevent trigger error
<27>Jul 24 00:15:12 node-2 multipathd: uevent trigger error
<43>Jul 24 00:15:13 node-2 apache2_error [Sun Jul 24 00:15:09.981106 2016] [mpm_worker:notice] [pid 7532:tid 140045394401152] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 00:15:13 node-2 apache2_error [Sun Jul 24 00:15:09.984023 2016] [mpm_worker:warn] [pid 7532:tid 140045394401152] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 00:15:13 node-2 apache2_error [Sun Jul 24 00:15:09.984321 2016] [mpm_worker:notice] [pid 7532:tid 140045394401152] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 00:15:13 node-2 apache2_error [Sun Jul 24 00:15:09.984327 2016] [core:notice] [pid 7532:tid 140045394401152] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 00:15:47 node-2 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 24 00:15:52 node-2 multipathd: uevent trigger error
<27>Jul 24 00:15:52 node-2 multipathd: uevent trigger error
<27>Jul 24 00:15:52 node-2 multipathd: uevent trigger error
<27>Jul 24 00:15:52 node-2 multipathd: uevent trigger error
<27>Jul 24 00:15:52 node-2 multipathd: uevent trigger error
<27>Jul 24 00:15:56 node-2 multipathd: uevent trigger error
<27>Jul 24 00:15:56 node-2 multipathd: uevent trigger error
<27>Jul 24 00:15:56 node-2 multipathd: uevent trigger error
<27>Jul 24 00:15:56 node-2 multipathd: uevent trigger error
<27>Jul 24 00:15:56 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:02 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:03 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:03 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:03 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:03 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:03 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:10 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:10 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:10 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:10 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:10 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:15 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:15 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:15 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:15 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:15 node-2 multipathd: uevent trigger error
<129>Jul 24 00:16:15 node-2 haproxy[20860]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:16:15 node-2 haproxy[20860]: proxy odl-jetty has no server available!
<129>Jul 24 00:16:18 node-2 haproxy[22041]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 00:16:20 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:20 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:20 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:20 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:20 node-2 multipathd: uevent trigger error
<129>Jul 24 00:16:21 node-2 haproxy[22041]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:16:21 node-2 haproxy[22041]: proxy odl-jetty has no server available!
<27>Jul 24 00:16:24 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:24 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:24 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:24 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:24 node-2 multipathd: uevent trigger error
<129>Jul 24 00:16:25 node-2 haproxy[22041]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer4 timeout, check duration: 5001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:16:25 node-2 haproxy[22041]: proxy odl-neutron-endpoint has no server available!
<129>Jul 24 00:16:26 node-2 haproxy[24451]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:27 node-2 haproxy[24455]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 00:16:29 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:29 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:29 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:29 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:29 node-2 multipathd: uevent trigger error
<129>Jul 24 00:16:30 node-2 haproxy[24455]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:16:30 node-2 haproxy[24455]: proxy odl-jetty has no server available!
<129>Jul 24 00:16:32 node-2 haproxy[25673]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 24 00:16:32 node-2 haproxy[25673]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:33 node-2 haproxy[25673]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 00:16:34 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:34 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:34 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:34 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:34 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:34 node-2 multipathd: uevent trigger error
<129>Jul 24 00:16:35 node-2 haproxy[25673]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:16:35 node-2 haproxy[25673]: proxy odl-jetty has no server available!
<129>Jul 24 00:16:37 node-2 haproxy[26909]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:37 node-2 haproxy[26909]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:38 node-2 haproxy[26918]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 24 00:16:38 node-2 haproxy[26918]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:38 node-2 haproxy[26918]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 00:16:40 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:40 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:40 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:40 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:40 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:40 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:40 node-2 multipathd: uevent trigger error
<129>Jul 24 00:16:41 node-2 haproxy[26918]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:16:41 node-2 haproxy[26918]: proxy odl-jetty has no server available!
<129>Jul 24 00:16:42 node-2 haproxy[28138]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:42 node-2 haproxy[28138]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:43 node-2 haproxy[28142]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 24 00:16:43 node-2 haproxy[28142]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:43 node-2 haproxy[28142]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 24 00:16:44 node-2 haproxy[28142]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 00:16:45 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:45 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:45 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:45 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:45 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:45 node-2 multipathd: uevent trigger error
<129>Jul 24 00:16:46 node-2 haproxy[28142]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:46 node-2 haproxy[28142]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:16:46 node-2 haproxy[28142]: proxy aodh has no server available!
<129>Jul 24 00:16:46 node-2 haproxy[28142]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:16:46 node-2 haproxy[28142]: proxy odl-jetty has no server available!
<129>Jul 24 00:16:48 node-2 haproxy[29344]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:48 node-2 haproxy[29344]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:48 node-2 haproxy[29344]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 24 00:16:48 node-2 haproxy[29344]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:49 node-2 haproxy[29344]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 24 00:16:49 node-2 haproxy[29344]: Server aodh/node-2 is DOWN, reason: Layer4 connection 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 24 00:16:49 node-2 haproxy[29344]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 00:16:50 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:50 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:50 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:51 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:51 node-2 multipathd: uevent trigger error
<129>Jul 24 00:16:51 node-2 haproxy[29344]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:51 node-2 haproxy[29344]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:16:51 node-2 haproxy[29344]: proxy aodh has no server available!
<129>Jul 24 00:16:51 node-2 haproxy[29344]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:51 node-2 haproxy[29344]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:16:51 node-2 haproxy[29344]: proxy ceilometer has no server available!
<129>Jul 24 00:16:51 node-2 haproxy[29344]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:16:51 node-2 haproxy[29344]: proxy odl-jetty has no server available!
<129>Jul 24 00:16:53 node-2 haproxy[30518]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:53 node-2 haproxy[30518]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:53 node-2 haproxy[30518]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 24 00:16:53 node-2 haproxy[30518]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:54 node-2 haproxy[30522]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 24 00:16:54 node-2 haproxy[30522]: Server aodh/node-2 is DOWN, reason: Layer4 connection 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 24 00:16:54 node-2 haproxy[30522]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 00:16:55 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:55 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:55 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:55 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:55 node-2 multipathd: uevent trigger error
<27>Jul 24 00:16:56 node-2 multipathd: uevent trigger error
<129>Jul 24 00:16:56 node-2 haproxy[30522]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:56 node-2 haproxy[30522]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:16:56 node-2 haproxy[30522]: proxy aodh has no server available!
<129>Jul 24 00:16:56 node-2 haproxy[30522]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:56 node-2 haproxy[30522]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:16:56 node-2 haproxy[30522]: proxy ceilometer has no server available!
<129>Jul 24 00:16:56 node-2 haproxy[30522]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:16:56 node-2 haproxy[30522]: proxy odl-jetty has no server available!
<129>Jul 24 00:16:58 node-2 haproxy[31731]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:58 node-2 haproxy[31731]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:59 node-2 haproxy[31735]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 24 00:16:59 node-2 haproxy[31735]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:16:59 node-2 haproxy[31735]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 24 00:16:59 node-2 haproxy[31735]: Server aodh/node-2 is DOWN, reason: Layer4 connection 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 24 00:16:59 node-2 haproxy[31735]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:00 node-2 haproxy[31735]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:00 node-2 haproxy[31735]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 00:17:01 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:01 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:01 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:01 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:01 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:01 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:01 node-2 multipathd: uevent trigger error
<129>Jul 24 00:17:01 node-2 haproxy[31735]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:01 node-2 haproxy[31735]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:01 node-2 haproxy[31735]: proxy aodh has no server available!
<129>Jul 24 00:17:01 node-2 haproxy[31735]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:02 node-2 haproxy[31735]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:02 node-2 haproxy[31735]: proxy ceilometer has no server available!
<129>Jul 24 00:17:02 node-2 haproxy[31735]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:02 node-2 haproxy[31735]: proxy odl-jetty has no server available!
<129>Jul 24 00:17:04 node-2 haproxy[565]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:04 node-2 haproxy[565]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:04 node-2 haproxy[565]: Server glance-api/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:04 node-2 haproxy[565]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:05 node-2 haproxy[569]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:05 node-2 haproxy[569]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:05 node-2 haproxy[569]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:05 node-2 haproxy[569]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:05 node-2 haproxy[569]: Server aodh/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:05 node-2 haproxy[569]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:06 node-2 haproxy[569]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:06 node-2 haproxy[569]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 00:17:07 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:07 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:07 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:07 node-2 multipathd: uevent trigger error
<129>Jul 24 00:17:07 node-2 haproxy[569]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 00:17:07 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:07 node-2 multipathd: uevent trigger error
<129>Jul 24 00:17:07 node-2 haproxy[569]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:07 node-2 haproxy[569]: proxy glance-registry has no server available!
<129>Jul 24 00:17:07 node-2 haproxy[569]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:07 node-2 haproxy[569]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:07 node-2 haproxy[569]: proxy aodh has no server available!
<129>Jul 24 00:17:07 node-2 haproxy[569]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:07 node-2 haproxy[569]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:07 node-2 haproxy[569]: proxy ceilometer has no server available!
<129>Jul 24 00:17:08 node-2 haproxy[569]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:08 node-2 haproxy[569]: proxy odl-jetty has no server available!
<129>Jul 24 00:17:09 node-2 haproxy[1839]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:10 node-2 haproxy[1843]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:10 node-2 haproxy[1843]: Server nova-api/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:10 node-2 haproxy[1843]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:10 node-2 haproxy[1843]: Server glance-api/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:10 node-2 haproxy[1843]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:10 node-2 haproxy[1843]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:10 node-2 haproxy[1843]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:11 node-2 haproxy[1843]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:11 node-2 haproxy[1843]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:11 node-2 haproxy[1843]: Server aodh/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:11 node-2 haproxy[1843]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:11 node-2 haproxy[1843]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:11 node-2 haproxy[1843]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:11 node-2 haproxy[1843]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:12 node-2 haproxy[1843]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:12 node-2 haproxy[1843]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:12 node-2 haproxy[1843]: proxy glance-registry has no server available!
<27>Jul 24 00:17:12 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:12 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:12 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:12 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:13 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:13 node-2 multipathd: uevent trigger error
<129>Jul 24 00:17:13 node-2 haproxy[1843]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:13 node-2 haproxy[1843]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:13 node-2 haproxy[1843]: proxy aodh has no server available!
<129>Jul 24 00:17:13 node-2 haproxy[1843]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:13 node-2 haproxy[1843]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:13 node-2 haproxy[1843]: proxy ceilometer has no server available!
<129>Jul 24 00:17:13 node-2 haproxy[1843]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:13 node-2 haproxy[1843]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:13 node-2 haproxy[1843]: proxy nova-novncproxy has no server available!
<129>Jul 24 00:17:13 node-2 haproxy[1843]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:13 node-2 haproxy[1843]: proxy odl-jetty has no server available!
<129>Jul 24 00:17:15 node-2 haproxy[3158]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:15 node-2 haproxy[3158]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:15 node-2 haproxy[3158]: Server nova-api/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:15 node-2 haproxy[3158]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:15 node-2 haproxy[3158]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:15 node-2 haproxy[3158]: Server glance-api/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:16 node-2 haproxy[3164]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:16 node-2 haproxy[3164]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:16 node-2 haproxy[3164]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:16 node-2 haproxy[3164]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:16 node-2 haproxy[3164]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:16 node-2 haproxy[3164]: Server aodh/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:16 node-2 haproxy[3164]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:16 node-2 haproxy[3164]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:17 node-2 haproxy[3164]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:17 node-2 haproxy[3164]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 00:17:18 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:18 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:18 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:18 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:18 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:18 node-2 multipathd: uevent trigger error
<129>Jul 24 00:17:18 node-2 haproxy[3164]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:18 node-2 haproxy[3164]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:18 node-2 haproxy[3164]: proxy glance-registry has no server available!
<129>Jul 24 00:17:18 node-2 haproxy[3164]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:18 node-2 haproxy[3164]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:18 node-2 haproxy[3164]: proxy aodh has no server available!
<129>Jul 24 00:17:18 node-2 haproxy[3164]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:18 node-2 haproxy[3164]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:18 node-2 haproxy[3164]: proxy ceilometer has no server available!
<129>Jul 24 00:17:18 node-2 haproxy[3164]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:18 node-2 haproxy[3164]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:18 node-2 haproxy[3164]: proxy nova-novncproxy has no server available!
<129>Jul 24 00:17:19 node-2 haproxy[3164]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:19 node-2 haproxy[3164]: proxy odl-jetty has no server available!
<129>Jul 24 00:17:20 node-2 haproxy[4393]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:20 node-2 haproxy[4393]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:21 node-2 haproxy[4397]: Server nova-api/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:21 node-2 haproxy[4397]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:21 node-2 haproxy[4397]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:21 node-2 haproxy[4397]: Server glance-api/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:21 node-2 haproxy[4397]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:21 node-2 haproxy[4397]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:21 node-2 haproxy[4397]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:21 node-2 haproxy[4397]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:21 node-2 haproxy[4397]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:21 node-2 haproxy[4397]: Server aodh/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:22 node-2 haproxy[4397]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:22 node-2 haproxy[4397]: Server heat-api/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:22 node-2 haproxy[4397]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:22 node-2 haproxy[4397]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:22 node-2 haproxy[4397]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection 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 24 00:17:22 node-2 haproxy[4397]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:22 node-2 haproxy[4397]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 00:17:23 node-2 multipathd: uevent trigger error
<129>Jul 24 00:17:23 node-2 haproxy[4397]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 00:17:23 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:23 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:23 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:23 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:23 node-2 multipathd: uevent trigger error
<129>Jul 24 00:17:23 node-2 haproxy[4397]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:23 node-2 haproxy[4397]: proxy glance-registry has no server available!
<129>Jul 24 00:17:23 node-2 haproxy[4397]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:24 node-2 haproxy[4397]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:24 node-2 haproxy[4397]: proxy aodh has no server available!
<129>Jul 24 00:17:24 node-2 haproxy[4397]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:24 node-2 haproxy[4397]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:24 node-2 haproxy[4397]: proxy ceilometer has no server available!
<129>Jul 24 00:17:24 node-2 haproxy[4397]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:24 node-2 haproxy[4397]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:24 node-2 haproxy[4397]: proxy nova-novncproxy has no server available!
<129>Jul 24 00:17:24 node-2 haproxy[4397]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:24 node-2 haproxy[4397]: proxy odl-jetty has no server available!
<27>Jul 24 00:17:26 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:26 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:26 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:26 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:26 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:26 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:30 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:30 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:30 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:30 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:30 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:30 node-2 multipathd: uevent trigger error
<129>Jul 24 00:17:30 node-2 haproxy[4397]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer4 timeout, check duration: 5001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:30 node-2 haproxy[4397]: proxy odl-neutron-endpoint has no server available!
<129>Jul 24 00:17:30 node-2 haproxy[4397]: Server keystone-1/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:30 node-2 haproxy[4397]: Server keystone-1/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:30 node-2 haproxy[4397]: proxy keystone-1 has no server available!
<129>Jul 24 00:17:30 node-2 haproxy[4397]: Server keystone-2/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:30 node-2 haproxy[4397]: Server keystone-2/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:30 node-2 haproxy[4397]: proxy keystone-2 has no server available!
<129>Jul 24 00:17:30 node-2 haproxy[4397]: Server nova-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:31 node-2 haproxy[4397]: Server nova-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:31 node-2 haproxy[4397]: proxy nova-api has no server available!
<129>Jul 24 00:17:31 node-2 haproxy[4397]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:31 node-2 haproxy[4397]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:31 node-2 haproxy[4397]: proxy nova-metadata-api has no server available!
<129>Jul 24 00:17:31 node-2 haproxy[4397]: Server cinder-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:31 node-2 haproxy[4397]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:31 node-2 haproxy[4397]: proxy cinder-api has no server available!
<129>Jul 24 00:17:31 node-2 haproxy[4397]: Server glance-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:31 node-2 haproxy[4397]: Server glance-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:31 node-2 haproxy[4397]: proxy glance-api has no server available!
<129>Jul 24 00:17:31 node-2 haproxy[4397]: Server glance-glare/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:31 node-2 haproxy[4397]: Server glance-glare/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:31 node-2 haproxy[4397]: proxy glance-glare has no server available!
<129>Jul 24 00:17:31 node-2 haproxy[4397]: Server neutron/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:31 node-2 haproxy[4397]: Server neutron/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:31 node-2 haproxy[4397]: proxy neutron has no server available!
<129>Jul 24 00:17:31 node-2 haproxy[4397]: Server mysqld/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:31 node-2 haproxy[4397]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:31 node-2 haproxy[4397]: proxy mysqld has no server available!
<129>Jul 24 00:17:31 node-2 haproxy[4397]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:31 node-2 haproxy[4397]: Server object-storage/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:31 node-2 haproxy[4397]: proxy object-storage has no server available!
<129>Jul 24 00:17:32 node-2 haproxy[4397]: Server heat-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:32 node-2 haproxy[4397]: Server heat-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:32 node-2 haproxy[4397]: proxy heat-api has no server available!
<129>Jul 24 00:17:32 node-2 haproxy[4397]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:32 node-2 haproxy[4397]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:32 node-2 haproxy[4397]: proxy heat-api-cfn has no server available!
<129>Jul 24 00:17:32 node-2 haproxy[4397]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 00:17:32 node-2 haproxy[4397]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 00:17:32 node-2 haproxy[4397]: proxy heat-api-cloudwatch has no server available!
<27>Jul 24 00:17:34 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:34 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:34 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:34 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:34 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:34 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:53 node-2 multipathd: uevent trigger error
<27>Jul 24 00:17:59 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 24 00:18:08 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 24 00:18:08 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 24 00:18:08 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 24 00:18:19 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 24 00:19:12 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 24 00:19:38 node-2 multipathd: uevent trigger error
<27>Jul 24 00:19:38 node-2 multipathd: uevent trigger error
<27>Jul 24 00:19:38 node-2 multipathd: uevent trigger error
<27>Jul 24 00:19:38 node-2 multipathd: uevent trigger error
<27>Jul 24 00:19:38 node-2 multipathd: uevent trigger error
<27>Jul 24 00:19:38 node-2 multipathd: uevent trigger error
<27>Jul 24 00:19:48 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 24 00:20:19 node-2 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 24 00:20:21 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 24 00:22:04 node-2 multipathd: uevent trigger error
<27>Jul 24 00:22:04 node-2 multipathd: uevent trigger error
<27>Jul 24 00:22:04 node-2 multipathd: uevent trigger error
<27>Jul 24 00:22:04 node-2 multipathd: uevent trigger error
<27>Jul 24 00:22:04 node-2 multipathd: uevent trigger error
<11>Jul 24 00:22:59 node-2 epmd: epmd: node name already occupied rabbitmq-cli-23
<27>Jul 24 00:25:17 node-2 multipathd: uevent trigger error
<27>Jul 24 00:25:17 node-2 multipathd: uevent trigger error
<27>Jul 24 00:25:17 node-2 multipathd: uevent trigger error
<27>Jul 24 00:25:17 node-2 multipathd: uevent trigger error
<27>Jul 24 00:25:17 node-2 multipathd: uevent trigger error
<43>Jul 24 00:26:35 node-2 apache2_error [Sun Jul 24 00:26:26.557712 2016] [mpm_worker:notice] [pid 7532:tid 140045394401152] AH00295: caught SIGTERM, shutting down
<43>Jul 24 00:26:35 node-2 apache2_error [Sun Jul 24 00:26:27.303213 2016] [mpm_worker:notice] [pid 12210:tid 140400422700928] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 00:26:35 node-2 apache2_error [Sun Jul 24 00:26:27.303253 2016] [core:notice] [pid 12210:tid 140400422700928] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 00:27:05 node-2 multipathd: uevent trigger error
<27>Jul 24 00:27:05 node-2 multipathd: uevent trigger error
<27>Jul 24 00:27:05 node-2 multipathd: uevent trigger error
<27>Jul 24 00:27:05 node-2 multipathd: uevent trigger error
<27>Jul 24 00:27:05 node-2 multipathd: uevent trigger error
<43>Jul 24 00:27:05 node-2 apache2_error [Sun Jul 24 00:26:59.207174 2016] [mpm_worker:notice] [pid 12210:tid 140400422700928] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 00:27:05 node-2 apache2_error [Sun Jul 24 00:26:59.217366 2016] [mpm_worker:warn] [pid 12210:tid 140400422700928] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 00:27:05 node-2 apache2_error [Sun Jul 24 00:26:59.224049 2016] [mpm_worker:notice] [pid 12210:tid 140400422700928] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 00:27:05 node-2 apache2_error [Sun Jul 24 00:26:59.224080 2016] [core:notice] [pid 12210:tid 140400422700928] AH00094: Command line: '/usr/sbin/apache2'
<11>Jul 24 00:27:32 node-2 epmd: epmd: node name already occupied rabbitmq-cli-23
<27>Jul 24 00:28:01 node-2 multipathd: uevent trigger error
<27>Jul 24 00:28:01 node-2 multipathd: uevent trigger error
<27>Jul 24 00:28:01 node-2 multipathd: uevent trigger error
<27>Jul 24 00:28:01 node-2 multipathd: uevent trigger error
<27>Jul 24 00:28:01 node-2 multipathd: uevent trigger error
<27>Jul 24 00:28:07 node-2 multipathd: uevent trigger error
<27>Jul 24 00:28:07 node-2 multipathd: uevent trigger error
<27>Jul 24 00:28:07 node-2 multipathd: uevent trigger error
<27>Jul 24 00:28:07 node-2 multipathd: uevent trigger error
<27>Jul 24 00:28:07 node-2 multipathd: uevent trigger error
<27>Jul 24 00:29:20 node-2 multipathd: uevent trigger error
<27>Jul 24 00:29:20 node-2 multipathd: uevent trigger error
<27>Jul 24 00:29:20 node-2 multipathd: uevent trigger error
<27>Jul 24 00:29:20 node-2 multipathd: uevent trigger error
<27>Jul 24 00:29:20 node-2 multipathd: uevent trigger error
<27>Jul 24 00:29:20 node-2 multipathd: uevent trigger error
<11>Jul 24 00:32:39 node-2 epmd: epmd: node name already occupied rabbitmq-cli-23
<11>Jul 24 00:32:45 node-2 epmd: epmd: node name already occupied rabbitmq-cli-23
<27>Jul 24 00:33:22 node-2 multipathd: uevent trigger error
<27>Jul 24 00:33:22 node-2 multipathd: uevent trigger error
<27>Jul 24 00:33:22 node-2 multipathd: uevent trigger error
<27>Jul 24 00:33:22 node-2 multipathd: uevent trigger error
<27>Jul 24 00:33:22 node-2 multipathd: uevent trigger error
<27>Jul 24 00:33:22 node-2 multipathd: uevent trigger error
<27>Jul 24 00:35:29 node-2 multipathd: uevent trigger error
<27>Jul 24 00:35:29 node-2 multipathd: uevent trigger error
<27>Jul 24 00:35:29 node-2 multipathd: uevent trigger error
<27>Jul 24 00:35:29 node-2 multipathd: uevent trigger error
<27>Jul 24 00:35:29 node-2 multipathd: uevent trigger error
<27>Jul 24 00:35:29 node-2 multipathd: uevent trigger error
<27>Jul 24 00:36:37 node-2 multipathd: uevent trigger error
<27>Jul 24 00:36:37 node-2 multipathd: uevent trigger error
<27>Jul 24 00:36:37 node-2 multipathd: uevent trigger error
<27>Jul 24 00:36:37 node-2 multipathd: uevent trigger error
<27>Jul 24 00:36:37 node-2 multipathd: uevent trigger error
<27>Jul 24 00:36:37 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:14 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:14 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:14 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:14 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:14 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:14 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:23 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:23 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:23 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:23 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:23 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:23 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:23 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:28 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:28 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:28 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:28 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:28 node-2 multipathd: uevent trigger error
<27>Jul 24 00:37:28 node-2 multipathd: uevent trigger error
<43>Jul 24 00:38:25 node-2 apache2_error [Sun Jul 24 00:38:18.427900 2016] [mpm_worker:notice] [pid 12210:tid 140400422700928] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 00:38:25 node-2 apache2_error [Sun Jul 24 00:38:18.808914 2016] [mpm_worker:warn] [pid 12210:tid 140400422700928] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 00:38:25 node-2 apache2_error [Sun Jul 24 00:38:18.812071 2016] [mpm_worker:notice] [pid 12210:tid 140400422700928] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 00:38:25 node-2 apache2_error [Sun Jul 24 00:38:18.812088 2016] [core:notice] [pid 12210:tid 140400422700928] AH00094: Command line: '/usr/sbin/apache2'
<11>Jul 24 00:38:39 node-2 epmd: epmd: node name already occupied rabbitmq-cli-23
<11>Jul 24 00:38:41 node-2 epmd: epmd: node name already occupied rabbitmq-cli-23
<43>Jul 24 00:38:55 node-2 apache2_error [Sun Jul 24 00:38:55.766431 2016] [mpm_worker:notice] [pid 12210:tid 140400422700928] AH00297: SIGUSR1 received.  Doing graceful restart
<27>Jul 24 00:39:00 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:00 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:00 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:00 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:00 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:00 node-2 multipathd: uevent trigger error
<43>Jul 24 00:39:05 node-2 apache2_error [Sun Jul 24 00:38:56.149543 2016] [mpm_worker:warn] [pid 12210:tid 140400422700928] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 00:39:05 node-2 apache2_error [Sun Jul 24 00:38:56.158708 2016] [mpm_worker:notice] [pid 12210:tid 140400422700928] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 00:39:05 node-2 apache2_error [Sun Jul 24 00:38:56.158738 2016] [core:notice] [pid 12210:tid 140400422700928] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 00:39:18 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:18 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:18 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:18 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:18 node-2 multipathd: uevent trigger error
<11>Jul 24 00:39:20 node-2 epmd: epmd: node name already occupied rabbitmq-cli-23
<27>Jul 24 00:39:34 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:35 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:35 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:41 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:41 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:41 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:41 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:41 node-2 multipathd: uevent trigger error
<27>Jul 24 00:39:42 node-2 multipathd: sda: spurious uevent, path already in pathvec
<27>Jul 24 00:40:30 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:30 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:30 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:30 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:30 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:35 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:35 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:35 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:35 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:36 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:40 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:40 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:40 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:40 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:40 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:52 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:52 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:52 node-2 multipathd: uevent trigger error
<27>Jul 24 00:40:52 node-2 multipathd: uevent trigger error
<27>Jul 24 00:41:14 node-2 multipathd: uevent trigger error
<27>Jul 24 00:41:14 node-2 multipathd: uevent trigger error
<27>Jul 24 00:41:14 node-2 multipathd: uevent trigger error
<27>Jul 24 00:41:14 node-2 multipathd: uevent trigger error
<27>Jul 24 00:41:14 node-2 multipathd: uevent trigger error
<11>Jul 24 00:41:58 node-2 epmd: epmd: node name already occupied rabbitmq-cli-23
<27>Jul 24 00:42:04 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:04 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:04 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:04 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:04 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:19 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:19 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:19 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:19 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:19 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:19 node-2 multipathd: uevent trigger error
<11>Jul 24 00:42:28 node-2 liberasurecode[71575]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:28 node-2 liberasurecode[71575]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:28 node-2 liberasurecode[71575]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:28 node-2 liberasurecode[71575]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:28 node-2 liberasurecode[71604]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:28 node-2 liberasurecode[71604]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:28 node-2 liberasurecode[71604]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:28 node-2 liberasurecode[71604]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:30 node-2 liberasurecode[72097]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:30 node-2 liberasurecode[72097]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:30 node-2 liberasurecode[72097]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:30 node-2 liberasurecode[72097]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:35 node-2 liberasurecode[72859]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:35 node-2 liberasurecode[72859]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:35 node-2 liberasurecode[72859]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:35 node-2 liberasurecode[72859]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:35 node-2 liberasurecode[72896]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:35 node-2 liberasurecode[72896]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:35 node-2 liberasurecode[72896]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:35 node-2 liberasurecode[72896]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:35 node-2 liberasurecode[72972]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:35 node-2 liberasurecode[72972]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:35 node-2 liberasurecode[72972]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:35 node-2 liberasurecode[72972]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:36 node-2 liberasurecode[73040]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:36 node-2 liberasurecode[73040]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:36 node-2 liberasurecode[73040]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:36 node-2 liberasurecode[73040]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:36 node-2 liberasurecode[73054]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:36 node-2 liberasurecode[73054]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:36 node-2 liberasurecode[73054]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:36 node-2 liberasurecode[73054]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:36 node-2 liberasurecode[73066]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:36 node-2 liberasurecode[73066]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:36 node-2 liberasurecode[73066]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:36 node-2 liberasurecode[73066]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:36 node-2 liberasurecode[73080]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:36 node-2 liberasurecode[73080]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:36 node-2 liberasurecode[73080]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:42:36 node-2 liberasurecode[73080]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 24 00:42:42 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:42 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:42 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:42 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:42 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:47 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:47 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:47 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:47 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:47 node-2 multipathd: uevent trigger error
<27>Jul 24 00:42:47 node-2 multipathd: uevent trigger error
<27>Jul 24 00:43:57 node-2 multipathd: uevent trigger error
<27>Jul 24 00:43:57 node-2 multipathd: uevent trigger error
<27>Jul 24 00:43:57 node-2 multipathd: uevent trigger error
<27>Jul 24 00:43:57 node-2 multipathd: uevent trigger error
<27>Jul 24 00:43:57 node-2 multipathd: uevent trigger error
<11>Jul 24 00:45:01 node-2 liberasurecode[94844]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:45:01 node-2 liberasurecode[94844]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:45:01 node-2 liberasurecode[94844]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:45:01 node-2 liberasurecode[94844]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 00:45:59 node-2 epmd: epmd: node name already occupied rabbitmq-cli-23
<27>Jul 24 00:46:00 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:00 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:00 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:00 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:00 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:00 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:05 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:05 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:05 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:05 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:05 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:19 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:19 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:19 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:19 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:19 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:23 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:23 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:23 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:23 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:23 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:41 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:41 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:41 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:41 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:41 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:41 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:55 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:55 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:55 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:55 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:59 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:59 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:59 node-2 multipathd: uevent trigger error
<27>Jul 24 00:46:59 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:04 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:04 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:04 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:04 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:04 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:09 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:09 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:09 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:09 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:09 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:13 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:13 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:13 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:13 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:13 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:13 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:18 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:18 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:18 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:18 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:18 node-2 multipathd: uevent trigger error
<27>Jul 24 00:47:18 node-2 multipathd: uevent trigger error
<11>Jul 24 00:49:29 node-2 epmd: epmd: node name already occupied rabbitmq-cli-23
<11>Jul 24 00:50:02 node-2 liberasurecode[143942]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:50:02 node-2 liberasurecode[143942]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:50:02 node-2 liberasurecode[143942]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 00:50:02 node-2 liberasurecode[143942]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
