Jul 19 10:47:00 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8814" x-info="http://www.rsyslog.com"] start
Jul 19 10:47:00 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 19 10:47:00 node-2 rsyslogd: rsyslogd's groupid changed to 104
Jul 19 10:47:00 node-2 rsyslogd: rsyslogd's userid changed to 101
Jul 19 10:47:00 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 19 10:47:00 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 19 10:47:00 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 19 10:47: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 19 10:47: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=df36a39e-30e8-4e0f-8c70-f39eae5d6ecd nomdmonddf nomdmonisw
Jul 19 10:47:00 node-2 kernel: [    0.000000] KERNEL supported cpus:
Jul 19 10:47:00 node-2 kernel: [    0.000000]   Intel GenuineIntel
Jul 19 10:47:00 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Jul 19 10:47:00 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Jul 19 10:47:00 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 19 10:47:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000093fff] usable
Jul 19 10:47:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000094000-0x000000000009ffff] reserved
Jul 19 10:47:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 19 10:47:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000005ac9cfff] usable
Jul 19 10:47:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000005ac9d000-0x000000005b95cfff] reserved
Jul 19 10:47:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000005b95d000-0x00000000790fefff] usable
Jul 19 10:47:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000790ff000-0x00000000791fefff] reserved
Jul 19 10:47:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000791ff000-0x000000007b5fefff] ACPI NVS
Jul 19 10:47:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007b5ff000-0x000000007b7fefff] ACPI data
Jul 19 10:47:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007b7ff000-0x000000007b7fffff] usable
Jul 19 10:47:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007b800000-0x000000008fffffff] reserved
Jul 19 10:47:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff800000-0x00000000ffffffff] reserved
Jul 19 10:47:00 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000207fffffff] usable
Jul 19 10:47:00 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 19 10:47:00 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 19 10:47:00 node-2 kernel: [    0.000000] DMI: HP ProLiant BL460c Gen9, BIOS I36 09/24/2015
Jul 19 10:47:00 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 19 10:47:00 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 19 10:47:00 node-2 kernel: [    0.000000] No AGP bridge found
Jul 19 10:47:00 node-2 kernel: [    0.000000] e820: last_pfn = 0x2080000 max_arch_pfn = 0x400000000
Jul 19 10:47:00 node-2 kernel: [    0.000000] MTRR default type: write-back
Jul 19 10:47:00 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 19 10:47:00 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Jul 19 10:47:00 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 19 10:47:00 node-2 kernel: [    0.000000]   C0000-DFFFF write-protect
Jul 19 10:47:00 node-2 kernel: [    0.000000]   E0000-EFFFF uncachable
Jul 19 10:47:00 node-2 kernel: [    0.000000]   F0000-FFFFF write-protect
Jul 19 10:47:00 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 19 10:47:00 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 19 10:47:00 node-2 kernel: [    0.000000]   1 base 002080000000 mask 3FFF80000000 uncachable
Jul 19 10:47:00 node-2 kernel: [    0.000000]   2 base 008000000000 mask 3F8000000000 uncachable
Jul 19 10:47:00 node-2 kernel: [    0.000000]   3 base 010000000000 mask 3F0000000000 uncachable
Jul 19 10:47:00 node-2 kernel: [    0.000000]   4 base 038000000000 mask 3FC000000000 uncachable
Jul 19 10:47:00 node-2 kernel: [    0.000000]   5 base 00007C000000 mask 3FFFFC000000 uncachable
Jul 19 10:47:00 node-2 kernel: [    0.000000]   6 base 00007FC00000 mask 3FFFFFC00000 uncachable
Jul 19 10:47:00 node-2 kernel: [    0.000000]   7 disabled
Jul 19 10:47:00 node-2 kernel: [    0.000000]   8 disabled
Jul 19 10:47:00 node-2 kernel: [    0.000000]   9 disabled
Jul 19 10:47:00 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 19 10:47:00 node-2 kernel: [    0.000000] e820: last_pfn = 0x7b800 max_arch_pfn = 0x400000000
Jul 19 10:47:00 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 19 10:47:00 node-2 kernel: [    0.000000] Base memory trampoline at [ffff88000008e000] 8e000 size 24576
Jul 19 10:47:00 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Jul 19 10:47:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 19 10:47:00 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 19 10:47:00 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 19 10:47:00 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 19 10:47:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x207fe00000-0x207fffffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]  [mem 0x207fe00000-0x207fffffff] page 1G
Jul 19 10:47:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x207c000000-0x207fdfffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]  [mem 0x207c000000-0x207fdfffff] page 1G
Jul 19 10:47:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x2000000000-0x207bffffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]  [mem 0x2000000000-0x207bffffff] page 1G
Jul 19 10:47:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x1000000000-0x1fffffffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]  [mem 0x1000000000-0x1fffffffff] page 1G
Jul 19 10:47:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x5ac9cfff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 19 10:47:00 node-2 kernel: [    0.000000]  [mem 0x00200000-0x5abfffff] page 2M
Jul 19 10:47:00 node-2 kernel: [    0.000000]  [mem 0x5ac00000-0x5ac9cfff] page 4k
Jul 19 10:47:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x5b95d000-0x790fefff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]  [mem 0x5b95d000-0x5b9fffff] page 4k
Jul 19 10:47:00 node-2 kernel: [    0.000000]  [mem 0x5ba00000-0x78ffffff] page 2M
Jul 19 10:47:00 node-2 kernel: [    0.000000]  [mem 0x79000000-0x790fefff] page 4k
Jul 19 10:47:00 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 19 10:47:00 node-2 kernel: [    0.000000] BRK [0x01fe6000, 0x01fe6fff] PGTABLE
Jul 19 10:47:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7b7ff000-0x7b7fffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]  [mem 0x7b7ff000-0x7b7fffff] page 4k
Jul 19 10:47:00 node-2 kernel: [    0.000000] BRK [0x01fe7000, 0x01fe7fff] PGTABLE
Jul 19 10:47:00 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0xfffffffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]  [mem 0x100000000-0xfffffffff] page 1G
Jul 19 10:47:00 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f4f00 000024 (v02 HP    )
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: XSDT 000000007b7e8188 0000EC (v01 HP     ProLiant 00000001      01000013)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: FACP 000000007b7f6000 00010C (v05 HP     ProLiant 00000001 HP   00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: DSDT 000000007b7dd000 00AE48 (v02 HP     DSDT     00000002 HPAG 00020000)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: FACS 000000007b52b000 000040
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: UEFI 000000007b539000 000042 (v01 HP     ProLiant 00000002      01000013)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: MCEJ 000000007b7fc000 000130 (v01 HP     ProLiant 00000001 INTL 0100000D)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: SSDT 000000007b7fb000 000064 (v02 HP     SpsNvs   00000002 INTL 20130328)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: HEST 000000007b7fa000 0000A8 (v01 HP     ProLiant 00000001 INTL 00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: BERT 000000007b7f9000 000030 (v01 HP     ProLiant 00000001 INTL 00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: ERST 000000007b7f8000 000230 (v01 HP     ProLiant 00000001 INTL 00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: EINJ 000000007b7f7000 000150 (v01 HP     ProLiant 00000001 INTL 00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: HPET 000000007b7f5000 000038 (v01 HP     ProLiant 00000001 HP   00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: PMCT 000000007b7f4000 000064 (v01 HP     ProLiant 00000001 HP   00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: WDDT 000000007b7f3000 000040 (v01 HP     ProLiant 00000001 HP   00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: APIC 000000007b7f2000 0005AA (v03 HP     ProLiant 00000001 HP   00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: MCFG 000000007b7f1000 00003C (v01 HP     ProLiant 00000001 HP   00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: SLIT 000000007b7f0000 000030 (v01 HP     ProLiant 00000001 HP   00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: SRAT 000000007b7ef000 000500 (v03 HP     ProLiant 00000001 HP   00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: SPMI 000000007b7ee000 000041 (v05 HP     ProLiant 00000001 HP   00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: RASF 000000007b7ed000 000030 (v01 HP     ProLiant 00000001 HP   00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: SPCR 000000007b7ec000 000050 (v01 HP     ProLiant 00000001 HP   00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: MSCT 000000007b7eb000 000064 (v01 HP     ProLiant 00000001 HP   00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: BDAT 000000007b7ea000 000030 (v01 HP     ProLiant 00000001 HP   00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: PCCT 000000007b7e9000 00006E (v01 HP     ProLiant 00000001 HP   00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: SSDT 000000007b7d6000 0061A4 (v02 HP     PCISSDT  00000002 HPAG 00020000)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: SSDT 000000007b7d5000 0001CB (v02 HP     TIMESSDT 00000002 HPAG 00020000)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: SSDT 000000007b7d4000 0002F2 (v01 HP         pmab 00000001 INTL 20130328)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: DMAR 000000007b7fd000 000300 (v01 INTEL  INTEL ID 00000001    ? 00000001)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0000 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0002 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0004 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0006 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0008 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x000a -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0010 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0012 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0014 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0016 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0018 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x001a -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0020 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0022 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0024 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0026 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0028 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x002a -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0030 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0032 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0034 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0036 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0038 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x003a -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0001 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0003 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0005 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0007 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0009 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x000b -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0011 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0013 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0015 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0017 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0019 -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x001b -> Node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0021 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0023 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0025 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0027 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0029 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x002b -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0031 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0033 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0035 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0037 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0039 -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x003b -> Node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x107fffffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x1080000000-0x207fffffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 19 10:47:00 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x107fffffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x107fffb000-0x107fffffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x1080000000-0x207fffffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x207fff8000-0x207fffcfff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0041ffffff] PMD -> [ffff88103fe00000-ffff88107fdfffff] on node 0
Jul 19 10:47:00 node-2 kernel: [    0.000000]  [ffffea0042000000-ffffea0081ffffff] PMD -> [ffff88203f600000-ffff88207f5fffff] on node 1
Jul 19 10:47:00 node-2 kernel: [    0.000000] Zone ranges:
Jul 19 10:47:00 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x207fffffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000] Movable zone start for each node
Jul 19 10:47:00 node-2 kernel: [    0.000000] Early memory node ranges
Jul 19 10:47:00 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x00093fff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x5ac9cfff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]   node   0: [mem 0x5b95d000-0x790fefff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]   node   0: [mem 0x7b7ff000-0x7b7fffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x107fffffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000]   node   1: [mem 0x1080000000-0x207fffffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000] On node 0 totalpages: 16745427
Jul 19 10:47:00 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 19 10:47:00 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 19 10:47:00 node-2 kernel: [    0.000000]   DMA zone: 3987 pages, LIFO batch:0
Jul 19 10:47:00 node-2 kernel: [    0.000000]   DMA32 zone: 7633 pages used for memmap
Jul 19 10:47:00 node-2 kernel: [    0.000000]   DMA32 zone: 488512 pages, LIFO batch:31
Jul 19 10:47:00 node-2 kernel: [    0.000000]   Normal zone: 253952 pages used for memmap
Jul 19 10:47:00 node-2 kernel: [    0.000000]   Normal zone: 16252928 pages, LIFO batch:31
Jul 19 10:47:00 node-2 kernel: [    0.000000] On node 1 totalpages: 16777216
Jul 19 10:47:00 node-2 kernel: [    0.000000]   Normal zone: 262144 pages used for memmap
Jul 19 10:47:00 node-2 kernel: [    0.000000]   Normal zone: 16777216 pages, LIFO batch:31
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x00] uid[0x00] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x02] uid[0x02] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x04] uid[0x04] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x06] uid[0x06] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x08] uid[0x08] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x0a] uid[0x0a] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x10] uid[0x10] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x12] uid[0x12] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x14] uid[0x14] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x16] uid[0x16] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x18] uid[0x18] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x1a] uid[0x1a] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x20] uid[0x20] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x22] uid[0x22] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x24] uid[0x24] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x26] uid[0x26] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x28] uid[0x28] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x2a] uid[0x2a] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x30] uid[0x30] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x32] uid[0x32] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x34] uid[0x34] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x36] uid[0x36] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x38] uid[0x38] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x3a] uid[0x3a] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x01] uid[0x01] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x03] uid[0x03] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x05] uid[0x05] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x07] uid[0x07] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x09] uid[0x09] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x0b] uid[0x0b] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x11] uid[0x11] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x13] uid[0x13] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x15] uid[0x15] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x17] uid[0x17] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x19] uid[0x19] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x1b] uid[0x1b] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x21] uid[0x21] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x23] uid[0x23] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x25] uid[0x25] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x27] uid[0x27] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x29] uid[0x29] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x2b] uid[0x2b] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x31] uid[0x31] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x33] uid[0x33] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x35] uid[0x35] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x37] uid[0x37] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x39] uid[0x39] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x3b] uid[0x3b] enabled)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x00] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x01] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x02] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x03] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x04] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x05] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x06] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x07] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x08] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x09] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x0a] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x0b] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x10] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x11] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x12] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x13] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x14] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x15] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x16] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x17] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x18] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x19] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x1a] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x1b] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x20] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x21] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x22] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x23] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x24] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x25] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x26] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x27] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x28] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x29] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x2a] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x2b] high level lint[0x1])
Jul 19 10:47: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 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x30] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x31] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x32] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x33] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x34] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x35] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x36] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x37] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x38] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x39] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x3a] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x3b] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 19 10:47:00 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 19 10:47:00 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 19 10:47:00 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 19 10:47:00 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 19 10:47:00 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 19 10:47:00 node-2 kernel: [    0.000000] smpboot: Allowing 48 CPUs, 0 hotplug CPUs
Jul 19 10:47:00 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 19 10:47:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x00094000-0x0009ffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x5ac9d000-0x5b95cfff]
Jul 19 10:47:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x790ff000-0x791fefff]
Jul 19 10:47:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x791ff000-0x7b5fefff]
Jul 19 10:47:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7b5ff000-0x7b7fefff]
Jul 19 10:47:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7b800000-0x8fffffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xff7fffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff800000-0xffffffff]
Jul 19 10:47:00 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xff7fffff] available for PCI devices
Jul 19 10:47:00 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 19 10:47:00 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:48 nr_node_ids:2
Jul 19 10:47:00 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88103fa00000 s81536 r8192 d20864 u131072
Jul 19 10:47:00 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u131072 alloc=1*2097152
Jul 19 10:47:00 node-2 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 08 09 10 11 24 25 26 27 
Jul 19 10:47:00 node-2 kernel: [    0.000000] pcpu-alloc: [0] 28 29 30 31 32 33 34 35 -- -- -- -- -- -- -- -- 
Jul 19 10:47:00 node-2 kernel: [    0.000000] pcpu-alloc: [1] 12 13 14 15 16 17 18 19 20 21 22 23 36 37 38 39 
Jul 19 10:47:00 node-2 kernel: [    0.000000] pcpu-alloc: [1] 40 41 42 43 44 45 46 47 -- -- -- -- -- -- -- -- 
Jul 19 10:47:00 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 32998829
Jul 19 10:47:00 node-2 kernel: [    0.000000] Policy zone: Normal
Jul 19 10:47: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=df36a39e-30e8-4e0f-8c70-f39eae5d6ecd nomdmonddf nomdmonisw
Jul 19 10:47:00 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 19 10:47:00 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 19 10:47:00 node-2 kernel: [    0.000000] Checking aperture...
Jul 19 10:47:00 node-2 kernel: [    0.000000] No AGP bridge found
Jul 19 10:47:00 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 19 10:47:00 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 19 10:47:00 node-2 kernel: [    0.000000] Memory: 131884968K/134090572K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 2205604K reserved)
Jul 19 10:47:00 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=48, Nodes=2
Jul 19 10:47:00 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 19 10:47:00 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 19 10:47:00 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=48.
Jul 19 10:47:00 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 19 10:47:00 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-47.
Jul 19 10:47:00 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1880 16
Jul 19 10:47:00 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 19 10:47:00 node-2 kernel: [    0.000000] console [tty0] enabled
Jul 19 10:47:00 node-2 kernel: [    0.000000] allocated 536870912 bytes of page_cgroup
Jul 19 10:47:00 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 19 10:47:00 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 19 10:47:00 node-2 kernel: [    0.000000] hpet clockevent registered
Jul 19 10:47:00 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 19 10:47:00 node-2 kernel: [    0.004000] tsc: Detected 2497.049 MHz processor
Jul 19 10:47:00 node-2 kernel: [    0.000025] Calibrating delay loop (skipped), value calculated using timer frequency.. 4994.09 BogoMIPS (lpj=9988196)
Jul 19 10:47:00 node-2 kernel: [    0.000033] pid_max: default: 49152 minimum: 384
Jul 19 10:47:00 node-2 kernel: [    0.000197] Security Framework initialized
Jul 19 10:47:00 node-2 kernel: [    0.000289] AppArmor: AppArmor initialized
Jul 19 10:47:00 node-2 kernel: [    0.000292] Yama: becoming mindful.
Jul 19 10:47:00 node-2 kernel: [    0.015706] Dentry cache hash table entries: 16777216 (order: 15, 134217728 bytes)
Jul 19 10:47:00 node-2 kernel: [    0.061983] Inode-cache hash table entries: 8388608 (order: 14, 67108864 bytes)
Jul 19 10:47:00 node-2 kernel: [    0.081462] Mount-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 19 10:47:00 node-2 kernel: [    0.081714] Mountpoint-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 19 10:47:00 node-2 kernel: [    0.083249] Initializing cgroup subsys memory
Jul 19 10:47:00 node-2 kernel: [    0.083279] Initializing cgroup subsys devices
Jul 19 10:47:00 node-2 kernel: [    0.083283] Initializing cgroup subsys freezer
Jul 19 10:47:00 node-2 kernel: [    0.083288] Initializing cgroup subsys blkio
Jul 19 10:47:00 node-2 kernel: [    0.083292] Initializing cgroup subsys perf_event
Jul 19 10:47:00 node-2 kernel: [    0.083309] Initializing cgroup subsys hugetlb
Jul 19 10:47:00 node-2 kernel: [    0.083369] CPU: Physical Processor ID: 0
Jul 19 10:47:00 node-2 kernel: [    0.083372] CPU: Processor Core ID: 0
Jul 19 10:47:00 node-2 kernel: [    0.084923] mce: CPU supports 22 MCE banks
Jul 19 10:47:00 node-2 kernel: [    0.085002] CPU0: Thermal monitoring enabled (TM1)
Jul 19 10:47:00 node-2 kernel: [    0.085009] process: using mwait in idle threads
Jul 19 10:47:00 node-2 kernel: [    0.085017] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 19 10:47:00 node-2 kernel: [    0.085017] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 19 10:47:00 node-2 kernel: [    0.085017] tlb_flushall_shift: 6
Jul 19 10:47:00 node-2 kernel: [    0.085251] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 19 10:47:00 node-2 kernel: [    0.087129] ACPI: Core revision 20131115
Jul 19 10:47:00 node-2 kernel: [    0.094004] ACPI: All ACPI Tables successfully acquired
Jul 19 10:47:00 node-2 kernel: [    0.094251] ftrace: allocating 28617 entries in 112 pages
Jul 19 10:47:00 node-2 kernel: [    0.118095] dmar: Host address width 46
Jul 19 10:47:00 node-2 kernel: [    0.118101] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 19 10:47:00 node-2 kernel: [    0.118113] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020df
Jul 19 10:47:00 node-2 kernel: [    0.118117] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 19 10:47:00 node-2 kernel: [    0.118127] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020df
Jul 19 10:47:00 node-2 kernel: [    0.118131] dmar: RMRR base: 0x00000079171000 end: 0x00000079173fff
Jul 19 10:47:00 node-2 kernel: [    0.118134] dmar: RMRR base: 0x000000791ed000 end: 0x000000791f0fff
Jul 19 10:47:00 node-2 kernel: [    0.118137] dmar: RMRR base: 0x000000791dd000 end: 0x000000791ecfff
Jul 19 10:47:00 node-2 kernel: [    0.118140] dmar: RMRR base: 0x000000791ca000 end: 0x000000791dafff
Jul 19 10:47:00 node-2 kernel: [    0.118143] dmar: RMRR base: 0x000000791db000 end: 0x000000791dcfff
Jul 19 10:47:00 node-2 kernel: [    0.118146] dmar: RMRR base: 0x0000005ac9d000 end: 0x0000005acdcfff
Jul 19 10:47:00 node-2 kernel: [    0.118286] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 19 10:47:00 node-2 kernel: [    0.118289] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 19 10:47:00 node-2 kernel: [    0.118292] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 19 10:47:00 node-2 kernel: [    0.118295] HPET id 0 under DRHD base 0xc7ffc000
Jul 19 10:47:00 node-2 kernel: [    0.119121] Enabled IRQ remapping in x2apic mode
Jul 19 10:47:00 node-2 kernel: [    0.119125] Enabling x2apic
Jul 19 10:47:00 node-2 kernel: [    0.119127] Enabled x2apic
Jul 19 10:47:00 node-2 kernel: [    0.119134] Switched APIC routing to cluster x2apic.
Jul 19 10:47:00 node-2 kernel: [    0.119911] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 19 10:47:00 node-2 kernel: [    0.159593] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 19 10:47:00 node-2 kernel: [    0.159607] TSC deadline timer enabled
Jul 19 10:47:00 node-2 kernel: [    0.159636] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Broken BIOS detected, complain to your hardware vendor.
Jul 19 10:47:00 node-2 kernel: [    0.159649] [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 38d is 330)
Jul 19 10:47:00 node-2 kernel: [    0.159653] Intel PMU driver.
Jul 19 10:47:00 node-2 kernel: [    0.159658] ... version:                3
Jul 19 10:47:00 node-2 kernel: [    0.159660] ... bit width:              48
Jul 19 10:47:00 node-2 kernel: [    0.159663] ... generic registers:      4
Jul 19 10:47:00 node-2 kernel: [    0.159666] ... value mask:             0000ffffffffffff
Jul 19 10:47:00 node-2 kernel: [    0.159669] ... max period:             0000ffffffffffff
Jul 19 10:47:00 node-2 kernel: [    0.159671] ... fixed-purpose events:   3
Jul 19 10:47:00 node-2 kernel: [    0.159674] ... event mask:             000000070000000f
Jul 19 10:47:00 node-2 kernel: [    0.165056] x86: Booting SMP configuration:
Jul 19 10:47:00 node-2 kernel: [    0.182477] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 19 10:47:00 node-2 kernel: [    0.165062] .... node  #0, CPUs:        #1  #2  #3  #4  #5  #6  #7  #8  #9 #10 #11
Jul 19 10:47:00 node-2 kernel: [    0.342100] .... node  #1, CPUs:   #12 #13 #14 #15 #16 #17 #18 #19 #20 #21 #22 #23
Jul 19 10:47:00 node-2 kernel: [    0.631328] .... node  #0, CPUs:   #24 #25 #26 #27 #28 #29 #30 #31 #32 #33 #34 #35
Jul 19 10:47:00 node-2 kernel: [    0.811262] .... node  #1, CPUs:   #36 #37 #38 #39 #40 #41 #42 #43 #44 #45 #46 #47
Jul 19 10:47:00 node-2 kernel: [    1.003394] x86: Booted up 2 nodes, 48 CPUs
Jul 19 10:47:00 node-2 kernel: [    1.003399] smpboot: Total of 48 processors activated (239758.71 BogoMIPS)
Jul 19 10:47:00 node-2 kernel: [    1.187021] devtmpfs: initialized
Jul 19 10:47:00 node-2 kernel: [    1.196777] EVM: security.selinux
Jul 19 10:47:00 node-2 kernel: [    1.196780] EVM: security.SMACK64
Jul 19 10:47:00 node-2 kernel: [    1.196781] EVM: security.ima
Jul 19 10:47:00 node-2 kernel: [    1.196782] EVM: security.capability
Jul 19 10:47:00 node-2 kernel: [    1.196855] PM: Registering ACPI NVS region [mem 0x791ff000-0x7b5fefff] (37748736 bytes)
Jul 19 10:47:00 node-2 kernel: [    1.198303] pinctrl core: initialized pinctrl subsystem
Jul 19 10:47:00 node-2 kernel: [    1.198378] regulator-dummy: no parameters
Jul 19 10:47:00 node-2 kernel: [    1.198409] RTC time: 10:46:21, date: 07/19/16
Jul 19 10:47:00 node-2 kernel: [    1.198471] NET: Registered protocol family 16
Jul 19 10:47:00 node-2 kernel: [    1.198586] cpuidle: using governor ladder
Jul 19 10:47:00 node-2 kernel: [    1.198588] cpuidle: using governor menu
Jul 19 10:47:00 node-2 kernel: [    1.198637] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Jul 19 10:47:00 node-2 kernel: [    1.198639] ACPI: bus type PCI registered
Jul 19 10:47:00 node-2 kernel: [    1.198641] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 19 10:47:00 node-2 kernel: [    1.198724] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 19 10:47:00 node-2 kernel: [    1.198727] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 19 10:47:00 node-2 kernel: [    1.217808] PCI: Using configuration type 1 for base access
Jul 19 10:47:00 node-2 kernel: [    1.220575] bio: create slab <bio-0> at 0
Jul 19 10:47:00 node-2 kernel: [    1.221123] ACPI: Added _OSI(Module Device)
Jul 19 10:47:00 node-2 kernel: [    1.221126] ACPI: Added _OSI(Processor Device)
Jul 19 10:47:00 node-2 kernel: [    1.221127] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 19 10:47:00 node-2 kernel: [    1.221129] ACPI: Added _OSI(Processor Aggregator Device)
Jul 19 10:47:00 node-2 kernel: [    1.232525] ACPI: Interpreter enabled
Jul 19 10:47:00 node-2 kernel: [    1.232531] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 19 10:47:00 node-2 kernel: [    1.232536] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 19 10:47:00 node-2 kernel: [    1.232539] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 19 10:47:00 node-2 kernel: [    1.232542] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S4_] (20131115/hwxface-580)
Jul 19 10:47:00 node-2 kernel: [    1.232548] ACPI: (supports S0 S5)
Jul 19 10:47:00 node-2 kernel: [    1.232549] ACPI: Using IOAPIC for interrupt routing
Jul 19 10:47:00 node-2 kernel: [    1.232597] HEST: Table parsing has been initialized.
Jul 19 10:47:00 node-2 kernel: [    1.232601] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 19 10:47:00 node-2 kernel: [    1.232793] ACPI: No dock devices found.
Jul 19 10:47:00 node-2 kernel: [    1.244244] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 19 10:47:00 node-2 kernel: [    1.244250] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 19 10:47:00 node-2 kernel: [    1.244255] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 19 10:47:00 node-2 kernel: [    1.244289] PCI host bridge to bus 0000:7f
Jul 19 10:47:00 node-2 kernel: [    1.244292] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 19 10:47:00 node-2 kernel: [    1.244302] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244346] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244386] pci 0000:7f:09.0: [8086:2f90] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244422] pci 0000:7f:09.3: [8086:2f93] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244460] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244489] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 19 10:47:00 node-2 kernel: [    1.244522] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 19 10:47:00 node-2 kernel: [    1.244556] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244591] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244621] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244650] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244680] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244710] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244740] pci 0000:7f:0c.6: [8086:2fe6] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244769] pci 0000:7f:0c.7: [8086:2fe7] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244799] pci 0000:7f:0d.0: [8086:2fe8] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244830] pci 0000:7f:0d.1: [8086:2fe9] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244859] pci 0000:7f:0d.2: [8086:2fea] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244889] pci 0000:7f:0d.3: [8086:2feb] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244921] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244951] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.244981] pci 0000:7f:0f.2: [8086:2ffa] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245011] pci 0000:7f:0f.3: [8086:2ffb] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245042] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245074] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245104] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245137] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245168] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 19 10:47:00 node-2 kernel: [    1.245203] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245231] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 19 10:47:00 node-2 kernel: [    1.245260] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245289] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245322] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 19 10:47:00 node-2 kernel: [    1.245356] pci 0000:7f:12.2: [8086:2f70] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245388] pci 0000:7f:12.4: [8086:2f60] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245421] pci 0000:7f:12.5: [8086:2f38] type 00 class 0x110100
Jul 19 10:47:00 node-2 kernel: [    1.245456] pci 0000:7f:12.6: [8086:2f78] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245490] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245526] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245562] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245597] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245637] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245668] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245702] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245738] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245772] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245808] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245844] pci 0000:7f:14.4: [8086:2fbc] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245880] pci 0000:7f:14.5: [8086:2fbd] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245914] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245948] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.245983] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246018] pci 0000:7f:16.1: [8086:2f79] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246052] pci 0000:7f:16.2: [8086:2f6a] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246088] pci 0000:7f:16.3: [8086:2f6b] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246127] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246162] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246196] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246236] pci 0000:7f:17.1: [8086:2fd1] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246273] pci 0000:7f:17.2: [8086:2fd2] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246310] pci 0000:7f:17.3: [8086:2fd3] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246347] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246381] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246416] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246452] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246490] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246524] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246557] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246591] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246628] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246667] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246702] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246771] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 19 10:47:00 node-2 kernel: [    1.246775] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 19 10:47:00 node-2 kernel: [    1.246779] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 19 10:47:00 node-2 kernel: [    1.246801] PCI host bridge to bus 0000:ff
Jul 19 10:47:00 node-2 kernel: [    1.246803] pci_bus 0000:ff: root bus resource [bus ff]
Jul 19 10:47:00 node-2 kernel: [    1.246811] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246849] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246890] pci 0000:ff:09.0: [8086:2f90] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246926] pci 0000:ff:09.3: [8086:2f93] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246964] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.246997] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 19 10:47:00 node-2 kernel: [    1.247030] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 19 10:47:00 node-2 kernel: [    1.247065] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247100] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247138] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247180] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247214] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247249] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247283] pci 0000:ff:0c.6: [8086:2fe6] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247319] pci 0000:ff:0c.7: [8086:2fe7] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247352] pci 0000:ff:0d.0: [8086:2fe8] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247386] pci 0000:ff:0d.1: [8086:2fe9] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247420] pci 0000:ff:0d.2: [8086:2fea] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247453] pci 0000:ff:0d.3: [8086:2feb] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247489] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247521] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247554] pci 0000:ff:0f.2: [8086:2ffa] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247587] pci 0000:ff:0f.3: [8086:2ffb] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247621] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247656] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247689] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247724] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247760] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 19 10:47:00 node-2 kernel: [    1.247794] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247826] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 19 10:47:00 node-2 kernel: [    1.247860] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247893] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.247931] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 19 10:47:00 node-2 kernel: [    1.247966] pci 0000:ff:12.2: [8086:2f70] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248003] pci 0000:ff:12.4: [8086:2f60] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248041] pci 0000:ff:12.5: [8086:2f38] type 00 class 0x110100
Jul 19 10:47:00 node-2 kernel: [    1.248079] pci 0000:ff:12.6: [8086:2f78] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248119] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248158] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248196] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248235] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248276] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248313] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248354] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248396] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248437] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248475] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248514] pci 0000:ff:14.4: [8086:2fbc] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248553] pci 0000:ff:14.5: [8086:2fbd] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248590] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248627] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248672] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248710] pci 0000:ff:16.1: [8086:2f79] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248751] pci 0000:ff:16.2: [8086:2f6a] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248792] pci 0000:ff:16.3: [8086:2f6b] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248835] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248874] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248912] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248954] pci 0000:ff:17.1: [8086:2fd1] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.248995] pci 0000:ff:17.2: [8086:2fd2] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.249037] pci 0000:ff:17.3: [8086:2fd3] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.249078] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.249116] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.249154] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.249192] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.249236] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.249273] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.249312] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.249349] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.249385] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.249427] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.249466] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.250333] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 19 10:47:00 node-2 kernel: [    1.250338] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 19 10:47:00 node-2 kernel: [    1.250411] acpi PNP0A08:00: _OSC: platform does not support [AER]
Jul 19 10:47:00 node-2 kernel: [    1.250473] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME PCIeCapability]
Jul 19 10:47:00 node-2 kernel: [    1.250476] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
Jul 19 10:47:00 node-2 kernel: [    1.250760] acpi PNP0A08:00: ignoring host bridge window [mem 0x000c4000-0x000cbfff] (conflicts with Video ROM [mem 0x000c0000-0x000c7fff])
Jul 19 10:47:00 node-2 kernel: [    1.250985] PCI host bridge to bus 0000:00
Jul 19 10:47:00 node-2 kernel: [    1.250987] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 19 10:47:00 node-2 kernel: [    1.250990] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 19 10:47:00 node-2 kernel: [    1.250991] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 19 10:47:00 node-2 kernel: [    1.250993] pci_bus 0000:00: root bus resource [io  0x03b0-0x03bb]
Jul 19 10:47:00 node-2 kernel: [    1.250995] pci_bus 0000:00: root bus resource [io  0x03c0-0x03df]
Jul 19 10:47:00 node-2 kernel: [    1.250997] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 19 10:47:00 node-2 kernel: [    1.250999] pci_bus 0000:00: root bus resource [io  0x1000-0x9fff]
Jul 19 10:47:00 node-2 kernel: [    1.251001] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 19 10:47:00 node-2 kernel: [    1.251003] pci_bus 0000:00: root bus resource [mem 0x38000000000-0x39fffffffff]
Jul 19 10:47:00 node-2 kernel: [    1.251011] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 19 10:47:00 node-2 kernel: [    1.251111] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.251148] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.251207] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 19 10:47:00 node-2 kernel: [    1.251239] pci 0000:00:01.1: [8086:2f03] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.251274] pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.251351] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.251386] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.251438] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 19 10:47:00 node-2 kernel: [    1.251462] pci 0000:00:02.1: [8086:2f05] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.251497] pci 0000:00:02.1: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.251569] pci 0000:00:02.2: [8086:2f06] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.251604] pci 0000:00:02.2: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.251674] pci 0000:00:02.3: [8086:2f07] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.251709] pci 0000:00:02.3: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.251787] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.251823] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.251875] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 19 10:47:00 node-2 kernel: [    1.251901] pci 0000:00:03.1: [8086:2f09] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.251936] pci 0000:00:03.1: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.252009] pci 0000:00:03.2: [8086:2f0a] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.252044] pci 0000:00:03.2: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.252117] pci 0000:00:03.3: [8086:2f0b] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.252151] pci 0000:00:03.3: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.252229] pci 0000:00:04.0: [8086:2f20] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.252238] pci 0000:00:04.0: reg 0x10: [mem 0x39ffff2c000-0x39ffff2ffff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.252335] pci 0000:00:04.1: [8086:2f21] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.252343] pci 0000:00:04.1: reg 0x10: [mem 0x39ffff28000-0x39ffff2bfff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.252441] pci 0000:00:04.2: [8086:2f22] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.252449] pci 0000:00:04.2: reg 0x10: [mem 0x39ffff24000-0x39ffff27fff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.252546] pci 0000:00:04.3: [8086:2f23] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.252554] pci 0000:00:04.3: reg 0x10: [mem 0x39ffff20000-0x39ffff23fff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.252649] pci 0000:00:04.4: [8086:2f24] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.252656] pci 0000:00:04.4: reg 0x10: [mem 0x39ffff1c000-0x39ffff1ffff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.252755] pci 0000:00:04.5: [8086:2f25] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.252762] pci 0000:00:04.5: reg 0x10: [mem 0x39ffff18000-0x39ffff1bfff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.252858] pci 0000:00:04.6: [8086:2f26] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.252866] pci 0000:00:04.6: reg 0x10: [mem 0x39ffff14000-0x39ffff17fff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.252962] pci 0000:00:04.7: [8086:2f27] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.252970] pci 0000:00:04.7: reg 0x10: [mem 0x39ffff10000-0x39ffff13fff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.253075] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.253162] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.253259] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.253348] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 19 10:47:00 node-2 kernel: [    1.253354] pci 0000:00:05.4: reg 0x10: [mem 0x95603000-0x95603fff]
Jul 19 10:47:00 node-2 kernel: [    1.253463] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 19 10:47:00 node-2 kernel: [    1.253623] pci 0000:00:14.0: [8086:8d31] type 00 class 0x0c0330
Jul 19 10:47:00 node-2 kernel: [    1.253639] pci 0000:00:14.0: reg 0x10: [mem 0x39ffff00000-0x39ffff0ffff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.253688] pci 0000:00:14.0: PME# supported from D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.253770] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 19 10:47:00 node-2 kernel: [    1.253789] pci 0000:00:1a.0: reg 0x10: [mem 0x95601000-0x956013ff]
Jul 19 10:47:00 node-2 kernel: [    1.253873] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.253958] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.254019] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.254097] pci 0000:00:1c.2: [8086:8d14] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.254158] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.254236] pci 0000:00:1c.4: [8086:8d18] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.254297] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.254374] pci 0000:00:1c.6: [8086:8d1c] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.254435] pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.254509] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.254570] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.254655] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 19 10:47:00 node-2 kernel: [    1.254675] pci 0000:00:1d.0: reg 0x10: [mem 0x95600000-0x956003ff]
Jul 19 10:47:00 node-2 kernel: [    1.254758] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.254840] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 19 10:47:00 node-2 kernel: [    1.255003] pci 0000:00:1f.3: [8086:8d22] type 00 class 0x0c0500
Jul 19 10:47:00 node-2 kernel: [    1.255016] pci 0000:00:1f.3: reg 0x10: [mem 0x39ffff31000-0x39ffff310ff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.255034] pci 0000:00:1f.3: reg 0x20: [io  0x4000-0x401f]
Jul 19 10:47:00 node-2 kernel: [    1.255195] pci 0000:00:01.0: PCI bridge to [bus 02]
Jul 19 10:47:00 node-2 kernel: [    1.255230] pci 0000:00:01.1: PCI bridge to [bus 05]
Jul 19 10:47:00 node-2 kernel: [    1.255282] pci 0000:06:00.0: [14e4:16a2] type 00 class 0x020000
Jul 19 10:47:00 node-2 kernel: [    1.255294] pci 0000:06:00.0: reg 0x10: [mem 0x94000000-0x947fffff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.255303] pci 0000:06:00.0: reg 0x18: [mem 0x94800000-0x94ffffff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.255312] pci 0000:06:00.0: reg 0x20: [mem 0x95010000-0x9501ffff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.255319] pci 0000:06:00.0: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.255352] pci 0000:06:00.0: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.255403] pci 0000:06:00.1: [14e4:16a2] type 00 class 0x020000
Jul 19 10:47:00 node-2 kernel: [    1.255414] pci 0000:06:00.1: reg 0x10: [mem 0x93000000-0x937fffff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.255423] pci 0000:06:00.1: reg 0x18: [mem 0x93800000-0x93ffffff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.255432] pci 0000:06:00.1: reg 0x20: [mem 0x95000000-0x9500ffff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.255439] pci 0000:06:00.1: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.255471] pci 0000:06:00.1: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.263179] pci 0000:00:02.0: PCI bridge to [bus 06]
Jul 19 10:47:00 node-2 kernel: [    1.263190] pci 0000:00:02.0:   bridge window [mem 0x93000000-0x950fffff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.263253] pci 0000:00:02.1: PCI bridge to [bus 0b]
Jul 19 10:47:00 node-2 kernel: [    1.263292] pci 0000:07:00.0: [103c:3239] type 00 class 0x010400
Jul 19 10:47:00 node-2 kernel: [    1.263301] pci 0000:07:00.0: reg 0x10: [mem 0x95400000-0x954fffff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.263308] pci 0000:07:00.0: reg 0x18: [mem 0x95500000-0x955003ff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.263314] pci 0000:07:00.0: reg 0x20: [io  0x3000-0x30ff]
Jul 19 10:47:00 node-2 kernel: [    1.263323] pci 0000:07:00.0: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.263348] pci 0000:07:00.0: PME# supported from D0 D1 D3hot
Jul 19 10:47:00 node-2 kernel: [    1.271179] pci 0000:00:02.2: PCI bridge to [bus 07]
Jul 19 10:47:00 node-2 kernel: [    1.271185] pci 0000:00:02.2:   bridge window [io  0x3000-0x3fff]
Jul 19 10:47:00 node-2 kernel: [    1.271189] pci 0000:00:02.2:   bridge window [mem 0x95400000-0x955fffff]
Jul 19 10:47:00 node-2 kernel: [    1.271246] pci 0000:00:02.3: PCI bridge to [bus 0c]
Jul 19 10:47:00 node-2 kernel: [    1.271390] pci 0000:08:00.0: [8086:10f8] type 00 class 0x020000
Jul 19 10:47:00 node-2 kernel: [    1.271398] pci 0000:08:00.0: reg 0x10: [mem 0x95200000-0x952fffff]
Jul 19 10:47:00 node-2 kernel: [    1.271408] pci 0000:08:00.0: reg 0x18: [io  0x2020-0x203f]
Jul 19 10:47:00 node-2 kernel: [    1.271413] pci 0000:08:00.0: reg 0x1c: [mem 0x95304000-0x95307fff]
Jul 19 10:47:00 node-2 kernel: [    1.271427] pci 0000:08:00.0: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.271455] pci 0000:08:00.0: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.271477] pci 0000:08:00.0: reg 0x184: [mem 0x39fffe00000-0x39fffe03fff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.271486] pci 0000:08:00.0: reg 0x190: [mem 0x39fffd00000-0x39fffd03fff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.271533] pci 0000:08:00.1: [8086:10f8] type 00 class 0x020000
Jul 19 10:47:00 node-2 kernel: [    1.271541] pci 0000:08:00.1: reg 0x10: [mem 0x95100000-0x951fffff]
Jul 19 10:47:00 node-2 kernel: [    1.271551] pci 0000:08:00.1: reg 0x18: [io  0x2000-0x201f]
Jul 19 10:47:00 node-2 kernel: [    1.271556] pci 0000:08:00.1: reg 0x1c: [mem 0x95300000-0x95303fff]
Jul 19 10:47:00 node-2 kernel: [    1.271570] pci 0000:08:00.1: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.271598] pci 0000:08:00.1: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.271617] pci 0000:08:00.1: reg 0x184: [mem 0x39fffc00000-0x39fffc03fff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.271627] pci 0000:08:00.1: reg 0x190: [mem 0x39fffb00000-0x39fffb03fff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.279188] pci 0000:00:03.0: PCI bridge to [bus 08]
Jul 19 10:47:00 node-2 kernel: [    1.279194] pci 0000:00:03.0:   bridge window [io  0x2000-0x2fff]
Jul 19 10:47:00 node-2 kernel: [    1.279198] pci 0000:00:03.0:   bridge window [mem 0x95100000-0x953fffff]
Jul 19 10:47:00 node-2 kernel: [    1.279204] pci 0000:00:03.0:   bridge window [mem 0x39fffb00000-0x39fffefffff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.279262] pci 0000:00:03.1: PCI bridge to [bus 0d]
Jul 19 10:47:00 node-2 kernel: [    1.279325] pci 0000:00:03.2: PCI bridge to [bus 0e]
Jul 19 10:47:00 node-2 kernel: [    1.279391] pci 0000:00:03.3: PCI bridge to [bus 0f]
Jul 19 10:47:00 node-2 kernel: [    1.279438] pci 0000:00:1c.0: PCI bridge to [bus 10]
Jul 19 10:47:00 node-2 kernel: [    1.279506] pci 0000:01:00.0: [103c:3306] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.279524] pci 0000:01:00.0: reg 0x10: [io  0x1200-0x12ff]
Jul 19 10:47:00 node-2 kernel: [    1.279536] pci 0000:01:00.0: reg 0x14: [mem 0x92a8d000-0x92a8d1ff]
Jul 19 10:47:00 node-2 kernel: [    1.279548] pci 0000:01:00.0: reg 0x18: [io  0x1100-0x11ff]
Jul 19 10:47:00 node-2 kernel: [    1.279700] pci 0000:01:00.1: [102b:0533] type 00 class 0x030000
Jul 19 10:47:00 node-2 kernel: [    1.279717] pci 0000:01:00.1: reg 0x10: [mem 0x91000000-0x91ffffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.279729] pci 0000:01:00.1: reg 0x14: [mem 0x92a88000-0x92a8bfff]
Jul 19 10:47:00 node-2 kernel: [    1.279741] pci 0000:01:00.1: reg 0x18: [mem 0x92000000-0x927fffff]
Jul 19 10:47:00 node-2 kernel: [    1.279892] pci 0000:01:00.2: [103c:3307] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.279909] pci 0000:01:00.2: reg 0x10: [io  0x1000-0x10ff]
Jul 19 10:47:00 node-2 kernel: [    1.279921] pci 0000:01:00.2: reg 0x14: [mem 0x92a8c000-0x92a8c0ff]
Jul 19 10:47:00 node-2 kernel: [    1.279934] pci 0000:01:00.2: reg 0x18: [mem 0x92900000-0x929fffff]
Jul 19 10:47:00 node-2 kernel: [    1.279946] pci 0000:01:00.2: reg 0x1c: [mem 0x92a00000-0x92a7ffff]
Jul 19 10:47:00 node-2 kernel: [    1.279958] pci 0000:01:00.2: reg 0x20: [mem 0x92a80000-0x92a87fff]
Jul 19 10:47:00 node-2 kernel: [    1.279970] pci 0000:01:00.2: reg 0x24: [mem 0x92800000-0x928fffff]
Jul 19 10:47:00 node-2 kernel: [    1.279983] pci 0000:01:00.2: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.280041] pci 0000:01:00.2: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.280098] pci 0000:01:00.4: [103c:3300] type 00 class 0x0c0300
Jul 19 10:47:00 node-2 kernel: [    1.280159] pci 0000:01:00.4: reg 0x20: [io  0x1300-0x131f]
Jul 19 10:47:00 node-2 kernel: [    1.287205] pci 0000:00:1c.2: PCI bridge to [bus 01]
Jul 19 10:47:00 node-2 kernel: [    1.287212] pci 0000:00:1c.2:   bridge window [io  0x1000-0x1fff]
Jul 19 10:47:00 node-2 kernel: [    1.287217] pci 0000:00:1c.2:   bridge window [mem 0x90000000-0x92afffff]
Jul 19 10:47:00 node-2 kernel: [    1.287285] pci 0000:00:1c.4: PCI bridge to [bus 11]
Jul 19 10:47:00 node-2 kernel: [    1.287370] pci 0000:00:1c.6: PCI bridge to [bus 12]
Jul 19 10:47:00 node-2 kernel: [    1.287438] pci 0000:00:1c.7: PCI bridge to [bus 13]
Jul 19 10:47:00 node-2 kernel: [    1.287526] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 19 10:47:00 node-2 kernel: [    1.287829] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
Jul 19 10:47:00 node-2 kernel: [    1.287925] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
Jul 19 10:47:00 node-2 kernel: [    1.288014] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
Jul 19 10:47:00 node-2 kernel: [    1.288102] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
Jul 19 10:47:00 node-2 kernel: [    1.288190] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
Jul 19 10:47:00 node-2 kernel: [    1.288279] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
Jul 19 10:47:00 node-2 kernel: [    1.288367] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
Jul 19 10:47:00 node-2 kernel: [    1.288454] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
Jul 19 10:47:00 node-2 kernel: [    1.288800] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 19 10:47:00 node-2 kernel: [    1.288808] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 19 10:47:00 node-2 kernel: [    1.288947] acpi PNP0A08:01: _OSC: platform does not support [AER]
Jul 19 10:47:00 node-2 kernel: [    1.289067] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME PCIeCapability]
Jul 19 10:47:00 node-2 kernel: [    1.289071] acpi PNP0A08:01: FADT indicates ASPM is unsupported, using BIOS configuration
Jul 19 10:47:00 node-2 kernel: [    1.289228] PCI host bridge to bus 0000:80
Jul 19 10:47:00 node-2 kernel: [    1.289233] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 19 10:47:00 node-2 kernel: [    1.289237] pci_bus 0000:80: root bus resource [io  0xa000-0xffff]
Jul 19 10:47:00 node-2 kernel: [    1.289241] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 19 10:47:00 node-2 kernel: [    1.289246] pci_bus 0000:80: root bus resource [mem 0x3a000000000-0x3bfffffffff]
Jul 19 10:47:00 node-2 kernel: [    1.289263] pci 0000:80:00.0: [8086:2f01] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.289328] pci 0000:80:00.0: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.289413] pci 0000:80:01.0: [8086:2f02] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.289477] pci 0000:80:01.0: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.289519] pci 0000:80:01.0: System wakeup disabled by ACPI
Jul 19 10:47:00 node-2 kernel: [    1.289565] pci 0000:80:01.1: [8086:2f03] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.289629] pci 0000:80:01.1: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.289675] pci 0000:80:01.1: System wakeup disabled by ACPI
Jul 19 10:47:00 node-2 kernel: [    1.289725] pci 0000:80:02.0: [8086:2f04] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.289788] pci 0000:80:02.0: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.289829] pci 0000:80:02.0: System wakeup disabled by ACPI
Jul 19 10:47:00 node-2 kernel: [    1.289872] pci 0000:80:02.1: [8086:2f05] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.289935] pci 0000:80:02.1: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.290018] pci 0000:80:02.2: [8086:2f06] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.290081] pci 0000:80:02.2: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.290122] pci 0000:80:02.2: System wakeup disabled by ACPI
Jul 19 10:47:00 node-2 kernel: [    1.290166] pci 0000:80:02.3: [8086:2f07] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.290229] pci 0000:80:02.3: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.290315] pci 0000:80:03.0: [8086:2f08] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.290379] pci 0000:80:03.0: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.290420] pci 0000:80:03.0: System wakeup disabled by ACPI
Jul 19 10:47:00 node-2 kernel: [    1.290464] pci 0000:80:03.1: [8086:2f09] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.290526] pci 0000:80:03.1: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.290602] pci 0000:80:03.2: [8086:2f0a] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.290665] pci 0000:80:03.2: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.290745] pci 0000:80:03.3: [8086:2f0b] type 01 class 0x060400
Jul 19 10:47:00 node-2 kernel: [    1.290808] pci 0000:80:03.3: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.290886] pci 0000:80:04.0: [8086:2f20] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.290900] pci 0000:80:04.0: reg 0x10: [mem 0x3bffff1c000-0x3bffff1ffff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.291022] pci 0000:80:04.1: [8086:2f21] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.291037] pci 0000:80:04.1: reg 0x10: [mem 0x3bffff18000-0x3bffff1bfff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.291160] pci 0000:80:04.2: [8086:2f22] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.291174] pci 0000:80:04.2: reg 0x10: [mem 0x3bffff14000-0x3bffff17fff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.291308] pci 0000:80:04.3: [8086:2f23] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.291322] pci 0000:80:04.3: reg 0x10: [mem 0x3bffff10000-0x3bffff13fff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.291444] pci 0000:80:04.4: [8086:2f24] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.291458] pci 0000:80:04.4: reg 0x10: [mem 0x3bffff0c000-0x3bffff0ffff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.291581] pci 0000:80:04.5: [8086:2f25] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.291594] pci 0000:80:04.5: reg 0x10: [mem 0x3bffff08000-0x3bffff0bfff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.291717] pci 0000:80:04.6: [8086:2f26] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.291731] pci 0000:80:04.6: reg 0x10: [mem 0x3bffff04000-0x3bffff07fff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.291855] pci 0000:80:04.7: [8086:2f27] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.291869] pci 0000:80:04.7: reg 0x10: [mem 0x3bffff00000-0x3bffff03fff 64bit]
Jul 19 10:47:00 node-2 kernel: [    1.291989] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.292095] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.292214] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 19 10:47:00 node-2 kernel: [    1.292319] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 19 10:47:00 node-2 kernel: [    1.292329] pci 0000:80:05.4: reg 0x10: [mem 0xc8300000-0xc8300fff]
Jul 19 10:47:00 node-2 kernel: [    1.292521] pci 0000:80:00.0: PCI bridge to [bus 8d]
Jul 19 10:47:00 node-2 kernel: [    1.292582] pci 0000:80:01.0: PCI bridge to [bus 81]
Jul 19 10:47:00 node-2 kernel: [    1.292639] pci 0000:80:01.1: PCI bridge to [bus 82]
Jul 19 10:47:00 node-2 kernel: [    1.292699] pci 0000:80:02.0: PCI bridge to [bus 83]
Jul 19 10:47:00 node-2 kernel: [    1.292756] pci 0000:80:02.1: PCI bridge to [bus 84]
Jul 19 10:47:00 node-2 kernel: [    1.292814] pci 0000:80:02.2: PCI bridge to [bus 85]
Jul 19 10:47:00 node-2 kernel: [    1.292870] pci 0000:80:02.3: PCI bridge to [bus 86]
Jul 19 10:47:00 node-2 kernel: [    1.293045] pci 0000:87:00.0: [8086:10f8] type 00 class 0x020000
Jul 19 10:47:00 node-2 kernel: [    1.293058] pci 0000:87:00.0: reg 0x10: [mem 0xc8100000-0xc81fffff]
Jul 19 10:47:00 node-2 kernel: [    1.293074] pci 0000:87:00.0: reg 0x18: [io  0xa020-0xa03f]
Jul 19 10:47:00 node-2 kernel: [    1.293083] pci 0000:87:00.0: reg 0x1c: [mem 0xc8204000-0xc8207fff]
Jul 19 10:47:00 node-2 kernel: [    1.293106] pci 0000:87:00.0: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.293151] pci 0000:87:00.0: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.293184] pci 0000:87:00.0: reg 0x184: [mem 0x3bfffe00000-0x3bfffe03fff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.293198] pci 0000:87:00.0: reg 0x190: [mem 0x3bfffd00000-0x3bfffd03fff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.293276] pci 0000:87:00.1: [8086:10f8] type 00 class 0x020000
Jul 19 10:47:00 node-2 kernel: [    1.293289] pci 0000:87:00.1: reg 0x10: [mem 0xc8000000-0xc80fffff]
Jul 19 10:47:00 node-2 kernel: [    1.293304] pci 0000:87:00.1: reg 0x18: [io  0xa000-0xa01f]
Jul 19 10:47:00 node-2 kernel: [    1.293313] pci 0000:87:00.1: reg 0x1c: [mem 0xc8200000-0xc8203fff]
Jul 19 10:47:00 node-2 kernel: [    1.293336] pci 0000:87:00.1: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.293380] pci 0000:87:00.1: PME# supported from D0 D3hot D3cold
Jul 19 10:47:00 node-2 kernel: [    1.293409] pci 0000:87:00.1: reg 0x184: [mem 0x3bfffc00000-0x3bfffc03fff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.293423] pci 0000:87:00.1: reg 0x190: [mem 0x3bfffb00000-0x3bfffb03fff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.299207] pci 0000:80:03.0: PCI bridge to [bus 87]
Jul 19 10:47:00 node-2 kernel: [    1.299213] pci 0000:80:03.0:   bridge window [io  0xa000-0xafff]
Jul 19 10:47:00 node-2 kernel: [    1.299217] pci 0000:80:03.0:   bridge window [mem 0xc8000000-0xc82fffff]
Jul 19 10:47:00 node-2 kernel: [    1.299223] pci 0000:80:03.0:   bridge window [mem 0x3bfffb00000-0x3bfffefffff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.299283] pci 0000:80:03.1: PCI bridge to [bus 8a]
Jul 19 10:47:00 node-2 kernel: [    1.299345] pci 0000:80:03.2: PCI bridge to [bus 8b]
Jul 19 10:47:00 node-2 kernel: [    1.299408] pci 0000:80:03.3: PCI bridge to [bus 8c]
Jul 19 10:47:00 node-2 kernel: [    1.299460] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 19 10:47:00 node-2 kernel: [    1.299650] ACPI: Enabled 9 GPEs in block 00 to 3F
Jul 19 10:47:00 node-2 kernel: [    1.299663] ACPI: \_SB_.UNC0: notify handler is installed
Jul 19 10:47:00 node-2 kernel: [    1.299666] ACPI: \_SB_.UNC1: notify handler is installed
Jul 19 10:47:00 node-2 kernel: [    1.299705] ACPI: \_SB_.PCI0: notify handler is installed
Jul 19 10:47:00 node-2 kernel: [    1.299787] ACPI: \_SB_.PCI1: notify handler is installed
Jul 19 10:47:00 node-2 kernel: [    1.299803] Found 4 acpi root devices
Jul 19 10:47:00 node-2 kernel: [    1.300012] vgaarb: setting as boot device: PCI:0000:01:00.1
Jul 19 10:47:00 node-2 kernel: [    1.300017] vgaarb: device added: PCI:0000:01:00.1,decodes=io+mem,owns=io+mem,locks=none
Jul 19 10:47:00 node-2 kernel: [    1.300027] vgaarb: loaded
Jul 19 10:47:00 node-2 kernel: [    1.300030] vgaarb: bridge control possible 0000:01:00.1
Jul 19 10:47:00 node-2 kernel: [    1.300297] SCSI subsystem initialized
Jul 19 10:47:00 node-2 kernel: [    1.300485] libata version 3.00 loaded.
Jul 19 10:47:00 node-2 kernel: [    1.300512] ACPI: bus type USB registered
Jul 19 10:47:00 node-2 kernel: [    1.300552] usbcore: registered new interface driver usbfs
Jul 19 10:47:00 node-2 kernel: [    1.300564] usbcore: registered new interface driver hub
Jul 19 10:47:00 node-2 kernel: [    1.300607] usbcore: registered new device driver usb
Jul 19 10:47:00 node-2 kernel: [    1.301083] PCI: Using ACPI for IRQ routing
Jul 19 10:47:00 node-2 kernel: [    1.306748] PCI: pci_cache_line_size set to 64 bytes
Jul 19 10:47:00 node-2 kernel: [    1.307116] e820: reserve RAM buffer [mem 0x00094000-0x0009ffff]
Jul 19 10:47:00 node-2 kernel: [    1.307119] e820: reserve RAM buffer [mem 0x5ac9d000-0x5bffffff]
Jul 19 10:47:00 node-2 kernel: [    1.307122] e820: reserve RAM buffer [mem 0x790ff000-0x7bffffff]
Jul 19 10:47:00 node-2 kernel: [    1.307124] e820: reserve RAM buffer [mem 0x7b800000-0x7bffffff]
Jul 19 10:47:00 node-2 kernel: [    1.307293] NetLabel: Initializing
Jul 19 10:47:00 node-2 kernel: [    1.307298] NetLabel:  domain hash size = 128
Jul 19 10:47:00 node-2 kernel: [    1.307300] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 19 10:47:00 node-2 kernel: [    1.307325] NetLabel:  unlabeled traffic allowed by default
Jul 19 10:47:00 node-2 kernel: [    1.307439] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 19 10:47:00 node-2 kernel: [    1.307450] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 19 10:47:00 node-2 kernel: [    1.309661] Switched to clocksource hpet
Jul 19 10:47:00 node-2 kernel: [    1.318634] AppArmor: AppArmor Filesystem Enabled
Jul 19 10:47:00 node-2 kernel: [    1.318660] pnp: PnP ACPI init
Jul 19 10:47:00 node-2 kernel: [    1.318680] ACPI: bus type PNP registered
Jul 19 10:47:00 node-2 kernel: [    1.318972] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 19 10:47:00 node-2 kernel: [    1.319215] pnp 00:01: [dma 4]
Jul 19 10:47:00 node-2 kernel: [    1.319251] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 19 10:47:00 node-2 kernel: [    1.319297] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 19 10:47:00 node-2 kernel: [    1.319347] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 19 10:47:00 node-2 kernel: [    1.319383] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 19 10:47:00 node-2 kernel: [    1.319473] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 19 10:47:00 node-2 kernel: [    1.319635] system 00:06: [io  0x0500-0x053f] has been reserved
Jul 19 10:47:00 node-2 kernel: [    1.319640] system 00:06: [io  0x0400-0x047f] has been reserved
Jul 19 10:47:00 node-2 kernel: [    1.319645] system 00:06: [io  0x0540-0x057f] has been reserved
Jul 19 10:47:00 node-2 kernel: [    1.319649] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 19 10:47:00 node-2 kernel: [    1.319653] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 19 10:47:00 node-2 kernel: [    1.319657] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 19 10:47:00 node-2 kernel: [    1.319663] system 00:06: [mem 0xfed1c000-0xfed3ffff] has been reserved
Jul 19 10:47:00 node-2 kernel: [    1.319667] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 19 10:47:00 node-2 kernel: [    1.319672] system 00:06: [mem 0xff000000-0xffffffff] could not be reserved
Jul 19 10:47:00 node-2 kernel: [    1.319677] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 19 10:47:00 node-2 kernel: [    1.319681] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 19 10:47:00 node-2 kernel: [    1.319685] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 19 10:47:00 node-2 kernel: [    1.319690] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 19 10:47:00 node-2 kernel: [    1.319695] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 19 10:47:00 node-2 kernel: [    1.319740] pnp 00:07: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 19 10:47:00 node-2 kernel: [    1.319805] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 19 10:47:00 node-2 kernel: [    1.319850] pnp 00:09: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 19 10:47:00 node-2 kernel: [    1.320015] pnp: PnP ACPI: found 10 devices
Jul 19 10:47:00 node-2 kernel: [    1.320019] ACPI: bus type PNP unregistered
Jul 19 10:47:00 node-2 kernel: [    1.327569] pci 0000:00:02.0: BAR 14: assigned [mem 0x92b00000-0x92bfffff]
Jul 19 10:47:00 node-2 kernel: [    1.327577] pci 0000:00:02.2: BAR 15: assigned [mem 0x92c00000-0x92cfffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.327583] pci 0000:00:1c.2: BAR 15: assigned [mem 0x92d00000-0x92dfffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.327589] pci 0000:00:01.0: PCI bridge to [bus 02]
Jul 19 10:47:00 node-2 kernel: [    1.327600] pci 0000:00:01.1: PCI bridge to [bus 05]
Jul 19 10:47:00 node-2 kernel: [    1.327612] pci 0000:06:00.0: BAR 6: assigned [mem 0x95080000-0x950fffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.327618] pci 0000:06:00.1: BAR 6: assigned [mem 0x92b00000-0x92b7ffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.327622] pci 0000:00:02.0: PCI bridge to [bus 06]
Jul 19 10:47:00 node-2 kernel: [    1.327628] pci 0000:00:02.0:   bridge window [mem 0x92b00000-0x92bfffff]
Jul 19 10:47:00 node-2 kernel: [    1.327634] pci 0000:00:02.0:   bridge window [mem 0x93000000-0x950fffff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.327641] pci 0000:00:02.1: PCI bridge to [bus 0b]
Jul 19 10:47:00 node-2 kernel: [    1.327653] pci 0000:07:00.0: BAR 6: assigned [mem 0x92c00000-0x92c7ffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.327657] pci 0000:00:02.2: PCI bridge to [bus 07]
Jul 19 10:47:00 node-2 kernel: [    1.327662] pci 0000:00:02.2:   bridge window [io  0x3000-0x3fff]
Jul 19 10:47:00 node-2 kernel: [    1.327668] pci 0000:00:02.2:   bridge window [mem 0x95400000-0x955fffff]
Jul 19 10:47:00 node-2 kernel: [    1.327674] pci 0000:00:02.2:   bridge window [mem 0x92c00000-0x92cfffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.327681] pci 0000:00:02.3: PCI bridge to [bus 0c]
Jul 19 10:47:00 node-2 kernel: [    1.327693] pci 0000:08:00.0: BAR 6: assigned [mem 0x95380000-0x953fffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.327699] pci 0000:08:00.1: BAR 6: can't assign mem pref (size 0x80000)
Jul 19 10:47:00 node-2 kernel: [    1.327703] pci 0000:00:03.0: PCI bridge to [bus 08]
Jul 19 10:47:00 node-2 kernel: [    1.327708] pci 0000:00:03.0:   bridge window [io  0x2000-0x2fff]
Jul 19 10:47:00 node-2 kernel: [    1.327714] pci 0000:00:03.0:   bridge window [mem 0x95100000-0x953fffff]
Jul 19 10:47:00 node-2 kernel: [    1.327720] pci 0000:00:03.0:   bridge window [mem 0x39fffb00000-0x39fffefffff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.327727] pci 0000:00:03.1: PCI bridge to [bus 0d]
Jul 19 10:47:00 node-2 kernel: [    1.327738] pci 0000:00:03.2: PCI bridge to [bus 0e]
Jul 19 10:47:00 node-2 kernel: [    1.327748] pci 0000:00:03.3: PCI bridge to [bus 0f]
Jul 19 10:47:00 node-2 kernel: [    1.327759] pci 0000:00:1c.0: PCI bridge to [bus 10]
Jul 19 10:47:00 node-2 kernel: [    1.327774] pci 0000:01:00.2: BAR 6: assigned [mem 0x92d00000-0x92d0ffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.327779] pci 0000:00:1c.2: PCI bridge to [bus 01]
Jul 19 10:47:00 node-2 kernel: [    1.327783] pci 0000:00:1c.2:   bridge window [io  0x1000-0x1fff]
Jul 19 10:47:00 node-2 kernel: [    1.327791] pci 0000:00:1c.2:   bridge window [mem 0x90000000-0x92afffff]
Jul 19 10:47:00 node-2 kernel: [    1.327797] pci 0000:00:1c.2:   bridge window [mem 0x92d00000-0x92dfffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.327805] pci 0000:00:1c.4: PCI bridge to [bus 11]
Jul 19 10:47:00 node-2 kernel: [    1.327819] pci 0000:00:1c.6: PCI bridge to [bus 12]
Jul 19 10:47:00 node-2 kernel: [    1.327832] pci 0000:00:1c.7: PCI bridge to [bus 13]
Jul 19 10:47:00 node-2 kernel: [    1.327847] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 19 10:47:00 node-2 kernel: [    1.327850] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 19 10:47:00 node-2 kernel: [    1.327852] pci_bus 0000:00: resource 6 [io  0x03b0-0x03bb]
Jul 19 10:47:00 node-2 kernel: [    1.327855] pci_bus 0000:00: resource 7 [io  0x03c0-0x03df]
Jul 19 10:47:00 node-2 kernel: [    1.327858] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 19 10:47:00 node-2 kernel: [    1.327860] pci_bus 0000:00: resource 9 [io  0x1000-0x9fff]
Jul 19 10:47:00 node-2 kernel: [    1.327863] pci_bus 0000:00: resource 10 [mem 0x90000000-0xc7ffbfff]
Jul 19 10:47:00 node-2 kernel: [    1.327865] pci_bus 0000:00: resource 11 [mem 0x38000000000-0x39fffffffff]
Jul 19 10:47:00 node-2 kernel: [    1.327869] pci_bus 0000:06: resource 1 [mem 0x92b00000-0x92bfffff]
Jul 19 10:47:00 node-2 kernel: [    1.327871] pci_bus 0000:06: resource 2 [mem 0x93000000-0x950fffff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.327874] pci_bus 0000:07: resource 0 [io  0x3000-0x3fff]
Jul 19 10:47:00 node-2 kernel: [    1.327877] pci_bus 0000:07: resource 1 [mem 0x95400000-0x955fffff]
Jul 19 10:47:00 node-2 kernel: [    1.327879] pci_bus 0000:07: resource 2 [mem 0x92c00000-0x92cfffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.327882] pci_bus 0000:08: resource 0 [io  0x2000-0x2fff]
Jul 19 10:47:00 node-2 kernel: [    1.327885] pci_bus 0000:08: resource 1 [mem 0x95100000-0x953fffff]
Jul 19 10:47:00 node-2 kernel: [    1.327887] pci_bus 0000:08: resource 2 [mem 0x39fffb00000-0x39fffefffff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.327891] pci_bus 0000:01: resource 0 [io  0x1000-0x1fff]
Jul 19 10:47:00 node-2 kernel: [    1.327893] pci_bus 0000:01: resource 1 [mem 0x90000000-0x92afffff]
Jul 19 10:47:00 node-2 kernel: [    1.327896] pci_bus 0000:01: resource 2 [mem 0x92d00000-0x92dfffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.327961] pci 0000:80:00.0: PCI bridge to [bus 8d]
Jul 19 10:47:00 node-2 kernel: [    1.327972] pci 0000:80:01.0: PCI bridge to [bus 81]
Jul 19 10:47:00 node-2 kernel: [    1.327983] pci 0000:80:01.1: PCI bridge to [bus 82]
Jul 19 10:47:00 node-2 kernel: [    1.327994] pci 0000:80:02.0: PCI bridge to [bus 83]
Jul 19 10:47:00 node-2 kernel: [    1.328005] pci 0000:80:02.1: PCI bridge to [bus 84]
Jul 19 10:47:00 node-2 kernel: [    1.328016] pci 0000:80:02.2: PCI bridge to [bus 85]
Jul 19 10:47:00 node-2 kernel: [    1.328027] pci 0000:80:02.3: PCI bridge to [bus 86]
Jul 19 10:47:00 node-2 kernel: [    1.328039] pci 0000:87:00.0: BAR 6: assigned [mem 0xc8280000-0xc82fffff pref]
Jul 19 10:47:00 node-2 kernel: [    1.328044] pci 0000:87:00.1: BAR 6: can't assign mem pref (size 0x80000)
Jul 19 10:47:00 node-2 kernel: [    1.328048] pci 0000:80:03.0: PCI bridge to [bus 87]
Jul 19 10:47:00 node-2 kernel: [    1.328053] pci 0000:80:03.0:   bridge window [io  0xa000-0xafff]
Jul 19 10:47:00 node-2 kernel: [    1.328059] pci 0000:80:03.0:   bridge window [mem 0xc8000000-0xc82fffff]
Jul 19 10:47:00 node-2 kernel: [    1.328065] pci 0000:80:03.0:   bridge window [mem 0x3bfffb00000-0x3bfffefffff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.328072] pci 0000:80:03.1: PCI bridge to [bus 8a]
Jul 19 10:47:00 node-2 kernel: [    1.328083] pci 0000:80:03.2: PCI bridge to [bus 8b]
Jul 19 10:47:00 node-2 kernel: [    1.328094] pci 0000:80:03.3: PCI bridge to [bus 8c]
Jul 19 10:47:00 node-2 kernel: [    1.328106] pci_bus 0000:80: resource 4 [io  0xa000-0xffff]
Jul 19 10:47:00 node-2 kernel: [    1.328108] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 19 10:47:00 node-2 kernel: [    1.328111] pci_bus 0000:80: resource 6 [mem 0x3a000000000-0x3bfffffffff]
Jul 19 10:47:00 node-2 kernel: [    1.328114] pci_bus 0000:87: resource 0 [io  0xa000-0xafff]
Jul 19 10:47:00 node-2 kernel: [    1.328116] pci_bus 0000:87: resource 1 [mem 0xc8000000-0xc82fffff]
Jul 19 10:47:00 node-2 kernel: [    1.328119] pci_bus 0000:87: resource 2 [mem 0x3bfffb00000-0x3bfffefffff 64bit pref]
Jul 19 10:47:00 node-2 kernel: [    1.328212] NET: Registered protocol family 2
Jul 19 10:47:00 node-2 kernel: [    1.329156] TCP established hash table entries: 524288 (order: 10, 4194304 bytes)
Jul 19 10:47:00 node-2 kernel: [    1.330381] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 19 10:47:00 node-2 kernel: [    1.330624] TCP: Hash tables configured (established 524288 bind 65536)
Jul 19 10:47:00 node-2 kernel: [    1.330681] TCP: reno registered
Jul 19 10:47:00 node-2 kernel: [    1.330929] UDP hash table entries: 65536 (order: 9, 2097152 bytes)
Jul 19 10:47:00 node-2 kernel: [    1.331658] UDP-Lite hash table entries: 65536 (order: 9, 2097152 bytes)
Jul 19 10:47:00 node-2 kernel: [    1.332437] NET: Registered protocol family 1
Jul 19 10:47:00 node-2 kernel: [    1.565844] pci 0000:01:00.1: Video device with shadowed ROM
Jul 19 10:47:00 node-2 kernel: [    1.566211] PCI: CLS 64 bytes, default 64
Jul 19 10:47:00 node-2 kernel: [    1.566293] Trying to unpack rootfs image as initramfs...
Jul 19 10:47:00 node-2 kernel: [    1.991990] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 19 10:47:00 node-2 kernel: [    1.992053] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 19 10:47:00 node-2 kernel: [    1.992056] software IO TLB [mem 0x750ff000-0x790ff000] (64MB) mapped at [ffff8800750ff000-ffff8800790fefff]
Jul 19 10:47:00 node-2 kernel: [    1.993482] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993495] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993504] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993517] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993539] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993553] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993568] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993582] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993596] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993610] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993625] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993644] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993662] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993681] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993698] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993715] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993732] microcode: CPU16 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993748] microcode: CPU17 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993765] microcode: CPU18 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993782] microcode: CPU19 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993799] microcode: CPU20 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993816] microcode: CPU21 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993833] microcode: CPU22 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993854] microcode: CPU23 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993869] microcode: CPU24 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993881] microcode: CPU25 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993892] microcode: CPU26 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993903] microcode: CPU27 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993914] microcode: CPU28 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993926] microcode: CPU29 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993938] microcode: CPU30 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993950] microcode: CPU31 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993962] microcode: CPU32 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993974] microcode: CPU33 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.993986] microcode: CPU34 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.994002] microcode: CPU35 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.994015] microcode: CPU36 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.994029] microcode: CPU37 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.994043] microcode: CPU38 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.994057] microcode: CPU39 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.994071] microcode: CPU40 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.994085] microcode: CPU41 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.994099] microcode: CPU42 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.994112] microcode: CPU43 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.994126] microcode: CPU44 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.994140] microcode: CPU45 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.994154] microcode: CPU46 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.994171] microcode: CPU47 sig=0x306f2, pf=0x1, revision=0x35
Jul 19 10:47:00 node-2 kernel: [    1.994289] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 19 10:47:00 node-2 kernel: [    1.994296] Scanning for low memory corruption every 60 seconds
Jul 19 10:47:00 node-2 kernel: [    1.995370] Initialise system trusted keyring
Jul 19 10:47:00 node-2 kernel: [    1.995504] audit: initializing netlink socket (disabled)
Jul 19 10:47:00 node-2 kernel: [    1.995541] type=2000 audit(1468925181.772:1): initialized
Jul 19 10:47:00 node-2 kernel: [    2.049424] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 19 10:47:00 node-2 kernel: [    2.055581] zbud: loaded
Jul 19 10:47:00 node-2 kernel: [    2.055876] VFS: Disk quotas dquot_6.5.2
Jul 19 10:47:00 node-2 kernel: [    2.055985] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 19 10:47:00 node-2 kernel: [    2.056937] fuse init (API version 7.22)
Jul 19 10:47:00 node-2 kernel: [    2.057078] msgmni has been set to 32768
Jul 19 10:47:00 node-2 kernel: [    2.057203] Key type big_key registered
Jul 19 10:47:00 node-2 kernel: [    2.058258] Key type asymmetric registered
Jul 19 10:47:00 node-2 kernel: [    2.058263] Asymmetric key parser 'x509' registered
Jul 19 10:47:00 node-2 kernel: [    2.058318] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 19 10:47:00 node-2 kernel: [    2.058506] io scheduler noop registered
Jul 19 10:47:00 node-2 kernel: [    2.058510] io scheduler deadline registered (default)
Jul 19 10:47:00 node-2 kernel: [    2.058564] io scheduler cfq registered
Jul 19 10:47:00 node-2 kernel: [    2.059449] pcieport 0000:00:01.0: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.059457] pcieport 0000:00:01.0: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.059529] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.059852] pcieport 0000:00:01.1: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.059858] pcieport 0000:00:01.1: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.059899] pcieport 0000:00:01.1: irq 91 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.060189] pcieport 0000:00:02.0: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.060194] pcieport 0000:00:02.0: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.060226] pcieport 0000:00:02.0: irq 92 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.060517] pcieport 0000:00:02.1: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.060522] pcieport 0000:00:02.1: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.060553] pcieport 0000:00:02.1: irq 93 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.060841] pcieport 0000:00:02.2: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.060845] pcieport 0000:00:02.2: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.060877] pcieport 0000:00:02.2: irq 94 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.061165] pcieport 0000:00:02.3: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.061170] pcieport 0000:00:02.3: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.061201] pcieport 0000:00:02.3: irq 95 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.061481] pcieport 0000:00:03.0: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.061486] pcieport 0000:00:03.0: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.061545] pcieport 0000:00:03.0: irq 96 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.061833] pcieport 0000:00:03.1: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.061838] pcieport 0000:00:03.1: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.061870] pcieport 0000:00:03.1: irq 97 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.062147] pcieport 0000:00:03.2: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.062152] pcieport 0000:00:03.2: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.062182] pcieport 0000:00:03.2: irq 98 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.062464] pcieport 0000:00:03.3: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.062469] pcieport 0000:00:03.3: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.062499] pcieport 0000:00:03.3: irq 99 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.062842] pcieport 0000:00:1c.0: irq 100 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.062961] pcieport 0000:00:1c.2: irq 101 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.063290] pcieport 0000:00:1c.4: irq 102 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.063612] pcieport 0000:00:1c.6: irq 103 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.063939] pcieport 0000:00:1c.7: irq 104 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.064084] pcieport 0000:80:00.0: irq 105 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.064244] pcieport 0000:80:01.0: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.064250] pcieport 0000:80:01.0: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.064284] pcieport 0000:80:01.0: irq 106 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.064382] pcieport 0000:80:01.1: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.064386] pcieport 0000:80:01.1: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.064417] pcieport 0000:80:01.1: irq 107 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.064514] pcieport 0000:80:02.0: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.064518] pcieport 0000:80:02.0: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.064549] pcieport 0000:80:02.0: irq 108 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.064638] pcieport 0000:80:02.1: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.064642] pcieport 0000:80:02.1: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.064680] pcieport 0000:80:02.1: irq 109 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.064773] pcieport 0000:80:02.2: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.064777] pcieport 0000:80:02.2: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.064808] pcieport 0000:80:02.2: irq 110 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.064897] pcieport 0000:80:02.3: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.064901] pcieport 0000:80:02.3: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.064931] pcieport 0000:80:02.3: irq 111 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.065024] pcieport 0000:80:03.0: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.065028] pcieport 0000:80:03.0: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.065060] pcieport 0000:80:03.0: irq 112 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.065153] pcieport 0000:80:03.1: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.065158] pcieport 0000:80:03.1: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.065188] pcieport 0000:80:03.1: irq 113 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.065281] pcieport 0000:80:03.2: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.065285] pcieport 0000:80:03.2: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.065315] pcieport 0000:80:03.2: irq 114 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.065407] pcieport 0000:80:03.3: can't derive routing for PCI INT A
Jul 19 10:47:00 node-2 kernel: [    2.065411] pcieport 0000:80:03.3: PCI INT A: no GSI
Jul 19 10:47:00 node-2 kernel: [    2.065442] pcieport 0000:80:03.3: irq 115 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    2.065550] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065558] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.065581] pcieport 0000:00:01.1: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065587] pcie_pme 0000:00:01.1:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.065619] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065624] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065628] pci 0000:06:00.1: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065634] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.065661] pcieport 0000:00:02.1: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065667] pcie_pme 0000:00:02.1:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.065690] pcieport 0000:00:02.2: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065700] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065706] pcie_pme 0000:00:02.2:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.065726] pcieport 0000:00:02.3: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065732] pcie_pme 0000:00:02.3:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.065754] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065758] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065762] pci 0000:08:00.1: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065768] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.065796] pcieport 0000:00:03.1: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065802] pcie_pme 0000:00:03.1:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.065825] pcieport 0000:00:03.2: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065831] pcie_pme 0000:00:03.2:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.065851] pcieport 0000:00:03.3: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065857] pcie_pme 0000:00:03.3:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.065879] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065886] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.065917] pcieport 0000:00:1c.2: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065927] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065930] pci 0000:01:00.1: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065934] pci 0000:01:00.2: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065938] pci 0000:01:00.4: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065945] pcie_pme 0000:00:1c.2:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.065968] pcieport 0000:00:1c.4: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.065974] pcie_pme 0000:00:1c.4:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.065995] pcieport 0000:00:1c.6: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.066001] pcie_pme 0000:00:1c.6:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.066022] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.066029] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.066049] pcieport 0000:80:00.0: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.066055] pcie_pme 0000:80:00.0:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.066076] pcieport 0000:80:01.0: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.066081] pcie_pme 0000:80:01.0:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.066107] pcieport 0000:80:01.1: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.066113] pcie_pme 0000:80:01.1:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.066132] pcieport 0000:80:02.0: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.066138] pcie_pme 0000:80:02.0:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.066167] pcieport 0000:80:02.1: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.066173] pcie_pme 0000:80:02.1:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.066195] pcieport 0000:80:02.2: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.066201] pcie_pme 0000:80:02.2:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.066227] pcieport 0000:80:02.3: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.066233] pcie_pme 0000:80:02.3:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.066253] pcieport 0000:80:03.0: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.066258] pci 0000:87:00.0: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.066262] pci 0000:87:00.1: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.066268] pcie_pme 0000:80:03.0:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.066289] pcieport 0000:80:03.1: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.066295] pcie_pme 0000:80:03.1:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.066316] pcieport 0000:80:03.2: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.066322] pcie_pme 0000:80:03.2:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.066344] pcieport 0000:80:03.3: Signaling PME through PCIe PME interrupt
Jul 19 10:47:00 node-2 kernel: [    2.066349] pcie_pme 0000:80:03.3:pcie01: service driver pcie_pme loaded
Jul 19 10:47:00 node-2 kernel: [    2.066411] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 19 10:47:00 node-2 kernel: [    2.066427] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 19 10:47:00 node-2 kernel: [    2.066437] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 19 10:47:00 node-2 kernel: [    2.066462] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 19 10:47:00 node-2 kernel: [    2.066567] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 19 10:47:00 node-2 kernel: [    2.066571] vesafb: scrolling: redraw
Jul 19 10:47:00 node-2 kernel: [    2.066575] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 19 10:47:00 node-2 kernel: [    2.287773] vesafb: framebuffer at 0x91000000, mapped to 0xffffc9001ce80000, using 1216k, total 1216k
Jul 19 10:47:00 node-2 kernel: [    2.300480] Console: switching to colour frame buffer device 80x30
Jul 19 10:47:00 node-2 kernel: [    2.313669] fb0: VESA VGA frame buffer device
Jul 19 10:47:00 node-2 kernel: [    2.313943] intel_idle: MWAIT substates: 0x2120
Jul 19 10:47:00 node-2 kernel: [    2.313945] intel_idle: v0.4 model 0x3F
Jul 19 10:47:00 node-2 kernel: [    2.313946] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 19 10:47:00 node-2 kernel: [    2.314847] ipmi message handler version 39.2
Jul 19 10:47:00 node-2 kernel: [    2.315206] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
Jul 19 10:47:00 node-2 kernel: [    2.315632] ACPI: Power Button [PWRF]
Jul 19 10:47:00 node-2 kernel: [    2.321606] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 19 10:47:00 node-2 kernel: [    2.332790] pstore: Registered erst as persistent store backend
Jul 19 10:47:00 node-2 kernel: [    2.339095] GHES: APEI firmware first mode is enabled by WHEA _OSC.
Jul 19 10:47:00 node-2 kernel: [    2.345696] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 19 10:47:00 node-2 kernel: [    2.372844] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 19 10:47:00 node-2 kernel: [    2.407295] 00:09: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 19 10:47:00 node-2 kernel: [    2.423740] Linux agpgart interface v0.103
Jul 19 10:47:00 node-2 kernel: [    2.433533] brd: module loaded
Jul 19 10:47:00 node-2 kernel: [    2.442437] loop: module loaded
Jul 19 10:47:00 node-2 kernel: [    2.450574] libphy: Fixed MDIO Bus: probed
Jul 19 10:47:00 node-2 kernel: [    2.458743] tun: Universal TUN/TAP device driver, 1.6
Jul 19 10:47:00 node-2 kernel: [    2.466785] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 19 10:47:00 node-2 kernel: [    2.474928] PPP generic driver version 2.4.2
Jul 19 10:47:00 node-2 kernel: [    2.483142] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 19 10:47:00 node-2 kernel: [    2.491577] ehci-pci: EHCI PCI platform driver
Jul 19 10:47:00 node-2 kernel: [    2.500324] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 19 10:47:00 node-2 kernel: [    2.508580] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 19 10:47:00 node-2 kernel: [    2.524901] ehci-pci 0000:00:1a.0: debug port 2
Jul 19 10:47:00 node-2 kernel: [    2.536961] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 19 10:47:00 node-2 kernel: [    2.537010] ehci-pci 0000:00:1a.0: irq 18, io mem 0x95601000
Jul 19 10:47:00 node-2 kernel: [    2.553425] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 19 10:47:00 node-2 kernel: [    2.561653] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 19 10:47:00 node-2 kernel: [    2.569705] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 19 10:47:00 node-2 kernel: [    2.585258] usb usb1: Product: EHCI Host Controller
Jul 19 10:47:00 node-2 kernel: [    2.592998] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 19 10:47:00 node-2 kernel: [    2.600816] usb usb1: SerialNumber: 0000:00:1a.0
Jul 19 10:47:00 node-2 kernel: [    2.608766] hub 1-0:1.0: USB hub found
Jul 19 10:47:00 node-2 kernel: [    2.616230] hub 1-0:1.0: 2 ports detected
Jul 19 10:47:00 node-2 kernel: [    2.624074] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 19 10:47:00 node-2 kernel: [    2.631380] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 19 10:47:00 node-2 kernel: [    2.645684] ehci-pci 0000:00:1d.0: debug port 2
Jul 19 10:47:00 node-2 kernel: [    2.656751] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 19 10:47:00 node-2 kernel: [    2.656759] ehci-pci 0000:00:1d.0: irq 18, io mem 0x95600000
Jul 19 10:47:00 node-2 kernel: [    2.673456] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 19 10:47:00 node-2 kernel: [    2.680358] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 19 10:47:00 node-2 kernel: [    2.687692] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 19 10:47:00 node-2 kernel: [    2.701744] usb usb2: Product: EHCI Host Controller
Jul 19 10:47:00 node-2 kernel: [    2.709031] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 19 10:47:00 node-2 kernel: [    2.716387] usb usb2: SerialNumber: 0000:00:1d.0
Jul 19 10:47:00 node-2 kernel: [    2.723854] hub 2-0:1.0: USB hub found
Jul 19 10:47:00 node-2 kernel: [    2.730942] hub 2-0:1.0: 2 ports detected
Jul 19 10:47:00 node-2 kernel: [    2.738083] ehci-platform: EHCI generic platform driver
Jul 19 10:47:00 node-2 kernel: [    2.745056] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 19 10:47:00 node-2 kernel: [    2.752200] ohci-pci: OHCI PCI platform driver
Jul 19 10:47:00 node-2 kernel: [    2.759287] ohci-platform: OHCI generic platform driver
Jul 19 10:47:00 node-2 kernel: [    2.766256] uhci_hcd: USB Universal Host Controller Interface driver
Jul 19 10:47:00 node-2 kernel: [    2.773534] uhci_hcd 0000:01:00.4: UHCI Host Controller
Jul 19 10:47:00 node-2 kernel: [    2.780640] uhci_hcd 0000:01:00.4: new USB bus registered, assigned bus number 3
Jul 19 10:47:00 node-2 kernel: [    2.794871] uhci_hcd 0000:01:00.4: port count misdetected? forcing to 2 ports
Jul 19 10:47:00 node-2 kernel: [    2.802363] uhci_hcd 0000:01:00.4: irq 19, io base 0x00001300
Jul 19 10:47:00 node-2 kernel: [    2.809599] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
Jul 19 10:47:00 node-2 kernel: [    2.817255] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 19 10:47:00 node-2 kernel: [    2.831838] usb usb3: Product: UHCI Host Controller
Jul 19 10:47:00 node-2 kernel: [    2.839361] usb usb3: Manufacturer: Linux 3.13.0-92-generic uhci_hcd
Jul 19 10:47:00 node-2 kernel: [    2.847033] usb usb3: SerialNumber: 0000:01:00.4
Jul 19 10:47:00 node-2 kernel: [    2.854892] hub 3-0:1.0: USB hub found
Jul 19 10:47:00 node-2 kernel: [    2.862335] hub 3-0:1.0: 2 ports detected
Jul 19 10:47:00 node-2 kernel: [    2.870213] xhci_hcd 0000:00:14.0: xHCI Host Controller
Jul 19 10:47:00 node-2 kernel: [    2.877543] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
Jul 19 10:47:00 node-2 kernel: [    2.893480] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
Jul 19 10:47:00 node-2 kernel: [    2.893539] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
Jul 19 10:47:00 node-2 kernel: [    2.901305] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 19 10:47:00 node-2 kernel: [    2.916332] usb usb4: Product: xHCI Host Controller
Jul 19 10:47:00 node-2 kernel: [    2.923910] usb usb4: Manufacturer: Linux 3.13.0-92-generic xhci_hcd
Jul 19 10:47:00 node-2 kernel: [    2.931640] usb usb4: SerialNumber: 0000:00:14.0
Jul 19 10:47:00 node-2 kernel: [    2.939685] hub 4-0:1.0: USB hub found
Jul 19 10:47:00 node-2 kernel: [    2.947274] hub 4-0:1.0: 15 ports detected
Jul 19 10:47:00 node-2 kernel: [    2.955508] xhci_hcd 0000:00:14.0: xHCI Host Controller
Jul 19 10:47:00 node-2 kernel: [    2.963161] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 5
Jul 19 10:47:00 node-2 kernel: [    2.965464] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 19 10:47:00 node-2 kernel: [    2.986311] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003
Jul 19 10:47:00 node-2 kernel: [    2.990210] tsc: Refined TSC clocksource calibration: 2497.074 MHz
Jul 19 10:47:00 node-2 kernel: [    3.002274] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 19 10:47:00 node-2 kernel: [    3.018254] usb usb5: Product: xHCI Host Controller
Jul 19 10:47:00 node-2 kernel: [    3.026151] usb usb5: Manufacturer: Linux 3.13.0-92-generic xhci_hcd
Jul 19 10:47:00 node-2 kernel: [    3.034246] usb usb5: SerialNumber: 0000:00:14.0
Jul 19 10:47:00 node-2 kernel: [    3.042155] hub 5-0:1.0: USB hub found
Jul 19 10:47:00 node-2 kernel: [    3.049950] hub 5-0:1.0: 6 ports detected
Jul 19 10:47:00 node-2 kernel: [    3.061534] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 19 10:47:00 node-2 kernel: [    3.071006] serio: i8042 KBD port at 0x60,0x64 irq 1
Jul 19 10:47:00 node-2 kernel: [    3.078664] serio: i8042 AUX port at 0x60,0x64 irq 12
Jul 19 10:47:00 node-2 kernel: [    3.086447] mousedev: PS/2 mouse device common for all mice
Jul 19 10:47:00 node-2 kernel: [    3.094209] rtc_cmos 00:02: RTC can wake from S4
Jul 19 10:47:00 node-2 kernel: [    3.102101] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 19 10:47:00 node-2 kernel: [    3.109721] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 19 10:47:00 node-2 kernel: [    3.118289] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 19 10:47:00 node-2 kernel: [    3.118290] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 19 10:47:00 node-2 kernel: [    3.119426] hub 1-1:1.0: USB hub found
Jul 19 10:47:00 node-2 kernel: [    3.119667] hub 1-1:1.0: 6 ports detected
Jul 19 10:47:00 node-2 kernel: [    3.155117] device-mapper: uevent: version 1.0.3
Jul 19 10:47:00 node-2 kernel: [    3.162629] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 19 10:47:00 node-2 kernel: [    3.177589] ledtrig-cpu: registered to indicate activity on CPUs
Jul 19 10:47:00 node-2 kernel: [    3.186079] TCP: cubic registered
Jul 19 10:47:00 node-2 kernel: [    3.194084] NET: Registered protocol family 10
Jul 19 10:47:00 node-2 kernel: [    3.202225] NET: Registered protocol family 17
Jul 19 10:47:00 node-2 kernel: [    3.209618] Key type dns_resolver registered
Jul 19 10:47:00 node-2 kernel: [    3.218566] Loading compiled-in X.509 certificates
Jul 19 10:47:00 node-2 kernel: [    3.227244] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 19 10:47:00 node-2 kernel: [    3.233467] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 19 10:47:00 node-2 kernel: [    3.249106] registered taskstats version 1
Jul 19 10:47:00 node-2 kernel: [    3.264732] Key type trusted registered
Jul 19 10:47:00 node-2 kernel: [    3.277621] Key type encrypted registered
Jul 19 10:47:00 node-2 kernel: [    3.284826] AppArmor: AppArmor sha1 policy hashing enabled
Jul 19 10:47:00 node-2 kernel: [    3.292121] IMA: No TPM chip found, activating TPM-bypass!
Jul 19 10:47:00 node-2 kernel: [    3.301827] regulator-dummy: disabling
Jul 19 10:47:00 node-2 kernel: [    3.309193]   Magic number: 8:728:780
Jul 19 10:47:00 node-2 kernel: [    3.316789] memory memory482: hash matches
Jul 19 10:47:00 node-2 kernel: [    3.324295] rtc_cmos 00:02: setting system clock to 2016-07-19 10:46:23 UTC (1468925183)
Jul 19 10:47:00 node-2 kernel: [    3.339558] pcc-cpufreq: (v1.10.00) driver loaded with frequency limits: 1200 MHz, 2500 MHz
Jul 19 10:47:00 node-2 kernel: [    3.358613] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 19 10:47:00 node-2 kernel: [    3.366392] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 19 10:47:00 node-2 kernel: [    3.366394] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 19 10:47:00 node-2 kernel: [    3.367382] hub 2-1:1.0: USB hub found
Jul 19 10:47:00 node-2 kernel: [    3.367644] hub 2-1:1.0: 8 ports detected
Jul 19 10:47:00 node-2 kernel: [    3.397017] EDD information not available.
Jul 19 10:47:00 node-2 kernel: [    3.404201] PM: Hibernation image not present or could not be loaded.
Jul 19 10:47:00 node-2 kernel: [    3.405472] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 19 10:47:00 node-2 kernel: [    3.420533] Write protecting the kernel read-only data: 12288k
Jul 19 10:47:00 node-2 kernel: [    3.429148] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 19 10:47:00 node-2 kernel: [    3.446115] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 19 10:47:00 node-2 kernel: [    3.489556] device-mapper: multipath: version 1.6.0 loaded
Jul 19 10:47:00 node-2 kernel: [    3.500336] systemd-udevd[443]: starting version 204
Jul 19 10:47:00 node-2 kernel: [    3.537279] usb 4-3: new high-speed USB device number 2 using xhci_hcd
Jul 19 10:47:00 node-2 kernel: [    3.551616] md: linear personality registered for level -1
Jul 19 10:47:00 node-2 kernel: [    3.564609] usb 4-3: New USB device found, idVendor=0424, idProduct=2660
Jul 19 10:47:00 node-2 kernel: [    3.564611] usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 19 10:47:00 node-2 kernel: [    3.569993] hub 4-3:1.0: USB hub found
Jul 19 10:47:00 node-2 kernel: [    3.570512] hub 4-3:1.0: 2 ports detected
Jul 19 10:47:00 node-2 kernel: [    3.575350] hpsa: module verification failed: signature and/or  required key missing - tainting kernel
Jul 19 10:47:00 node-2 kernel: [    3.619082] HP HPSA Driver (v 3.4.12-110)
Jul 19 10:47:00 node-2 kernel: [    3.628132] pps_core: LinuxPPS API ver. 1 registered
Jul 19 10:47:00 node-2 kernel: [    3.628853] hpsa 0000:07:00.0: MSI-X capable controller
Jul 19 10:47:00 node-2 kernel: [    3.630134] hpsa 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    3.630341] hpsa 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    3.630431] hpsa 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    3.630776] hpsa 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    3.631198] hpsa 0000:07:00.0: Using 4 reply queue(s)
Jul 19 10:47:00 node-2 kernel: [    3.632398] Physical aborts supported: yes
Jul 19 10:47:00 node-2 kernel: [    3.632399] Logical aborts supported: no
Jul 19 10:47:00 node-2 kernel: [    3.632406] HP SSD Smart Path aborts supported: yes
Jul 19 10:47:00 node-2 kernel: [    3.646916] hpsa 0000:07:00.0: hpsa0: <0x3239> at IRQ 116 using DAC
Jul 19 10:47:00 node-2 kernel: [    3.685944] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Jul 19 10:47:00 node-2 kernel: [    3.694509] bft2_offset = 0x8f4
Jul 19 10:47:00 node-2 kernel: [    3.710979] bnx2x: Broadcom NetXtreme II 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.78.17-0 (2013/04/11)
Jul 19 10:47:00 node-2 kernel: [    3.713016] scsi0 : hpsa
Jul 19 10:47:00 node-2 kernel: [    3.731024] hpsa 0000:07:00.0: added scsi 0:3:0:0: RAID              HP      P244br          RAID-UNKNOWN SSDSmartPathCap- En- Exp=4 qd=1024
Jul 19 10:47:00 node-2 kernel: [    3.731026] hpsa 0000:07:00.0: added scsi 0:2:0:0: Direct-Access     HP       EG0600JEMCV      RAID-UNKNOWN SSDSmartPathCap- En- Exp=2 qd=58
Jul 19 10:47:00 node-2 kernel: [    3.731042] hpsa 0000:07:00.0: added scsi 0:2:1:0: Direct-Access     HP       EG0600JEMCV      RAID-UNKNOWN SSDSmartPathCap- En- Exp=2 qd=58
Jul 19 10:47:00 node-2 kernel: [    3.731067] hpsa 0000:07:00.0: added scsi 0:0:0:0: Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=4 qd=1024
Jul 19 10:47:00 node-2 kernel: [    3.732598] scsi 0:3:0:0: RAID              HP       P244br           3.00 PQ: 0 ANSI: 5
Jul 19 10:47:00 node-2 kernel: [    3.733978] scsi 0:0:0:0: Direct-Access     HP       LOGICAL VOLUME   3.00 PQ: 0 ANSI: 5
Jul 19 10:47:00 node-2 kernel: [    3.735911] scsi 0:3:0:0: Attached scsi generic sg0 type 12
Jul 19 10:47:00 node-2 kernel: [    3.740000] sd 0:0:0:0: Attached scsi generic sg1 type 0
Jul 19 10:47:00 node-2 kernel: [    3.740731] sd 0:0:0:0: [sda] 2344114096 512-byte logical blocks: (1.20 TB/1.09 TiB)
Jul 19 10:47:00 node-2 kernel: [    3.742273] sd 0:0:0:0: [sda] Write Protect is off
Jul 19 10:47:00 node-2 kernel: [    3.742282] sd 0:0:0:0: [sda] Mode Sense: 73 00 00 08
Jul 19 10:47:00 node-2 kernel: [    3.742642] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jul 19 10:47:00 node-2 kernel: [    3.766521]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 19 10:47:00 node-2 kernel: [    3.782902] sd 0:0:0:0: [sda] Attached SCSI disk
Jul 19 10:47:00 node-2 kernel: [    3.913614] md: multipath personality registered for level -4
Jul 19 10:47:00 node-2 kernel: [    3.914246] bnx2x 0000:06:00.0: msix capability found
Jul 19 10:47:00 node-2 kernel: [    3.917677] bnx2x 0000:06:00.0: part number 0-0-0-0
Jul 19 10:47:00 node-2 kernel: [    3.940878] PTP clock support registered
Jul 19 10:47:00 node-2 kernel: [    3.949808] md: raid0 personality registered for level 0
Jul 19 10:47:00 node-2 kernel: [    3.959707] dca service started, version 1.12.1
Jul 19 10:47:00 node-2 kernel: [    3.968672] md: raid1 personality registered for level 1
Jul 19 10:47:00 node-2 kernel: [    3.978091] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 3.15.1-k
Jul 19 10:47:00 node-2 kernel: [    3.994994] ixgbe: Copyright (c) 1999-2013 Intel Corporation.
Jul 19 10:47:00 node-2 kernel: [    4.003672] Switched to clocksource tsc
Jul 19 10:47:00 node-2 kernel: [    4.037198] bnx2x 0000:06:00.0: irq 120 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.037205] bnx2x 0000:06:00.0: irq 121 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.037211] bnx2x 0000:06:00.0: irq 122 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.037216] bnx2x 0000:06:00.0: irq 123 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.037221] bnx2x 0000:06:00.0: irq 124 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.037226] bnx2x 0000:06:00.0: irq 125 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.037231] bnx2x 0000:06:00.0: irq 126 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.037236] bnx2x 0000:06:00.0: irq 127 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.037242] bnx2x 0000:06:00.0: irq 128 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.037247] bnx2x 0000:06:00.0: irq 129 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.037895] bnx2x 0000:06:00.1: msix capability found
Jul 19 10:47:00 node-2 kernel: [    4.047079] bnx2x 0000:06:00.1: part number 0-0-0-0
Jul 19 10:47:00 node-2 kernel: [    4.077159] raid6: sse2x1    7013 MB/s
Jul 19 10:47:00 node-2 kernel: [    4.109043] ixgbe 0000:08:00.0: irq 130 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109050] ixgbe 0000:08:00.0: irq 131 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109055] ixgbe 0000:08:00.0: irq 132 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109059] ixgbe 0000:08:00.0: irq 133 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109064] ixgbe 0000:08:00.0: irq 134 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109068] ixgbe 0000:08:00.0: irq 135 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109073] ixgbe 0000:08:00.0: irq 136 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109081] ixgbe 0000:08:00.0: irq 137 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109085] ixgbe 0000:08:00.0: irq 138 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109090] ixgbe 0000:08:00.0: irq 139 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109095] ixgbe 0000:08:00.0: irq 140 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109099] ixgbe 0000:08:00.0: irq 141 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109104] ixgbe 0000:08:00.0: irq 142 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109109] ixgbe 0000:08:00.0: irq 143 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109113] ixgbe 0000:08:00.0: irq 144 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109118] ixgbe 0000:08:00.0: irq 145 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109122] ixgbe 0000:08:00.0: irq 146 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109128] ixgbe 0000:08:00.0: irq 147 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109133] ixgbe 0000:08:00.0: irq 148 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109146] ixgbe 0000:08:00.0: irq 149 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109151] ixgbe 0000:08:00.0: irq 150 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109155] ixgbe 0000:08:00.0: irq 151 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109159] ixgbe 0000:08:00.0: irq 152 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109166] ixgbe 0000:08:00.0: irq 153 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109170] ixgbe 0000:08:00.0: irq 154 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109175] ixgbe 0000:08:00.0: irq 155 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109179] ixgbe 0000:08:00.0: irq 156 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109184] ixgbe 0000:08:00.0: irq 157 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109188] ixgbe 0000:08:00.0: irq 158 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109193] ixgbe 0000:08:00.0: irq 159 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109198] ixgbe 0000:08:00.0: irq 160 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109203] ixgbe 0000:08:00.0: irq 161 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109207] ixgbe 0000:08:00.0: irq 162 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109212] ixgbe 0000:08:00.0: irq 163 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109216] ixgbe 0000:08:00.0: irq 164 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109221] ixgbe 0000:08:00.0: irq 165 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109225] ixgbe 0000:08:00.0: irq 166 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109229] ixgbe 0000:08:00.0: irq 167 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109235] ixgbe 0000:08:00.0: irq 168 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109242] ixgbe 0000:08:00.0: irq 169 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109246] ixgbe 0000:08:00.0: irq 170 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109250] ixgbe 0000:08:00.0: irq 171 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109255] ixgbe 0000:08:00.0: irq 172 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109259] ixgbe 0000:08:00.0: irq 173 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109264] ixgbe 0000:08:00.0: irq 174 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109268] ixgbe 0000:08:00.0: irq 175 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109273] ixgbe 0000:08:00.0: irq 176 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109277] ixgbe 0000:08:00.0: irq 177 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109282] ixgbe 0000:08:00.0: irq 178 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.109369] ixgbe 0000:08:00.0: Multiqueue Enabled: Rx Queue count = 48, Tx Queue count = 48
Jul 19 10:47:00 node-2 kernel: [    4.125322] ixgbe 0000:08:00.0: PCI Express bandwidth of 32GT/s available
Jul 19 10:47:00 node-2 kernel: [    4.133414] ixgbe 0000:08:00.0: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Jul 19 10:47:00 node-2 kernel: [    4.141820] ixgbe 0000:08:00.0: MAC: 2, PHY: 1, PBA No: G43498-012
Jul 19 10:47:00 node-2 kernel: [    4.149184] raid6: sse2x2    4831 MB/s
Jul 19 10:47:00 node-2 kernel: [    4.157654] ixgbe 0000:08:00.0: 5c:b9:01:8b:9d:4c
Jul 19 10:47:00 node-2 kernel: [    4.177173] bnx2x 0000:06:00.1: irq 179 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.177180] bnx2x 0000:06:00.1: irq 180 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.177185] bnx2x 0000:06:00.1: irq 181 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.177194] bnx2x 0000:06:00.1: irq 182 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.177199] bnx2x 0000:06:00.1: irq 183 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.177204] bnx2x 0000:06:00.1: irq 184 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.177209] bnx2x 0000:06:00.1: irq 185 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.177213] bnx2x 0000:06:00.1: irq 186 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.177218] bnx2x 0000:06:00.1: irq 187 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.177222] bnx2x 0000:06:00.1: irq 188 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.200931] ixgbe 0000:08:00.0: Intel(R) 10 Gigabit Network Connection
Jul 19 10:47:00 node-2 kernel: [    4.201193] random: lvm urandom read with 29 bits of entropy available
Jul 19 10:47:00 node-2 kernel: [    4.217131] raid6: sse2x4    8045 MB/s
Jul 19 10:47:00 node-2 kernel: [    4.289115] raid6: avx2x1   19333 MB/s
Jul 19 10:47:00 node-2 kernel: [    4.320807] ixgbe 0000:08:00.1: irq 189 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320813] ixgbe 0000:08:00.1: irq 190 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320818] ixgbe 0000:08:00.1: irq 191 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320822] ixgbe 0000:08:00.1: irq 192 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320827] ixgbe 0000:08:00.1: irq 193 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320831] ixgbe 0000:08:00.1: irq 194 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320835] ixgbe 0000:08:00.1: irq 195 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320839] ixgbe 0000:08:00.1: irq 196 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320844] ixgbe 0000:08:00.1: irq 197 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320848] ixgbe 0000:08:00.1: irq 198 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320853] ixgbe 0000:08:00.1: irq 199 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320858] ixgbe 0000:08:00.1: irq 200 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320862] ixgbe 0000:08:00.1: irq 201 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320866] ixgbe 0000:08:00.1: irq 202 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320871] ixgbe 0000:08:00.1: irq 203 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320875] ixgbe 0000:08:00.1: irq 204 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320879] ixgbe 0000:08:00.1: irq 205 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320883] ixgbe 0000:08:00.1: irq 206 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320888] ixgbe 0000:08:00.1: irq 207 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320892] ixgbe 0000:08:00.1: irq 208 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320897] ixgbe 0000:08:00.1: irq 209 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320901] ixgbe 0000:08:00.1: irq 210 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320905] ixgbe 0000:08:00.1: irq 211 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320911] ixgbe 0000:08:00.1: irq 212 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320915] ixgbe 0000:08:00.1: irq 213 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320919] ixgbe 0000:08:00.1: irq 214 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320925] ixgbe 0000:08:00.1: irq 215 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320929] ixgbe 0000:08:00.1: irq 216 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320935] ixgbe 0000:08:00.1: irq 217 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320943] ixgbe 0000:08:00.1: irq 218 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320947] ixgbe 0000:08:00.1: irq 219 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320952] ixgbe 0000:08:00.1: irq 220 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320956] ixgbe 0000:08:00.1: irq 221 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320960] ixgbe 0000:08:00.1: irq 222 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320965] ixgbe 0000:08:00.1: irq 223 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320969] ixgbe 0000:08:00.1: irq 224 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320973] ixgbe 0000:08:00.1: irq 225 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320978] ixgbe 0000:08:00.1: irq 226 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320982] ixgbe 0000:08:00.1: irq 227 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320986] ixgbe 0000:08:00.1: irq 228 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320991] ixgbe 0000:08:00.1: irq 229 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320995] ixgbe 0000:08:00.1: irq 230 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.320999] ixgbe 0000:08:00.1: irq 231 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.321004] ixgbe 0000:08:00.1: irq 232 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.321008] ixgbe 0000:08:00.1: irq 233 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.321012] ixgbe 0000:08:00.1: irq 234 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.321017] ixgbe 0000:08:00.1: irq 235 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.321021] ixgbe 0000:08:00.1: irq 236 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.321025] ixgbe 0000:08:00.1: irq 237 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.321117] ixgbe 0000:08:00.1: Multiqueue Enabled: Rx Queue count = 48, Tx Queue count = 48
Jul 19 10:47:00 node-2 kernel: [    4.336717] ixgbe 0000:08:00.1: PCI Express bandwidth of 32GT/s available
Jul 19 10:47:00 node-2 kernel: [    4.344599] ixgbe 0000:08:00.1: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Jul 19 10:47:00 node-2 kernel: [    4.352862] ixgbe 0000:08:00.1: MAC: 2, PHY: 1, PBA No: G43498-012
Jul 19 10:47:00 node-2 kernel: [    4.360653] ixgbe 0000:08:00.1: 5c:b9:01:8b:9d:4d
Jul 19 10:47:00 node-2 kernel: [    4.361169] raid6: avx2x2    9594 MB/s
Jul 19 10:47:00 node-2 kernel: [    4.411355] ixgbe 0000:08:00.1: Intel(R) 10 Gigabit Network Connection
Jul 19 10:47:00 node-2 kernel: [    4.429083] raid6: avx2x4   19829 MB/s
Jul 19 10:47:00 node-2 kernel: [    4.437131] raid6: using algorithm avx2x4 (19829 MB/s)
Jul 19 10:47:00 node-2 kernel: [    4.445072] raid6: using avx2x2 recovery algorithm
Jul 19 10:47:00 node-2 kernel: [    4.453991] xor: automatically using best checksumming function:
Jul 19 10:47:00 node-2 kernel: [    4.462142] bio: create slab <bio-1> at 1
Jul 19 10:47:00 node-2 kernel: [    4.501082]    avx       : 30640.000 MB/sec
Jul 19 10:47:00 node-2 kernel: [    4.509638] async_tx: api initialized (async)
Jul 19 10:47:00 node-2 kernel: [    4.513148] ixgbe 0000:87:00.0: irq 238 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513157] ixgbe 0000:87:00.0: irq 239 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513162] ixgbe 0000:87:00.0: irq 240 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513167] ixgbe 0000:87:00.0: irq 241 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513172] ixgbe 0000:87:00.0: irq 242 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513176] ixgbe 0000:87:00.0: irq 243 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513181] ixgbe 0000:87:00.0: irq 244 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513186] ixgbe 0000:87:00.0: irq 245 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513191] ixgbe 0000:87:00.0: irq 246 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513196] ixgbe 0000:87:00.0: irq 247 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513200] ixgbe 0000:87:00.0: irq 248 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513205] ixgbe 0000:87:00.0: irq 249 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513209] ixgbe 0000:87:00.0: irq 250 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513214] ixgbe 0000:87:00.0: irq 251 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513218] ixgbe 0000:87:00.0: irq 252 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513222] ixgbe 0000:87:00.0: irq 253 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513227] ixgbe 0000:87:00.0: irq 254 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513236] ixgbe 0000:87:00.0: irq 255 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513242] ixgbe 0000:87:00.0: irq 256 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513246] ixgbe 0000:87:00.0: irq 257 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513251] ixgbe 0000:87:00.0: irq 258 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513256] ixgbe 0000:87:00.0: irq 259 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513260] ixgbe 0000:87:00.0: irq 260 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513265] ixgbe 0000:87:00.0: irq 261 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513269] ixgbe 0000:87:00.0: irq 262 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513274] ixgbe 0000:87:00.0: irq 263 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513278] ixgbe 0000:87:00.0: irq 264 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513283] ixgbe 0000:87:00.0: irq 265 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513288] ixgbe 0000:87:00.0: irq 266 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513292] ixgbe 0000:87:00.0: irq 267 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513300] ixgbe 0000:87:00.0: irq 268 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513305] ixgbe 0000:87:00.0: irq 269 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513310] ixgbe 0000:87:00.0: irq 270 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513319] ixgbe 0000:87:00.0: irq 271 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513324] ixgbe 0000:87:00.0: irq 272 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513328] ixgbe 0000:87:00.0: irq 273 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513333] ixgbe 0000:87:00.0: irq 274 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513338] ixgbe 0000:87:00.0: irq 275 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513342] ixgbe 0000:87:00.0: irq 276 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513346] ixgbe 0000:87:00.0: irq 277 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513353] ixgbe 0000:87:00.0: irq 278 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513363] ixgbe 0000:87:00.0: irq 279 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513373] ixgbe 0000:87:00.0: irq 280 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513383] ixgbe 0000:87:00.0: irq 281 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513393] ixgbe 0000:87:00.0: irq 282 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513402] ixgbe 0000:87:00.0: irq 283 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513412] ixgbe 0000:87:00.0: irq 284 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513422] ixgbe 0000:87:00.0: irq 285 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513432] ixgbe 0000:87:00.0: irq 286 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.513519] ixgbe 0000:87:00.0: Multiqueue Enabled: Rx Queue count = 48, Tx Queue count = 48
Jul 19 10:47:00 node-2 kernel: [    4.513644] ixgbe 0000:87:00.0: PCI Express bandwidth of 32GT/s available
Jul 19 10:47:00 node-2 kernel: [    4.513645] ixgbe 0000:87:00.0: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Jul 19 10:47:00 node-2 kernel: [    4.513965] ixgbe 0000:87:00.0: MAC: 2, PHY: 1, PBA No: G43498-012
Jul 19 10:47:00 node-2 kernel: [    4.513965] ixgbe 0000:87:00.0: 5c:b9:01:8b:9d:6c
Jul 19 10:47:00 node-2 kernel: [    4.549285] ixgbe 0000:87:00.0: Intel(R) 10 Gigabit Network Connection
Jul 19 10:47:00 node-2 kernel: [    4.576484] md: raid6 personality registered for level 6
Jul 19 10:47:00 node-2 kernel: [    4.584224] md: raid5 personality registered for level 5
Jul 19 10:47:00 node-2 kernel: [    4.591655] md: raid4 personality registered for level 4
Jul 19 10:47:00 node-2 kernel: [    4.602654] md: raid10 personality registered for level 10
Jul 19 10:47:00 node-2 kernel: [    4.648763] ixgbe 0000:87:00.1: irq 287 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.648860] ixgbe 0000:87:00.1: irq 288 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.649082] ixgbe 0000:87:00.1: irq 289 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.649185] ixgbe 0000:87:00.1: irq 290 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.649197] ixgbe 0000:87:00.1: irq 291 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.649331] ixgbe 0000:87:00.1: irq 292 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.649452] ixgbe 0000:87:00.1: irq 293 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.649470] ixgbe 0000:87:00.1: irq 294 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.649642] ixgbe 0000:87:00.1: irq 295 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.649666] ixgbe 0000:87:00.1: irq 296 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.649699] ixgbe 0000:87:00.1: irq 297 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.649818] ixgbe 0000:87:00.1: irq 298 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.649905] ixgbe 0000:87:00.1: irq 299 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.649959] ixgbe 0000:87:00.1: irq 300 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.650276] ixgbe 0000:87:00.1: irq 301 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.650310] ixgbe 0000:87:00.1: irq 302 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.650434] ixgbe 0000:87:00.1: irq 303 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.650601] ixgbe 0000:87:00.1: irq 304 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.650739] ixgbe 0000:87:00.1: irq 305 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.650776] ixgbe 0000:87:00.1: irq 306 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.650876] ixgbe 0000:87:00.1: irq 307 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.650914] ixgbe 0000:87:00.1: irq 308 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.650985] ixgbe 0000:87:00.1: irq 309 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.651049] ixgbe 0000:87:00.1: irq 310 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.651066] ixgbe 0000:87:00.1: irq 311 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.651165] ixgbe 0000:87:00.1: irq 312 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.651332] ixgbe 0000:87:00.1: irq 313 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.651425] ixgbe 0000:87:00.1: irq 314 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.651455] ixgbe 0000:87:00.1: irq 315 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.651585] ixgbe 0000:87:00.1: irq 316 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.651742] ixgbe 0000:87:00.1: irq 317 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.651847] ixgbe 0000:87:00.1: irq 318 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.651909] ixgbe 0000:87:00.1: irq 319 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.651929] ixgbe 0000:87:00.1: irq 320 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.652036] ixgbe 0000:87:00.1: irq 321 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.652108] ixgbe 0000:87:00.1: irq 322 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.652134] ixgbe 0000:87:00.1: irq 323 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.652237] ixgbe 0000:87:00.1: irq 324 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.652352] ixgbe 0000:87:00.1: irq 325 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.652428] ixgbe 0000:87:00.1: irq 326 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.652549] ixgbe 0000:87:00.1: irq 327 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.652772] ixgbe 0000:87:00.1: irq 328 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.652837] ixgbe 0000:87:00.1: irq 329 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.652975] ixgbe 0000:87:00.1: irq 330 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.653027] ixgbe 0000:87:00.1: irq 331 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.653037] ixgbe 0000:87:00.1: irq 332 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.653086] ixgbe 0000:87:00.1: irq 333 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.653223] ixgbe 0000:87:00.1: irq 334 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.653306] ixgbe 0000:87:00.1: irq 335 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    4.653620] ixgbe 0000:87:00.1: Multiqueue Enabled: Rx Queue count = 48, Tx Queue count = 48
Jul 19 10:47:00 node-2 kernel: [    4.654006] ixgbe 0000:87:00.1: PCI Express bandwidth of 32GT/s available
Jul 19 10:47:00 node-2 kernel: [    4.654017] ixgbe 0000:87:00.1: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Jul 19 10:47:00 node-2 kernel: [    4.654368] ixgbe 0000:87:00.1: MAC: 2, PHY: 1, PBA No: G43498-012
Jul 19 10:47:00 node-2 kernel: [    4.654400] ixgbe 0000:87:00.1: 5c:b9:01:8b:9d:6d
Jul 19 10:47:00 node-2 kernel: [    4.700084] ixgbe 0000:87:00.1: Intel(R) 10 Gigabit Network Connection
Jul 19 10:47:00 node-2 kernel: [    4.717871] multipathd (722): /proc/722/oom_adj is deprecated, please use /proc/722/oom_score_adj instead.
Jul 19 10:47:00 node-2 kernel: [    5.413482] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 19 10:47:00 node-2 kernel: [    5.785838] random: nonblocking pool is initialized
Jul 19 10:47:00 node-2 kernel: [    5.878472] init: plymouth-upstart-bridge main process (880) terminated with status 1
Jul 19 10:47:00 node-2 kernel: [    5.896094] init: plymouth-upstart-bridge main process ended, respawning
Jul 19 10:47:00 node-2 kernel: [    5.992936] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 19 10:47:00 node-2 kernel: [    6.037531] Adding 4194300k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:4194300k FS
Jul 19 10:47:00 node-2 kernel: [    6.079608] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 19 10:47:00 node-2 kernel: [    6.115781] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 19 10:47:00 node-2 kernel: [    6.140430] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 19 10:47:00 node-2 kernel: [    6.299874] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 19 10:47:00 node-2 kernel: [    6.347334] XFS (dm-0): Mounting Filesystem
Jul 19 10:47:00 node-2 kernel: [    6.671804] XFS (dm-0): Ending clean mount
Jul 19 10:47:00 node-2 kernel: [    6.709293] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 19 10:47:00 node-2 kernel: [    6.758791] XFS (dm-1): Mounting Filesystem
Jul 19 10:47:00 node-2 kernel: [    6.897334] XFS (dm-1): Ending clean mount
Jul 19 10:47:00 node-2 kernel: [    8.449351] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 19 10:47:00 node-2 kernel: [    8.467585] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 19 10:47:00 node-2 kernel: [    8.614920] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 19 10:47:00 node-2 kernel: [    8.614932] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 19 10:47:00 node-2 kernel: [    8.614941] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 19 10:47:00 node-2 kernel: [    8.614950] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 19 10:47:00 node-2 kernel: [    8.614958] IPv6: ADDRCONF(NETDEV_UP): eth4: link is not ready
Jul 19 10:47:00 node-2 kernel: [    8.614967] IPv6: ADDRCONF(NETDEV_UP): eth5: link is not ready
Jul 19 10:47:00 node-2 kernel: [    8.628444] systemd-udevd[1101]: starting version 204
Jul 19 10:47:00 node-2 kernel: [    8.756665] wmi: Mapper loaded
Jul 19 10:47:00 node-2 kernel: [    8.791479] power_meter ACPI000D:00: Found ACPI power meter.
Jul 19 10:47:00 node-2 kernel: [    8.791493] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 19 10:47:00 node-2 kernel: [    8.810362] IPMI System Interface driver.
Jul 19 10:47:00 node-2 kernel: [    8.810438] ipmi_si: probing via ACPI
Jul 19 10:47:00 node-2 kernel: [    8.810451] ipmi_si 00:07: [io  0x0ca2-0x0ca3] regsize 1 spacing 1 irq 0
Jul 19 10:47:00 node-2 kernel: [    8.810452] ipmi_si: Adding ACPI-specified kcs state machine
Jul 19 10:47:00 node-2 kernel: [    8.810466] ipmi_si: probing via SMBIOS
Jul 19 10:47:00 node-2 kernel: [    8.810467] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 19 10:47:00 node-2 kernel: [    8.810467] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 19 10:47:00 node-2 kernel: [    8.810469] ipmi_si: probing via SPMI
Jul 19 10:47:00 node-2 kernel: [    8.810470] ipmi_si: SPMI: io 0xca3 regsize 1 spacing 1 irq 0
Jul 19 10:47:00 node-2 kernel: [    8.810471] ipmi_si: Adding SPMI-specified kcs state machine
Jul 19 10:47:00 node-2 kernel: [    8.810472] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 19 10:47:00 node-2 kernel: [    8.879689] ioatdma: Intel(R) QuickData Technology Driver 4.00
Jul 19 10:47:00 node-2 kernel: [    8.879972] ioatdma 0000:00:04.0: irq 336 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    8.880421] ioatdma 0000:00:04.1: irq 337 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    8.880699] ioatdma 0000:00:04.2: irq 338 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    8.880989] ioatdma 0000:00:04.3: irq 339 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    8.881400] ioatdma 0000:00:04.4: irq 340 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    8.881817] ioatdma 0000:00:04.5: irq 341 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    8.882123] ioatdma 0000:00:04.6: irq 342 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    8.882393] ioatdma 0000:00:04.7: irq 343 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    8.882692] ioatdma 0000:80:04.0: irq 344 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    8.883044] ioatdma 0000:80:04.1: irq 345 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    8.883264] ioatdma 0000:80:04.2: irq 346 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    8.883479] ioatdma 0000:80:04.3: irq 347 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    8.883682] ioatdma 0000:80:04.4: irq 348 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    8.883884] ioatdma 0000:80:04.5: irq 349 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    8.884083] ioatdma 0000:80:04.6: irq 350 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    8.884288] ioatdma 0000:80:04.7: irq 351 for MSI/MSI-X
Jul 19 10:47:00 node-2 kernel: [    8.888371] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 19 10:47:00 node-2 kernel: [    8.912561] systemd-udevd[1130]: renamed network interface eth1 to eno50
Jul 19 10:47:00 node-2 kernel: [    8.936320] systemd-udevd[1127]: renamed network interface eth0 to eno49
Jul 19 10:47:00 node-2 kernel: [    8.964656] systemd-udevd[1128]: renamed network interface eth3 to ens1f1
Jul 19 10:47:00 node-2 kernel: [    8.992354] systemd-udevd[1150]: renamed network interface eth5 to ens2f1
Jul 19 10:47:00 node-2 kernel: [    9.016308] systemd-udevd[1121]: renamed network interface eth2 to ens1f0
Jul 19 10:47:00 node-2 kernel: [    9.048346] systemd-udevd[1148]: renamed network interface eth4 to ens2f0
Jul 19 10:47:00 node-2 kernel: [    9.065861] ipmi_si 00:07: Found new BMC (man_id: 0x00000b, prod_id: 0x2020, dev_id: 0x13)
Jul 19 10:47:00 node-2 kernel: [    9.065875] ipmi_si 00:07: IPMI kcs interface initialized
Jul 19 10:47:00 node-2 kernel: [    9.241506] type=1400 audit(1468925189.416:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1429 comm="apparmor_parser"
Jul 19 10:47:00 node-2 kernel: [    9.241629] type=1400 audit(1468925189.416:3): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1473 comm="apparmor_parser"
Jul 19 10:47:00 node-2 kernel: [    9.241691] type=1400 audit(1468925189.416:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1429 comm="apparmor_parser"
Jul 19 10:47:00 node-2 kernel: [    9.241821] type=1400 audit(1468925189.416:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1473 comm="apparmor_parser"
Jul 19 10:47:00 node-2 kernel: [    9.241872] type=1400 audit(1468925189.416:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1429 comm="apparmor_parser"
Jul 19 10:47:00 node-2 kernel: [    9.241973] type=1400 audit(1468925189.416:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1473 comm="apparmor_parser"
Jul 19 10:47:00 node-2 kernel: [    9.242123] type=1400 audit(1468925189.416:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1443 comm="apparmor_parser"
Jul 19 10:47:00 node-2 kernel: [    9.242156] type=1400 audit(1468925189.416:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1445 comm="apparmor_parser"
Jul 19 10:47:00 node-2 kernel: [    9.242310] type=1400 audit(1468925189.416:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1443 comm="apparmor_parser"
Jul 19 10:47:00 node-2 kernel: [    9.242344] type=1400 audit(1468925189.416:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1445 comm="apparmor_parser"
Jul 19 10:47:00 node-2 kernel: [    9.833317] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 19 10:47:00 node-2 kernel: [    9.849562] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 19 10:47:00 node-2 kernel: [   10.549395] bnx2x 0000:06:00.1 eno50: using MSI-X  IRQs: sp 179  fp[0] 181 ... fp[7] 188
Jul 19 10:47:00 node-2 kernel: [   10.695989] IPv6: ADDRCONF(NETDEV_UP): eno50: link is not ready
Jul 19 10:47:00 node-2 kernel: [   10.903825] bnx2x 0000:06:00.1 eno50: NIC Link is Up, 10000 Mbps full duplex, Flow control: ON - receive & transmit
Jul 19 10:47:00 node-2 kernel: [   10.903858] IPv6: ADDRCONF(NETDEV_CHANGE): eno50: link becomes ready
Jul 19 10:47:00 node-2 kernel: [   18.609944] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 19 10:47:01 node-2 failsafe: Failsafe of 120 seconds reached.
Jul 19 10:47:01 node-2 kernel: [   40.891454] init: failsafe main process (8841) killed by TERM signal
Jul 19 10:47:01 node-2 dbus[8877]: [system] AppArmor D-Bus mediation is enabled
Jul 19 10:47:01 node-2 kernel: [   41.103996] audit_printk_skb: 54 callbacks suppressed
Jul 19 10:47:01 node-2 kernel: [   41.103998] type=1400 audit(1468925221.663:30): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8965 comm="apparmor_parser"
Jul 19 10:47:01 node-2 kernel: [   41.104256] type=1400 audit(1468925221.663:31): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8964 comm="apparmor_parser"
Jul 19 10:47:01 node-2 kernel: [   41.104261] type=1400 audit(1468925221.663:32): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8964 comm="apparmor_parser"
Jul 19 10:47:01 node-2 kernel: [   41.104265] type=1400 audit(1468925221.663:33): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8964 comm="apparmor_parser"
Jul 19 10:47:01 node-2 kernel: [   41.104530] type=1400 audit(1468925221.663:34): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8964 comm="apparmor_parser"
Jul 19 10:47:01 node-2 kernel: [   41.104532] type=1400 audit(1468925221.663:35): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8964 comm="apparmor_parser"
Jul 19 10:47:01 node-2 kernel: [   41.104678] type=1400 audit(1468925221.663:36): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8964 comm="apparmor_parser"
Jul 19 10:47:01 node-2 kernel: [   41.204844] type=1400 audit(1468925221.763:37): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8967 comm="apparmor_parser"
Jul 19 10:47:01 node-2 anacron[9033]: Anacron 2.3 started on 2016-07-19
Jul 19 10:47:01 node-2 anacron[9033]: Will run job `cron.daily' in 5 min.
Jul 19 10:47:01 node-2 anacron[9033]: Will run job `cron.weekly' in 10 min.
Jul 19 10:47:01 node-2 anacron[9033]: Will run job `cron.monthly' in 15 min.
Jul 19 10:47:01 node-2 anacron[9033]: Jobs will be executed sequentially
Jul 19 10:47:01 node-2 cron[8996]: (CRON) INFO (pidfile fd = 3)
Jul 19 10:47:01 node-2 cron[9040]: (CRON) STARTUP (fork ok)
Jul 19 10:47:01 node-2 multipathd: path checkers start up
Jul 19 10:47:01 node-2 cron[9040]: (CRON) INFO (Running @reboot jobs)
Jul 19 10:47:02 node-2 postfix/master[9178]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 19 10:47:05 node-2 puppet-agent[9362]: Reopening log files
Jul 19 10:47:05 node-2 puppet-agent[9362]: Could not request certificate: Connection refused - connect(2)
Jul 19 10:47:49 node-2 puppet-user[9862]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 19 10:47:49 node-2 puppet-user[9862]: Compiled catalog for node-2.opnfvericsson.ca in environment production in 0.02 seconds
Jul 19 10:47:51 node-2 puppet-user[9862]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 19 10:47:51 node-2 puppet-user[9862]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 19 10:47:51 node-2 puppet-user[9862]: Finished catalog run in 2.33 seconds
Jul 19 10:47:52 node-2 multipathd: uevent trigger error
Jul 19 10:47:53 node-2 puppet-user[10439]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 19 10:47:53 node-2 puppet-user[10439]: Compiled catalog for node-2.opnfvericsson.ca in environment production in 0.07 seconds
Jul 19 10:47:53 node-2 puppet-user[10439]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 19 10:47:53 node-2 puppet-user[10439]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 19 10:47:53 node-2 puppet-user[10439]: (/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 19 10:47:53 node-2 puppet-user[10439]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 19 10:47:53 node-2 puppet-user[10439]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 19 10:47:53 node-2 puppet-user[10439]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 19 10:47:53 node-2 puppet-user[10439]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 19 10:47:53 node-2 puppet-user[10439]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 19 10:47:53 node-2 puppet-user[10439]: Finished catalog run in 0.02 seconds
Jul 19 10:47:54 node-2 puppet-user[11038]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 19 10:47:54 node-2 puppet-user[11038]: Compiled catalog for node-2.opnfvericsson.ca in environment production in 0.07 seconds
Jul 19 10:47:54 node-2 puppet-user[11038]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 19 10:47:54 node-2 puppet-user[11038]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 19 10:47:54 node-2 puppet-user[11038]: Finished catalog run in 0.01 seconds
Jul 19 10:47:56 node-2 puppet-user[11639]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 19 10:47:56 node-2 puppet-user[11639]: Compiled catalog for node-2.opnfvericsson.ca in environment production in 0.03 seconds
Jul 19 10:47:56 node-2 puppet-user[11639]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 19 10:47:56 node-2 puppet-user[11639]: Finished catalog run in 0.01 seconds
Jul 19 10:47:58 node-2 puppet-user[12229]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 19 10:47:58 node-2 puppet-user[12229]: Compiled catalog for node-2.opnfvericsson.ca in environment production in 0.14 seconds
Jul 19 10:47:58 node-2 puppet-user[12229]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 19 10:47:58 node-2 puppet-user[12229]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Jul 19 10:47:59 node-2 puppet-user[12229]: (/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 19 10:47:59 node-2 puppet-user[12229]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/bgpvpn-0.9/]/Exec[rsync /etc/fuel/plugins/bgpvpn-0.9/]/returns) executed successfully
Jul 19 10:47:59 node-2 puppet-user[12229]: Finished catalog run in 1.19 seconds
Jul 19 10:48:01 node-2 puppet-user[12877]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 19 10:48:01 node-2 puppet-user[12877]: Compiled catalog for node-2.opnfvericsson.ca in environment production in 0.20 seconds
Jul 19 10:48:01 node-2 puppet-user[12877]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Jul 19 10:48:01 node-2 puppet-user[12877]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[bgpvpn-0.9.0]/Apt::Setting[list-bgpvpn-0.9.0]/File[/etc/apt/sources.list.d/bgpvpn-0.9.0.list]/ensure) created
Jul 19 10:48:01 node-2 puppet-user[12877]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 19 10:48:01 node-2 puppet-user[12877]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 19 10:48:01 node-2 puppet-user[12877]: (/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 19 10:48:01 node-2 puppet-user[12877]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 19 10:48:01 node-2 puppet-user[12877]: Finished catalog run in 0.16 seconds
Jul 19 10:48:02 node-2 CRON[13474]: (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 19 10:48:04 node-2 puppet-user[13504]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 19 10:48:04 node-2 puppet-user[13504]: Compiled catalog for node-2.opnfvericsson.ca in environment production in 0.17 seconds
Jul 19 10:48:04 node-2 puppet-user[13504]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 19 10:48:04 node-2 kernel: [  103.851246] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 19 10:48:04 node-2 kernel: [  103.851306] 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 19 10:48:04 node-2 puppet-user[13504]: (/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 19 10:48:04 node-2 puppet-user[13504]: Finished catalog run in 0.09 seconds
Jul 19 10:48:08 node-2 puppet-user[14120]: (Scope(Class[main])) MODULAR: sync_time
Jul 19 10:48:08 node-2 puppet-user[14120]: Compiled catalog for node-2.opnfvericsson.ca in environment production in 0.04 seconds
Jul 19 10:48:09 node-2 ntpdate[14724]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 19 10:48:09 node-2 kernel: [  109.079910] init: plymouth-upstart-bridge main process ended, respawning
Jul 19 10:48:09 node-2 puppet-agent[9362]: Could not run: SIGTERM
Jul 19 10:48:10 node-2 kernel: [  109.482951] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 19 10:48:10 node-2 ec2: 
Jul 19 10:48:10 node-2 ec2: #############################################################
Jul 19 10:48:10 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 19 10:48:10 node-2 ec2: 1024 af:4d:38:7a:a3:9c:bb:d4:b6:7b:94:0e:86:ad:0f:c2  root@node-2.opnfvericsson.ca (DSA)
Jul 19 10:48:10 node-2 ec2: 256 84:64:f2:fa:15:13:95:69:f2:83:27:b4:bd:8e:e4:77  root@node-2.opnfvericsson.ca (ECDSA)
Jul 19 10:48:10 node-2 ec2: 256 a0:9e:be:47:98:fa:c0:05:f3:c5:86:8f:00:0a:3a:f2  root@node-2.opnfvericsson.ca (ED25519)
Jul 19 10:48:10 node-2 ec2: 2048 37:b9:75:a5:40:e5:35:54:a9:88:73:37:2d:8e:37:37  root@node-2.opnfvericsson.ca (RSA)
Jul 19 10:48:10 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 19 10:48:10 node-2 ec2: #############################################################
Jul 19 10:48:15 node-2 ntpdate[14724]: adjust time server 10.20.0.2 offset -0.001265 sec
Jul 19 10:48:15 node-2 puppet-user[14120]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 19 10:48:15 node-2 puppet-user[14120]: Finished catalog run in 6.15 seconds
Jul 19 10:48:19 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 19 10:48:19 node-2 nailgun-agent: D, [2016-07-19T10:48:02.156915 #13477] DEBUG -- : Sleep for 17 seconds before sending request
Jul 19 10:48:19 node-2 nailgun-agent: I, [2016-07-19T10:48:19.182091 #13477]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 19 10:48:19 node-2 nailgun-agent: D, [2016-07-19T10:48:19.849817 #13477] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.868244 #13477] DEBUG -- : Trying to find block devices
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.868451 #13477] DEBUG -- : Found block device: sda
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.868530 #13477] DEBUG -- : Block device info: {"size"=>"2344114096", "removable"=>"0", "model"=>"LOGICAL VOLUME", "rev"=>"3.00", "state"=>"running", "timeout"=>"30", "vendor"=>"HP"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.868581 #13477] DEBUG -- : Trying to get list of physical devices
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.868827 #13477] DEBUG -- : Getting udev properties for device: sda
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.872565 #13477] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3600508b1001ce878a70d81a7384b3866 /dev/disk/by-id/wwn-0x600508b1001ce878a70d81a7384b3866 /dev/disk/by-path/pci-0000:07:00.0-scsi-0:0:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:02.2/0000:07:00.0/host0/target0:0:0/0:0:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"LOGICAL_VOLUME", "ID_MODEL_ENC"=>"LOGICAL\\x20VOLUME\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:07:00.0-scsi-0:0:0:0", "ID_PATH_TAG"=>"pci-0000_07_00_0-scsi-0_0_0_0", "ID_REVISION"=>"3.00", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"PDZVU0RLM9A3JQ", "ID_SERIAL"=>"3600508b1001ce878a70d81a7384b3866", "ID_SERIAL_SHORT"=>"600508b1001ce878a70d81a7384b3866", "ID_TYPE"=>"disk", "ID_VENDOR"=>"HP", "ID_VENDOR_ENC"=>"HP\\x20\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x600508b1001ce878", "ID_WWN_VENDOR_EXTENSION"=>"0xa70d81a7384b3866", "ID_WWN_WITH_EXTENSION"=>"0x600508b1001ce878a70d81a7384b3866", "
Jul 19 10:48:41 node-2 nailgun-agent: MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"5785", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.872632 #13477] DEBUG -- : Trying to find out if device sda is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.872733 #13477] DEBUG -- : Device sda removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.872773 #13477] DEBUG -- : Device sda seems to be appropriate
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.873617 #13477] DEBUG -- : Getting udev properties for device: dm-0
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.878158 #13477] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-AjSSL3kjW7fiHFcomub3MuJFnfcBTVaatG71jAVxzSxI3tRHitC5q9BiWzC13m74 /dev/disk/by-uuid/ecb5297d-5aa8-4409-ab8d-36ef54574966 /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-AjSSL3kjW7fiHFcomub3MuJFnfcBTVaatG71jAVxzSxI3tRHitC5q9BiWzC13m74", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ecb5297d-5aa8-4409-ab8d-36ef54574966", "ID_FS_UUID_ENC"=>"ecb5297d-5aa8-4409-ab8d-36ef54574966", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44913", "nomdmonddf"=>"1", "nom
Jul 19 10:48:41 node-2 nailgun-agent: dmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.878233 #13477] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.878324 #13477] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.878369 #13477] DEBUG -- : Device dm-0 seems to be appropriate
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.878414 #13477] DEBUG -- : Getting udev properties for device: dm-1
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.882741 #13477] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-LmEiFIqAMHn8JevAblcK7SUtnBcQVyf51PTKGvPfZ8MevkPDEfRNe2jhoPsR14Cd /dev/disk/by-uuid/c0d1e749-96ea-45e0-9f30-603184b599b4 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-LmEiFIqAMHn8JevAblcK7SUtnBcQVyf51PTKGvPfZ8MevkPDEfRNe2jhoPsR14Cd", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"c0d1e749-96ea-45e0-9f30-603184b599b4", "ID_FS_UUID_ENC"=>"c0d1e749-96ea-45e0-9f30-603184b599b4", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2
Jul 19 10:48:41 node-2 nailgun-agent: 7970", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.882815 #13477] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.882909 #13477] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.882953 #13477] DEBUG -- : Device dm-1 seems to be appropriate
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.882996 #13477] DEBUG -- : Getting udev properties for device: dm-2
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.887306 #13477] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-KhVydJEwPNfRThEo0209syrTkJWdASqrNKKftfy26VDsvawrph883wxyNi1nMqdA /dev/disk/by-uuid/6c49f83b-269e-4a37-baae-4d48c88af58d /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-KhVydJEwPNfRThEo0209syrTkJWdASqrNKKftfy26VDsvawrph883wxyNi1nMqdA", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"6c49f83b-269e-4a37-baae-4d48c88af58d", "ID_FS_UUID_ENC"=>"6c49f83b-269e-4a37-baae-4d48c88af58d", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48532", "nomdmon
Jul 19 10:48:41 node-2 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.887379 #13477] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.887468 #13477] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.887507 #13477] DEBUG -- : Device dm-2 seems to be appropriate
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.887578 #13477] DEBUG -- : Getting udev properties for device: dm-3
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.892175 #13477] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-SjNCjskEu5puioipKuifLMbG0RBrBvbjwwdPQ8n752JYxyYPQzm05fQyftml47UO /dev/disk/by-uuid/a20e7282-0d03-45f0-93a9-e7a61e66d011 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-SjNCjskEu5puioipKuifLMbG0RBrBvbjwwdPQ8n752JYxyYPQzm05fQyftml47UO", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"a20e7282-0d03-45f0-93a9-e7a61e66d011", "ID_FS_UUID_ENC"=>"a20e7282-0d03-45f0-93a9-e7a61e66d011", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39965", "nomdmonddf"=>"1",
Jul 19 10:48:41 node-2 nailgun-agent:  "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.892234 #13477] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.892304 #13477] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.892336 #13477] DEBUG -- : Device dm-3 seems to be appropriate
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.892371 #13477] DEBUG -- : Getting udev properties for device: dm-4
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.896087 #13477] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-XTwWzdtWcaAeqDqKuecdGA8dogSIkyMxHqiH5gv1LewsrH02eZ02yHjej6vZqfOj /dev/disk/by-uuid/df36a39e-30e8-4e0f-8c70-f39eae5d6ecd /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-XTwWzdtWcaAeqDqKuecdGA8dogSIkyMxHqiH5gv1LewsrH02eZ02yHjej6vZqfOj", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"df36a39e-30e8-4e0f-8c70-f39eae5d6ecd", "ID_FS_UUID_ENC"=>"df36a39e-30e8-4e0f-8c70-f39eae5d6ecd", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"38418", "nomdmonddf"=>"1", "nom
Jul 19 10:48:41 node-2 nailgun-agent: dmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.896147 #13477] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.896216 #13477] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.896250 #13477] DEBUG -- : Device dm-4 seems to be appropriate
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.896283 #13477] DEBUG -- : Getting udev properties for device: dm-5
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.900267 #13477] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-XTwWzdtWcaAeqDqKuecdGA8dogSIkyMxbaRIYwG9AkS6rS5gNzxenKSta4Y7He9j /dev/disk/by-uuid/a0e3ae02-41b9-4721-98b2-5873cdf3fed2 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-XTwWzdtWcaAeqDqKuecdGA8dogSIkyMxbaRIYwG9AkS6rS5gNzxenKSta4Y7He9j", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"a0e3ae02-41b9-4721-98b2-5873cdf3fed2", "ID_FS_UUID_ENC"=>"a0e3ae02-41b9-4721-98b2-5873cdf3fed2", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"38835", "nomdmonddf"=>"1", "nomdmonisw
Jul 19 10:48:41 node-2 nailgun-agent: "=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.900334 #13477] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.900413 #13477] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.900448 #13477] DEBUG -- : Device dm-5 seems to be appropriate
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.900487 #13477] DEBUG -- : Getting udev properties for device: ram0
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.903840 #13477] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"10", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.903904 #13477] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.903982 #13477] DEBUG -- : Device ram0 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.904029 #13477] DEBUG -- : Getting udev properties for device: ram1
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.908097 #13477] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"19", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.908161 #13477] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.908235 #13477] DEBUG -- : Device ram1 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.908283 #13477] DEBUG -- : Getting udev properties for device: ram2
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.911878 #13477] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"92", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.911940 #13477] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.912013 #13477] DEBUG -- : Device ram2 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.912058 #13477] DEBUG -- : Getting udev properties for device: ram3
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.915235 #13477] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"104", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.915296 #13477] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.915372 #13477] DEBUG -- : Device ram3 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.915417 #13477] DEBUG -- : Getting udev properties for device: ram4
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.919024 #13477] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"116", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.919086 #13477] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.919158 #13477] DEBUG -- : Device ram4 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.919205 #13477] DEBUG -- : Getting udev properties for device: ram5
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.922397 #13477] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"131", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.922459 #13477] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.922532 #13477] DEBUG -- : Device ram5 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.922578 #13477] DEBUG -- : Getting udev properties for device: ram6
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.926152 #13477] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"143", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.926217 #13477] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.926296 #13477] DEBUG -- : Device ram6 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.926346 #13477] DEBUG -- : Getting udev properties for device: ram7
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.929709 #13477] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"153", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.929775 #13477] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.929856 #13477] DEBUG -- : Device ram7 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.929905 #13477] DEBUG -- : Getting udev properties for device: ram8
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.933263 #13477] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"169", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.933328 #13477] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.933406 #13477] DEBUG -- : Device ram8 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.933453 #13477] DEBUG -- : Getting udev properties for device: ram9
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.937287 #13477] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"181", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.937345 #13477] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.937415 #13477] DEBUG -- : Device ram9 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.937458 #13477] DEBUG -- : Getting udev properties for device: loop0
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.940435 #13477] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99933", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.940491 #13477] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.940558 #13477] DEBUG -- : Device loop0 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.940602 #13477] DEBUG -- : Getting udev properties for device: loop1
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.943636 #13477] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99944", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.943694 #13477] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.943761 #13477] DEBUG -- : Device loop1 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.943806 #13477] DEBUG -- : Getting udev properties for device: loop2
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.946861 #13477] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99954", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.946917 #13477] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.946984 #13477] DEBUG -- : Device loop2 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.947026 #13477] DEBUG -- : Getting udev properties for device: loop3
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.950077 #13477] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99964", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.950138 #13477] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.950205 #13477] DEBUG -- : Device loop3 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.950247 #13477] DEBUG -- : Getting udev properties for device: loop4
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.953515 #13477] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99973", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.953574 #13477] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.953642 #13477] DEBUG -- : Device loop4 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.953686 #13477] DEBUG -- : Getting udev properties for device: loop5
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.956741 #13477] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99982", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.956799 #13477] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.956869 #13477] DEBUG -- : Device loop5 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.956912 #13477] DEBUG -- : Getting udev properties for device: loop6
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.960282 #13477] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99990", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.960336 #13477] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.960398 #13477] DEBUG -- : Device loop6 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.960440 #13477] DEBUG -- : Getting udev properties for device: loop7
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.963397 #13477] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99997", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.963453 #13477] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.963520 #13477] DEBUG -- : Device loop7 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.963581 #13477] DEBUG -- : Getting udev properties for device: ram10
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.966903 #13477] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"27", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.966956 #13477] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.967023 #13477] DEBUG -- : Device ram10 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.967063 #13477] DEBUG -- : Getting udev properties for device: ram11
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.969922 #13477] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"35", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.969975 #13477] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.970038 #13477] DEBUG -- : Device ram11 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.970081 #13477] DEBUG -- : Getting udev properties for device: ram12
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.973548 #13477] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.973611 #13477] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.973687 #13477] DEBUG -- : Device ram12 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.973735 #13477] DEBUG -- : Getting udev properties for device: ram13
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.976915 #13477] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.976976 #13477] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.977056 #13477] DEBUG -- : Device ram13 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.977104 #13477] DEBUG -- : Getting udev properties for device: ram14
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.980744 #13477] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.980809 #13477] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.980887 #13477] DEBUG -- : Device ram14 removable parameter: "0"
Jul 19 10:48:41 node-2 nailgun-agent: D, [2016-07-19T10:48:41.980934 #13477] DEBUG -- : Getting udev properties for device: ram15
Jul 19 10:48:42 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984414 #13477] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984472 #13477] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984540 #13477] DEBUG -- : Device ram15 removable parameter: "0"
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984616 #13477] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:07:00.0-scsi-0:0:0:0", :extra=>["disk/by-id/wwn-0x600508b1001ce878a70d81a7384b3866", "disk/by-id/scsi-3600508b1001ce878a70d81a7384b3866"], :removable=>"0"}]
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984647 #13477] DEBUG -- : Block device seems to be physical data storage: sda
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984708 #13477] DEBUG -- : Found block device: dm-0
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984741 #13477] DEBUG -- : Block device info: {"size"=>"1071603712", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984771 #13477] DEBUG -- : Found block device: dm-1
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984797 #13477] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984820 #13477] DEBUG -- : Found block device: dm-2
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984844 #13477] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984864 #13477] DEBUG -- : Found block device: dm-3
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984886 #13477] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984908 #13477] DEBUG -- : Found block device: dm-4
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984931 #13477] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984951 #13477] DEBUG -- : Found block device: dm-5
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984975 #13477] DEBUG -- : Block device info: {"size"=>"8388608", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.984994 #13477] DEBUG -- : Found block device: ram0
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985017 #13477] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985036 #13477] DEBUG -- : Found block device: ram1
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985059 #13477] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985080 #13477] DEBUG -- : Found block device: ram2
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985102 #13477] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985123 #13477] DEBUG -- : Found block device: ram3
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985145 #13477] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985163 #13477] DEBUG -- : Found block device: ram4
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985185 #13477] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985206 #13477] DEBUG -- : Found block device: ram5
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985226 #13477] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985245 #13477] DEBUG -- : Found block device: ram6
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985265 #13477] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985287 #13477] DEBUG -- : Found block device: ram7
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985307 #13477] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985327 #13477] DEBUG -- : Found block device: ram8
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985351 #13477] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985372 #13477] DEBUG -- : Found block device: ram9
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985394 #13477] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985414 #13477] DEBUG -- : Found block device: loop0
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985438 #13477] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985456 #13477] DEBUG -- : Found block device: loop1
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985480 #13477] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985501 #13477] DEBUG -- : Found block device: loop2
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985523 #13477] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985543 #13477] DEBUG -- : Found block device: loop3
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985566 #13477] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985584 #13477] DEBUG -- : Found block device: loop4
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985607 #13477] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985627 #13477] DEBUG -- : Found block device: loop5
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985650 #13477] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985669 #13477] DEBUG -- : Found block device: loop6
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985690 #13477] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985710 #13477] DEBUG -- : Found block device: loop7
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985732 #13477] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985751 #13477] DEBUG -- : Found block device: ram10
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985776 #13477] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985796 #13477] DEBUG -- : Found block device: ram11
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985817 #13477] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985837 #13477] DEBUG -- : Found block device: ram12
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985862 #13477] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985882 #13477] DEBUG -- : Found block device: ram13
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985903 #13477] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985923 #13477] DEBUG -- : Found block device: ram14
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985944 #13477] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985963 #13477] DEBUG -- : Found block device: ram15
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.985984 #13477] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:41.986042 #13477] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"LOGICAL VOLUME", :size=>1200186417152, :disk=>"disk/by-path/pci-0000:07:00.0-scsi-0:0:0:0", :extra=>["disk/by-id/wwn-0x600508b1001ce878a70d81a7384b3866", "disk/by-id/scsi-3600508b1001ce878a70d81a7384b3866"], :removable=>"0", :paths=>nil}]
Jul 19 10:48:42 node-2 nailgun-agent: D, [2016-07-19T10:48:42.335490 #13477] DEBUG -- : Response: status: 200 body: {"id": 2}
Jul 19 10:48:42 node-2 nailgun-agent: I, [2016-07-19T10:48:42.335988 #13477]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 19 10:49:01 node-2 CRON[15520]: (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 19 10:49:09 node-2 puppet-user[15550]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 19 10:49:09 node-2 puppet-user[15550]: Compiled catalog for node-2.opnfvericsson.ca in environment production in 0.11 seconds
Jul 19 10:49:09 node-2 puppet-user[15550]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 19 10:49:09 node-2 puppet-user[15550]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/bgpvpn", "plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Jul 19 10:49:09 node-2 puppet-user[15550]: Finished catalog run in 0.08 seconds
Jul 19 10:49:11 node-2 puppet-user[16151]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 19 10:49:12 node-2 puppet-user[16151]: Compiled catalog for node-2.opnfvericsson.ca in environment production in 1.14 seconds
Jul 19 10:49:13 node-2 puppet-user[16151]: (/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 19 10:49:13 node-2 puppet-user[16151]: (/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 19 10:49:13 node-2 puppet-user[16151]: (/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 19 10:49:13 node-2 puppet-user[16151]: (/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 19 10:49:13 node-2 puppet-user[16151]: (/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 19 10:49:13 node-2 puppet-user[16151]: (/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 19 10:49:13 node-2 puppet-user[16151]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 19 10:49:13 node-2 puppet-user[16151]: (/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 19 10:49:13 node-2 puppet-user[16151]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 19 10:49:13 node-2 puppet-user[16151]: (/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 19 10:49:13 node-2 puppet-user[16151]: (/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 19 10:49:13 node-2 puppet-user[16151]: (/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 19 10:49:13 node-2 puppet-user[16151]: (/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 19 10:49:13 node-2 puppet-user[16151]: (/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 19 10:49:13 node-2 puppet-user[16151]: (/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 19 10:49:13 node-2 puppet-user[16151]: (/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 19 10:49:27 node-2 puppet-user[16151]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 19 10:49:27 node-2 puppet-user[16151]: Finished catalog run in 14.26 seconds
Jul 19 10:49:29 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 19 10:49:29 node-2 nailgun-agent: I, [2016-07-19T10:49:29.572007 #15523]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 19 10:49:29 node-2 puppet-user[17041]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 19 10:49:29 node-2 puppet-user[17041]: Compiled catalog for node-2.opnfvericsson.ca in environment production in 0.14 seconds
Jul 19 10:49:33 node-2 puppet-user[17041]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 19 10:49:41 node-2 puppet-user[17041]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 19 10:49:42 node-2 puppet-user[17041]: Finished catalog run in 11.85 seconds
Jul 19 10:49:44 node-2 puppet-user[19338]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 19 10:49:44 node-2 puppet-user[19338]: Compiled catalog for node-2.opnfvericsson.ca in environment production in 0.60 seconds
Jul 19 10:49:44 node-2 puppet-user[19338]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 19 10:49:44 node-2 puppet-user[19338]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 19 10:49:44 node-2 puppet-user[19338]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 19 10:49:44 node-2 puppet-user[19338]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 19 10:49:44 node-2 puppet-user[19338]: Finished catalog run in 0.05 seconds
Jul 19 10:49:47 node-2 puppet-user[19944]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 19 10:49:47 node-2 puppet-user[19944]: Compiled catalog for node-2.opnfvericsson.ca in environment production in 0.83 seconds
Jul 19 10:49:48 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 19 10:49:48 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 19 10:49:48 node-2 crontab[20523]: (root) LIST (root)
Jul 19 10:49:48 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 19 10:49:48 node-2 crontab[20524]: (root) REPLACE (root)
Jul 19 10:49:49 node-2 puppet-user[19944]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/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 19 10:49:50 node-2 puppet-user[19944]: (/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 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/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 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/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 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/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 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/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 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/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 19 10:49:50 node-2 puppet-user[19944]: (/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 19 10:49:50 node-2 puppet-user[19944]: (/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 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/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 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/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 19 10:49:50 node-2 puppet-user[19944]: (/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 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 19 10:49:50 node-2 puppet-user[19944]: (/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 19 10:49:50 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8814" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 19 10:49:50 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 19 10:49:52 node-2 multipathd: uevent trigger error
<27>Jul 19 10:49:52 node-2 multipathd: uevent trigger error
<27>Jul 19 10:49:52 node-2 multipathd: uevent trigger error
<27>Jul 19 10:49:52 node-2 multipathd: uevent trigger error
<27>Jul 19 10:49:52 node-2 multipathd: uevent trigger error
<27>Jul 19 10:50:08 node-2 multipathd: uevent trigger error
<27>Jul 19 10:50:08 node-2 multipathd: uevent trigger error
<27>Jul 19 10:50:08 node-2 multipathd: uevent trigger error
<27>Jul 19 10:50:08 node-2 multipathd: uevent trigger error
<27>Jul 19 10:50:08 node-2 multipathd: uevent trigger error
<27>Jul 19 10:50:08 node-2 multipathd: uevent trigger error
<27>Jul 19 10:50:11 node-2 multipathd: uevent trigger error
<27>Jul 19 10:50:11 node-2 multipathd: uevent trigger error
<27>Jul 19 10:50:11 node-2 multipathd: uevent trigger error
<27>Jul 19 10:50:11 node-2 multipathd: uevent trigger error
<27>Jul 19 10:50:11 node-2 multipathd: uevent trigger error
<27>Jul 19 10:50:14 node-2 multipathd: uevent trigger error
<27>Jul 19 10:50:14 node-2 multipathd: uevent trigger error
<27>Jul 19 10:50:14 node-2 multipathd: uevent trigger error
<27>Jul 19 10:50:14 node-2 multipathd: uevent trigger error
<27>Jul 19 10:50:14 node-2 multipathd: uevent trigger error
<27>Jul 19 10:51:09 node-2 ntpdate[31685]: no servers can be used, exiting
<27>Jul 19 10:51:53 node-2 multipathd: uevent trigger error
<27>Jul 19 10:51:53 node-2 multipathd: uevent trigger error
<27>Jul 19 10:51:53 node-2 multipathd: uevent trigger error
<27>Jul 19 10:51:53 node-2 multipathd: uevent trigger error
<27>Jul 19 10:51:53 node-2 multipathd: uevent trigger error
<27>Jul 19 10:51:57 node-2 multipathd: uevent trigger error
<27>Jul 19 10:51:57 node-2 multipathd: uevent trigger error
<27>Jul 19 10:51:57 node-2 multipathd: uevent trigger error
<27>Jul 19 10:51:57 node-2 multipathd: uevent trigger error
<27>Jul 19 10:51:57 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:09 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:09 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:09 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:09 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:09 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:12 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:12 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:12 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:12 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:12 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:54 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:54 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:54 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:54 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:54 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:54 node-2 multipathd: uevent trigger error
<27>Jul 19 10:52:55 node-2 ocf-ns_vrouter: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 19 10:53:03 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:03 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:03 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:03 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:03 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:06 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 19 10:53:06 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 19 10:53:11 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 19 10:53:11 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 19 10:53:17 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 19 10:53:22 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 19 10:53:23 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 19 10:53:30 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:30 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:30 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:30 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:30 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:42 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:42 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:42 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:42 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:42 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:48 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:48 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:48 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:48 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:48 node-2 multipathd: uevent trigger error
<129>Jul 19 10:53:50 node-2 haproxy[4667]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:53:50 node-2 haproxy[4667]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:53:51 node-2 haproxy[4671]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:53:51 node-2 haproxy[4671]: proxy mysqld has no server available!
<27>Jul 19 10:53:53 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:53 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:53 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:53 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:53 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:57 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:57 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:57 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:57 node-2 multipathd: uevent trigger error
<27>Jul 19 10:53:57 node-2 multipathd: uevent trigger error
<129>Jul 19 10:53:59 node-2 haproxy[7400]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:00 node-2 haproxy[7404]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:00 node-2 haproxy[7404]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:00 node-2 haproxy[7404]: proxy mysqld has no server available!
<129>Jul 19 10:54:00 node-2 haproxy[7404]: 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 19 10:54:00 node-2 haproxy[7404]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:01 node-2 haproxy[7404]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:01 node-2 haproxy[7404]: proxy object-storage has no server available!
<27>Jul 19 10:54:03 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:03 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:03 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:03 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:03 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:03 node-2 multipathd: uevent trigger error
<129>Jul 19 10:54:05 node-2 haproxy[8858]: 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 19 10:54:05 node-2 haproxy[8858]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:06 node-2 haproxy[8862]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:06 node-2 haproxy[8862]: proxy neutron has no server available!
<129>Jul 19 10:54:06 node-2 haproxy[8862]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:06 node-2 haproxy[8862]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:06 node-2 haproxy[8862]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:06 node-2 haproxy[8862]: proxy mysqld has no server available!
<129>Jul 19 10:54:06 node-2 haproxy[8862]: 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 19 10:54:06 node-2 haproxy[8862]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:07 node-2 haproxy[8862]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:07 node-2 haproxy[8862]: proxy object-storage has no server available!
<27>Jul 19 10:54:09 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:09 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:09 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:09 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:09 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:09 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:09 node-2 multipathd: uevent trigger error
<129>Jul 19 10:54:11 node-2 haproxy[10491]: Server keystone-1/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 19 10:54:11 node-2 haproxy[10491]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:11 node-2 haproxy[10491]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:11 node-2 haproxy[10491]: proxy keystone-1 has no server available!
<129>Jul 19 10:54:11 node-2 haproxy[10491]: Server keystone-2/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 19 10:54:12 node-2 haproxy[10495]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:12 node-2 haproxy[10495]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:12 node-2 haproxy[10495]: proxy keystone-2 has no server available!
<129>Jul 19 10:54:12 node-2 haproxy[10495]: 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 19 10:54:12 node-2 haproxy[10495]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:12 node-2 haproxy[10495]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:12 node-2 haproxy[10495]: proxy neutron has no server available!
<129>Jul 19 10:54:12 node-2 haproxy[10495]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:12 node-2 haproxy[10495]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:12 node-2 haproxy[10495]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:12 node-2 haproxy[10495]: proxy mysqld has no server available!
<129>Jul 19 10:54:13 node-2 haproxy[10495]: 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 19 10:54:13 node-2 haproxy[10495]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:13 node-2 haproxy[10495]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:13 node-2 haproxy[10495]: proxy object-storage has no server available!
<27>Jul 19 10:54:15 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:15 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:15 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:15 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:15 node-2 multipathd: uevent trigger error
<129>Jul 19 10:54:17 node-2 haproxy[11956]: Server keystone-1/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 19 10:54:17 node-2 haproxy[11956]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:17 node-2 haproxy[11956]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:17 node-2 haproxy[11956]: proxy keystone-1 has no server available!
<129>Jul 19 10:54:17 node-2 haproxy[11956]: Server keystone-2/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 19 10:54:17 node-2 haproxy[11956]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:17 node-2 haproxy[11956]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:17 node-2 haproxy[11956]: proxy keystone-2 has no server available!
<129>Jul 19 10:54:17 node-2 haproxy[11956]: 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 19 10:54:17 node-2 haproxy[11956]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:18 node-2 haproxy[11960]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:18 node-2 haproxy[11960]: proxy neutron has no server available!
<129>Jul 19 10:54:18 node-2 haproxy[11960]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:18 node-2 haproxy[11960]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:18 node-2 haproxy[11960]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:18 node-2 haproxy[11960]: proxy mysqld has no server available!
<129>Jul 19 10:54:18 node-2 haproxy[11960]: 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 19 10:54:18 node-2 haproxy[11960]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:18 node-2 haproxy[11960]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:18 node-2 haproxy[11960]: proxy object-storage has no server available!
<129>Jul 19 10:54:18 node-2 haproxy[11960]: 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 19 10:54:18 node-2 haproxy[11960]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:18 node-2 haproxy[11960]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:18 node-2 haproxy[11960]: proxy aodh has no server available!
<27>Jul 19 10:54:20 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:20 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:20 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:20 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:20 node-2 multipathd: uevent trigger error
<129>Jul 19 10:54:22 node-2 haproxy[13386]: Server keystone-1/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 19 10:54:22 node-2 haproxy[13386]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:22 node-2 haproxy[13386]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:22 node-2 haproxy[13386]: proxy keystone-1 has no server available!
<129>Jul 19 10:54:23 node-2 haproxy[13390]: Server keystone-2/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 19 10:54:23 node-2 haproxy[13390]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:23 node-2 haproxy[13390]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:23 node-2 haproxy[13390]: proxy keystone-2 has no server available!
<129>Jul 19 10:54:23 node-2 haproxy[13390]: 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 19 10:54:23 node-2 haproxy[13390]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:23 node-2 haproxy[13390]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:23 node-2 haproxy[13390]: proxy neutron has no server available!
<129>Jul 19 10:54:23 node-2 haproxy[13390]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:23 node-2 haproxy[13390]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:23 node-2 haproxy[13390]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:23 node-2 haproxy[13390]: proxy mysqld has no server available!
<129>Jul 19 10:54:23 node-2 haproxy[13390]: 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 19 10:54:23 node-2 haproxy[13390]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:24 node-2 haproxy[13390]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:24 node-2 haproxy[13390]: proxy object-storage has no server available!
<129>Jul 19 10:54:24 node-2 haproxy[13390]: 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 19 10:54:24 node-2 haproxy[13390]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:24 node-2 haproxy[13390]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:24 node-2 haproxy[13390]: proxy aodh has no server available!
<129>Jul 19 10:54:24 node-2 haproxy[13390]: 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 19 10:54:24 node-2 haproxy[13390]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:24 node-2 haproxy[13390]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:24 node-2 haproxy[13390]: proxy ceilometer has no server available!
<27>Jul 19 10:54:26 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:26 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:26 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:26 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:26 node-2 multipathd: uevent trigger error
<129>Jul 19 10:54:28 node-2 haproxy[14851]: Server keystone-1/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 19 10:54:28 node-2 haproxy[14851]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:28 node-2 haproxy[14851]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:28 node-2 haproxy[14851]: proxy keystone-1 has no server available!
<129>Jul 19 10:54:28 node-2 haproxy[14851]: Server keystone-2/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 19 10:54:28 node-2 haproxy[14851]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:28 node-2 haproxy[14851]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:28 node-2 haproxy[14851]: proxy keystone-2 has no server available!
<129>Jul 19 10:54:28 node-2 haproxy[14851]: 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 19 10:54:29 node-2 haproxy[14855]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:29 node-2 haproxy[14855]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:29 node-2 haproxy[14855]: proxy neutron has no server available!
<129>Jul 19 10:54:29 node-2 haproxy[14855]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:29 node-2 haproxy[14855]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:29 node-2 haproxy[14855]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:29 node-2 haproxy[14855]: proxy mysqld has no server available!
<129>Jul 19 10:54:29 node-2 haproxy[14855]: 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 19 10:54:29 node-2 haproxy[14855]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:29 node-2 haproxy[14855]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:29 node-2 haproxy[14855]: proxy object-storage has no server available!
<129>Jul 19 10:54:29 node-2 haproxy[14855]: 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 19 10:54:29 node-2 haproxy[14855]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:29 node-2 haproxy[14855]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:29 node-2 haproxy[14855]: proxy aodh has no server available!
<129>Jul 19 10:54:30 node-2 haproxy[14855]: 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 19 10:54:30 node-2 haproxy[14855]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:30 node-2 haproxy[14855]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:30 node-2 haproxy[14855]: proxy ceilometer has no server available!
<27>Jul 19 10:54:31 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:31 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:31 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:31 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:31 node-2 multipathd: uevent trigger error
<129>Jul 19 10:54:33 node-2 haproxy[16303]: Server horizon/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 19 10:54:34 node-2 haproxy[16322]: Server horizon/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:34 node-2 haproxy[16322]: Server keystone-1/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 19 10:54:34 node-2 haproxy[16322]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:34 node-2 haproxy[16322]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:34 node-2 haproxy[16322]: proxy keystone-1 has no server available!
<129>Jul 19 10:54:34 node-2 haproxy[16322]: Server keystone-2/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 19 10:54:34 node-2 haproxy[16322]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:34 node-2 haproxy[16322]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:34 node-2 haproxy[16322]: proxy keystone-2 has no server available!
<129>Jul 19 10:54:34 node-2 haproxy[16322]: 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 19 10:54:34 node-2 haproxy[16322]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:34 node-2 haproxy[16322]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:34 node-2 haproxy[16322]: proxy neutron has no server available!
<129>Jul 19 10:54:34 node-2 haproxy[16322]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:34 node-2 haproxy[16322]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:34 node-2 haproxy[16322]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:34 node-2 haproxy[16322]: proxy mysqld has no server available!
<129>Jul 19 10:54:35 node-2 haproxy[16322]: 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 19 10:54:35 node-2 haproxy[16322]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:35 node-2 haproxy[16322]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:35 node-2 haproxy[16322]: proxy object-storage has no server available!
<129>Jul 19 10:54:35 node-2 haproxy[16322]: 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 19 10:54:35 node-2 haproxy[16322]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:35 node-2 haproxy[16322]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:35 node-2 haproxy[16322]: proxy aodh has no server available!
<129>Jul 19 10:54:35 node-2 haproxy[16322]: 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 19 10:54:35 node-2 haproxy[16322]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:35 node-2 haproxy[16322]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:35 node-2 haproxy[16322]: proxy ceilometer has no server available!
<27>Jul 19 10:54:37 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:37 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:37 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:37 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:37 node-2 multipathd: uevent trigger error
<129>Jul 19 10:54:40 node-2 haproxy[18060]: Server horizon/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 19 10:54:40 node-2 haproxy[18060]: Server horizon/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:40 node-2 haproxy[18060]: Server keystone-1/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 19 10:54:40 node-2 haproxy[18060]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:40 node-2 haproxy[18060]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:40 node-2 haproxy[18060]: proxy keystone-1 has no server available!
<129>Jul 19 10:54:40 node-2 haproxy[18060]: Server keystone-2/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 19 10:54:40 node-2 haproxy[18060]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:40 node-2 haproxy[18060]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:40 node-2 haproxy[18060]: proxy keystone-2 has no server available!
<129>Jul 19 10:54:40 node-2 haproxy[18060]: 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 19 10:54:40 node-2 haproxy[18060]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:40 node-2 haproxy[18060]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:40 node-2 haproxy[18060]: proxy glance-api has no server available!
<129>Jul 19 10:54:40 node-2 haproxy[18060]: 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 19 10:54:40 node-2 haproxy[18060]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:40 node-2 haproxy[18060]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:40 node-2 haproxy[18060]: proxy glance-glare has no server available!
<129>Jul 19 10:54:41 node-2 haproxy[18069]: 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 19 10:54:41 node-2 haproxy[18069]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:41 node-2 haproxy[18069]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:41 node-2 haproxy[18069]: proxy neutron has no server available!
<129>Jul 19 10:54:41 node-2 haproxy[18069]: 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 19 10:54:41 node-2 haproxy[18069]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:41 node-2 haproxy[18069]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:41 node-2 haproxy[18069]: proxy glance-registry has no server available!
<129>Jul 19 10:54:41 node-2 haproxy[18069]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:41 node-2 haproxy[18069]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:41 node-2 haproxy[18069]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:41 node-2 haproxy[18069]: proxy mysqld has no server available!
<129>Jul 19 10:54:41 node-2 haproxy[18069]: 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 19 10:54:41 node-2 haproxy[18069]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:41 node-2 haproxy[18069]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:41 node-2 haproxy[18069]: proxy object-storage has no server available!
<129>Jul 19 10:54:41 node-2 haproxy[18069]: 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 19 10:54:41 node-2 haproxy[18069]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:41 node-2 haproxy[18069]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:41 node-2 haproxy[18069]: proxy aodh has no server available!
<129>Jul 19 10:54:41 node-2 haproxy[18069]: 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 19 10:54:41 node-2 haproxy[18069]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:42 node-2 haproxy[18069]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:42 node-2 haproxy[18069]: proxy ceilometer has no server available!
<27>Jul 19 10:54:43 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:43 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:43 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:43 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:43 node-2 multipathd: uevent trigger error
<129>Jul 19 10:54:46 node-2 haproxy[19539]: Server horizon/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 19 10:54:46 node-2 haproxy[19539]: Server horizon/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:46 node-2 haproxy[19539]: Server keystone-1/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 19 10:54:46 node-2 haproxy[19539]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:46 node-2 haproxy[19539]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:46 node-2 haproxy[19539]: proxy keystone-1 has no server available!
<129>Jul 19 10:54:46 node-2 haproxy[19539]: Server keystone-2/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 19 10:54:46 node-2 haproxy[19539]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:46 node-2 haproxy[19539]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:46 node-2 haproxy[19539]: proxy keystone-2 has no server available!
<129>Jul 19 10:54:46 node-2 haproxy[19539]: 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 19 10:54:46 node-2 haproxy[19539]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:47 node-2 haproxy[19545]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:47 node-2 haproxy[19545]: proxy nova-api has no server available!
<129>Jul 19 10:54:47 node-2 haproxy[19545]: 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 19 10:54:47 node-2 haproxy[19545]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:47 node-2 haproxy[19545]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:47 node-2 haproxy[19545]: proxy nova-metadata-api has no server available!
<129>Jul 19 10:54:47 node-2 haproxy[19545]: 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 19 10:54:47 node-2 haproxy[19545]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:47 node-2 haproxy[19545]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:47 node-2 haproxy[19545]: proxy glance-api has no server available!
<129>Jul 19 10:54:47 node-2 haproxy[19545]: 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 19 10:54:47 node-2 haproxy[19545]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:47 node-2 haproxy[19545]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:47 node-2 haproxy[19545]: proxy glance-glare has no server available!
<129>Jul 19 10:54:47 node-2 haproxy[19545]: 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 19 10:54:47 node-2 haproxy[19545]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:47 node-2 haproxy[19545]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:47 node-2 haproxy[19545]: proxy neutron has no server available!
<129>Jul 19 10:54:47 node-2 haproxy[19545]: 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 19 10:54:47 node-2 haproxy[19545]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:47 node-2 haproxy[19545]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:47 node-2 haproxy[19545]: proxy glance-registry has no server available!
<129>Jul 19 10:54:47 node-2 haproxy[19545]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:47 node-2 haproxy[19545]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:47 node-2 haproxy[19545]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:47 node-2 haproxy[19545]: proxy mysqld has no server available!
<129>Jul 19 10:54:47 node-2 haproxy[19545]: 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 19 10:54:47 node-2 haproxy[19545]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:47 node-2 haproxy[19545]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:47 node-2 haproxy[19545]: proxy object-storage has no server available!
<129>Jul 19 10:54:47 node-2 haproxy[19545]: 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 19 10:54:48 node-2 haproxy[19545]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:48 node-2 haproxy[19545]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:48 node-2 haproxy[19545]: proxy aodh has no server available!
<129>Jul 19 10:54:48 node-2 haproxy[19545]: 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 19 10:54:48 node-2 haproxy[19545]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:48 node-2 haproxy[19545]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:48 node-2 haproxy[19545]: proxy ceilometer has no server available!
<129>Jul 19 10:54:48 node-2 haproxy[19545]: 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 19 10:54:48 node-2 haproxy[19545]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:48 node-2 haproxy[19545]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:48 node-2 haproxy[19545]: proxy nova-novncproxy has no server available!
<27>Jul 19 10:54:49 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:49 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:49 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:49 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:49 node-2 multipathd: uevent trigger error
<129>Jul 19 10:54:52 node-2 haproxy[20967]: Server horizon/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 19 10:54:52 node-2 haproxy[20967]: Server horizon/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:52 node-2 haproxy[20967]: Server keystone-1/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 19 10:54:52 node-2 haproxy[20967]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:52 node-2 haproxy[20967]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:52 node-2 haproxy[20967]: proxy keystone-1 has no server available!
<129>Jul 19 10:54:52 node-2 haproxy[20967]: Server keystone-2/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 19 10:54:52 node-2 haproxy[20967]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:52 node-2 haproxy[20967]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:52 node-2 haproxy[20967]: proxy keystone-2 has no server available!
<129>Jul 19 10:54:52 node-2 haproxy[20967]: 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 19 10:54:52 node-2 haproxy[20967]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:52 node-2 haproxy[20967]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:52 node-2 haproxy[20967]: proxy nova-api has no server available!
<129>Jul 19 10:54:52 node-2 haproxy[20967]: 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 19 10:54:52 node-2 haproxy[20967]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:52 node-2 haproxy[20967]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:52 node-2 haproxy[20967]: proxy nova-metadata-api has no server available!
<129>Jul 19 10:54:52 node-2 haproxy[20967]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:52 node-2 haproxy[20967]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:52 node-2 haproxy[20967]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:52 node-2 haproxy[20967]: proxy cinder-api has no server available!
<129>Jul 19 10:54:52 node-2 haproxy[20967]: 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 19 10:54:53 node-2 haproxy[20981]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:53 node-2 haproxy[20981]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:53 node-2 haproxy[20981]: proxy glance-api has no server available!
<129>Jul 19 10:54:53 node-2 haproxy[20981]: 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 19 10:54:53 node-2 haproxy[20981]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:53 node-2 haproxy[20981]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:53 node-2 haproxy[20981]: proxy glance-glare has no server available!
<129>Jul 19 10:54:53 node-2 haproxy[20981]: 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 19 10:54:53 node-2 haproxy[20981]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:53 node-2 haproxy[20981]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:53 node-2 haproxy[20981]: proxy neutron has no server available!
<129>Jul 19 10:54:53 node-2 haproxy[20981]: 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 19 10:54:53 node-2 haproxy[20981]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:53 node-2 haproxy[20981]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:53 node-2 haproxy[20981]: proxy glance-registry has no server available!
<129>Jul 19 10:54:53 node-2 haproxy[20981]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:53 node-2 haproxy[20981]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:53 node-2 haproxy[20981]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:53 node-2 haproxy[20981]: proxy mysqld has no server available!
<129>Jul 19 10:54:53 node-2 haproxy[20981]: 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 19 10:54:53 node-2 haproxy[20981]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:53 node-2 haproxy[20981]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:53 node-2 haproxy[20981]: proxy object-storage has no server available!
<129>Jul 19 10:54:53 node-2 haproxy[20981]: 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 19 10:54:53 node-2 haproxy[20981]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:53 node-2 haproxy[20981]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:53 node-2 haproxy[20981]: proxy aodh has no server available!
<129>Jul 19 10:54:53 node-2 haproxy[20981]: 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 19 10:54:53 node-2 haproxy[20981]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:53 node-2 haproxy[20981]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:53 node-2 haproxy[20981]: proxy ceilometer has no server available!
<129>Jul 19 10:54:53 node-2 haproxy[20981]: 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 19 10:54:54 node-2 haproxy[20981]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:54 node-2 haproxy[20981]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:54 node-2 haproxy[20981]: proxy nova-novncproxy has no server available!
<27>Jul 19 10:54:55 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:55 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:55 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:55 node-2 multipathd: uevent trigger error
<27>Jul 19 10:54:55 node-2 multipathd: uevent trigger error
<129>Jul 19 10:54:58 node-2 haproxy[22472]: Server horizon/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 19 10:54:58 node-2 haproxy[22472]: Server horizon/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:58 node-2 haproxy[22472]: Server keystone-1/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 19 10:54:58 node-2 haproxy[22472]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:58 node-2 haproxy[22472]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:58 node-2 haproxy[22472]: proxy keystone-1 has no server available!
<129>Jul 19 10:54:58 node-2 haproxy[22472]: Server keystone-2/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 19 10:54:58 node-2 haproxy[22472]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:58 node-2 haproxy[22472]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:58 node-2 haproxy[22472]: proxy keystone-2 has no server available!
<129>Jul 19 10:54:58 node-2 haproxy[22472]: 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 19 10:54:58 node-2 haproxy[22472]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:58 node-2 haproxy[22472]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:58 node-2 haproxy[22472]: proxy nova-api has no server available!
<129>Jul 19 10:54:58 node-2 haproxy[22472]: 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 19 10:54:58 node-2 haproxy[22472]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:58 node-2 haproxy[22472]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:58 node-2 haproxy[22472]: proxy nova-metadata-api has no server available!
<129>Jul 19 10:54:58 node-2 haproxy[22472]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:58 node-2 haproxy[22472]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:58 node-2 haproxy[22472]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:58 node-2 haproxy[22472]: proxy cinder-api has no server available!
<129>Jul 19 10:54:58 node-2 haproxy[22472]: 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 19 10:54:58 node-2 haproxy[22472]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:59 node-2 haproxy[22476]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:59 node-2 haproxy[22476]: proxy glance-api has no server available!
<129>Jul 19 10:54:59 node-2 haproxy[22476]: 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 19 10:54:59 node-2 haproxy[22476]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:59 node-2 haproxy[22476]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:59 node-2 haproxy[22476]: proxy glance-glare has no server available!
<129>Jul 19 10:54:59 node-2 haproxy[22476]: 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 19 10:54:59 node-2 haproxy[22476]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:59 node-2 haproxy[22476]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:59 node-2 haproxy[22476]: proxy neutron has no server available!
<129>Jul 19 10:54:59 node-2 haproxy[22476]: 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 19 10:54:59 node-2 haproxy[22476]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:59 node-2 haproxy[22476]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:59 node-2 haproxy[22476]: proxy glance-registry has no server available!
<129>Jul 19 10:54:59 node-2 haproxy[22476]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:59 node-2 haproxy[22476]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:59 node-2 haproxy[22476]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:59 node-2 haproxy[22476]: proxy mysqld has no server available!
<129>Jul 19 10:54:59 node-2 haproxy[22476]: 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 19 10:54:59 node-2 haproxy[22476]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:59 node-2 haproxy[22476]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:59 node-2 haproxy[22476]: proxy object-storage has no server available!
<129>Jul 19 10:54:59 node-2 haproxy[22476]: 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 19 10:54:59 node-2 haproxy[22476]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:59 node-2 haproxy[22476]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:59 node-2 haproxy[22476]: proxy aodh has no server available!
<129>Jul 19 10:54:59 node-2 haproxy[22476]: 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 19 10:54:59 node-2 haproxy[22476]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:59 node-2 haproxy[22476]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:59 node-2 haproxy[22476]: proxy ceilometer has no server available!
<129>Jul 19 10:54:59 node-2 haproxy[22476]: 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 19 10:54:59 node-2 haproxy[22476]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:59 node-2 haproxy[22476]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:59 node-2 haproxy[22476]: proxy heat-api has no server available!
<129>Jul 19 10:54:59 node-2 haproxy[22476]: 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 19 10:54:59 node-2 haproxy[22476]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:54:59 node-2 haproxy[22476]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:54:59 node-2 haproxy[22476]: proxy heat-api-cfn has no server available!
<129>Jul 19 10:55:00 node-2 haproxy[22476]: 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 19 10:55:00 node-2 haproxy[22476]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:55:00 node-2 haproxy[22476]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:55:00 node-2 haproxy[22476]: proxy heat-api-cloudwatch has no server available!
<129>Jul 19 10:55:00 node-2 haproxy[22476]: 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 19 10:55:00 node-2 haproxy[22476]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 19 10:55:00 node-2 haproxy[22476]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 19 10:55:00 node-2 haproxy[22476]: proxy nova-novncproxy has no server available!
<27>Jul 19 10:55:01 node-2 multipathd: uevent trigger error
<27>Jul 19 10:55:01 node-2 multipathd: uevent trigger error
<27>Jul 19 10:55:01 node-2 multipathd: uevent trigger error
<27>Jul 19 10:55:01 node-2 multipathd: uevent trigger error
<27>Jul 19 10:55:01 node-2 multipathd: uevent trigger error
<27>Jul 19 10:55:01 node-2 multipathd: uevent trigger error
<27>Jul 19 10:55:05 node-2 multipathd: uevent trigger error
<27>Jul 19 10:55:05 node-2 multipathd: uevent trigger error
<27>Jul 19 10:55:05 node-2 multipathd: uevent trigger error
<27>Jul 19 10:55:05 node-2 multipathd: uevent trigger error
<27>Jul 19 10:55:05 node-2 multipathd: uevent trigger error
<27>Jul 19 10:55:13 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 19 10:55:33 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 19 10:55:35 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 19 10:56:05 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 19 10:56:12 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 19 10:56:31 node-2 multipathd: uevent trigger error
<27>Jul 19 10:56:31 node-2 multipathd: uevent trigger error
<27>Jul 19 10:56:31 node-2 multipathd: uevent trigger error
<27>Jul 19 10:56:31 node-2 multipathd: uevent trigger error
<27>Jul 19 10:56:31 node-2 multipathd: uevent trigger error
<27>Jul 19 10:56:31 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:00 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:00 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:00 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:00 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:00 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:00 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:06 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:06 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:06 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:06 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:06 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:06 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:08 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 19 10:59:11 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:11 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:11 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:11 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:11 node-2 multipathd: uevent trigger error
<43>Jul 19 10:59:21 node-2 apache2_error [Tue Jul 19 10:59:17.434779 2016] [mpm_event:notice] [pid 19551:tid 140585533671296] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 19 10:59:21 node-2 apache2_error [Tue Jul 19 10:59:17.434903 2016] [core:notice] [pid 19551:tid 140585533671296] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 19 10:59:21 node-2 apache2_error [Tue Jul 19 10:59:19.696877 2016] [mpm_event:notice] [pid 19551:tid 140585533671296] AH00491: caught SIGTERM, shutting down
<43>Jul 19 10:59:21 node-2 apache2_error [Tue Jul 19 10:59:20.799462 2016] [mpm_worker:notice] [pid 21372:tid 140470493255552] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 19 10:59:21 node-2 apache2_error [Tue Jul 19 10:59:20.799494 2016] [core:notice] [pid 21372:tid 140470493255552] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 19 10:59:25 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:25 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:25 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:25 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:25 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:28 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:28 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:29 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:29 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:29 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:32 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:32 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:32 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:32 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:32 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:32 node-2 multipathd: uevent trigger error
<27>Jul 19 10:59:32 node-2 multipathd: uevent trigger error
<43>Jul 19 11:00:11 node-2 apache2_error [Tue Jul 19 11:00:09.420501 2016] [mpm_worker:notice] [pid 21372:tid 140470493255552] AH00295: caught SIGTERM, shutting down
<43>Jul 19 11:00:11 node-2 apache2_error [Tue Jul 19 11:00:10.220041 2016] [mpm_worker:notice] [pid 32785:tid 140141749979008] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 19 11:00:11 node-2 apache2_error [Tue Jul 19 11:00:10.220074 2016] [core:notice] [pid 32785:tid 140141749979008] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 19 11:00:51 node-2 apache2_error [Tue Jul 19 11:00:46.920812 2016] [mpm_worker:notice] [pid 32785:tid 140141749979008] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 19 11:00:51 node-2 apache2_error [Tue Jul 19 11:00:47.119633 2016] [mpm_worker:warn] [pid 32785:tid 140141749979008] AH00317: MaxRequestWorkers of 12881 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 12875
<43>Jul 19 11:00:51 node-2 apache2_error [Tue Jul 19 11:00:47.123127 2016] [mpm_worker:notice] [pid 32785:tid 140141749979008] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 19 11:00:51 node-2 apache2_error [Tue Jul 19 11:00:47.123154 2016] [core:notice] [pid 32785:tid 140141749979008] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 19 11:01:45 node-2 multipathd: uevent trigger error
<27>Jul 19 11:01:45 node-2 multipathd: uevent trigger error
<27>Jul 19 11:01:45 node-2 multipathd: uevent trigger error
<27>Jul 19 11:01:45 node-2 multipathd: uevent trigger error
<27>Jul 19 11:01:45 node-2 multipathd: uevent trigger error
<27>Jul 19 11:01:50 node-2 multipathd: uevent trigger error
<27>Jul 19 11:01:50 node-2 multipathd: uevent trigger error
<27>Jul 19 11:01:50 node-2 multipathd: uevent trigger error
<27>Jul 19 11:01:50 node-2 multipathd: uevent trigger error
<27>Jul 19 11:01:50 node-2 multipathd: uevent trigger error
<27>Jul 19 11:01:55 node-2 multipathd: uevent trigger error
<27>Jul 19 11:01:55 node-2 multipathd: uevent trigger error
<27>Jul 19 11:01:55 node-2 multipathd: uevent trigger error
<27>Jul 19 11:01:55 node-2 multipathd: uevent trigger error
<27>Jul 19 11:01:55 node-2 multipathd: uevent trigger error
<27>Jul 19 11:02:09 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 19 11:02:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:02:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:02:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:02:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:02:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:02:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:02:41 node-2 multipathd: uevent trigger error
<27>Jul 19 11:02:41 node-2 multipathd: uevent trigger error
<27>Jul 19 11:02:41 node-2 multipathd: uevent trigger error
<27>Jul 19 11:02:41 node-2 multipathd: uevent trigger error
<27>Jul 19 11:02:41 node-2 multipathd: uevent trigger error
<27>Jul 19 11:02:46 node-2 multipathd: uevent trigger error
<27>Jul 19 11:02:46 node-2 multipathd: uevent trigger error
<27>Jul 19 11:02:46 node-2 multipathd: uevent trigger error
<27>Jul 19 11:02:46 node-2 multipathd: uevent trigger error
<27>Jul 19 11:02:46 node-2 multipathd: uevent trigger error
<27>Jul 19 11:03:03 node-2 multipathd: uevent trigger error
<27>Jul 19 11:03:03 node-2 multipathd: uevent trigger error
<27>Jul 19 11:03:03 node-2 multipathd: uevent trigger error
<27>Jul 19 11:03:04 node-2 multipathd: uevent trigger error
<27>Jul 19 11:03:04 node-2 multipathd: uevent trigger error
<27>Jul 19 11:03:47 node-2 multipathd: uevent trigger error
<27>Jul 19 11:03:47 node-2 multipathd: uevent trigger error
<27>Jul 19 11:03:47 node-2 multipathd: uevent trigger error
<27>Jul 19 11:03:47 node-2 multipathd: uevent trigger error
<27>Jul 19 11:03:47 node-2 multipathd: uevent trigger error
<27>Jul 19 11:04:51 node-2 multipathd: uevent trigger error
<27>Jul 19 11:04:51 node-2 multipathd: uevent trigger error
<27>Jul 19 11:04:51 node-2 multipathd: uevent trigger error
<27>Jul 19 11:04:51 node-2 multipathd: uevent trigger error
<27>Jul 19 11:04:51 node-2 multipathd: uevent trigger error
<27>Jul 19 11:04:51 node-2 multipathd: uevent trigger error
<27>Jul 19 11:05:11 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 19 11:05:31 node-2 multipathd: uevent trigger error
<27>Jul 19 11:05:31 node-2 multipathd: uevent trigger error
<27>Jul 19 11:05:31 node-2 multipathd: uevent trigger error
<27>Jul 19 11:05:31 node-2 multipathd: uevent trigger error
<27>Jul 19 11:05:31 node-2 multipathd: uevent trigger error
<27>Jul 19 11:05:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:05:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:05:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:05:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:05:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:05:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:05:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:06:11 node-2 multipathd: uevent trigger error
<27>Jul 19 11:06:11 node-2 multipathd: uevent trigger error
<27>Jul 19 11:06:11 node-2 multipathd: uevent trigger error
<27>Jul 19 11:06:11 node-2 multipathd: uevent trigger error
<27>Jul 19 11:06:11 node-2 multipathd: uevent trigger error
<27>Jul 19 11:06:17 node-2 multipathd: uevent trigger error
<27>Jul 19 11:06:17 node-2 multipathd: uevent trigger error
<27>Jul 19 11:06:17 node-2 multipathd: uevent trigger error
<27>Jul 19 11:06:17 node-2 multipathd: uevent trigger error
<27>Jul 19 11:06:17 node-2 multipathd: uevent trigger error
<27>Jul 19 11:06:17 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:09 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:09 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:09 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:09 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:09 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:09 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:13 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 19 11:08:25 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:25 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:25 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:25 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:25 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:38 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:38 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:38 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:38 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:38 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:38 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:44 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:44 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:44 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:44 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:44 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:50 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:50 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:50 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:50 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:50 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:50 node-2 multipathd: uevent trigger error
<27>Jul 19 11:08:50 node-2 multipathd: uevent trigger error
<27>Jul 19 11:09:15 node-2 multipathd: uevent trigger error
<27>Jul 19 11:09:15 node-2 multipathd: uevent trigger error
<27>Jul 19 11:09:15 node-2 multipathd: uevent trigger error
<27>Jul 19 11:09:15 node-2 multipathd: uevent trigger error
<27>Jul 19 11:09:15 node-2 multipathd: uevent trigger error
<27>Jul 19 11:09:19 node-2 multipathd: uevent trigger error
<27>Jul 19 11:09:19 node-2 multipathd: uevent trigger error
<27>Jul 19 11:09:19 node-2 multipathd: uevent trigger error
<27>Jul 19 11:09:19 node-2 multipathd: uevent trigger error
<27>Jul 19 11:09:19 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:03 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:03 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:03 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:03 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:03 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:26 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:26 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:26 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:26 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:26 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:26 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:26 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:26 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:42 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:42 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:42 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:42 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:42 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:10:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:11:15 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 19 11:13:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:13:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:13:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:13:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:13:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:13:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:13:22 node-2 multipathd: uevent trigger error
<27>Jul 19 11:13:22 node-2 multipathd: uevent trigger error
<27>Jul 19 11:13:22 node-2 multipathd: uevent trigger error
<27>Jul 19 11:13:38 node-2 multipathd: uevent trigger error
<27>Jul 19 11:13:38 node-2 multipathd: uevent trigger error
<27>Jul 19 11:13:38 node-2 multipathd: uevent trigger error
<27>Jul 19 11:13:38 node-2 multipathd: uevent trigger error
<27>Jul 19 11:13:38 node-2 multipathd: uevent trigger error
<27>Jul 19 11:13:38 node-2 multipathd: sda: spurious uevent, path already in pathvec
<27>Jul 19 11:14:16 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 19 11:14:55 node-2 multipathd: uevent trigger error
<27>Jul 19 11:14:55 node-2 multipathd: uevent trigger error
<27>Jul 19 11:14:55 node-2 multipathd: uevent trigger error
<27>Jul 19 11:14:55 node-2 multipathd: uevent trigger error
<27>Jul 19 11:14:55 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:01 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:01 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:01 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:01 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:01 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:37 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:37 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:37 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:37 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:37 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:41 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:41 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:41 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:41 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:41 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:46 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:46 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:46 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:46 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:46 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:58 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:58 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:58 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:58 node-2 multipathd: uevent trigger error
<27>Jul 19 11:15:58 node-2 multipathd: uevent trigger error
<27>Jul 19 11:16:04 node-2 multipathd: uevent trigger error
<27>Jul 19 11:16:04 node-2 multipathd: uevent trigger error
<27>Jul 19 11:16:04 node-2 multipathd: uevent trigger error
<27>Jul 19 11:16:05 node-2 multipathd: uevent trigger error
<27>Jul 19 11:16:05 node-2 multipathd: uevent trigger error
<27>Jul 19 11:16:38 node-2 multipathd: uevent trigger error
<27>Jul 19 11:16:38 node-2 multipathd: uevent trigger error
<27>Jul 19 11:16:38 node-2 multipathd: uevent trigger error
<27>Jul 19 11:16:38 node-2 multipathd: uevent trigger error
<27>Jul 19 11:16:38 node-2 multipathd: uevent trigger error
<27>Jul 19 11:17:19 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 19 11:17:28 node-2 multipathd: uevent trigger error
<27>Jul 19 11:17:28 node-2 multipathd: uevent trigger error
<27>Jul 19 11:17:28 node-2 multipathd: uevent trigger error
<27>Jul 19 11:17:28 node-2 multipathd: uevent trigger error
<27>Jul 19 11:17:28 node-2 multipathd: uevent trigger error
<27>Jul 19 11:17:45 node-2 multipathd: uevent trigger error
<27>Jul 19 11:17:45 node-2 multipathd: uevent trigger error
<27>Jul 19 11:17:45 node-2 multipathd: uevent trigger error
<27>Jul 19 11:17:45 node-2 multipathd: uevent trigger error
<27>Jul 19 11:17:45 node-2 multipathd: uevent trigger error
<11>Jul 19 11:17:58 node-2 liberasurecode[95189]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:17:58 node-2 liberasurecode[95189]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:17:58 node-2 liberasurecode[95189]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:17:58 node-2 liberasurecode[95189]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 19 11:17:58 node-2 liberasurecode[95229]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:17:58 node-2 liberasurecode[95229]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:17:58 node-2 liberasurecode[95229]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:17:58 node-2 liberasurecode[95229]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 19 11:17:59 node-2 liberasurecode[95645]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:17:59 node-2 liberasurecode[95645]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:17:59 node-2 liberasurecode[95645]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:17:59 node-2 liberasurecode[95645]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96462]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96462]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96462]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96462]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96498]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96498]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96498]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96498]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96651]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96651]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96651]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96651]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96888]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96888]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96888]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96888]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96923]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96923]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96923]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96923]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96944]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96944]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96944]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96944]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96983]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96983]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96983]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:03 node-2 liberasurecode[96983]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:12 node-2 liberasurecode[99051]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:12 node-2 liberasurecode[99051]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:12 node-2 liberasurecode[99051]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:18:12 node-2 liberasurecode[99051]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 19 11:18:20 node-2 multipathd: uevent trigger error
<27>Jul 19 11:18:20 node-2 multipathd: uevent trigger error
<27>Jul 19 11:18:20 node-2 multipathd: uevent trigger error
<27>Jul 19 11:18:20 node-2 multipathd: uevent trigger error
<27>Jul 19 11:18:20 node-2 multipathd: uevent trigger error
<43>Jul 19 11:19:02 node-2 apache2_error [Tue Jul 19 11:18:53.333618 2016] [mpm_worker:notice] [pid 32785:tid 140141749979008] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 19 11:19:02 node-2 apache2_error [Tue Jul 19 11:18:53.719274 2016] [mpm_worker:warn] [pid 32785:tid 140141749979008] AH00317: MaxRequestWorkers of 12881 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 12875
<43>Jul 19 11:19:02 node-2 apache2_error [Tue Jul 19 11:18:53.726031 2016] [mpm_worker:notice] [pid 32785:tid 140141749979008] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 19 11:19:02 node-2 apache2_error [Tue Jul 19 11:18:53.726056 2016] [core:notice] [pid 32785:tid 140141749979008] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 19 11:19:32 node-2 apache2_error [Tue Jul 19 11:19:31.909381 2016] [mpm_worker:notice] [pid 32785:tid 140141749979008] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 19 11:19:32 node-2 apache2_error [Tue Jul 19 11:19:32.113995 2016] [mpm_worker:warn] [pid 32785:tid 140141749979008] AH00317: MaxRequestWorkers of 12881 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 12875
<43>Jul 19 11:19:32 node-2 apache2_error [Tue Jul 19 11:19:32.134933 2016] [mpm_worker:notice] [pid 32785:tid 140141749979008] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 19 11:19:32 node-2 apache2_error [Tue Jul 19 11:19:32.134953 2016] [core:notice] [pid 32785:tid 140141749979008] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 19 11:19:36 node-2 multipathd: uevent trigger error
<27>Jul 19 11:19:36 node-2 multipathd: uevent trigger error
<27>Jul 19 11:19:36 node-2 multipathd: uevent trigger error
<27>Jul 19 11:19:36 node-2 multipathd: uevent trigger error
<27>Jul 19 11:19:36 node-2 multipathd: uevent trigger error
<27>Jul 19 11:19:44 node-2 multipathd: uevent trigger error
<27>Jul 19 11:19:44 node-2 multipathd: uevent trigger error
<27>Jul 19 11:19:44 node-2 multipathd: uevent trigger error
<27>Jul 19 11:19:44 node-2 multipathd: uevent trigger error
<27>Jul 19 11:19:44 node-2 multipathd: uevent trigger error
<27>Jul 19 11:19:50 node-2 multipathd: uevent trigger error
<27>Jul 19 11:19:50 node-2 multipathd: uevent trigger error
<27>Jul 19 11:19:50 node-2 multipathd: uevent trigger error
<27>Jul 19 11:19:50 node-2 multipathd: uevent trigger error
<27>Jul 19 11:19:50 node-2 multipathd: uevent trigger error
<11>Jul 19 11:20:01 node-2 liberasurecode[120002]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:20:01 node-2 liberasurecode[120002]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:20:01 node-2 liberasurecode[120002]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:20:01 node-2 liberasurecode[120002]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 19 11:20:20 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 19 11:20:29 node-2 multipathd: uevent trigger error
<27>Jul 19 11:20:29 node-2 multipathd: uevent trigger error
<27>Jul 19 11:20:29 node-2 multipathd: uevent trigger error
<27>Jul 19 11:20:29 node-2 multipathd: uevent trigger error
<27>Jul 19 11:20:29 node-2 multipathd: uevent trigger error
<43>Jul 19 11:20:33 node-2 apache2_error [Tue Jul 19 11:20:25.141294 2016] [mpm_worker:notice] [pid 32785:tid 140141749979008] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 19 11:20:33 node-2 apache2_error [Tue Jul 19 11:20:25.383252 2016] [mpm_worker:warn] [pid 32785:tid 140141749979008] AH00317: MaxRequestWorkers of 12881 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 12875
<43>Jul 19 11:20:33 node-2 apache2_error [Tue Jul 19 11:20:25.418944 2016] [mpm_worker:notice] [pid 32785:tid 140141749979008] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 19 11:20:33 node-2 apache2_error [Tue Jul 19 11:20:25.418975 2016] [core:notice] [pid 32785:tid 140141749979008] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 19 11:20:36 node-2 multipathd: uevent trigger error
<27>Jul 19 11:20:36 node-2 multipathd: uevent trigger error
<27>Jul 19 11:20:36 node-2 multipathd: uevent trigger error
<27>Jul 19 11:20:36 node-2 multipathd: uevent trigger error
<27>Jul 19 11:20:36 node-2 multipathd: uevent trigger error
<27>Jul 19 11:20:43 node-2 multipathd: uevent trigger error
<27>Jul 19 11:20:43 node-2 multipathd: uevent trigger error
<27>Jul 19 11:20:43 node-2 multipathd: uevent trigger error
<27>Jul 19 11:20:43 node-2 multipathd: uevent trigger error
<27>Jul 19 11:20:43 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:01 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:01 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:01 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:01 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:01 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:26 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:34 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:34 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:34 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:34 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:34 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:34 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:39 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 19 11:21:49 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:49 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:49 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:49 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:49 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:54 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:54 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:54 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:54 node-2 multipathd: uevent trigger error
<27>Jul 19 11:21:54 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:05 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:05 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:05 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:05 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:05 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:11 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:11 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:11 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:11 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:11 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:24 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:24 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:24 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:24 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:24 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:27 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 19 11:22:29 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:29 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:29 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:29 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:29 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:35 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:35 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:35 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:35 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:35 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:49 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:49 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:49 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:49 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:49 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:22:57 node-2 multipathd: uevent trigger error
<27>Jul 19 11:23:47 node-2 multipathd: uevent trigger error
<27>Jul 19 11:23:47 node-2 multipathd: uevent trigger error
<27>Jul 19 11:23:47 node-2 multipathd: uevent trigger error
<27>Jul 19 11:23:47 node-2 multipathd: uevent trigger error
<27>Jul 19 11:23:47 node-2 multipathd: uevent trigger error
<27>Jul 19 11:23:52 node-2 multipathd: uevent trigger error
<27>Jul 19 11:23:52 node-2 multipathd: uevent trigger error
<27>Jul 19 11:23:52 node-2 multipathd: uevent trigger error
<27>Jul 19 11:23:52 node-2 multipathd: uevent trigger error
<27>Jul 19 11:23:52 node-2 multipathd: uevent trigger error
<11>Jul 19 11:25:01 node-2 liberasurecode[186798]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:25:01 node-2 liberasurecode[186798]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:25:01 node-2 liberasurecode[186798]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 19 11:25:01 node-2 liberasurecode[186798]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 19 11:25:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:13 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:18 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:18 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:18 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:18 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:18 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:23 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:23 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:23 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:23 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:23 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:28 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:28 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:28 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:28 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:28 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:37 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:37 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:37 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:37 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:37 node-2 multipathd: uevent trigger error
<129>Jul 19 11:25:39 node-2 haproxy[22476]: 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.
<27>Jul 19 11:25:42 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:42 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:42 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:42 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:42 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:48 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:48 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:48 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:48 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:48 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:53 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:53 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:53 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:53 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:53 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:58 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:58 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:58 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:58 node-2 multipathd: uevent trigger error
<27>Jul 19 11:25:58 node-2 multipathd: uevent trigger error
