Jul 30 12:52:00 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8370" x-info="http://www.rsyslog.com"] start
Jul 30 12:52:00 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 30 12:52:00 node-2 rsyslogd: rsyslogd's groupid changed to 104
Jul 30 12:52:00 node-2 rsyslogd: rsyslogd's userid changed to 101
Jul 30 12:52:00 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 30 12:52:00 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 30 12:52:00 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 30 12:52:00 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 30 12:52:00 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=f5c27b76-3a34-441a-b7d4-e769fd2fba9a nomdmonddf nomdmonisw
Jul 30 12:52:00 node-2 kernel: [    0.000000] KERNEL supported cpus:
Jul 30 12:52:00 node-2 kernel: [    0.000000]   Intel GenuineIntel
Jul 30 12:52:00 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Jul 30 12:52:00 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Jul 30 12:52:00 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 30 12:52:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 30 12:52:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 30 12:52:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 30 12:52:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Jul 30 12:52:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Jul 30 12:52:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Jul 30 12:52:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Jul 30 12:52:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Jul 30 12:52:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 30 12:52:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 30 12:52:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 30 12:52:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 30 12:52:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 30 12:52:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 30 12:52:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 30 12:52:00 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 30 12:52:00 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 30 12:52:00 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 30 12:52:00 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 30 12:52:00 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 30 12:52:00 node-2 kernel: [    0.000000] No AGP bridge found
Jul 30 12:52:00 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 30 12:52:00 node-2 kernel: [    0.000000] MTRR default type: write-back
Jul 30 12:52:00 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 30 12:52:00 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Jul 30 12:52:00 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 30 12:52:00 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 30 12:52:00 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 30 12:52:00 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 30 12:52:00 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 30 12:52:00 node-2 kernel: [    0.000000]   2 disabled
Jul 30 12:52:00 node-2 kernel: [    0.000000]   3 disabled
Jul 30 12:52:00 node-2 kernel: [    0.000000]   4 disabled
Jul 30 12:52:00 node-2 kernel: [    0.000000]   5 disabled
Jul 30 12:52:00 node-2 kernel: [    0.000000]   6 disabled
Jul 30 12:52:00 node-2 kernel: [    0.000000]   7 disabled
Jul 30 12:52:00 node-2 kernel: [    0.000000]   8 disabled
Jul 30 12:52:00 node-2 kernel: [    0.000000]   9 disabled
Jul 30 12:52:00 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 30 12:52:00 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 30 12:52:00 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 30 12:52:00 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 30 12:52:00 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 30 12:52:00 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Jul 30 12:52:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 30 12:52:00 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 30 12:52:00 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 30 12:52:00 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 30 12:52:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 30 12:52:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 30 12:52:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 30 12:52:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 30 12:52:00 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 30 12:52:00 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Jul 30 12:52:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 30 12:52:00 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 30 12:52:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 30 12:52:00 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 30 12:52:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 30 12:52:00 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 30 12:52:00 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 30 12:52:00 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 30 12:52:00 node-2 kernel: [    0.000000] Zone ranges:
Jul 30 12:52:00 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] Movable zone start for each node
Jul 30 12:52:00 node-2 kernel: [    0.000000] Early memory node ranges
Jul 30 12:52:00 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] On node 0 totalpages: 4125855
Jul 30 12:52:00 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 30 12:52:00 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 30 12:52:00 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 30 12:52:00 node-2 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Jul 30 12:52:00 node-2 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Jul 30 12:52:00 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 30 12:52:00 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 30 12:52:00 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 30 12:52:00 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 30 12:52:00 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 30 12:52:00 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 30 12:52:00 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 30 12:52:00 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 30 12:52:00 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 30 12:52:00 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 30 12:52:00 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 30 12:52:00 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 30 12:52:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 30 12:52:00 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 30 12:52:00 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 30 12:52:00 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 30 12:52:00 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 30 12:52:00 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 30 12:52:00 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 30 12:52:00 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Jul 30 12:52:00 node-2 kernel: [    0.000000] Policy zone: Normal
Jul 30 12:52:00 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=f5c27b76-3a34-441a-b7d4-e769fd2fba9a nomdmonddf nomdmonisw
Jul 30 12:52:00 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 30 12:52:00 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 30 12:52:00 node-2 kernel: [    0.000000] Checking aperture...
Jul 30 12:52:00 node-2 kernel: [    0.000000] No AGP bridge found
Jul 30 12:52:00 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 30 12:52:00 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 30 12:52:00 node-2 kernel: [    0.000000] Memory: 32653456K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 30 12:52:00 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 30 12:52:00 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 30 12:52:00 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 30 12:52:00 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 30 12:52:00 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 30 12:52:00 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 30 12:52:00 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 30 12:52:00 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 30 12:52:00 node-2 kernel: [    0.000000] console [tty0] enabled
Jul 30 12:52:00 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 30 12:52:00 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 30 12:52:00 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 30 12:52:00 node-2 kernel: [    0.000000] hpet clockevent registered
Jul 30 12:52:00 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 30 12:52:00 node-2 kernel: [    0.004000] tsc: Detected 3492.254 MHz processor
Jul 30 12:52:00 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.50 BogoMIPS (lpj=13969016)
Jul 30 12:52:00 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 30 12:52:00 node-2 kernel: [    0.000043] Security Framework initialized
Jul 30 12:52:00 node-2 kernel: [    0.000062] AppArmor: AppArmor initialized
Jul 30 12:52:00 node-2 kernel: [    0.000063] Yama: becoming mindful.
Jul 30 12:52:00 node-2 kernel: [    0.001454] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 30 12:52:00 node-2 kernel: [    0.006290] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 30 12:52:00 node-2 kernel: [    0.008218] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 30 12:52:00 node-2 kernel: [    0.008246] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 30 12:52:00 node-2 kernel: [    0.008533] Initializing cgroup subsys memory
Jul 30 12:52:00 node-2 kernel: [    0.008541] Initializing cgroup subsys devices
Jul 30 12:52:00 node-2 kernel: [    0.008543] Initializing cgroup subsys freezer
Jul 30 12:52:00 node-2 kernel: [    0.008545] Initializing cgroup subsys blkio
Jul 30 12:52:00 node-2 kernel: [    0.008547] Initializing cgroup subsys perf_event
Jul 30 12:52:00 node-2 kernel: [    0.008549] Initializing cgroup subsys hugetlb
Jul 30 12:52:00 node-2 kernel: [    0.008569] CPU: Physical Processor ID: 0
Jul 30 12:52:00 node-2 kernel: [    0.008570] CPU: Processor Core ID: 0
Jul 30 12:52:00 node-2 kernel: [    0.008574] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 30 12:52:00 node-2 kernel: [    0.008574] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 30 12:52:00 node-2 kernel: [    0.009268] mce: CPU supports 22 MCE banks
Jul 30 12:52:00 node-2 kernel: [    0.009295] CPU0: Thermal monitoring enabled (TM1)
Jul 30 12:52:00 node-2 kernel: [    0.009316] process: using mwait in idle threads
Jul 30 12:52:00 node-2 kernel: [    0.009319] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 30 12:52:00 node-2 kernel: [    0.009319] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 30 12:52:00 node-2 kernel: [    0.009319] tlb_flushall_shift: 6
Jul 30 12:52:00 node-2 kernel: [    0.009409] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 30 12:52:00 node-2 kernel: [    0.010134] ACPI: Core revision 20131115
Jul 30 12:52:00 node-2 kernel: [    0.022809] ACPI: All ACPI Tables successfully acquired
Jul 30 12:52:00 node-2 kernel: [    0.022971] ftrace: allocating 28617 entries in 112 pages
Jul 30 12:52:00 node-2 kernel: [    0.031765] dmar: Host address width 46
Jul 30 12:52:00 node-2 kernel: [    0.031767] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 30 12:52:00 node-2 kernel: [    0.031773] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 30 12:52:00 node-2 kernel: [    0.031775] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 30 12:52:00 node-2 kernel: [    0.031779] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 30 12:52:00 node-2 kernel: [    0.031780] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 30 12:52:00 node-2 kernel: [    0.031782] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 30 12:52:00 node-2 kernel: [    0.031783] dmar: ATSR flags: 0x0
Jul 30 12:52:00 node-2 kernel: [    0.031784] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 30 12:52:00 node-2 kernel: [    0.031785] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 30 12:52:00 node-2 kernel: [    0.031901] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 30 12:52:00 node-2 kernel: [    0.031902] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 30 12:52:00 node-2 kernel: [    0.031903] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 30 12:52:00 node-2 kernel: [    0.031904] HPET id 0 under DRHD base 0xc7ffc000
Jul 30 12:52:00 node-2 kernel: [    0.031905] Your BIOS is broken and requested that x2apic be disabled.
Jul 30 12:52:00 node-2 kernel: [    0.031905] This will slightly decrease performance.
Jul 30 12:52:00 node-2 kernel: [    0.031905] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 30 12:52:00 node-2 kernel: [    0.032336] Enabled IRQ remapping in xapic mode
Jul 30 12:52:00 node-2 kernel: [    0.032337] x2apic not enabled, IRQ remapping is in xapic mode
Jul 30 12:52:00 node-2 kernel: [    0.032341] Switched APIC routing to physical flat.
Jul 30 12:52:00 node-2 kernel: [    0.032966] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 30 12:52:00 node-2 kernel: [    0.072620] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 30 12:52:00 node-2 kernel: [    0.072626] TSC deadline timer enabled
Jul 30 12:52:00 node-2 kernel: [    0.072633] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 30 12:52:00 node-2 kernel: [    0.072639] ... version:                3
Jul 30 12:52:00 node-2 kernel: [    0.072640] ... bit width:              48
Jul 30 12:52:00 node-2 kernel: [    0.072641] ... generic registers:      4
Jul 30 12:52:00 node-2 kernel: [    0.072642] ... value mask:             0000ffffffffffff
Jul 30 12:52:00 node-2 kernel: [    0.072643] ... max period:             0000ffffffffffff
Jul 30 12:52:00 node-2 kernel: [    0.072644] ... fixed-purpose events:   3
Jul 30 12:52:00 node-2 kernel: [    0.072645] ... event mask:             000000070000000f
Jul 30 12:52:00 node-2 kernel: [    0.074060] x86: Booting SMP configuration:
Jul 30 12:52:00 node-2 kernel: [    0.088167] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 30 12:52:00 node-2 kernel: [    0.074062] .... node  #0, CPUs:        #1  #2  #3
Jul 30 12:52:00 node-2 kernel: [    0.116076] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 30 12:52:00 node-2 kernel: [    0.270036] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 30 12:52:00 node-2 kernel: [    0.325654] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 30 12:52:00 node-2 kernel: [    0.382511] x86: Booted up 2 nodes, 16 CPUs
Jul 30 12:52:00 node-2 kernel: [    0.382514] smpboot: Total of 16 processors activated (111763.87 BogoMIPS)
Jul 30 12:52:00 node-2 kernel: [    0.406747] devtmpfs: initialized
Jul 30 12:52:00 node-2 kernel: [    0.409846] EVM: security.selinux
Jul 30 12:52:00 node-2 kernel: [    0.409847] EVM: security.SMACK64
Jul 30 12:52:00 node-2 kernel: [    0.409848] EVM: security.ima
Jul 30 12:52:00 node-2 kernel: [    0.409849] EVM: security.capability
Jul 30 12:52:00 node-2 kernel: [    0.409900] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Jul 30 12:52:00 node-2 kernel: [    0.410580] pinctrl core: initialized pinctrl subsystem
Jul 30 12:52:00 node-2 kernel: [    0.410642] regulator-dummy: no parameters
Jul 30 12:52:00 node-2 kernel: [    0.410672] RTC time: 12:51:24, date: 07/30/16
Jul 30 12:52:00 node-2 kernel: [    0.410705] NET: Registered protocol family 16
Jul 30 12:52:00 node-2 kernel: [    0.410791] cpuidle: using governor ladder
Jul 30 12:52:00 node-2 kernel: [    0.410792] cpuidle: using governor menu
Jul 30 12:52:00 node-2 kernel: [    0.410826] ACPI: bus type PCI registered
Jul 30 12:52:00 node-2 kernel: [    0.410828] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 30 12:52:00 node-2 kernel: [    0.410873] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 30 12:52:00 node-2 kernel: [    0.410875] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 30 12:52:00 node-2 kernel: [    0.424606] PCI: Using configuration type 1 for base access
Jul 30 12:52:00 node-2 kernel: [    0.425610] bio: create slab <bio-0> at 0
Jul 30 12:52:00 node-2 kernel: [    0.425892] ACPI: Added _OSI(Module Device)
Jul 30 12:52:00 node-2 kernel: [    0.425894] ACPI: Added _OSI(Processor Device)
Jul 30 12:52:00 node-2 kernel: [    0.425895] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 30 12:52:00 node-2 kernel: [    0.425896] ACPI: Added _OSI(Processor Aggregator Device)
Jul 30 12:52:00 node-2 kernel: [    0.438550] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 30 12:52:00 node-2 kernel: [    0.450195] ACPI: Interpreter enabled
Jul 30 12:52:00 node-2 kernel: [    0.450201] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 30 12:52:00 node-2 kernel: [    0.450205] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 30 12:52:00 node-2 kernel: [    0.450208] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 30 12:52:00 node-2 kernel: [    0.450214] ACPI: (supports S0 S4 S5)
Jul 30 12:52:00 node-2 kernel: [    0.450216] ACPI: Using IOAPIC for interrupt routing
Jul 30 12:52:00 node-2 kernel: [    0.450257] HEST: Table parsing has been initialized.
Jul 30 12:52:00 node-2 kernel: [    0.450260] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 30 12:52:00 node-2 kernel: [    0.450814] ACPI: No dock devices found.
Jul 30 12:52:00 node-2 kernel: [    0.462420] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 30 12:52:00 node-2 kernel: [    0.462425] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 30 12:52:00 node-2 kernel: [    0.462429] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 30 12:52:00 node-2 kernel: [    0.462456] PCI host bridge to bus 0000:ff
Jul 30 12:52:00 node-2 kernel: [    0.462458] pci_bus 0000:ff: root bus resource [bus ff]
Jul 30 12:52:00 node-2 kernel: [    0.462466] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.462504] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 30 12:52:00 node-2 kernel: [    0.462535] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.462569] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.462598] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 30 12:52:00 node-2 kernel: [    0.462626] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 30 12:52:00 node-2 kernel: [    0.462657] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.462685] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.462714] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.462742] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.462768] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.462794] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.462821] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.462847] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.462873] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.462900] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.462929] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.462956] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.462982] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 30 12:52:00 node-2 kernel: [    0.463010] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463035] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 30 12:52:00 node-2 kernel: [    0.463062] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463089] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463120] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 30 12:52:00 node-2 kernel: [    0.463156] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463187] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463216] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463247] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463277] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463309] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463341] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463372] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463402] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463434] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463464] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463495] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463528] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463557] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463585] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463616] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463647] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463684] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463718] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463751] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463779] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463809] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463840] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463870] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463901] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463931] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463963] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.463991] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464019] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464047] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464076] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464106] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464137] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464194] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 30 12:52:00 node-2 kernel: [    0.464196] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 30 12:52:00 node-2 kernel: [    0.464199] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 30 12:52:00 node-2 kernel: [    0.464216] PCI host bridge to bus 0000:7f
Jul 30 12:52:00 node-2 kernel: [    0.464218] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 30 12:52:00 node-2 kernel: [    0.464223] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464250] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 30 12:52:00 node-2 kernel: [    0.464277] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464306] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464328] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 30 12:52:00 node-2 kernel: [    0.464352] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 30 12:52:00 node-2 kernel: [    0.464381] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464407] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464431] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464456] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464480] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464502] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464526] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464548] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464571] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464596] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464618] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464640] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464663] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 30 12:52:00 node-2 kernel: [    0.464686] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464708] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 30 12:52:00 node-2 kernel: [    0.464729] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464751] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464778] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 30 12:52:00 node-2 kernel: [    0.464810] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464836] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464864] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464891] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464916] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464942] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464967] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.464995] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465019] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465047] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465075] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465103] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465130] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465156] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465182] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465209] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465234] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465260] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465290] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465318] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465345] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465369] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465395] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465421] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465448] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465475] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465505] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465531] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465553] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465579] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465605] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465635] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.465661] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.466922] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 30 12:52:00 node-2 kernel: [    0.466926] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 30 12:52:00 node-2 kernel: [    0.468043] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 30 12:52:00 node-2 kernel: [    0.468558] PCI host bridge to bus 0000:00
Jul 30 12:52:00 node-2 kernel: [    0.468560] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 30 12:52:00 node-2 kernel: [    0.468562] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 30 12:52:00 node-2 kernel: [    0.468563] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 30 12:52:00 node-2 kernel: [    0.468564] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 30 12:52:00 node-2 kernel: [    0.468566] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 30 12:52:00 node-2 kernel: [    0.468567] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 30 12:52:00 node-2 kernel: [    0.468569] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 30 12:52:00 node-2 kernel: [    0.468574] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 30 12:52:00 node-2 kernel: [    0.468657] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 30 12:52:00 node-2 kernel: [    0.468688] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 30 12:52:00 node-2 kernel: [    0.468729] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 30 12:52:00 node-2 kernel: [    0.468748] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 30 12:52:00 node-2 kernel: [    0.468777] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 30 12:52:00 node-2 kernel: [    0.468817] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 30 12:52:00 node-2 kernel: [    0.468835] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 30 12:52:00 node-2 kernel: [    0.468865] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 30 12:52:00 node-2 kernel: [    0.468904] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 30 12:52:00 node-2 kernel: [    0.468921] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.468993] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.469070] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.469148] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 30 12:52:00 node-2 kernel: [    0.469153] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 30 12:52:00 node-2 kernel: [    0.469237] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 30 12:52:00 node-2 kernel: [    0.469386] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 30 12:52:00 node-2 kernel: [    0.469403] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 30 12:52:00 node-2 kernel: [    0.469481] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 30 12:52:00 node-2 kernel: [    0.469535] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 30 12:52:00 node-2 kernel: [    0.469557] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 30 12:52:00 node-2 kernel: [    0.469612] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 30 12:52:00 node-2 kernel: [    0.469656] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 30 12:52:00 node-2 kernel: [    0.469684] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 30 12:52:00 node-2 kernel: [    0.469739] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 30 12:52:00 node-2 kernel: [    0.469782] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 30 12:52:00 node-2 kernel: [    0.469805] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 30 12:52:00 node-2 kernel: [    0.469823] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 30 12:52:00 node-2 kernel: [    0.469900] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 30 12:52:00 node-2 kernel: [    0.469950] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 30 12:52:00 node-2 kernel: [    0.469977] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 30 12:52:00 node-2 kernel: [    0.470226] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 30 12:52:00 node-2 kernel: [    0.470231] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 30 12:52:00 node-2 kernel: [    0.470238] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 30 12:52:00 node-2 kernel: [    0.470243] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 30 12:52:00 node-2 kernel: [    0.470251] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 30 12:52:00 node-2 kernel: [    0.470281] pci 0000:01:00.0: supports D1 D2
Jul 30 12:52:00 node-2 kernel: [    0.480377] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 30 12:52:00 node-2 kernel: [    0.480384] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 30 12:52:00 node-2 kernel: [    0.480388] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 30 12:52:00 node-2 kernel: [    0.480641] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 30 12:52:00 node-2 kernel: [    0.480675] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 30 12:52:00 node-2 kernel: [    0.488375] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 30 12:52:00 node-2 kernel: [    0.488381] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 30 12:52:00 node-2 kernel: [    0.488385] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 30 12:52:00 node-2 kernel: [    0.488468] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 30 12:52:00 node-2 kernel: [    0.488541] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 30 12:52:00 node-2 kernel: [    0.488635] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 30 12:52:00 node-2 kernel: [    0.488696] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 30 12:52:00 node-2 kernel: [    0.488699] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 12:52:00 node-2 kernel: [    0.488701] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 30 12:52:00 node-2 kernel: [    0.488754] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 30 12:52:00 node-2 kernel: [    0.488893] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 30 12:52:00 node-2 kernel: [    0.488948] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 30 12:52:00 node-2 kernel: [    0.488951] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 12:52:00 node-2 kernel: [    0.488953] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 30 12:52:00 node-2 kernel: [    0.489001] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 30 12:52:00 node-2 kernel: [    0.489121] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 30 12:52:00 node-2 kernel: [    0.489164] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 30 12:52:00 node-2 kernel: [    0.489283] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 30 12:52:00 node-2 kernel: [    0.489319] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 30 12:52:00 node-2 kernel: [    0.489439] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 30 12:52:00 node-2 kernel: [    0.489476] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 30 12:52:00 node-2 kernel: [    0.489597] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 30 12:52:00 node-2 kernel: [    0.489638] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 30 12:52:00 node-2 kernel: [    0.489641] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 12:52:00 node-2 kernel: [    0.489643] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 30 12:52:00 node-2 kernel: [    0.489703] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 30 12:52:00 node-2 kernel: [    0.489767] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 30 12:52:00 node-2 kernel: [    0.489819] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 30 12:52:00 node-2 kernel: [    0.489860] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 30 12:52:00 node-2 kernel: [    0.489966] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 30 12:52:00 node-2 kernel: [    0.490073] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 30 12:52:00 node-2 kernel: [    0.490076] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 12:52:00 node-2 kernel: [    0.490078] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 30 12:52:00 node-2 kernel: [    0.490134] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 30 12:52:00 node-2 kernel: [    0.490191] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 30 12:52:00 node-2 kernel: [    0.490239] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 30 12:52:00 node-2 kernel: [    0.490452] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 30 12:52:00 node-2 kernel: [    0.490456] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 30 12:52:00 node-2 kernel: [    0.490519] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 30 12:52:00 node-2 kernel: [    0.490572] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 30 12:52:00 node-2 kernel: [    0.490620] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 30 12:52:00 node-2 kernel: [    0.490832] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 30 12:52:00 node-2 kernel: [    0.490835] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 30 12:52:00 node-2 kernel: [    0.490912] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 30 12:52:00 node-2 kernel: [    0.490976] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 30 12:52:00 node-2 kernel: [    0.491028] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 30 12:52:00 node-2 kernel: [    0.491248] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 30 12:52:00 node-2 kernel: [    0.491251] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 30 12:52:00 node-2 kernel: [    0.491425] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 30 12:52:00 node-2 kernel: [    0.491463] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 30 12:52:00 node-2 kernel: [    0.491539] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 30 12:52:00 node-2 kernel: [    0.491558] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 30 12:52:00 node-2 kernel: [    0.491571] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 30 12:52:00 node-2 kernel: [    0.491584] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 30 12:52:00 node-2 kernel: [    0.491634] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 30 12:52:00 node-2 kernel: [    0.496379] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 30 12:52:00 node-2 kernel: [    0.496384] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 30 12:52:00 node-2 kernel: [    0.496415] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 30 12:52:00 node-2 kernel: [    0.496904] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 30 12:52:00 node-2 kernel: [    0.496908] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 30 12:52:00 node-2 kernel: [    0.497027] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 30 12:52:00 node-2 kernel: [    0.497134] PCI host bridge to bus 0000:80
Jul 30 12:52:00 node-2 kernel: [    0.497136] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 30 12:52:00 node-2 kernel: [    0.497137] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 30 12:52:00 node-2 kernel: [    0.497139] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 30 12:52:00 node-2 kernel: [    0.497147] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.497210] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.497277] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 30 12:52:00 node-2 kernel: [    0.497338] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 30 12:52:00 node-2 kernel: [    0.497343] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 30 12:52:00 node-2 kernel: [    0.497413] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 30 12:52:00 node-2 kernel: [    0.497710] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 30 12:52:00 node-2 kernel: [    0.497741] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 30 12:52:00 node-2 kernel: [    0.497771] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 30 12:52:00 node-2 kernel: [    0.497800] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 30 12:52:00 node-2 kernel: [    0.497830] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 30 12:52:00 node-2 kernel: [    0.497860] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 30 12:52:00 node-2 kernel: [    0.497889] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 30 12:52:00 node-2 kernel: [    0.497919] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 30 12:52:00 node-2 kernel: [    0.498003] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 30 12:52:00 node-2 kernel: [    0.498007] ACPI: \_SB_.UNC1: notify handler is installed
Jul 30 12:52:00 node-2 kernel: [    0.498008] ACPI: \_SB_.UNC0: notify handler is installed
Jul 30 12:52:00 node-2 kernel: [    0.498023] ACPI: \_SB_.PCI0: notify handler is installed
Jul 30 12:52:00 node-2 kernel: [    0.498076] ACPI: \_SB_.PCI1: notify handler is installed
Jul 30 12:52:00 node-2 kernel: [    0.498156] Found 4 acpi root devices
Jul 30 12:52:00 node-2 kernel: [    0.498272] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 30 12:52:00 node-2 kernel: [    0.498274] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 30 12:52:00 node-2 kernel: [    0.498276] vgaarb: loaded
Jul 30 12:52:00 node-2 kernel: [    0.498277] vgaarb: bridge control possible 0000:0c:00.0
Jul 30 12:52:00 node-2 kernel: [    0.498392] SCSI subsystem initialized
Jul 30 12:52:00 node-2 kernel: [    0.498456] libata version 3.00 loaded.
Jul 30 12:52:00 node-2 kernel: [    0.498470] ACPI: bus type USB registered
Jul 30 12:52:00 node-2 kernel: [    0.498480] usbcore: registered new interface driver usbfs
Jul 30 12:52:00 node-2 kernel: [    0.498485] usbcore: registered new interface driver hub
Jul 30 12:52:00 node-2 kernel: [    0.498508] usbcore: registered new device driver usb
Jul 30 12:52:00 node-2 kernel: [    0.498669] PCI: Using ACPI for IRQ routing
Jul 30 12:52:00 node-2 kernel: [    0.502268] PCI: pci_cache_line_size set to 64 bytes
Jul 30 12:52:00 node-2 kernel: [    0.502471] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 30 12:52:00 node-2 kernel: [    0.502472] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Jul 30 12:52:00 node-2 kernel: [    0.502473] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 30 12:52:00 node-2 kernel: [    0.502538] NetLabel: Initializing
Jul 30 12:52:00 node-2 kernel: [    0.502539] NetLabel:  domain hash size = 128
Jul 30 12:52:00 node-2 kernel: [    0.502540] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 30 12:52:00 node-2 kernel: [    0.502549] NetLabel:  unlabeled traffic allowed by default
Jul 30 12:52:00 node-2 kernel: [    0.502605] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 30 12:52:00 node-2 kernel: [    0.502609] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 30 12:52:00 node-2 kernel: [    0.504674] Switched to clocksource hpet
Jul 30 12:52:00 node-2 kernel: [    0.508699] AppArmor: AppArmor Filesystem Enabled
Jul 30 12:52:00 node-2 kernel: [    0.508712] pnp: PnP ACPI init
Jul 30 12:52:00 node-2 kernel: [    0.508719] ACPI: bus type PNP registered
Jul 30 12:52:00 node-2 kernel: [    0.508828] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 30 12:52:00 node-2 kernel: [    0.508836] pnp 00:01: [dma 4]
Jul 30 12:52:00 node-2 kernel: [    0.508847] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 30 12:52:00 node-2 kernel: [    0.508874] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 30 12:52:00 node-2 kernel: [    0.508893] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 30 12:52:00 node-2 kernel: [    0.508910] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 30 12:52:00 node-2 kernel: [    0.508943] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 30 12:52:00 node-2 kernel: [    0.508995] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 30 12:52:00 node-2 kernel: [    0.508997] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 30 12:52:00 node-2 kernel: [    0.508999] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 30 12:52:00 node-2 kernel: [    0.509000] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 30 12:52:00 node-2 kernel: [    0.509002] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 30 12:52:00 node-2 kernel: [    0.509006] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 30 12:52:00 node-2 kernel: [    0.509008] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 30 12:52:00 node-2 kernel: [    0.509010] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 30 12:52:00 node-2 kernel: [    0.509011] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 30 12:52:00 node-2 kernel: [    0.509013] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 30 12:52:00 node-2 kernel: [    0.509014] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 30 12:52:00 node-2 kernel: [    0.509016] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 30 12:52:00 node-2 kernel: [    0.509017] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 30 12:52:00 node-2 kernel: [    0.509020] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 30 12:52:00 node-2 kernel: [    0.509103] pnp 00:07: [dma 0 disabled]
Jul 30 12:52:00 node-2 kernel: [    0.509131] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 30 12:52:00 node-2 kernel: [    0.509206] pnp 00:08: [dma 0 disabled]
Jul 30 12:52:00 node-2 kernel: [    0.509237] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 30 12:52:00 node-2 kernel: [    0.509288] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 30 12:52:00 node-2 kernel: [    0.509634] pnp: PnP ACPI: found 10 devices
Jul 30 12:52:00 node-2 kernel: [    0.509636] ACPI: bus type PNP unregistered
Jul 30 12:52:00 node-2 kernel: [    0.515913] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 30 12:52:00 node-2 kernel: [    0.515916] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 30 12:52:00 node-2 kernel: [    0.515918] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 30 12:52:00 node-2 kernel: [    0.515923] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 30 12:52:00 node-2 kernel: [    0.515925] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 12:52:00 node-2 kernel: [    0.515939] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 30 12:52:00 node-2 kernel: [    0.515968] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 30 12:52:00 node-2 kernel: [    0.515982] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 30 12:52:00 node-2 kernel: [    0.516011] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 30 12:52:00 node-2 kernel: [    0.516026] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 30 12:52:00 node-2 kernel: [    0.516054] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 30 12:52:00 node-2 kernel: [    0.516069] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 30 12:52:00 node-2 kernel: [    0.516097] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 30 12:52:00 node-2 kernel: [    0.516099] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 12:52:00 node-2 kernel: [    0.516114] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 30 12:52:00 node-2 kernel: [    0.516143] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 30 12:52:00 node-2 kernel: [    0.516144] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 12:52:00 node-2 kernel: [    0.516159] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 30 12:52:00 node-2 kernel: [    0.516191] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 30 12:52:00 node-2 kernel: [    0.516192] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 12:52:00 node-2 kernel: [    0.516195] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 30 12:52:00 node-2 kernel: [    0.516199] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 30 12:52:00 node-2 kernel: [    0.516201] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 30 12:52:00 node-2 kernel: [    0.516203] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 30 12:52:00 node-2 kernel: [    0.516207] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 30 12:52:00 node-2 kernel: [    0.516212] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 30 12:52:00 node-2 kernel: [    0.516220] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 30 12:52:00 node-2 kernel: [    0.516223] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 30 12:52:00 node-2 kernel: [    0.516230] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 30 12:52:00 node-2 kernel: [    0.516231] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 30 12:52:00 node-2 kernel: [    0.516231] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 30 12:52:00 node-2 kernel: [    0.516232] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 30 12:52:00 node-2 kernel: [    0.516233] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 30 12:52:00 node-2 kernel: [    0.516234] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 30 12:52:00 node-2 kernel: [    0.516235] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 30 12:52:00 node-2 kernel: [    0.516236] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 30 12:52:00 node-2 kernel: [    0.516237] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 30 12:52:00 node-2 kernel: [    0.516238] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 30 12:52:00 node-2 kernel: [    0.516239] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 30 12:52:00 node-2 kernel: [    0.516239] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 30 12:52:00 node-2 kernel: [    0.516240] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 30 12:52:00 node-2 kernel: [    0.516241] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 30 12:52:00 node-2 kernel: [    0.516242] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 30 12:52:00 node-2 kernel: [    0.516243] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 30 12:52:00 node-2 kernel: [    0.516244] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 30 12:52:00 node-2 kernel: [    0.516245] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 30 12:52:00 node-2 kernel: [    0.516246] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 30 12:52:00 node-2 kernel: [    0.516247] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 30 12:52:00 node-2 kernel: [    0.516248] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 30 12:52:00 node-2 kernel: [    0.516249] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 30 12:52:00 node-2 kernel: [    0.516251] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 30 12:52:00 node-2 kernel: [    0.516252] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 30 12:52:00 node-2 kernel: [    0.516290] NET: Registered protocol family 2
Jul 30 12:52:00 node-2 kernel: [    0.516556] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 30 12:52:00 node-2 kernel: [    0.516894] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 30 12:52:00 node-2 kernel: [    0.517040] TCP: Hash tables configured (established 262144 bind 65536)
Jul 30 12:52:00 node-2 kernel: [    0.517077] TCP: reno registered
Jul 30 12:52:00 node-2 kernel: [    0.517104] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 30 12:52:00 node-2 kernel: [    0.517199] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 30 12:52:00 node-2 kernel: [    0.517348] NET: Registered protocol family 1
Jul 30 12:52:00 node-2 kernel: [    0.552773] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 30 12:52:00 node-2 kernel: [    0.552787] PCI: CLS 64 bytes, default 64
Jul 30 12:52:00 node-2 kernel: [    0.552864] Trying to unpack rootfs image as initramfs...
Jul 30 12:52:00 node-2 kernel: [    0.772152] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 30 12:52:00 node-2 kernel: [    0.772187] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 30 12:52:00 node-2 kernel: [    0.772189] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Jul 30 12:52:00 node-2 kernel: [    0.772637] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 12:52:00 node-2 kernel: [    0.772643] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 12:52:00 node-2 kernel: [    0.772648] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 12:52:00 node-2 kernel: [    0.772654] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 12:52:00 node-2 kernel: [    0.772663] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 12:52:00 node-2 kernel: [    0.772674] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 12:52:00 node-2 kernel: [    0.772683] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 12:52:00 node-2 kernel: [    0.772692] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 12:52:00 node-2 kernel: [    0.772700] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 12:52:00 node-2 kernel: [    0.772713] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 12:52:00 node-2 kernel: [    0.772719] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 12:52:00 node-2 kernel: [    0.772725] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 12:52:00 node-2 kernel: [    0.772732] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 12:52:00 node-2 kernel: [    0.772740] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 12:52:00 node-2 kernel: [    0.772747] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 12:52:00 node-2 kernel: [    0.772754] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 12:52:00 node-2 kernel: [    0.772829] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 30 12:52:00 node-2 kernel: [    0.772832] Scanning for low memory corruption every 60 seconds
Jul 30 12:52:00 node-2 kernel: [    0.773214] Initialise system trusted keyring
Jul 30 12:52:00 node-2 kernel: [    0.773266] audit: initializing netlink socket (disabled)
Jul 30 12:52:00 node-2 kernel: [    0.773283] type=2000 audit(1469883084.724:1): initialized
Jul 30 12:52:00 node-2 kernel: [    0.791166] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 30 12:52:00 node-2 kernel: [    0.792680] zbud: loaded
Jul 30 12:52:00 node-2 kernel: [    0.792806] VFS: Disk quotas dquot_6.5.2
Jul 30 12:52:00 node-2 kernel: [    0.792840] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 30 12:52:00 node-2 kernel: [    0.793214] fuse init (API version 7.22)
Jul 30 12:52:00 node-2 kernel: [    0.793275] msgmni has been set to 32768
Jul 30 12:52:00 node-2 kernel: [    0.793322] Key type big_key registered
Jul 30 12:52:00 node-2 kernel: [    0.793852] Key type asymmetric registered
Jul 30 12:52:00 node-2 kernel: [    0.793854] Asymmetric key parser 'x509' registered
Jul 30 12:52:00 node-2 kernel: [    0.793875] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 30 12:52:00 node-2 kernel: [    0.793971] io scheduler noop registered
Jul 30 12:52:00 node-2 kernel: [    0.793973] io scheduler deadline registered (default)
Jul 30 12:52:00 node-2 kernel: [    0.793990] io scheduler cfq registered
Jul 30 12:52:00 node-2 kernel: [    0.794410] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    0.794531] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    0.794642] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    0.794774] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    0.794884] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    0.795002] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    0.795380] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 30 12:52:00 node-2 kernel: [    0.795405] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 30 12:52:00 node-2 kernel: [    0.795421] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 30 12:52:00 node-2 kernel: [    0.795430] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795432] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795435] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 30 12:52:00 node-2 kernel: [    0.795440] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795441] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795443] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795445] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795446] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795448] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795449] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795451] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795452] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795453] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795455] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795456] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795458] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 30 12:52:00 node-2 kernel: [    0.795463] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795466] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 30 12:52:00 node-2 kernel: [    0.795480] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795484] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 30 12:52:00 node-2 kernel: [    0.795494] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795495] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 30 12:52:00 node-2 kernel: [    0.795498] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 30 12:52:00 node-2 kernel: [    0.795533] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 30 12:52:00 node-2 kernel: [    0.795540] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 30 12:52:00 node-2 kernel: [    0.795544] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 30 12:52:00 node-2 kernel: [    0.795554] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 30 12:52:00 node-2 kernel: [    0.795593] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 30 12:52:00 node-2 kernel: [    0.795595] vesafb: scrolling: redraw
Jul 30 12:52:00 node-2 kernel: [    0.795596] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 30 12:52:00 node-2 kernel: [    0.816252] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 30 12:52:00 node-2 kernel: [    0.824748] Console: switching to colour frame buffer device 80x30
Jul 30 12:52:00 node-2 kernel: [    0.833415] fb0: VESA VGA frame buffer device
Jul 30 12:52:00 node-2 kernel: [    0.833613] intel_idle: MWAIT substates: 0x2120
Jul 30 12:52:00 node-2 kernel: [    0.833614] intel_idle: v0.4 model 0x3F
Jul 30 12:52:00 node-2 kernel: [    0.833615] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 30 12:52:00 node-2 kernel: [    0.833862] ipmi message handler version 39.2
Jul 30 12:52:00 node-2 kernel: [    0.834131] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 30 12:52:00 node-2 kernel: [    0.834566] ACPI: AC Adapter [P111] (on-line)
Jul 30 12:52:00 node-2 kernel: [    0.839781] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 30 12:52:00 node-2 kernel: [    0.850792] ACPI: Power Button [PWRB]
Jul 30 12:52:00 node-2 kernel: [    0.856543] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 30 12:52:00 node-2 kernel: [    0.868166] ACPI: Power Button [PWRF]
Jul 30 12:52:00 node-2 kernel: [    0.894218] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 30 12:52:00 node-2 kernel: [    0.905850] pstore: Registered erst as persistent store backend
Jul 30 12:52:00 node-2 kernel: [    0.912040] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 30 12:52:00 node-2 kernel: [    0.923949] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 30 12:52:00 node-2 kernel: [    0.950668] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 30 12:52:00 node-2 kernel: [    0.984050] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 30 12:52:00 node-2 kernel: [    0.998096] Linux agpgart interface v0.103
Jul 30 12:52:00 node-2 kernel: [    1.005711] brd: module loaded
Jul 30 12:52:00 node-2 kernel: [    1.012757] loop: module loaded
Jul 30 12:52:00 node-2 kernel: [    1.019491] libphy: Fixed MDIO Bus: probed
Jul 30 12:52:00 node-2 kernel: [    1.025945] tun: Universal TUN/TAP device driver, 1.6
Jul 30 12:52:00 node-2 kernel: [    1.032422] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 30 12:52:00 node-2 kernel: [    1.038937] PPP generic driver version 2.4.2
Jul 30 12:52:00 node-2 kernel: [    1.045321] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 30 12:52:00 node-2 kernel: [    1.051766] ehci-pci: EHCI PCI platform driver
Jul 30 12:52:00 node-2 kernel: [    1.058302] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 30 12:52:00 node-2 kernel: [    1.064719] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 30 12:52:00 node-2 kernel: [    1.077247] ehci-pci 0000:00:1a.0: debug port 2
Jul 30 12:52:00 node-2 kernel: [    1.087433] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 30 12:52:00 node-2 kernel: [    1.087451] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 30 12:52:00 node-2 kernel: [    1.104171] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 30 12:52:00 node-2 kernel: [    1.110242] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 30 12:52:00 node-2 kernel: [    1.116412] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 30 12:52:00 node-2 kernel: [    1.128324] usb usb1: Product: EHCI Host Controller
Jul 30 12:52:00 node-2 kernel: [    1.134343] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 30 12:52:00 node-2 kernel: [    1.140376] usb usb1: SerialNumber: 0000:00:1a.0
Jul 30 12:52:00 node-2 kernel: [    1.146322] hub 1-0:1.0: USB hub found
Jul 30 12:52:00 node-2 kernel: [    1.152092] hub 1-0:1.0: 2 ports detected
Jul 30 12:52:00 node-2 kernel: [    1.157902] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 30 12:52:00 node-2 kernel: [    1.163475] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 30 12:52:00 node-2 kernel: [    1.174341] ehci-pci 0000:00:1d.0: debug port 2
Jul 30 12:52:00 node-2 kernel: [    1.183634] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 30 12:52:00 node-2 kernel: [    1.183637] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 30 12:52:00 node-2 kernel: [    1.200089] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 30 12:52:00 node-2 kernel: [    1.205283] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 30 12:52:00 node-2 kernel: [    1.210583] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 30 12:52:00 node-2 kernel: [    1.221131] usb usb2: Product: EHCI Host Controller
Jul 30 12:52:00 node-2 kernel: [    1.226578] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 30 12:52:00 node-2 kernel: [    1.232165] usb usb2: SerialNumber: 0000:00:1d.0
Jul 30 12:52:00 node-2 kernel: [    1.237743] hub 2-0:1.0: USB hub found
Jul 30 12:52:00 node-2 kernel: [    1.243127] hub 2-0:1.0: 2 ports detected
Jul 30 12:52:00 node-2 kernel: [    1.248408] ehci-platform: EHCI generic platform driver
Jul 30 12:52:00 node-2 kernel: [    1.253615] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 30 12:52:00 node-2 kernel: [    1.258917] ohci-pci: OHCI PCI platform driver
Jul 30 12:52:00 node-2 kernel: [    1.264226] ohci-platform: OHCI generic platform driver
Jul 30 12:52:00 node-2 kernel: [    1.269470] uhci_hcd: USB Universal Host Controller Interface driver
Jul 30 12:52:00 node-2 kernel: [    1.274796] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 30 12:52:00 node-2 kernel: [    1.467869] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 30 12:52:00 node-2 kernel: [    1.767678] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 30 12:52:00 node-2 kernel: [    1.783968] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 30 12:52:00 node-2 kernel: [    1.789616] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 30 12:52:00 node-2 kernel: [    1.795360] hub 1-1:1.0: USB hub found
Jul 30 12:52:00 node-2 kernel: [    1.800956] hub 1-1:1.0: 6 ports detected
Jul 30 12:52:00 node-2 kernel: [    1.915510] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 30 12:52:00 node-2 kernel: [    2.313732] i8042: No controller found
Jul 30 12:52:00 node-2 kernel: [    2.319259] mousedev: PS/2 mouse device common for all mice
Jul 30 12:52:00 node-2 kernel: [    2.324971] rtc_cmos 00:02: RTC can wake from S4
Jul 30 12:52:00 node-2 kernel: [    2.327946] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 30 12:52:00 node-2 kernel: [    2.327947] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 30 12:52:00 node-2 kernel: [    2.328705] hub 2-1:1.0: USB hub found
Jul 30 12:52:00 node-2 kernel: [    2.328942] hub 2-1:1.0: 8 ports detected
Jul 30 12:52:00 node-2 kernel: [    2.353243] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 30 12:52:00 node-2 kernel: [    2.358975] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 30 12:52:00 node-2 kernel: [    2.370281] device-mapper: uevent: version 1.0.3
Jul 30 12:52:00 node-2 kernel: [    2.375996] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 30 12:52:00 node-2 kernel: [    2.387525] ledtrig-cpu: registered to indicate activity on CPUs
Jul 30 12:52:00 node-2 kernel: [    2.393547] TCP: cubic registered
Jul 30 12:52:00 node-2 kernel: [    2.399418] NET: Registered protocol family 10
Jul 30 12:52:00 node-2 kernel: [    2.405491] NET: Registered protocol family 17
Jul 30 12:52:00 node-2 kernel: [    2.411266] Key type dns_resolver registered
Jul 30 12:52:00 node-2 kernel: [    2.417362] Loading compiled-in X.509 certificates
Jul 30 12:52:00 node-2 kernel: [    2.423565] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 30 12:52:00 node-2 kernel: [    2.435186] registered taskstats version 1
Jul 30 12:52:00 node-2 kernel: [    2.443262] Key type trusted registered
Jul 30 12:52:00 node-2 kernel: [    2.450900] Key type encrypted registered
Jul 30 12:52:00 node-2 kernel: [    2.456437] AppArmor: AppArmor sha1 policy hashing enabled
Jul 30 12:52:00 node-2 kernel: [    2.461965] IMA: No TPM chip found, activating TPM-bypass!
Jul 30 12:52:00 node-2 kernel: [    2.468115] regulator-dummy: disabling
Jul 30 12:52:00 node-2 kernel: [    2.473659]   Magic number: 8:871:886
Jul 30 12:52:00 node-2 kernel: [    2.479222] acpi device:f5: hash matches
Jul 30 12:52:00 node-2 kernel: [    2.484830] rtc_cmos 00:02: setting system clock to 2016-07-30 12:51:27 UTC (1469883087)
Jul 30 12:52:00 node-2 kernel: [    2.497234] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 30 12:52:00 node-2 kernel: [    2.502859] EDD information not available.
Jul 30 12:52:00 node-2 kernel: [    2.508409] PM: Hibernation image not present or could not be loaded.
Jul 30 12:52:00 node-2 kernel: [    2.509275] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 30 12:52:00 node-2 kernel: [    2.520549] Write protecting the kernel read-only data: 12288k
Jul 30 12:52:00 node-2 kernel: [    2.526942] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 30 12:52:00 node-2 kernel: [    2.539933] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 30 12:52:00 node-2 kernel: [    2.571715] device-mapper: multipath: version 1.6.0 loaded
Jul 30 12:52:00 node-2 kernel: [    2.579483] systemd-udevd[216]: starting version 204
Jul 30 12:52:00 node-2 kernel: [    2.602122] md: linear personality registered for level -1
Jul 30 12:52:00 node-2 kernel: [    2.607123] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 30 12:52:00 node-2 kernel: [    2.621879] md: multipath personality registered for level -4
Jul 30 12:52:00 node-2 kernel: [    2.629948] md: raid0 personality registered for level 0
Jul 30 12:52:00 node-2 kernel: [    2.638336] md: raid1 personality registered for level 1
Jul 30 12:52:00 node-2 kernel: [    2.649600] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 30 12:52:00 node-2 kernel: [    2.655815] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 30 12:52:00 node-2 kernel: [    2.662010] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 30 12:52:00 node-2 kernel: [    2.664629] megasas: FW now in Ready state
Jul 30 12:52:00 node-2 kernel: [    2.665305] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.665413] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.665533] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.665631] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.665747] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.665878] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.666006] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.666132] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.666269] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.666439] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.666549] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.666665] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.666805] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.667073] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.667232] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.667349] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.667985] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 30 12:52:00 node-2 kernel: [    2.695767] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Jul 30 12:52:00 node-2 kernel: [    2.708913] 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 30 12:52:00 node-2 kernel: [    2.710952] raid6: sse2x1    2399 MB/s
Jul 30 12:52:00 node-2 kernel: [    2.729515] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 30 12:52:00 node-2 kernel: [    2.736448] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.736454] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.736459] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.736464] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.736512] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 30 12:52:00 node-2 kernel: [    2.743660] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 30 12:52:00 node-2 kernel: [    2.743671] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 30 12:52:00 node-2 kernel: [    2.743672] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 30 12:52:00 node-2 kernel: [    2.743684] usb 2-1.4: Manufacturer: Avocent
Jul 30 12:52:00 node-2 kernel: [    2.743685] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 30 12:52:00 node-2 kernel: [    2.779017] raid6: sse2x2     768 MB/s
Jul 30 12:52:00 node-2 kernel: [    2.846705] raid6: sse2x4    8421 MB/s
Jul 30 12:52:00 node-2 kernel: [    2.918643] raid6: avx2x1   14935 MB/s
Jul 30 12:52:00 node-2 kernel: [    2.990580] raid6: avx2x2   18863 MB/s
Jul 30 12:52:00 node-2 kernel: [    3.062518] raid6: avx2x4   21223 MB/s
Jul 30 12:52:00 node-2 kernel: [    3.068090] raid6: using algorithm avx2x4 (21223 MB/s)
Jul 30 12:52:00 node-2 kernel: [    3.073679] raid6: using avx2x2 recovery algorithm
Jul 30 12:52:00 node-2 kernel: [    3.079160] Switched to clocksource tsc
Jul 30 12:52:00 node-2 kernel: [    3.079167] megasas:IOC Init cmd success
Jul 30 12:52:00 node-2 kernel: [    3.088620] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Jul 30 12:52:00 node-2 kernel: [    3.088621] 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 30 12:52:00 node-2 kernel: [    3.088622] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 30 12:52:00 node-2 kernel: [    3.088690] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    3.088719] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    3.088755] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    3.088794] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    3.088883] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 30 12:52:00 node-2 kernel: [    3.098245] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Jul 30 12:52:00 node-2 kernel: [    3.098247] 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 30 12:52:00 node-2 kernel: [    3.098248] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 30 12:52:00 node-2 kernel: [    3.098309] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    3.098345] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    3.098370] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    3.098408] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    3.098490] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 30 12:52:00 node-2 kernel: [    3.106494] megasas: INIT adapter done
Jul 30 12:52:00 node-2 kernel: [    3.108936] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Jul 30 12:52:00 node-2 kernel: [    3.108937] 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 30 12:52:00 node-2 kernel: [    3.108938] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 30 12:52:00 node-2 kernel: [    3.109002] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    3.109037] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    3.109067] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    3.109099] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 30 12:52:00 node-2 kernel: [    3.109184] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 30 12:52:00 node-2 kernel: [    3.167714] xor: automatically using best checksumming function:
Jul 30 12:52:00 node-2 kernel: [    3.174410] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 30 12:52:00 node-2 kernel: [    3.174744] scsi0 : LSI SAS based MegaRAID driver
Jul 30 12:52:00 node-2 kernel: [    3.181725] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 30 12:52:00 node-2 kernel: [    3.184106] hidraw: raw HID events driver (C) Jiri Kosina
Jul 30 12:52:00 node-2 kernel: [    3.194184] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 30 12:52:00 node-2 kernel: [    3.199464] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 30 12:52:00 node-2 kernel: [    3.199635] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 30 12:52:00 node-2 kernel: [    3.199932] sd 0:2:0:0: [sda] Write Protect is off
Jul 30 12:52:00 node-2 kernel: [    3.199933] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 30 12:52:00 node-2 kernel: [    3.200004] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 30 12:52:00 node-2 kernel: [    3.206377]    avx       : 35596.000 MB/sec
Jul 30 12:52:00 node-2 kernel: [    3.229695]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 30 12:52:00 node-2 kernel: [    3.231711] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 30 12:52:00 node-2 kernel: [    3.254197] usbcore: registered new interface driver usbhid
Jul 30 12:52:00 node-2 kernel: [    3.254198] usbhid: USB HID core driver
Jul 30 12:52:00 node-2 kernel: [    3.284435] async_tx: api initialized (async)
Jul 30 12:52:00 node-2 kernel: [    3.342360] 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 30 12:52:00 node-2 kernel: [    3.355254] 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 30 12:52:00 node-2 kernel: [    3.368428] 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 30 12:52:00 node-2 kernel: [    3.381598] 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 30 12:52:00 node-2 kernel: [    3.395107] 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 30 12:52:00 node-2 kernel: [    3.396028] md: raid6 personality registered for level 6
Jul 30 12:52:00 node-2 kernel: [    3.396030] md: raid5 personality registered for level 5
Jul 30 12:52:00 node-2 kernel: [    3.396040] md: raid4 personality registered for level 4
Jul 30 12:52:00 node-2 kernel: [    3.429088] 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 30 12:52:00 node-2 kernel: [    3.436524] random: lvm urandom read with 32 bits of entropy available
Jul 30 12:52:00 node-2 kernel: [    3.451225] md: raid10 personality registered for level 10
Jul 30 12:52:00 node-2 kernel: [    3.506487] multipathd (367): /proc/367/oom_adj is deprecated, please use /proc/367/oom_score_adj instead.
Jul 30 12:52:00 node-2 kernel: [    3.615561] bio: create slab <bio-1> at 1
Jul 30 12:52:00 node-2 kernel: [    4.392303] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 30 12:52:00 node-2 kernel: [    4.896797] init: plymouth-upstart-bridge main process (553) terminated with status 1
Jul 30 12:52:00 node-2 kernel: [    4.909523] init: plymouth-upstart-bridge main process ended, respawning
Jul 30 12:52:00 node-2 kernel: [    5.052522] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 30 12:52:00 node-2 kernel: [    5.103913] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 30 12:52:00 node-2 kernel: [    5.117420] random: nonblocking pool is initialized
Jul 30 12:52:00 node-2 kernel: [    5.223395] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 30 12:52:00 node-2 kernel: [    5.277234] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 30 12:52:00 node-2 kernel: [    5.346529] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 30 12:52:00 node-2 kernel: [    5.575262] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 30 12:52:00 node-2 kernel: [    5.654968] XFS (dm-0): Mounting Filesystem
Jul 30 12:52:00 node-2 kernel: [    5.859739] XFS (dm-0): Ending clean mount
Jul 30 12:52:00 node-2 kernel: [    5.909529] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 30 12:52:00 node-2 kernel: [    5.942217] XFS (dm-1): Mounting Filesystem
Jul 30 12:52:00 node-2 kernel: [    6.019449] XFS (dm-1): Ending clean mount
Jul 30 12:52:00 node-2 kernel: [    7.974353] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 30 12:52:00 node-2 kernel: [    8.002526] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 30 12:52:00 node-2 kernel: [    8.174138] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 30 12:52:00 node-2 kernel: [    8.174143] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 30 12:52:00 node-2 kernel: [    8.174147] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 30 12:52:00 node-2 kernel: [    8.174157] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 30 12:52:00 node-2 kernel: [    8.228394] systemd-udevd[777]: starting version 204
Jul 30 12:52:00 node-2 kernel: [    8.439863] power_meter ACPI000D:00: Found ACPI power meter.
Jul 30 12:52:00 node-2 kernel: [    8.439874] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 30 12:52:00 node-2 kernel: [    8.472350] wmi: Mapper loaded
Jul 30 12:52:00 node-2 kernel: [    8.477257] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 30 12:52:00 node-2 kernel: [    8.477262] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 30 12:52:00 node-2 kernel: [    8.477265] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 30 12:52:00 node-2 kernel: [    8.477266] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 30 12:52:00 node-2 kernel: [    8.477288] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 30 12:52:00 node-2 kernel: [    8.487492] IPMI System Interface driver.
Jul 30 12:52:00 node-2 kernel: [    8.487532] ipmi_si: probing via ACPI
Jul 30 12:52:00 node-2 kernel: [    8.487544] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 30 12:52:00 node-2 kernel: [    8.487545] ipmi_si: Adding ACPI-specified kcs state machine
Jul 30 12:52:00 node-2 kernel: [    8.487552] ipmi_si: probing via SMBIOS
Jul 30 12:52:00 node-2 kernel: [    8.487553] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 30 12:52:00 node-2 kernel: [    8.487554] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 30 12:52:00 node-2 kernel: [    8.487555] ipmi_si: probing via SPMI
Jul 30 12:52:00 node-2 kernel: [    8.487556] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 30 12:52:00 node-2 kernel: [    8.487557] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 30 12:52:00 node-2 kernel: [    8.487558] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 30 12:52:00 node-2 kernel: [    8.505395] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 30 12:52:00 node-2 kernel: [    8.554335] systemd-udevd[796]: renamed network interface eth0 to enp6s0
Jul 30 12:52:00 node-2 kernel: [    8.581273] systemd-udevd[801]: renamed network interface eth1 to enp7s0
Jul 30 12:52:00 node-2 kernel: [    8.614179] systemd-udevd[806]: renamed network interface eth2 to enp8s0
Jul 30 12:52:00 node-2 kernel: [    8.633238] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 30 12:52:00 node-2 kernel: [    8.633244] ipmi_si 00:09: IPMI kcs interface initialized
Jul 30 12:52:00 node-2 kernel: [    8.646149] systemd-udevd[795]: renamed network interface eth3 to enp9s0
Jul 30 12:52:00 node-2 kernel: [    8.999749] type=1400 audit(1469883094.015:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1058 comm="apparmor_parser"
Jul 30 12:52:00 node-2 kernel: [    8.999904] type=1400 audit(1469883094.015:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1058 comm="apparmor_parser"
Jul 30 12:52:00 node-2 kernel: [    9.000035] type=1400 audit(1469883094.015:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1058 comm="apparmor_parser"
Jul 30 12:52:00 node-2 kernel: [    9.012134] type=1400 audit(1469883094.027:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1059 comm="apparmor_parser"
Jul 30 12:52:00 node-2 kernel: [    9.012275] type=1400 audit(1469883094.027:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1059 comm="apparmor_parser"
Jul 30 12:52:00 node-2 kernel: [    9.012394] type=1400 audit(1469883094.027:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1059 comm="apparmor_parser"
Jul 30 12:52:00 node-2 kernel: [    9.015949] type=1400 audit(1469883094.031:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1053 comm="apparmor_parser"
Jul 30 12:52:00 node-2 kernel: [    9.016101] type=1400 audit(1469883094.031:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1053 comm="apparmor_parser"
Jul 30 12:52:00 node-2 kernel: [    9.016220] type=1400 audit(1469883094.031:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1053 comm="apparmor_parser"
Jul 30 12:52:00 node-2 kernel: [    9.018773] type=1400 audit(1469883094.035:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1055 comm="apparmor_parser"
Jul 30 12:52:00 node-2 kernel: [    9.628058] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 30 12:52:00 node-2 kernel: [    9.628759] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 30 12:52:00 node-2 kernel: [    9.773797] enic 0000:06:00.0 enp6s0: Link UP
Jul 30 12:52:00 node-2 kernel: [    9.774819] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 30 12:52:00 node-2 kernel: [    9.774824] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 30 12:52:00 node-2 kernel: [   18.595810] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 30 12:52:00 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 30 12:52:01 node-2 failsafe: Failsafe of 120 seconds reached.
Jul 30 12:52:02 node-2 kernel: [   37.890442] init: failsafe main process (8397) killed by TERM signal
Jul 30 12:52:02 node-2 dbus[8448]: [system] AppArmor D-Bus mediation is enabled
Jul 30 12:52:02 node-2 kernel: [   38.078674] audit_printk_skb: 30 callbacks suppressed
Jul 30 12:52:02 node-2 kernel: [   38.078676] type=1400 audit(1469883122.202:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8517 comm="apparmor_parser"
Jul 30 12:52:02 node-2 kernel: [   38.082960] type=1400 audit(1469883122.206:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8516 comm="apparmor_parser"
Jul 30 12:52:02 node-2 kernel: [   38.082964] type=1400 audit(1469883122.206:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8516 comm="apparmor_parser"
Jul 30 12:52:02 node-2 kernel: [   38.082966] type=1400 audit(1469883122.206:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8516 comm="apparmor_parser"
Jul 30 12:52:02 node-2 kernel: [   38.083186] type=1400 audit(1469883122.206:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8516 comm="apparmor_parser"
Jul 30 12:52:02 node-2 kernel: [   38.083187] type=1400 audit(1469883122.206:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8516 comm="apparmor_parser"
Jul 30 12:52:02 node-2 kernel: [   38.083300] type=1400 audit(1469883122.206:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8516 comm="apparmor_parser"
Jul 30 12:52:02 node-2 kernel: [   38.152999] type=1400 audit(1469883122.278:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8519 comm="apparmor_parser"
Jul 30 12:52:02 node-2 cron[8557]: (CRON) INFO (pidfile fd = 3)
Jul 30 12:52:02 node-2 anacron[8592]: Anacron 2.3 started on 2016-07-30
Jul 30 12:52:02 node-2 cron[8599]: (CRON) STARTUP (fork ok)
Jul 30 12:52:02 node-2 multipathd: path checkers start up
Jul 30 12:52:02 node-2 cron[8599]: (CRON) INFO (Running @reboot jobs)
Jul 30 12:52:02 node-2 anacron[8592]: Will run job `cron.daily' in 5 min.
Jul 30 12:52:02 node-2 anacron[8592]: Will run job `cron.weekly' in 10 min.
Jul 30 12:52:02 node-2 anacron[8592]: Will run job `cron.monthly' in 15 min.
Jul 30 12:52:02 node-2 anacron[8592]: Jobs will be executed sequentially
Jul 30 12:52:02 node-2 postfix/master[8736]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 30 12:52:06 node-2 puppet-agent[8921]: Reopening log files
Jul 30 12:52:06 node-2 puppet-agent[8921]: Could not request certificate: Connection refused - connect(2)
Jul 30 12:52:20 node-2 puppet-user[9000]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 30 12:52:20 node-2 puppet-user[9000]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Jul 30 12:52:21 node-2 puppet-user[9000]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 30 12:52:21 node-2 puppet-user[9000]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 30 12:52:21 node-2 puppet-user[9000]: Finished catalog run in 0.63 seconds
Jul 30 12:52:22 node-2 multipathd: uevent trigger error
Jul 30 12:52:22 node-2 puppet-user[9425]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 30 12:52:22 node-2 puppet-user[9425]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Jul 30 12:52:22 node-2 puppet-user[9425]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 30 12:52:22 node-2 puppet-user[9425]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 30 12:52:22 node-2 puppet-user[9425]: (/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 30 12:52:22 node-2 puppet-user[9425]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 30 12:52:22 node-2 puppet-user[9425]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 30 12:52:22 node-2 puppet-user[9425]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 30 12:52:22 node-2 puppet-user[9425]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 30 12:52:22 node-2 puppet-user[9425]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 30 12:52:22 node-2 puppet-user[9425]: Finished catalog run in 0.05 seconds
Jul 30 12:52:24 node-2 puppet-user[9898]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 30 12:52:24 node-2 puppet-user[9898]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Jul 30 12:52:24 node-2 puppet-user[9898]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 30 12:52:24 node-2 puppet-user[9898]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 30 12:52:24 node-2 puppet-user[9898]: Finished catalog run in 0.02 seconds
Jul 30 12:52:26 node-2 puppet-user[10365]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 30 12:52:26 node-2 puppet-user[10365]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Jul 30 12:52:26 node-2 puppet-user[10365]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 30 12:52:26 node-2 puppet-user[10365]: Finished catalog run in 0.03 seconds
Jul 30 12:52:27 node-2 puppet-user[10829]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 30 12:52:27 node-2 puppet-user[10829]: Compiled catalog for node-2.domain.tld in environment production in 0.20 seconds
Jul 30 12:52:28 node-2 puppet-user[10829]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 30 12:52:28 node-2 puppet-user[10829]: (/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 30 12:52:28 node-2 puppet-user[10829]: Finished catalog run in 0.42 seconds
Jul 30 12:52:29 node-2 puppet-user[11312]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 30 12:52:30 node-2 puppet-user[11312]: Compiled catalog for node-2.domain.tld in environment production in 0.26 seconds
Jul 30 12:52:30 node-2 puppet-user[11312]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 30 12:52:30 node-2 puppet-user[11312]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 30 12:52:30 node-2 puppet-user[11312]: (/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 30 12:52:30 node-2 puppet-user[11312]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 30 12:52:30 node-2 puppet-user[11312]: Finished catalog run in 0.29 seconds
Jul 30 12:52:32 node-2 puppet-user[11923]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 30 12:52:32 node-2 puppet-user[11923]: Compiled catalog for node-2.domain.tld in environment production in 0.15 seconds
Jul 30 12:52:32 node-2 puppet-user[11923]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 30 12:52:32 node-2 kernel: [   68.177008] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 30 12:52:32 node-2 kernel: [   68.177058] 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 30 12:52:32 node-2 puppet-user[11923]: (/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 30 12:52:32 node-2 puppet-user[11923]: Finished catalog run in 0.05 seconds
Jul 30 12:52:34 node-2 puppet-user[12383]: (Scope(Class[main])) MODULAR: sync_time
Jul 30 12:52:34 node-2 puppet-user[12383]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 30 12:52:34 node-2 ntpdate[12808]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 30 12:52:40 node-2 ntpdate[12808]: adjust time server 10.20.0.2 offset 0.457178 sec
Jul 30 12:52:40 node-2 puppet-user[12383]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 30 12:52:40 node-2 puppet-user[12383]: Finished catalog run in 6.16 seconds
Jul 30 12:52:45 node-2 puppet-user[13190]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 30 12:52:45 node-2 puppet-user[13190]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Jul 30 12:52:45 node-2 puppet-user[13190]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 30 12:52:45 node-2 puppet-user[13190]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Jul 30 12:52:45 node-2 puppet-user[13190]: Finished catalog run in 0.06 seconds
Jul 30 12:52:46 node-2 puppet-user[13647]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 30 12:52:48 node-2 puppet-user[13647]: Compiled catalog for node-2.domain.tld in environment production in 1.14 seconds
Jul 30 12:52:48 node-2 puppet-user[13647]: (/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 30 12:52:48 node-2 puppet-user[13647]: (/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 30 12:52:48 node-2 puppet-user[13647]: (/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 30 12:52:48 node-2 puppet-user[13647]: (/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 30 12:52:48 node-2 puppet-user[13647]: (/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 30 12:52:48 node-2 puppet-user[13647]: (/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 30 12:52:48 node-2 puppet-user[13647]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 30 12:52:48 node-2 puppet-user[13647]: (/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 30 12:52:48 node-2 puppet-user[13647]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 30 12:52:48 node-2 puppet-user[13647]: (/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 30 12:52:48 node-2 puppet-user[13647]: (/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 30 12:52:48 node-2 puppet-user[13647]: (/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 30 12:52:48 node-2 puppet-user[13647]: (/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 30 12:52:48 node-2 puppet-user[13647]: (/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 30 12:52:48 node-2 puppet-user[13647]: (/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 30 12:52:48 node-2 puppet-user[13647]: (/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 30 12:52:55 node-2 kernel: [   91.390465] init: plymouth-upstart-bridge main process ended, respawning
Jul 30 12:52:55 node-2 puppet-agent[8921]: Could not run: SIGTERM
Jul 30 12:52:55 node-2 kernel: [   91.669537] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 30 12:52:55 node-2 ec2: 
Jul 30 12:52:55 node-2 ec2: #############################################################
Jul 30 12:52:55 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 30 12:52:55 node-2 ec2: 1024 b5:d8:20:29:d5:83:21:bc:48:d1:3a:a8:7b:00:10:92  root@node-2.domain.tld (DSA)
Jul 30 12:52:55 node-2 ec2: 256 a0:5d:31:eb:ba:9e:f0:ef:f6:d4:fb:59:73:0b:7b:4c  root@node-2.domain.tld (ECDSA)
Jul 30 12:52:55 node-2 ec2: 256 f3:57:2a:7d:98:1d:96:b7:6a:b7:99:89:cb:0a:93:df  root@node-2.domain.tld (ED25519)
Jul 30 12:52:55 node-2 ec2: 2048 8a:fe:fd:50:f7:bb:9c:3c:9b:3a:b0:01:95:76:d4:04  root@node-2.domain.tld (RSA)
Jul 30 12:52:55 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 30 12:52:55 node-2 ec2: #############################################################
Jul 30 12:53:01 node-2 CRON[14737]: (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 30 12:53:05 node-2 puppet-user[13647]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 30 12:53:05 node-2 puppet-user[13647]: Finished catalog run in 17.21 seconds
Jul 30 12:53:07 node-2 puppet-user[14876]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 30 12:53:07 node-2 puppet-user[14876]: Compiled catalog for node-2.domain.tld in environment production in 0.16 seconds
Jul 30 12:53:10 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 30 12:53:10 node-2 nailgun-agent: I, [2016-07-30T12:53:10.680888 #14740]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 30 12:53:12 node-2 puppet-user[14876]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 30 12:53:23 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 30 12:53:23 node-2 nailgun-agent: I, [2016-07-30T12:53:23.965833 #14740]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 30 12:53:44 node-2 puppet-user[14876]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 30 12:53:44 node-2 puppet-user[14876]: Finished catalog run in 36.68 seconds
Jul 30 12:53:46 node-2 puppet-user[17656]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 30 12:53:47 node-2 puppet-user[17656]: Compiled catalog for node-2.domain.tld in environment production in 0.55 seconds
Jul 30 12:53:47 node-2 puppet-user[17656]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 30 12:53:47 node-2 puppet-user[17656]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 30 12:53:47 node-2 puppet-user[17656]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 30 12:53:47 node-2 puppet-user[17656]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 30 12:53:47 node-2 puppet-user[17656]: Finished catalog run in 0.14 seconds
Jul 30 12:53:49 node-2 puppet-user[18119]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 30 12:53:50 node-2 puppet-user[18119]: Compiled catalog for node-2.domain.tld in environment production in 0.84 seconds
Jul 30 12:53:50 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 30 12:53:50 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 30 12:53:50 node-2 crontab[18566]: (root) LIST (root)
Jul 30 12:53:50 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 30 12:53:50 node-2 crontab[18569]: (root) REPLACE (root)
Jul 30 12:53:52 node-2 puppet-user[18119]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/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 30 12:53:54 node-2 puppet-user[18119]: (/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 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/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 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/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 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/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 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/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 30 12:53:54 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 30 12:53:54 node-2 puppet-user[18119]: (/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 30 12:53:55 node-2 puppet-user[18119]: (/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 30 12:53:55 node-2 puppet-user[18119]: (/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 30 12:53:55 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 30 12:53:55 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 30 12:53:55 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 30 12:53:55 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 30 12:53:55 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 30 12:53:55 node-2 puppet-user[18119]: (/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 30 12:53:55 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 30 12:53:55 node-2 puppet-user[18119]: (/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 30 12:53:55 node-2 puppet-user[18119]: (/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 30 12:53:55 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 30 12:53:55 node-2 puppet-user[18119]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 30 12:53:55 node-2 puppet-user[18119]: (/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 30 12:53:55 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8370" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 12:53:55 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 30 12:53:57 node-2 multipathd: uevent trigger error
<27>Jul 30 12:53:57 node-2 multipathd: uevent trigger error
<27>Jul 30 12:53:57 node-2 multipathd: uevent trigger error
<27>Jul 30 12:53:57 node-2 multipathd: uevent trigger error
<27>Jul 30 12:53:57 node-2 multipathd: uevent trigger error
<27>Jul 30 12:53:57 node-2 multipathd: uevent trigger error
<27>Jul 30 12:54:15 node-2 multipathd: uevent trigger error
<27>Jul 30 12:54:15 node-2 multipathd: uevent trigger error
<27>Jul 30 12:54:15 node-2 multipathd: uevent trigger error
<27>Jul 30 12:54:15 node-2 multipathd: uevent trigger error
<27>Jul 30 12:54:15 node-2 multipathd: uevent trigger error
<27>Jul 30 12:54:19 node-2 multipathd: uevent trigger error
<27>Jul 30 12:54:19 node-2 multipathd: uevent trigger error
<27>Jul 30 12:54:19 node-2 multipathd: uevent trigger error
<27>Jul 30 12:54:19 node-2 multipathd: uevent trigger error
<27>Jul 30 12:54:19 node-2 multipathd: uevent trigger error
<27>Jul 30 12:54:21 node-2 multipathd: uevent trigger error
<27>Jul 30 12:54:21 node-2 multipathd: uevent trigger error
<27>Jul 30 12:54:21 node-2 multipathd: uevent trigger error
<27>Jul 30 12:54:21 node-2 multipathd: uevent trigger error
<27>Jul 30 12:54:21 node-2 multipathd: uevent trigger error
<27>Jul 30 12:55:21 node-2 ntpdate[29784]: no servers can be used, exiting
<27>Jul 30 12:55:21 node-2 ntpdate[30045]: no servers can be used, exiting
<27>Jul 30 12:55:53 node-2 multipathd: uevent trigger error
<27>Jul 30 12:55:53 node-2 multipathd: uevent trigger error
<27>Jul 30 12:55:53 node-2 multipathd: uevent trigger error
<27>Jul 30 12:55:53 node-2 multipathd: uevent trigger error
<27>Jul 30 12:55:53 node-2 multipathd: uevent trigger error
<27>Jul 30 12:55:53 node-2 multipathd: uevent trigger error
<27>Jul 30 12:55:56 node-2 multipathd: uevent trigger error
<27>Jul 30 12:55:56 node-2 multipathd: uevent trigger error
<27>Jul 30 12:55:56 node-2 multipathd: uevent trigger error
<27>Jul 30 12:55:56 node-2 multipathd: uevent trigger error
<27>Jul 30 12:55:56 node-2 multipathd: uevent trigger error
<27>Jul 30 12:55:56 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:08 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:08 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:08 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:08 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:08 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:11 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:11 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:11 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:11 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:11 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:11 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:17 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:17 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:17 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:17 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:17 node-2 multipathd: uevent trigger error
<43>Jul 30 12:56:35 node-2 apache2_error [Sat Jul 30 12:56:30.594718 2016] [mpm_event:notice] [pid 7278:tid 139813760214912] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 30 12:56:35 node-2 apache2_error [Sat Jul 30 12:56:30.594808 2016] [core:notice] [pid 7278:tid 139813760214912] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 30 12:56:35 node-2 apache2_error [Sat Jul 30 12:56:33.703147 2016] [mpm_event:notice] [pid 7278:tid 139813760214912] AH00491: caught SIGTERM, shutting down
<43>Jul 30 12:56:35 node-2 apache2_error [Sat Jul 30 12:56:34.806796 2016] [mpm_worker:notice] [pid 7633:tid 139679348922240] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 30 12:56:35 node-2 apache2_error [Sat Jul 30 12:56:34.806854 2016] [core:notice] [pid 7633:tid 139679348922240] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 12:56:37 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:37 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:37 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:37 node-2 multipathd: uevent trigger error
<27>Jul 30 12:56:37 node-2 multipathd: uevent trigger error
<27>Jul 30 12:57:14 node-2 multipathd: uevent trigger error
<27>Jul 30 12:57:14 node-2 multipathd: uevent trigger error
<27>Jul 30 12:57:14 node-2 multipathd: uevent trigger error
<27>Jul 30 12:57:14 node-2 multipathd: uevent trigger error
<27>Jul 30 12:57:14 node-2 multipathd: uevent trigger error
<43>Jul 30 12:57:15 node-2 apache2_error [Sat Jul 30 12:57:11.315250 2016] [mpm_worker:notice] [pid 7633:tid 139679348922240] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 12:57:15 node-2 apache2_error [Sat Jul 30 12:57:11.321962 2016] [mpm_worker:warn] [pid 7633:tid 139679348922240] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 12:57:15 node-2 apache2_error [Sat Jul 30 12:57:11.322413 2016] [mpm_worker:notice] [pid 7633:tid 139679348922240] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 30 12:57:15 node-2 apache2_error [Sat Jul 30 12:57:11.322422 2016] [core:notice] [pid 7633:tid 139679348922240] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 12:57:32 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:08 node-2 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 30 12:58:13 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:13 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:13 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:13 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:13 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:13 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:13 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:17 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:17 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:17 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:17 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:17 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:17 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:17 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:23 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:23 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:23 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:23 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:23 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:23 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:30 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:30 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:30 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:30 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:30 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:30 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:36 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:36 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:36 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:36 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:36 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:36 node-2 multipathd: uevent trigger error
<129>Jul 30 12:58:36 node-2 haproxy[25168]: Server odl-jetty/node-5 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 30 12:58:36 node-2 haproxy[25168]: proxy odl-jetty has no server available!
<129>Jul 30 12:58:38 node-2 haproxy[25168]: Server odl-neutron-endpoint/node-5 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 30 12:58:38 node-2 haproxy[25168]: proxy odl-neutron-endpoint has no server available!
<129>Jul 30 12:58:38 node-2 haproxy[26517]: 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 30 12:58:41 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:41 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:41 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:41 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:41 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:41 node-2 multipathd: uevent trigger error
<129>Jul 30 12:58:42 node-2 haproxy[26526]: Server odl-jetty/node-5 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 30 12:58:42 node-2 haproxy[26526]: proxy odl-jetty has no server available!
<27>Jul 30 12:58:44 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:44 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:44 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:44 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:44 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:44 node-2 multipathd: uevent trigger error
<129>Jul 30 12:58:46 node-2 haproxy[26526]: Server odl-neutron-endpoint/node-5 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 30 12:58:46 node-2 haproxy[26526]: proxy odl-neutron-endpoint has no server available!
<129>Jul 30 12:58:47 node-2 haproxy[28790]: 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 30 12:58:48 node-2 haproxy[28799]: 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 30 12:58:50 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:50 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:50 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:50 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:50 node-2 multipathd: uevent trigger error
<129>Jul 30 12:58:51 node-2 haproxy[28799]: Server odl-jetty/node-5 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 30 12:58:51 node-2 haproxy[28799]: proxy odl-jetty has no server available!
<129>Jul 30 12:58:52 node-2 haproxy[30006]: 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 30 12:58:53 node-2 haproxy[30017]: 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 30 12:58:53 node-2 haproxy[30017]: 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 30 12:58:55 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:55 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:55 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:55 node-2 multipathd: uevent trigger error
<27>Jul 30 12:58:55 node-2 multipathd: uevent trigger error
<129>Jul 30 12:58:56 node-2 haproxy[30017]: Server odl-jetty/node-5 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 30 12:58:56 node-2 haproxy[30017]: proxy odl-jetty has no server available!
<129>Jul 30 12:58:58 node-2 haproxy[31239]: 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 30 12:58:58 node-2 haproxy[31239]: 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 30 12:58:58 node-2 haproxy[31239]: 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 30 12:58:59 node-2 haproxy[31239]: 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 30 12:58:59 node-2 haproxy[31239]: 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 30 12:59:01 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:01 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:01 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:01 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:01 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:01 node-2 multipathd: uevent trigger error
<129>Jul 30 12:59:01 node-2 haproxy[31239]: Server odl-jetty/node-5 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 30 12:59:01 node-2 haproxy[31239]: proxy odl-jetty has no server available!
<129>Jul 30 12:59:03 node-2 haproxy[32445]: 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 30 12:59:03 node-2 haproxy[32445]: 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 30 12:59:04 node-2 haproxy[32454]: 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 30 12:59:04 node-2 haproxy[32454]: 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 30 12:59:04 node-2 haproxy[32454]: 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 30 12:59:04 node-2 haproxy[32454]: 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 30 12:59:06 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:06 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:06 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:06 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:06 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:06 node-2 multipathd: uevent trigger error
<129>Jul 30 12:59:06 node-2 haproxy[32454]: 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 30 12:59:07 node-2 haproxy[32454]: Server aodh/node-5 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 30 12:59:07 node-2 haproxy[32454]: proxy aodh has no server available!
<129>Jul 30 12:59:07 node-2 haproxy[32454]: Server odl-jetty/node-5 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 30 12:59:07 node-2 haproxy[32454]: proxy odl-jetty has no server available!
<129>Jul 30 12:59:08 node-2 haproxy[1211]: 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 30 12:59:09 node-2 haproxy[1220]: 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 30 12:59:09 node-2 haproxy[1220]: 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 30 12:59:09 node-2 haproxy[1220]: 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 30 12:59:09 node-2 haproxy[1220]: 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 30 12:59:10 node-2 haproxy[1220]: 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 30 12:59:10 node-2 haproxy[1220]: 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 30 12:59:11 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:11 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:11 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:11 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:11 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:11 node-2 multipathd: uevent trigger error
<129>Jul 30 12:59:12 node-2 haproxy[1220]: 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 30 12:59:12 node-2 haproxy[1220]: Server aodh/node-5 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 30 12:59:12 node-2 haproxy[1220]: proxy aodh has no server available!
<129>Jul 30 12:59:12 node-2 haproxy[1220]: 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 30 12:59:12 node-2 haproxy[1220]: Server ceilometer/node-5 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 30 12:59:12 node-2 haproxy[1220]: proxy ceilometer has no server available!
<129>Jul 30 12:59:12 node-2 haproxy[1220]: Server odl-jetty/node-5 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 30 12:59:12 node-2 haproxy[1220]: proxy odl-jetty has no server available!
<129>Jul 30 12:59:14 node-2 haproxy[2546]: 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 30 12:59:14 node-2 haproxy[2546]: 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 30 12:59:14 node-2 haproxy[2546]: 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 30 12:59:14 node-2 haproxy[2546]: 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 30 12:59:15 node-2 haproxy[2546]: 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 30 12:59:15 node-2 haproxy[2546]: 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 30 12:59:15 node-2 haproxy[2546]: 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 30 12:59:16 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:16 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:16 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:16 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:16 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:16 node-2 multipathd: uevent trigger error
<129>Jul 30 12:59:17 node-2 haproxy[2546]: 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 30 12:59:17 node-2 haproxy[2546]: Server aodh/node-5 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 30 12:59:17 node-2 haproxy[2546]: proxy aodh has no server available!
<129>Jul 30 12:59:17 node-2 haproxy[2546]: 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 30 12:59:17 node-2 haproxy[2546]: Server ceilometer/node-5 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 30 12:59:17 node-2 haproxy[2546]: proxy ceilometer has no server available!
<129>Jul 30 12:59:17 node-2 haproxy[2546]: Server odl-jetty/node-5 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 30 12:59:17 node-2 haproxy[2546]: proxy odl-jetty has no server available!
<129>Jul 30 12:59:19 node-2 haproxy[3753]: 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 30 12:59:19 node-2 haproxy[3753]: 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 30 12:59:19 node-2 haproxy[3753]: 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 30 12:59:19 node-2 haproxy[3753]: 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 30 12:59:20 node-2 haproxy[3753]: 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 30 12:59:20 node-2 haproxy[3753]: 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 30 12:59:20 node-2 haproxy[3753]: 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 30 12:59:20 node-2 haproxy[3753]: 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 30 12:59:21 node-2 haproxy[3753]: Server horizon/node-5 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 30 12:59:21 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:21 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:21 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:21 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:21 node-2 multipathd: uevent trigger error
<129>Jul 30 12:59:22 node-2 haproxy[3753]: Server aodh/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 30 12:59:22 node-2 haproxy[3753]: Server aodh/node-5 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 30 12:59:22 node-2 haproxy[3753]: proxy aodh has no server available!
<129>Jul 30 12:59:22 node-2 haproxy[3753]: 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 30 12:59:22 node-2 haproxy[3753]: Server ceilometer/node-5 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 30 12:59:22 node-2 haproxy[3753]: proxy ceilometer has no server available!
<129>Jul 30 12:59:22 node-2 haproxy[3753]: Server odl-jetty/node-5 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 30 12:59:22 node-2 haproxy[3753]: proxy odl-jetty has no server available!
<129>Jul 30 12:59:24 node-2 haproxy[5191]: 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 30 12:59:25 node-2 haproxy[5200]: 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 30 12:59:25 node-2 haproxy[5200]: 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 30 12:59:25 node-2 haproxy[5200]: 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 30 12:59:25 node-2 haproxy[5200]: 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 30 12:59:25 node-2 haproxy[5200]: 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 30 12:59:25 node-2 haproxy[5200]: 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 30 12:59:26 node-2 haproxy[5200]: 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 30 12:59:26 node-2 haproxy[5200]: 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 30 12:59:26 node-2 haproxy[5200]: 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 30 12:59:26 node-2 haproxy[5200]: 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 30 12:59:26 node-2 haproxy[5200]: Server horizon/node-5 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 30 12:59:27 node-2 haproxy[5200]: 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 30 12:59:27 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:27 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:27 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:27 node-2 multipathd: uevent trigger error
<129>Jul 30 12:59:27 node-2 haproxy[5200]: Server glance-registry/node-5 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 30 12:59:27 node-2 haproxy[5200]: proxy glance-registry has no server available!
<27>Jul 30 12:59:27 node-2 multipathd: uevent trigger error
<129>Jul 30 12:59:28 node-2 haproxy[5200]: Server aodh/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 30 12:59:28 node-2 haproxy[5200]: Server aodh/node-5 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 30 12:59:28 node-2 haproxy[5200]: proxy aodh has no server available!
<129>Jul 30 12:59:28 node-2 haproxy[5200]: 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 30 12:59:28 node-2 haproxy[5200]: Server ceilometer/node-5 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 30 12:59:28 node-2 haproxy[5200]: proxy ceilometer has no server available!
<129>Jul 30 12:59:28 node-2 haproxy[5200]: Server odl-jetty/node-5 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 30 12:59:28 node-2 haproxy[5200]: proxy odl-jetty has no server available!
<129>Jul 30 12:59:30 node-2 haproxy[6464]: 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 30 12:59:31 node-2 haproxy[6473]: 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 30 12:59:31 node-2 haproxy[6473]: 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 30 12:59:31 node-2 haproxy[6473]: 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 30 12:59:31 node-2 haproxy[6473]: 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 30 12:59:31 node-2 haproxy[6473]: 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 30 12:59:31 node-2 haproxy[6473]: 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 30 12:59:31 node-2 haproxy[6473]: 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 30 12:59:31 node-2 haproxy[6473]: 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 30 12:59:32 node-2 haproxy[6473]: 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 30 12:59:32 node-2 haproxy[6473]: 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 30 12:59:32 node-2 haproxy[6473]: 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 30 12:59:32 node-2 haproxy[6473]: 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 30 12:59:32 node-2 haproxy[6473]: 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 30 12:59:32 node-2 haproxy[6473]: Server horizon/node-5 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 30 12:59:33 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:33 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:33 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:33 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:33 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:33 node-2 multipathd: uevent trigger error
<129>Jul 30 12:59:33 node-2 haproxy[6473]: 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 30 12:59:33 node-2 haproxy[6473]: Server glance-registry/node-5 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 30 12:59:33 node-2 haproxy[6473]: proxy glance-registry has no server available!
<129>Jul 30 12:59:34 node-2 haproxy[6473]: Server aodh/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 30 12:59:34 node-2 haproxy[6473]: Server aodh/node-5 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 30 12:59:34 node-2 haproxy[6473]: proxy aodh has no server available!
<129>Jul 30 12:59:34 node-2 haproxy[6473]: 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 30 12:59:34 node-2 haproxy[6473]: Server ceilometer/node-5 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 30 12:59:34 node-2 haproxy[6473]: proxy ceilometer has no server available!
<129>Jul 30 12:59:34 node-2 haproxy[6473]: 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 30 12:59:34 node-2 haproxy[6473]: Server nova-novncproxy/node-5 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 30 12:59:34 node-2 haproxy[6473]: proxy nova-novncproxy has no server available!
<129>Jul 30 12:59:34 node-2 haproxy[6473]: Server odl-jetty/node-5 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 30 12:59:34 node-2 haproxy[6473]: proxy odl-jetty has no server available!
<27>Jul 30 12:59:34 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Jul 30 12:59:36 node-2 haproxy[7683]: 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 30 12:59:36 node-2 haproxy[7683]: 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 30 12:59:36 node-2 haproxy[7683]: 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 30 12:59:36 node-2 haproxy[7683]: 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 30 12:59:36 node-2 haproxy[7683]: 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 30 12:59:36 node-2 haproxy[7683]: 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 30 12:59:36 node-2 haproxy[7683]: 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 30 12:59:37 node-2 haproxy[7695]: 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 30 12:59:37 node-2 haproxy[7695]: 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 30 12:59:37 node-2 haproxy[7695]: 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 30 12:59:37 node-2 haproxy[7695]: 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 30 12:59:37 node-2 haproxy[7695]: 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 30 12:59:37 node-2 haproxy[7695]: 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 30 12:59:37 node-2 haproxy[7695]: 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 30 12:59:38 node-2 haproxy[7695]: 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 30 12:59:38 node-2 haproxy[7695]: Server horizon/node-5 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 30 12:59:39 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:39 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:39 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:39 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:39 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:39 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:39 node-2 multipathd: uevent trigger error
<129>Jul 30 12:59:39 node-2 haproxy[7695]: 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 30 12:59:39 node-2 haproxy[7695]: Server glance-registry/node-5 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 30 12:59:39 node-2 haproxy[7695]: proxy glance-registry has no server available!
<129>Jul 30 12:59:39 node-2 haproxy[7695]: 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 30 12:59:39 node-2 haproxy[7695]: Server aodh/node-5 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 30 12:59:39 node-2 haproxy[7695]: proxy aodh has no server available!
<129>Jul 30 12:59:39 node-2 haproxy[7695]: 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 30 12:59:39 node-2 haproxy[7695]: Server ceilometer/node-5 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 30 12:59:39 node-2 haproxy[7695]: proxy ceilometer has no server available!
<129>Jul 30 12:59:39 node-2 haproxy[7695]: 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 30 12:59:39 node-2 haproxy[7695]: Server nova-novncproxy/node-5 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 30 12:59:39 node-2 haproxy[7695]: proxy nova-novncproxy has no server available!
<129>Jul 30 12:59:39 node-2 haproxy[7695]: Server odl-jetty/node-5 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 30 12:59:39 node-2 haproxy[7695]: proxy odl-jetty has no server available!
<129>Jul 30 12:59:42 node-2 haproxy[8982]: 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 30 12:59:42 node-2 haproxy[8982]: 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 30 12:59:42 node-2 haproxy[8982]: 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 30 12:59:42 node-2 haproxy[8982]: 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 30 12:59:42 node-2 haproxy[8982]: 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 30 12:59:42 node-2 haproxy[8982]: 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 30 12:59:42 node-2 haproxy[8982]: 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 30 12:59:42 node-2 haproxy[8982]: 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 30 12:59:42 node-2 haproxy[8982]: 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 30 12:59:43 node-2 haproxy[8982]: 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 30 12:59:43 node-2 haproxy[8982]: 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 30 12:59:43 node-2 haproxy[8982]: 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 30 12:59:43 node-2 haproxy[8982]: 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 30 12:59:43 node-2 haproxy[8982]: 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 30 12:59:43 node-2 haproxy[8982]: 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 30 12:59:43 node-2 haproxy[8982]: 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 30 12:59:43 node-2 haproxy[8982]: 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 30 12:59:43 node-2 haproxy[8982]: 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 30 12:59:43 node-2 haproxy[8982]: Server horizon/node-5 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 30 12:59:44 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:44 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:44 node-2 multipathd: uevent trigger error
<129>Jul 30 12:59:44 node-2 haproxy[8982]: 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 30 12:59:44 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:44 node-2 multipathd: uevent trigger error
<129>Jul 30 12:59:44 node-2 haproxy[8982]: Server glance-registry/node-5 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 30 12:59:44 node-2 haproxy[8982]: proxy glance-registry has no server available!
<129>Jul 30 12:59:45 node-2 haproxy[8982]: 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 30 12:59:45 node-2 haproxy[8982]: Server aodh/node-5 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 30 12:59:45 node-2 haproxy[8982]: proxy aodh has no server available!
<129>Jul 30 12:59:45 node-2 haproxy[8982]: 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 30 12:59:45 node-2 haproxy[8982]: Server ceilometer/node-5 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 30 12:59:45 node-2 haproxy[8982]: proxy ceilometer has no server available!
<129>Jul 30 12:59:45 node-2 haproxy[8982]: 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 30 12:59:45 node-2 haproxy[8982]: Server nova-novncproxy/node-5 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 30 12:59:45 node-2 haproxy[8982]: proxy nova-novncproxy has no server available!
<129>Jul 30 12:59:45 node-2 haproxy[8982]: Server odl-jetty/node-5 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 30 12:59:45 node-2 haproxy[8982]: proxy odl-jetty has no server available!
<27>Jul 30 12:59:48 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:48 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:48 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:48 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:48 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:48 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:51 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:51 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:51 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:51 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:51 node-2 multipathd: uevent trigger error
<129>Jul 30 12:59:51 node-2 haproxy[8982]: Server odl-neutron-endpoint/node-5 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 30 12:59:51 node-2 haproxy[8982]: proxy odl-neutron-endpoint has no server available!
<129>Jul 30 12:59:52 node-2 haproxy[8982]: Server keystone-1/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 30 12:59:52 node-2 haproxy[8982]: Server keystone-1/node-5 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 30 12:59:52 node-2 haproxy[8982]: proxy keystone-1 has no server available!
<129>Jul 30 12:59:52 node-2 haproxy[8982]: 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 30 12:59:52 node-2 haproxy[8982]: Server keystone-2/node-5 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 30 12:59:52 node-2 haproxy[8982]: proxy keystone-2 has no server available!
<129>Jul 30 12:59:52 node-2 haproxy[8982]: Server nova-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 30 12:59:52 node-2 haproxy[8982]: Server nova-api/node-5 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 30 12:59:52 node-2 haproxy[8982]: proxy nova-api has no server available!
<129>Jul 30 12:59:52 node-2 haproxy[8982]: Server nova-metadata-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 30 12:59:52 node-2 haproxy[8982]: Server nova-metadata-api/node-5 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 30 12:59:52 node-2 haproxy[8982]: proxy nova-metadata-api has no server available!
<129>Jul 30 12:59:52 node-2 haproxy[8982]: 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 30 12:59:52 node-2 haproxy[8982]: Backup Server cinder-api/node-5 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 30 12:59:52 node-2 haproxy[8982]: proxy cinder-api has no server available!
<129>Jul 30 12:59:52 node-2 haproxy[8982]: Server glance-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 30 12:59:52 node-2 haproxy[8982]: Server glance-api/node-5 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 30 12:59:52 node-2 haproxy[8982]: proxy glance-api has no server available!
<129>Jul 30 12:59:52 node-2 haproxy[8982]: Server glance-glare/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 30 12:59:52 node-2 haproxy[8982]: Server glance-glare/node-5 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 30 12:59:52 node-2 haproxy[8982]: proxy glance-glare has no server available!
<129>Jul 30 12:59:52 node-2 haproxy[8982]: Server neutron/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 30 12:59:52 node-2 haproxy[8982]: Server neutron/node-5 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 30 12:59:52 node-2 haproxy[8982]: proxy neutron has no server available!
<129>Jul 30 12:59:52 node-2 haproxy[8982]: 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 30 12:59:53 node-2 haproxy[8982]: Backup Server mysqld/node-5 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 30 12:59:53 node-2 haproxy[8982]: proxy mysqld has no server available!
<129>Jul 30 12:59:53 node-2 haproxy[8982]: Server object-storage/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 30 12:59:53 node-2 haproxy[8982]: Server object-storage/node-5 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 30 12:59:53 node-2 haproxy[8982]: proxy object-storage has no server available!
<129>Jul 30 12:59:53 node-2 haproxy[8982]: 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 30 12:59:53 node-2 haproxy[8982]: Server heat-api/node-5 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 30 12:59:53 node-2 haproxy[8982]: proxy heat-api has no server available!
<129>Jul 30 12:59:53 node-2 haproxy[8982]: 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 30 12:59:53 node-2 haproxy[8982]: Server heat-api-cfn/node-5 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 30 12:59:53 node-2 haproxy[8982]: proxy heat-api-cfn has no server available!
<129>Jul 30 12:59:53 node-2 haproxy[8982]: Server heat-api-cloudwatch/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 30 12:59:53 node-2 haproxy[8982]: Server heat-api-cloudwatch/node-5 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 30 12:59:53 node-2 haproxy[8982]: proxy heat-api-cloudwatch has no server available!
<27>Jul 30 12:59:55 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:55 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:55 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:55 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:55 node-2 multipathd: uevent trigger error
<27>Jul 30 12:59:55 node-2 multipathd: uevent trigger error
<27>Jul 30 13:00:26 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 30 13:00:26 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 30 13:00:30 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 30 13:00:30 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 30 13:00:30 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 30 13:00:54 node-2 multipathd: uevent trigger error
<27>Jul 30 13:00:54 node-2 multipathd: uevent trigger error
<27>Jul 30 13:00:54 node-2 multipathd: uevent trigger error
<27>Jul 30 13:00:54 node-2 multipathd: uevent trigger error
<27>Jul 30 13:00:54 node-2 multipathd: uevent trigger error
<27>Jul 30 13:00:54 node-2 multipathd: uevent trigger error
<27>Jul 30 13:01:35 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 30 13:01:37 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 30 13:03:16 node-2 multipathd: uevent trigger error
<27>Jul 30 13:03:16 node-2 multipathd: uevent trigger error
<27>Jul 30 13:03:16 node-2 multipathd: uevent trigger error
<27>Jul 30 13:03:16 node-2 multipathd: uevent trigger error
<27>Jul 30 13:03:16 node-2 multipathd: uevent trigger error
<11>Jul 30 13:04:12 node-2 epmd: epmd: node name already occupied rabbitmq-cli-58
<11>Jul 30 13:04:44 node-2 epmd: epmd: node name already occupied rabbitmq-cli-58
<11>Jul 30 13:05:22 node-2 epmd: epmd: node name already occupied rabbitmq-cli-58
<27>Jul 30 13:06:36 node-2 multipathd: uevent trigger error
<27>Jul 30 13:06:36 node-2 multipathd: uevent trigger error
<27>Jul 30 13:06:36 node-2 multipathd: uevent trigger error
<27>Jul 30 13:06:36 node-2 multipathd: uevent trigger error
<27>Jul 30 13:06:36 node-2 multipathd: uevent trigger error
<43>Jul 30 13:07:46 node-2 apache2_error [Sat Jul 30 13:07:45.595423 2016] [mpm_worker:notice] [pid 7633:tid 139679348922240] AH00295: caught SIGTERM, shutting down
<43>Jul 30 13:07:46 node-2 apache2_error [Sat Jul 30 13:07:46.357709 2016] [mpm_worker:notice] [pid 10991:tid 140101758556032] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 13:07:46 node-2 apache2_error [Sat Jul 30 13:07:46.357748 2016] [core:notice] [pid 10991:tid 140101758556032] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 13:08:24 node-2 multipathd: uevent trigger error
<27>Jul 30 13:08:24 node-2 multipathd: uevent trigger error
<27>Jul 30 13:08:24 node-2 multipathd: uevent trigger error
<27>Jul 30 13:08:24 node-2 multipathd: uevent trigger error
<27>Jul 30 13:08:24 node-2 multipathd: uevent trigger error
<27>Jul 30 13:08:24 node-2 multipathd: uevent trigger error
<27>Jul 30 13:08:24 node-2 multipathd: uevent trigger error
<27>Jul 30 13:08:24 node-2 multipathd: uevent trigger error
<43>Jul 30 13:08:26 node-2 apache2_error [Sat Jul 30 13:08:18.356668 2016] [mpm_worker:notice] [pid 10991:tid 140101758556032] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 13:08:26 node-2 apache2_error [Sat Jul 30 13:08:18.366715 2016] [mpm_worker:warn] [pid 10991:tid 140101758556032] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 13:08:26 node-2 apache2_error [Sat Jul 30 13:08:18.373748 2016] [mpm_worker:notice] [pid 10991:tid 140101758556032] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 13:08:26 node-2 apache2_error [Sat Jul 30 13:08:18.373775 2016] [core:notice] [pid 10991:tid 140101758556032] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 13:09:21 node-2 multipathd: uevent trigger error
<27>Jul 30 13:09:21 node-2 multipathd: uevent trigger error
<27>Jul 30 13:09:21 node-2 multipathd: uevent trigger error
<27>Jul 30 13:09:21 node-2 multipathd: uevent trigger error
<27>Jul 30 13:09:21 node-2 multipathd: uevent trigger error
<27>Jul 30 13:09:21 node-2 multipathd: uevent trigger error
<27>Jul 30 13:10:33 node-2 multipathd: uevent trigger error
<27>Jul 30 13:10:33 node-2 multipathd: uevent trigger error
<27>Jul 30 13:10:33 node-2 multipathd: uevent trigger error
<27>Jul 30 13:10:33 node-2 multipathd: uevent trigger error
<27>Jul 30 13:10:33 node-2 multipathd: uevent trigger error
<27>Jul 30 13:10:33 node-2 multipathd: uevent trigger error
<27>Jul 30 13:10:33 node-2 multipathd: uevent trigger error
<11>Jul 30 13:13:23 node-2 epmd: epmd: node name already occupied rabbitmq-cli-58
<27>Jul 30 13:15:28 node-2 multipathd: uevent trigger error
<27>Jul 30 13:15:28 node-2 multipathd: uevent trigger error
<27>Jul 30 13:15:28 node-2 multipathd: uevent trigger error
<27>Jul 30 13:15:28 node-2 multipathd: uevent trigger error
<27>Jul 30 13:15:28 node-2 multipathd: uevent trigger error
<27>Jul 30 13:15:28 node-2 multipathd: uevent trigger error
<11>Jul 30 13:16:31 node-2 epmd: epmd: node name already occupied rabbitmq-cli-58
<27>Jul 30 13:17:34 node-2 multipathd: uevent trigger error
<27>Jul 30 13:17:34 node-2 multipathd: uevent trigger error
<27>Jul 30 13:17:34 node-2 multipathd: uevent trigger error
<27>Jul 30 13:17:34 node-2 multipathd: uevent trigger error
<27>Jul 30 13:17:34 node-2 multipathd: uevent trigger error
<27>Jul 30 13:17:34 node-2 multipathd: uevent trigger error
<27>Jul 30 13:18:39 node-2 multipathd: uevent trigger error
<27>Jul 30 13:18:40 node-2 multipathd: uevent trigger error
<27>Jul 30 13:18:40 node-2 multipathd: uevent trigger error
<27>Jul 30 13:18:40 node-2 multipathd: uevent trigger error
<27>Jul 30 13:18:40 node-2 multipathd: uevent trigger error
<27>Jul 30 13:18:40 node-2 multipathd: uevent trigger error
<27>Jul 30 13:18:40 node-2 multipathd: uevent trigger error
<11>Jul 30 13:19:12 node-2 epmd: epmd: node name already occupied rabbitmq-cli-58
<27>Jul 30 13:19:17 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:17 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:17 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:17 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:17 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:17 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:25 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:25 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:25 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:25 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:25 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:25 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:25 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:31 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:31 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:31 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:31 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:31 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:31 node-2 multipathd: uevent trigger error
<27>Jul 30 13:19:31 node-2 multipathd: uevent trigger error
<43>Jul 30 13:20:17 node-2 apache2_error [Sat Jul 30 13:20:17.459344 2016] [mpm_worker:notice] [pid 10991:tid 140101758556032] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 13:20:27 node-2 apache2_error [Sat Jul 30 13:20:17.840843 2016] [mpm_worker:warn] [pid 10991:tid 140101758556032] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 13:20:27 node-2 apache2_error [Sat Jul 30 13:20:17.844321 2016] [mpm_worker:notice] [pid 10991:tid 140101758556032] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 13:20:27 node-2 apache2_error [Sat Jul 30 13:20:17.844334 2016] [core:notice] [pid 10991:tid 140101758556032] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 30 13:20:57 node-2 apache2_error [Sat Jul 30 13:20:54.917386 2016] [mpm_worker:notice] [pid 10991:tid 140101758556032] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 13:20:57 node-2 apache2_error [Sat Jul 30 13:20:55.306242 2016] [mpm_worker:warn] [pid 10991:tid 140101758556032] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 13:20:57 node-2 apache2_error [Sat Jul 30 13:20:55.318195 2016] [mpm_worker:notice] [pid 10991:tid 140101758556032] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 13:20:57 node-2 apache2_error [Sat Jul 30 13:20:55.318219 2016] [core:notice] [pid 10991:tid 140101758556032] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 13:20:59 node-2 multipathd: uevent trigger error
<27>Jul 30 13:20:59 node-2 multipathd: uevent trigger error
<27>Jul 30 13:20:59 node-2 multipathd: uevent trigger error
<27>Jul 30 13:20:59 node-2 multipathd: uevent trigger error
<27>Jul 30 13:20:59 node-2 multipathd: uevent trigger error
<11>Jul 30 13:21:08 node-2 epmd: epmd: node name already occupied rabbitmq-cli-58
<27>Jul 30 13:21:15 node-2 multipathd: uevent trigger error
<27>Jul 30 13:21:16 node-2 multipathd: uevent trigger error
<27>Jul 30 13:21:16 node-2 multipathd: uevent trigger error
<27>Jul 30 13:21:38 node-2 multipathd: uevent trigger error
<27>Jul 30 13:21:38 node-2 multipathd: uevent trigger error
<27>Jul 30 13:21:38 node-2 multipathd: uevent trigger error
<27>Jul 30 13:21:38 node-2 multipathd: uevent trigger error
<27>Jul 30 13:21:38 node-2 multipathd: uevent trigger error
<27>Jul 30 13:21:38 node-2 multipathd: uevent trigger error
<27>Jul 30 13:21:38 node-2 multipathd: sda: spurious uevent, path already in pathvec
<27>Jul 30 13:22:37 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:37 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:37 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:37 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:37 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:43 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:43 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:43 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:43 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:43 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:47 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:47 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:47 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:47 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:47 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:59 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:59 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:59 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:59 node-2 multipathd: uevent trigger error
<27>Jul 30 13:22:59 node-2 multipathd: uevent trigger error
<27>Jul 30 13:23:27 node-2 multipathd: uevent trigger error
<27>Jul 30 13:23:27 node-2 multipathd: uevent trigger error
<27>Jul 30 13:23:27 node-2 multipathd: uevent trigger error
<27>Jul 30 13:23:27 node-2 multipathd: uevent trigger error
<27>Jul 30 13:23:27 node-2 multipathd: uevent trigger error
<27>Jul 30 13:24:16 node-2 multipathd: uevent trigger error
<27>Jul 30 13:24:16 node-2 multipathd: uevent trigger error
<27>Jul 30 13:24:16 node-2 multipathd: uevent trigger error
<27>Jul 30 13:24:16 node-2 multipathd: uevent trigger error
<27>Jul 30 13:24:32 node-2 multipathd: uevent trigger error
<27>Jul 30 13:24:32 node-2 multipathd: uevent trigger error
<27>Jul 30 13:24:32 node-2 multipathd: uevent trigger error
<27>Jul 30 13:24:32 node-2 multipathd: uevent trigger error
<27>Jul 30 13:24:32 node-2 multipathd: uevent trigger error
<11>Jul 30 13:24:41 node-2 liberasurecode[72726]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:41 node-2 liberasurecode[72726]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:41 node-2 liberasurecode[72726]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:41 node-2 liberasurecode[72726]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:41 node-2 liberasurecode[72750]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:41 node-2 liberasurecode[72750]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:41 node-2 liberasurecode[72750]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:41 node-2 liberasurecode[72750]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:43 node-2 liberasurecode[73174]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:43 node-2 liberasurecode[73174]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:43 node-2 liberasurecode[73174]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:43 node-2 liberasurecode[73174]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73726]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73726]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73726]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73726]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73767]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73767]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73767]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73767]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73805]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73805]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73805]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73805]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73867]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73867]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73867]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73867]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73884]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73884]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73884]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73884]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73908]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73908]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73908]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73908]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73896]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73896]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73896]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:49 node-2 liberasurecode[73896]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:52 node-2 liberasurecode[74112]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:52 node-2 liberasurecode[74112]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:52 node-2 liberasurecode[74112]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:24:52 node-2 liberasurecode[74112]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 30 13:24:58 node-2 multipathd: uevent trigger error
<27>Jul 30 13:24:59 node-2 multipathd: uevent trigger error
<27>Jul 30 13:24:59 node-2 multipathd: uevent trigger error
<27>Jul 30 13:24:59 node-2 multipathd: uevent trigger error
<27>Jul 30 13:24:59 node-2 multipathd: uevent trigger error
<11>Jul 30 13:25:01 node-2 liberasurecode[76036]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:25:01 node-2 liberasurecode[76036]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:25:01 node-2 liberasurecode[76036]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:25:01 node-2 liberasurecode[76036]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 30 13:25:04 node-2 multipathd: uevent trigger error
<27>Jul 30 13:25:04 node-2 multipathd: uevent trigger error
<27>Jul 30 13:25:04 node-2 multipathd: uevent trigger error
<27>Jul 30 13:25:04 node-2 multipathd: uevent trigger error
<27>Jul 30 13:25:04 node-2 multipathd: uevent trigger error
<11>Jul 30 13:25:11 node-2 epmd: epmd: node name already occupied rabbitmq-cli-58
<27>Jul 30 13:26:12 node-2 multipathd: uevent trigger error
<27>Jul 30 13:26:12 node-2 multipathd: uevent trigger error
<27>Jul 30 13:26:12 node-2 multipathd: uevent trigger error
<27>Jul 30 13:26:12 node-2 multipathd: uevent trigger error
<27>Jul 30 13:26:12 node-2 multipathd: uevent trigger error
<11>Jul 30 13:26:47 node-2 epmd: epmd: node name already occupied rabbitmq-cli-58
<11>Jul 30 13:27:21 node-2 epmd: epmd: node name already occupied rabbitmq-cli-58
<27>Jul 30 13:28:12 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:12 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:12 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:12 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:12 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:12 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:17 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:17 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:17 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:17 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:17 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:30 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:30 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:30 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:30 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:30 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:35 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:35 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:35 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:35 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:35 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:50 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:50 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:50 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:50 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:50 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:57 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:57 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:57 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:57 node-2 multipathd: uevent trigger error
<27>Jul 30 13:28:57 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:01 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:01 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:01 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:02 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:02 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:06 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:06 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:06 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:06 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:06 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:10 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:10 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:10 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:10 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:10 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:18 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:18 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:18 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:18 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:18 node-2 multipathd: uevent trigger error
<27>Jul 30 13:29:18 node-2 multipathd: uevent trigger error
<11>Jul 30 13:30:01 node-2 liberasurecode[129219]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:30:01 node-2 liberasurecode[129219]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:30:01 node-2 liberasurecode[129219]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 13:30:01 node-2 liberasurecode[129219]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 13:30:57 node-2 epmd: epmd: node name already occupied rabbitmq-cli-58
<11>Jul 30 13:31:01 node-2 epmd: epmd: node name already occupied rabbitmq-cli-58
