Nov  9 18:23:33 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8874" x-info="http://www.rsyslog.com"] start
Nov  9 18:23:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Nov  9 18:23:33 node-2 rsyslogd: rsyslogd's groupid changed to 104
Nov  9 18:23:33 node-2 rsyslogd: rsyslogd's userid changed to 101
Nov  9 18:23:33 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Nov  9 18:23:33 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Nov  9 18:23:33 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Nov  9 18:23:33 node-2 kernel: [    0.000000] Linux version 3.13.0-100-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #147-Ubuntu SMP Tue Oct 18 16:48:51 UTC 2016 (Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39)
Nov  9 18:23:33 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=eed3d8cb-cc70-422e-b3a3-42005ac4da02 nomdmonddf nomdmonisw
Nov  9 18:23:33 node-2 kernel: [    0.000000] KERNEL supported cpus:
Nov  9 18:23:33 node-2 kernel: [    0.000000]   Intel GenuineIntel
Nov  9 18:23:33 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Nov  9 18:23:33 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Nov  9 18:23:33 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Nov  9 18:23:33 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000093fff] usable
Nov  9 18:23:33 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000094000-0x000000000009ffff] reserved
Nov  9 18:23:33 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Nov  9 18:23:33 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000005ae23fff] usable
Nov  9 18:23:33 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000005ae24000-0x000000005bae3fff] reserved
Nov  9 18:23:33 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000005bae4000-0x00000000790fefff] usable
Nov  9 18:23:33 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000790ff000-0x00000000791fefff] reserved
Nov  9 18:23:33 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000791ff000-0x000000007b5fefff] ACPI NVS
Nov  9 18:23:33 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007b5ff000-0x000000007b7fefff] ACPI data
Nov  9 18:23:33 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007b7ff000-0x000000007b7fffff] usable
Nov  9 18:23:33 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007b800000-0x000000008fffffff] reserved
Nov  9 18:23:33 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff800000-0x00000000ffffffff] reserved
Nov  9 18:23:33 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000207fffffff] usable
Nov  9 18:23:33 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Nov  9 18:23:33 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Nov  9 18:23:33 node-2 kernel: [    0.000000] DMI: HP ProLiant BL460c Gen9, BIOS I36 05/06/2015
Nov  9 18:23:33 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov  9 18:23:33 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Nov  9 18:23:33 node-2 kernel: [    0.000000] No AGP bridge found
Nov  9 18:23:33 node-2 kernel: [    0.000000] e820: last_pfn = 0x2080000 max_arch_pfn = 0x400000000
Nov  9 18:23:33 node-2 kernel: [    0.000000] MTRR default type: write-back
Nov  9 18:23:33 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Nov  9 18:23:33 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Nov  9 18:23:33 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Nov  9 18:23:33 node-2 kernel: [    0.000000]   C0000-DFFFF write-protect
Nov  9 18:23:33 node-2 kernel: [    0.000000]   E0000-EFFFF uncachable
Nov  9 18:23:33 node-2 kernel: [    0.000000]   F0000-FFFFF write-protect
Nov  9 18:23:33 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Nov  9 18:23:33 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Nov  9 18:23:33 node-2 kernel: [    0.000000]   1 base 002080000000 mask 3FFF80000000 uncachable
Nov  9 18:23:33 node-2 kernel: [    0.000000]   2 base 008000000000 mask 3F8000000000 uncachable
Nov  9 18:23:33 node-2 kernel: [    0.000000]   3 base 010000000000 mask 3F0000000000 uncachable
Nov  9 18:23:33 node-2 kernel: [    0.000000]   4 base 038000000000 mask 3FC000000000 uncachable
Nov  9 18:23:33 node-2 kernel: [    0.000000]   5 base 00007C000000 mask 3FFFFC000000 uncachable
Nov  9 18:23:33 node-2 kernel: [    0.000000]   6 base 00007FC00000 mask 3FFFFFC00000 uncachable
Nov  9 18:23:33 node-2 kernel: [    0.000000]   7 disabled
Nov  9 18:23:33 node-2 kernel: [    0.000000]   8 disabled
Nov  9 18:23:33 node-2 kernel: [    0.000000]   9 disabled
Nov  9 18:23:33 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Nov  9 18:23:33 node-2 kernel: [    0.000000] e820: last_pfn = 0x7b800 max_arch_pfn = 0x400000000
Nov  9 18:23:33 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Nov  9 18:23:33 node-2 kernel: [    0.000000] Base memory trampoline at [ffff88000008e000] 8e000 size 24576
Nov  9 18:23:33 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Nov  9 18:23:33 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Nov  9 18:23:33 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Nov  9 18:23:33 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Nov  9 18:23:33 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Nov  9 18:23:33 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x207fe00000-0x207fffffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]  [mem 0x207fe00000-0x207fffffff] page 1G
Nov  9 18:23:33 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x207c000000-0x207fdfffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]  [mem 0x207c000000-0x207fdfffff] page 1G
Nov  9 18:23:33 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x2000000000-0x207bffffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]  [mem 0x2000000000-0x207bffffff] page 1G
Nov  9 18:23:33 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x1000000000-0x1fffffffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]  [mem 0x1000000000-0x1fffffffff] page 1G
Nov  9 18:23:33 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x5ae23fff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Nov  9 18:23:33 node-2 kernel: [    0.000000]  [mem 0x00200000-0x5adfffff] page 2M
Nov  9 18:23:33 node-2 kernel: [    0.000000]  [mem 0x5ae00000-0x5ae23fff] page 4k
Nov  9 18:23:33 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x5bae4000-0x790fefff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]  [mem 0x5bae4000-0x5bbfffff] page 4k
Nov  9 18:23:33 node-2 kernel: [    0.000000]  [mem 0x5bc00000-0x78ffffff] page 2M
Nov  9 18:23:33 node-2 kernel: [    0.000000]  [mem 0x79000000-0x790fefff] page 4k
Nov  9 18:23:33 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Nov  9 18:23:33 node-2 kernel: [    0.000000] BRK [0x01fe6000, 0x01fe6fff] PGTABLE
Nov  9 18:23:33 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7b7ff000-0x7b7fffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]  [mem 0x7b7ff000-0x7b7fffff] page 4k
Nov  9 18:23:33 node-2 kernel: [    0.000000] BRK [0x01fe7000, 0x01fe7fff] PGTABLE
Nov  9 18:23:33 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0xfffffffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]  [mem 0x100000000-0xfffffffff] page 1G
Nov  9 18:23:33 node-2 kernel: [    0.000000] RAMDISK: [mem 0x3581e000-0x36c06fff]
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f4f00 000024 (v02 HP    )
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: XSDT 000000007b7e8188 0000EC (v01 HP     ProLiant 00000001      01000013)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: FACP 000000007b7f6000 00010C (v05 HP     ProLiant 00000001 HP   00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: DSDT 000000007b7dd000 00AE48 (v02 HP     DSDT     00000002 HPAG 00020000)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: FACS 000000007b52b000 000040
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: UEFI 000000007b539000 000042 (v01 HP     ProLiant 00000002      01000013)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: MCEJ 000000007b7fc000 000130 (v01 HP     ProLiant 00000001 INTL 0100000D)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: SSDT 000000007b7fb000 000064 (v02 HP     SpsNvs   00000002 INTL 20130328)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: HEST 000000007b7fa000 0000A8 (v01 HP     ProLiant 00000001 INTL 00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: BERT 000000007b7f9000 000030 (v01 HP     ProLiant 00000001 INTL 00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: ERST 000000007b7f8000 000230 (v01 HP     ProLiant 00000001 INTL 00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: EINJ 000000007b7f7000 000150 (v01 HP     ProLiant 00000001 INTL 00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: HPET 000000007b7f5000 000038 (v01 HP     ProLiant 00000001 HP   00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: PMCT 000000007b7f4000 000064 (v01 HP     ProLiant 00000001 HP   00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: WDDT 000000007b7f3000 000040 (v01 HP     ProLiant 00000001 HP   00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: APIC 000000007b7f2000 0005AA (v03 HP     ProLiant 00000001 HP   00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: MCFG 000000007b7f1000 00003C (v01 HP     ProLiant 00000001 HP   00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: SLIT 000000007b7f0000 000030 (v01 HP     ProLiant 00000001 HP   00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: SRAT 000000007b7ef000 000500 (v03 HP     ProLiant 00000001 HP   00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: SPMI 000000007b7ee000 000041 (v05 HP     ProLiant 00000001 HP   00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: RASF 000000007b7ed000 000030 (v01 HP     ProLiant 00000001 HP   00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: SPCR 000000007b7ec000 000050 (v01 HP     ProLiant 00000001 HP   00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: MSCT 000000007b7eb000 000064 (v01 HP     ProLiant 00000001 HP   00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: BDAT 000000007b7ea000 000030 (v01 HP     ProLiant 00000001 HP   00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: PCCT 000000007b7e9000 00006E (v01 HP     ProLiant 00000001 HP   00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: SSDT 000000007b7d6000 0062CE (v02 HP     PCISSDT  00000002 HPAG 00020000)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: SSDT 000000007b7d5000 0001CB (v02 HP     TIMESSDT 00000002 HPAG 00020000)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: SSDT 000000007b7d4000 0002F2 (v01 HP         pmab 00000001 INTL 20130328)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: DMAR 000000007b7fd000 000300 (v01 INTEL  INTEL ID 00000001    ? 00000001)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0000 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0002 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0004 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0006 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0008 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x000a -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0010 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0012 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0014 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0016 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0018 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x001a -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0020 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0022 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0024 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0026 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0028 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x002a -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0030 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0032 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0034 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0036 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0038 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x003a -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0001 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0003 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0005 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0007 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0009 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x000b -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0011 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0013 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0015 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0017 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0019 -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x001b -> Node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0021 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0023 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0025 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0027 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0029 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x002b -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0031 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0033 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0035 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0037 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0039 -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x003b -> Node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x107fffffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x1080000000-0x207fffffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Nov  9 18:23:33 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x107fffffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x107fffb000-0x107fffffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x1080000000-0x207fffffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x207fff8000-0x207fffcfff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0041ffffff] PMD -> [ffff88103fe00000-ffff88107fdfffff] on node 0
Nov  9 18:23:33 node-2 kernel: [    0.000000]  [ffffea0042000000-ffffea0081ffffff] PMD -> [ffff88203f600000-ffff88207f5fffff] on node 1
Nov  9 18:23:33 node-2 kernel: [    0.000000] Zone ranges:
Nov  9 18:23:33 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x207fffffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000] Movable zone start for each node
Nov  9 18:23:33 node-2 kernel: [    0.000000] Early memory node ranges
Nov  9 18:23:33 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x00093fff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x5ae23fff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]   node   0: [mem 0x5bae4000-0x790fefff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]   node   0: [mem 0x7b7ff000-0x7b7fffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x107fffffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000]   node   1: [mem 0x1080000000-0x207fffffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000] On node 0 totalpages: 16745427
Nov  9 18:23:33 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Nov  9 18:23:33 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Nov  9 18:23:33 node-2 kernel: [    0.000000]   DMA zone: 3987 pages, LIFO batch:0
Nov  9 18:23:33 node-2 kernel: [    0.000000]   DMA32 zone: 7633 pages used for memmap
Nov  9 18:23:33 node-2 kernel: [    0.000000]   DMA32 zone: 488512 pages, LIFO batch:31
Nov  9 18:23:33 node-2 kernel: [    0.000000]   Normal zone: 253952 pages used for memmap
Nov  9 18:23:33 node-2 kernel: [    0.000000]   Normal zone: 16252928 pages, LIFO batch:31
Nov  9 18:23:33 node-2 kernel: [    0.000000] On node 1 totalpages: 16777216
Nov  9 18:23:33 node-2 kernel: [    0.000000]   Normal zone: 262144 pages used for memmap
Nov  9 18:23:33 node-2 kernel: [    0.000000]   Normal zone: 16777216 pages, LIFO batch:31
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x00] uid[0x00] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x02] uid[0x02] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x04] uid[0x04] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x06] uid[0x06] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x08] uid[0x08] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x0a] uid[0x0a] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x10] uid[0x10] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x12] uid[0x12] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x14] uid[0x14] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x16] uid[0x16] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x18] uid[0x18] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x1a] uid[0x1a] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x20] uid[0x20] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x22] uid[0x22] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x24] uid[0x24] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x26] uid[0x26] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x28] uid[0x28] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x2a] uid[0x2a] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x30] uid[0x30] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x32] uid[0x32] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x34] uid[0x34] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x36] uid[0x36] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x38] uid[0x38] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x3a] uid[0x3a] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x01] uid[0x01] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x03] uid[0x03] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x05] uid[0x05] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x07] uid[0x07] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x09] uid[0x09] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x0b] uid[0x0b] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x11] uid[0x11] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x13] uid[0x13] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x15] uid[0x15] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x17] uid[0x17] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x19] uid[0x19] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x1b] uid[0x1b] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x21] uid[0x21] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x23] uid[0x23] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x25] uid[0x25] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x27] uid[0x27] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x29] uid[0x29] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x2b] uid[0x2b] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x31] uid[0x31] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x33] uid[0x33] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x35] uid[0x35] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x37] uid[0x37] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x39] uid[0x39] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x3b] uid[0x3b] enabled)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x00] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x01] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x02] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x03] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x04] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x05] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x06] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x07] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x08] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x09] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x0a] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x0b] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x10] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x11] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x12] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x13] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x14] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x15] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x16] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x17] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x18] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x19] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x1a] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x1b] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x20] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x21] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x22] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x23] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x24] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x25] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x26] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x27] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x28] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x29] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x2a] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x2b] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x30] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x31] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x32] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x33] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x34] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x35] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x36] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x37] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x38] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x39] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x3a] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x3b] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Nov  9 18:23:33 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Nov  9 18:23:33 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Nov  9 18:23:33 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Nov  9 18:23:33 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Nov  9 18:23:33 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Nov  9 18:23:33 node-2 kernel: [    0.000000] smpboot: Allowing 48 CPUs, 0 hotplug CPUs
Nov  9 18:23:33 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Nov  9 18:23:33 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x00094000-0x0009ffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x5ae24000-0x5bae3fff]
Nov  9 18:23:33 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x790ff000-0x791fefff]
Nov  9 18:23:33 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x791ff000-0x7b5fefff]
Nov  9 18:23:33 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7b5ff000-0x7b7fefff]
Nov  9 18:23:33 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7b800000-0x8fffffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xff7fffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff800000-0xffffffff]
Nov  9 18:23:33 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xff7fffff] available for PCI devices
Nov  9 18:23:33 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Nov  9 18:23:33 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:48 nr_node_ids:2
Nov  9 18:23:33 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88103fa00000 s81536 r8192 d20864 u131072
Nov  9 18:23:33 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u131072 alloc=1*2097152
Nov  9 18:23:33 node-2 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 08 09 10 11 24 25 26 27 
Nov  9 18:23:33 node-2 kernel: [    0.000000] pcpu-alloc: [0] 28 29 30 31 32 33 34 35 -- -- -- -- -- -- -- -- 
Nov  9 18:23:33 node-2 kernel: [    0.000000] pcpu-alloc: [1] 12 13 14 15 16 17 18 19 20 21 22 23 36 37 38 39 
Nov  9 18:23:33 node-2 kernel: [    0.000000] pcpu-alloc: [1] 40 41 42 43 44 45 46 47 -- -- -- -- -- -- -- -- 
Nov  9 18:23:33 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 32998829
Nov  9 18:23:33 node-2 kernel: [    0.000000] Policy zone: Normal
Nov  9 18:23:33 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=eed3d8cb-cc70-422e-b3a3-42005ac4da02 nomdmonddf nomdmonisw
Nov  9 18:23:33 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Nov  9 18:23:33 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Nov  9 18:23:33 node-2 kernel: [    0.000000] Checking aperture...
Nov  9 18:23:33 node-2 kernel: [    0.000000] No AGP bridge found
Nov  9 18:23:33 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Nov  9 18:23:33 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Nov  9 18:23:33 node-2 kernel: [    0.000000] Memory: 131884960K/134090572K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 2205612K reserved)
Nov  9 18:23:33 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=48, Nodes=2
Nov  9 18:23:33 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Nov  9 18:23:33 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Nov  9 18:23:33 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=48.
Nov  9 18:23:33 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Nov  9 18:23:33 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-47.
Nov  9 18:23:33 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1880 16
Nov  9 18:23:33 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Nov  9 18:23:33 node-2 kernel: [    0.000000] console [tty0] enabled
Nov  9 18:23:33 node-2 kernel: [    0.000000] allocated 536870912 bytes of page_cgroup
Nov  9 18:23:33 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Nov  9 18:23:33 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Nov  9 18:23:33 node-2 kernel: [    0.000000] hpet clockevent registered
Nov  9 18:23:33 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Nov  9 18:23:33 node-2 kernel: [    0.004000] tsc: Detected 2496.999 MHz processor
Nov  9 18:23:33 node-2 kernel: [    0.000026] Calibrating delay loop (skipped), value calculated using timer frequency.. 4993.99 BogoMIPS (lpj=9987996)
Nov  9 18:23:33 node-2 kernel: [    0.000035] pid_max: default: 49152 minimum: 384
Nov  9 18:23:33 node-2 kernel: [    0.000190] Security Framework initialized
Nov  9 18:23:33 node-2 kernel: [    0.000279] AppArmor: AppArmor initialized
Nov  9 18:23:33 node-2 kernel: [    0.000283] Yama: becoming mindful.
Nov  9 18:23:33 node-2 kernel: [    0.016140] Dentry cache hash table entries: 16777216 (order: 15, 134217728 bytes)
Nov  9 18:23:33 node-2 kernel: [    0.062209] Inode-cache hash table entries: 8388608 (order: 14, 67108864 bytes)
Nov  9 18:23:33 node-2 kernel: [    0.081667] Mount-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Nov  9 18:23:33 node-2 kernel: [    0.081929] Mountpoint-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Nov  9 18:23:33 node-2 kernel: [    0.083468] Initializing cgroup subsys memory
Nov  9 18:23:33 node-2 kernel: [    0.083496] Initializing cgroup subsys devices
Nov  9 18:23:33 node-2 kernel: [    0.083501] Initializing cgroup subsys freezer
Nov  9 18:23:33 node-2 kernel: [    0.083505] Initializing cgroup subsys blkio
Nov  9 18:23:33 node-2 kernel: [    0.083510] Initializing cgroup subsys perf_event
Nov  9 18:23:33 node-2 kernel: [    0.083526] Initializing cgroup subsys hugetlb
Nov  9 18:23:33 node-2 kernel: [    0.083585] CPU: Physical Processor ID: 0
Nov  9 18:23:33 node-2 kernel: [    0.083588] CPU: Processor Core ID: 0
Nov  9 18:23:33 node-2 kernel: [    0.085129] mce: CPU supports 22 MCE banks
Nov  9 18:23:33 node-2 kernel: [    0.085208] CPU0: Thermal monitoring enabled (TM1)
Nov  9 18:23:33 node-2 kernel: [    0.085215] process: using mwait in idle threads
Nov  9 18:23:33 node-2 kernel: [    0.085223] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Nov  9 18:23:33 node-2 kernel: [    0.085223] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Nov  9 18:23:33 node-2 kernel: [    0.085223] tlb_flushall_shift: 6
Nov  9 18:23:33 node-2 kernel: [    0.085457] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Nov  9 18:23:33 node-2 kernel: [    0.087336] ACPI: Core revision 20131115
Nov  9 18:23:33 node-2 kernel: [    0.094279] ACPI: All ACPI Tables successfully acquired
Nov  9 18:23:33 node-2 kernel: [    0.094510] ftrace: allocating 28622 entries in 112 pages
Nov  9 18:23:33 node-2 kernel: [    0.118236] dmar: Host address width 46
Nov  9 18:23:33 node-2 kernel: [    0.118243] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Nov  9 18:23:33 node-2 kernel: [    0.118254] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020df
Nov  9 18:23:33 node-2 kernel: [    0.118259] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Nov  9 18:23:33 node-2 kernel: [    0.118268] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020df
Nov  9 18:23:33 node-2 kernel: [    0.118272] dmar: RMRR base: 0x00000079171000 end: 0x00000079173fff
Nov  9 18:23:33 node-2 kernel: [    0.118276] dmar: RMRR base: 0x000000791ed000 end: 0x000000791f0fff
Nov  9 18:23:33 node-2 kernel: [    0.118279] dmar: RMRR base: 0x000000791dd000 end: 0x000000791ecfff
Nov  9 18:23:33 node-2 kernel: [    0.118282] dmar: RMRR base: 0x000000791ca000 end: 0x000000791dafff
Nov  9 18:23:33 node-2 kernel: [    0.118285] dmar: RMRR base: 0x000000791db000 end: 0x000000791dcfff
Nov  9 18:23:33 node-2 kernel: [    0.118288] dmar: RMRR base: 0x0000005ae24000 end: 0x0000005ae63fff
Nov  9 18:23:33 node-2 kernel: [    0.118429] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Nov  9 18:23:33 node-2 kernel: [    0.118432] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Nov  9 18:23:33 node-2 kernel: [    0.118435] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Nov  9 18:23:33 node-2 kernel: [    0.118438] HPET id 0 under DRHD base 0xc7ffc000
Nov  9 18:23:33 node-2 kernel: [    0.119271] Enabled IRQ remapping in x2apic mode
Nov  9 18:23:33 node-2 kernel: [    0.119275] Enabling x2apic
Nov  9 18:23:33 node-2 kernel: [    0.119278] Enabled x2apic
Nov  9 18:23:33 node-2 kernel: [    0.119285] Switched APIC routing to cluster x2apic.
Nov  9 18:23:33 node-2 kernel: [    0.120028] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov  9 18:23:33 node-2 kernel: [    0.159708] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz (fam: 06, model: 3f, stepping: 02)
Nov  9 18:23:33 node-2 kernel: [    0.159722] TSC deadline timer enabled
Nov  9 18:23:33 node-2 kernel: [    0.159750] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Broken BIOS detected, complain to your hardware vendor.
Nov  9 18:23:33 node-2 kernel: [    0.159764] [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 38d is 330)
Nov  9 18:23:33 node-2 kernel: [    0.159767] Intel PMU driver.
Nov  9 18:23:33 node-2 kernel: [    0.159772] ... version:                3
Nov  9 18:23:33 node-2 kernel: [    0.159775] ... bit width:              48
Nov  9 18:23:33 node-2 kernel: [    0.159777] ... generic registers:      4
Nov  9 18:23:33 node-2 kernel: [    0.159780] ... value mask:             0000ffffffffffff
Nov  9 18:23:33 node-2 kernel: [    0.159783] ... max period:             0000ffffffffffff
Nov  9 18:23:33 node-2 kernel: [    0.159786] ... fixed-purpose events:   3
Nov  9 18:23:33 node-2 kernel: [    0.159789] ... event mask:             000000070000000f
Nov  9 18:23:33 node-2 kernel: [    0.165077] x86: Booting SMP configuration:
Nov  9 18:23:33 node-2 kernel: [    0.182508] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Nov  9 18:23:33 node-2 kernel: [    0.165083] .... node  #0, CPUs:        #1  #2  #3  #4  #5  #6  #7  #8  #9 #10 #11
Nov  9 18:23:33 node-2 kernel: [    0.343517] .... node  #1, CPUs:   #12 #13 #14 #15 #16 #17 #18 #19 #20 #21 #22 #23
Nov  9 18:23:33 node-2 kernel: [    0.632470] .... node  #0, CPUs:   #24 #25 #26 #27 #28 #29 #30 #31 #32 #33 #34 #35
Nov  9 18:23:33 node-2 kernel: [    0.824245] .... node  #1, CPUs:   #36 #37 #38 #39 #40 #41 #42 #43 #44 #45 #46 #47
Nov  9 18:23:33 node-2 kernel: [    1.016352] x86: Booted up 2 nodes, 48 CPUs
Nov  9 18:23:33 node-2 kernel: [    1.016358] smpboot: Total of 48 processors activated (239783.53 BogoMIPS)
Nov  9 18:23:33 node-2 kernel: [    1.210860] devtmpfs: initialized
Nov  9 18:23:33 node-2 kernel: [    1.219678] EVM: security.selinux
Nov  9 18:23:33 node-2 kernel: [    1.219680] EVM: security.SMACK64
Nov  9 18:23:33 node-2 kernel: [    1.219682] EVM: security.ima
Nov  9 18:23:33 node-2 kernel: [    1.219683] EVM: security.capability
Nov  9 18:23:33 node-2 kernel: [    1.219759] PM: Registering ACPI NVS region [mem 0x791ff000-0x7b5fefff] (37748736 bytes)
Nov  9 18:23:33 node-2 kernel: [    1.221169] pinctrl core: initialized pinctrl subsystem
Nov  9 18:23:33 node-2 kernel: [    1.221241] regulator-dummy: no parameters
Nov  9 18:23:33 node-2 kernel: [    1.221272] RTC time: 18:21:16, date: 11/09/16
Nov  9 18:23:33 node-2 kernel: [    1.221332] NET: Registered protocol family 16
Nov  9 18:23:33 node-2 kernel: [    1.221440] cpuidle: using governor ladder
Nov  9 18:23:33 node-2 kernel: [    1.221442] cpuidle: using governor menu
Nov  9 18:23:33 node-2 kernel: [    1.221490] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Nov  9 18:23:33 node-2 kernel: [    1.221493] ACPI: bus type PCI registered
Nov  9 18:23:33 node-2 kernel: [    1.221495] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov  9 18:23:33 node-2 kernel: [    1.221576] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Nov  9 18:23:33 node-2 kernel: [    1.221579] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Nov  9 18:23:33 node-2 kernel: [    1.240595] PCI: Using configuration type 1 for base access
Nov  9 18:23:33 node-2 kernel: [    1.243314] bio: create slab <bio-0> at 0
Nov  9 18:23:33 node-2 kernel: [    1.243858] ACPI: Added _OSI(Module Device)
Nov  9 18:23:33 node-2 kernel: [    1.243860] ACPI: Added _OSI(Processor Device)
Nov  9 18:23:33 node-2 kernel: [    1.243862] ACPI: Added _OSI(3.0 _SCP Extensions)
Nov  9 18:23:33 node-2 kernel: [    1.243863] ACPI: Added _OSI(Processor Aggregator Device)
Nov  9 18:23:33 node-2 kernel: [    1.252326] ACPI: Interpreter enabled
Nov  9 18:23:33 node-2 kernel: [    1.252332] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Nov  9 18:23:33 node-2 kernel: [    1.252337] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Nov  9 18:23:33 node-2 kernel: [    1.252340] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Nov  9 18:23:33 node-2 kernel: [    1.252343] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S4_] (20131115/hwxface-580)
Nov  9 18:23:33 node-2 kernel: [    1.252349] ACPI: (supports S0 S5)
Nov  9 18:23:33 node-2 kernel: [    1.252350] ACPI: Using IOAPIC for interrupt routing
Nov  9 18:23:33 node-2 kernel: [    1.252393] HEST: Table parsing has been initialized.
Nov  9 18:23:33 node-2 kernel: [    1.252396] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov  9 18:23:33 node-2 kernel: [    1.252589] ACPI: No dock devices found.
Nov  9 18:23:33 node-2 kernel: [    1.264059] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Nov  9 18:23:33 node-2 kernel: [    1.264066] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  9 18:23:33 node-2 kernel: [    1.264070] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov  9 18:23:33 node-2 kernel: [    1.264097] PCI host bridge to bus 0000:7f
Nov  9 18:23:33 node-2 kernel: [    1.264099] pci_bus 0000:7f: root bus resource [bus 7f]
Nov  9 18:23:33 node-2 kernel: [    1.264109] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264153] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264192] pci 0000:7f:09.0: [8086:2f90] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264224] pci 0000:7f:09.3: [8086:2f93] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264262] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264294] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Nov  9 18:23:33 node-2 kernel: [    1.264327] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Nov  9 18:23:33 node-2 kernel: [    1.264361] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264395] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264425] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264454] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264484] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264514] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264544] pci 0000:7f:0c.6: [8086:2fe6] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264574] pci 0000:7f:0c.7: [8086:2fe7] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264602] pci 0000:7f:0d.0: [8086:2fe8] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264633] pci 0000:7f:0d.1: [8086:2fe9] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264663] pci 0000:7f:0d.2: [8086:2fea] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264693] pci 0000:7f:0d.3: [8086:2feb] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264726] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264755] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264785] pci 0000:7f:0f.2: [8086:2ffa] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264822] pci 0000:7f:0f.3: [8086:2ffb] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264853] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264885] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264916] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264947] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.264976] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Nov  9 18:23:33 node-2 kernel: [    1.265009] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265041] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Nov  9 18:23:33 node-2 kernel: [    1.265072] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265104] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265140] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Nov  9 18:23:33 node-2 kernel: [    1.265172] pci 0000:7f:12.2: [8086:2f70] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265205] pci 0000:7f:12.4: [8086:2f60] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265237] pci 0000:7f:12.5: [8086:2f38] type 00 class 0x110100
Nov  9 18:23:33 node-2 kernel: [    1.265269] pci 0000:7f:12.6: [8086:2f78] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265303] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265337] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265370] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265406] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265441] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265472] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265505] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265541] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265575] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265610] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265644] pci 0000:7f:14.4: [8086:2fbc] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265678] pci 0000:7f:14.5: [8086:2fbd] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265709] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265742] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265773] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265810] pci 0000:7f:16.1: [8086:2f79] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265847] pci 0000:7f:16.2: [8086:2f6a] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265884] pci 0000:7f:16.3: [8086:2f6b] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265923] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265960] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.265995] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266038] pci 0000:7f:17.1: [8086:2fd1] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266075] pci 0000:7f:17.2: [8086:2fd2] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266114] pci 0000:7f:17.3: [8086:2fd3] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266151] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266186] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266218] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266267] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266309] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266343] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266376] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266410] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266444] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266483] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266519] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266590] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Nov  9 18:23:33 node-2 kernel: [    1.266593] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  9 18:23:33 node-2 kernel: [    1.266597] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov  9 18:23:33 node-2 kernel: [    1.266620] PCI host bridge to bus 0000:ff
Nov  9 18:23:33 node-2 kernel: [    1.266622] pci_bus 0000:ff: root bus resource [bus ff]
Nov  9 18:23:33 node-2 kernel: [    1.266629] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266666] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266703] pci 0000:ff:09.0: [8086:2f90] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266739] pci 0000:ff:09.3: [8086:2f93] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266779] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266811] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Nov  9 18:23:33 node-2 kernel: [    1.266843] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Nov  9 18:23:33 node-2 kernel: [    1.266877] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266910] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266942] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.266974] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267006] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267037] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267069] pci 0000:ff:0c.6: [8086:2fe6] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267102] pci 0000:ff:0c.7: [8086:2fe7] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267135] pci 0000:ff:0d.0: [8086:2fe8] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267169] pci 0000:ff:0d.1: [8086:2fe9] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267203] pci 0000:ff:0d.2: [8086:2fea] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267237] pci 0000:ff:0d.3: [8086:2feb] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267273] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267307] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267342] pci 0000:ff:0f.2: [8086:2ffa] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267374] pci 0000:ff:0f.3: [8086:2ffb] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267406] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267440] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267473] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267504] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267536] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Nov  9 18:23:33 node-2 kernel: [    1.267570] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267602] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Nov  9 18:23:33 node-2 kernel: [    1.267635] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267670] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267711] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Nov  9 18:23:33 node-2 kernel: [    1.267745] pci 0000:ff:12.2: [8086:2f70] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267779] pci 0000:ff:12.4: [8086:2f60] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267813] pci 0000:ff:12.5: [8086:2f38] type 00 class 0x110100
Nov  9 18:23:33 node-2 kernel: [    1.267847] pci 0000:ff:12.6: [8086:2f78] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267884] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267919] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267957] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.267998] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268035] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268069] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268110] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268147] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268186] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268222] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268260] pci 0000:ff:14.4: [8086:2fbc] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268297] pci 0000:ff:14.5: [8086:2fbd] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268337] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268369] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268407] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268446] pci 0000:ff:16.1: [8086:2f79] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268487] pci 0000:ff:16.2: [8086:2f6a] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268526] pci 0000:ff:16.3: [8086:2f6b] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268567] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268606] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268643] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268683] pci 0000:ff:17.1: [8086:2fd1] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268723] pci 0000:ff:17.2: [8086:2fd2] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268763] pci 0000:ff:17.3: [8086:2fd3] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268802] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268837] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268873] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268912] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268955] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.268991] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.269027] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.269063] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.269099] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.269140] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.269177] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.270034] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Nov  9 18:23:33 node-2 kernel: [    1.270038] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  9 18:23:33 node-2 kernel: [    1.270111] acpi PNP0A08:00: _OSC: platform does not support [AER]
Nov  9 18:23:33 node-2 kernel: [    1.270174] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME PCIeCapability]
Nov  9 18:23:33 node-2 kernel: [    1.270176] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
Nov  9 18:23:33 node-2 kernel: [    1.270466] acpi PNP0A08:00: ignoring host bridge window [mem 0x000c4000-0x000cbfff] (conflicts with Video ROM [mem 0x000c0000-0x000c7fff])
Nov  9 18:23:33 node-2 kernel: [    1.270710] PCI host bridge to bus 0000:00
Nov  9 18:23:33 node-2 kernel: [    1.270712] pci_bus 0000:00: root bus resource [bus 00-7e]
Nov  9 18:23:33 node-2 kernel: [    1.270714] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Nov  9 18:23:33 node-2 kernel: [    1.270716] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Nov  9 18:23:33 node-2 kernel: [    1.270718] pci_bus 0000:00: root bus resource [io  0x03b0-0x03bb]
Nov  9 18:23:33 node-2 kernel: [    1.270720] pci_bus 0000:00: root bus resource [io  0x03c0-0x03df]
Nov  9 18:23:33 node-2 kernel: [    1.270722] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Nov  9 18:23:33 node-2 kernel: [    1.270724] pci_bus 0000:00: root bus resource [io  0x1000-0x9fff]
Nov  9 18:23:33 node-2 kernel: [    1.270726] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Nov  9 18:23:33 node-2 kernel: [    1.270728] pci_bus 0000:00: root bus resource [mem 0x38000000000-0x39fffffffff]
Nov  9 18:23:33 node-2 kernel: [    1.270735] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Nov  9 18:23:33 node-2 kernel: [    1.270837] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.270874] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.270929] pci 0000:00:01.0: System wakeup disabled by ACPI
Nov  9 18:23:33 node-2 kernel: [    1.270954] pci 0000:00:01.1: [8086:2f03] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.270989] pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.271067] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.271103] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.271155] pci 0000:00:02.0: System wakeup disabled by ACPI
Nov  9 18:23:33 node-2 kernel: [    1.271177] pci 0000:00:02.1: [8086:2f05] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.271212] pci 0000:00:02.1: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.271284] pci 0000:00:02.2: [8086:2f06] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.271319] pci 0000:00:02.2: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.271389] pci 0000:00:02.3: [8086:2f07] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.271424] pci 0000:00:02.3: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.271496] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.271532] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.271585] pci 0000:00:03.0: System wakeup disabled by ACPI
Nov  9 18:23:33 node-2 kernel: [    1.271608] pci 0000:00:03.1: [8086:2f09] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.271643] pci 0000:00:03.1: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.271715] pci 0000:00:03.2: [8086:2f0a] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.271750] pci 0000:00:03.2: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.271822] pci 0000:00:03.3: [8086:2f0b] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.271857] pci 0000:00:03.3: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.271936] pci 0000:00:04.0: [8086:2f20] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.271945] pci 0000:00:04.0: reg 0x10: [mem 0x39ffff2c000-0x39ffff2ffff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.272043] pci 0000:00:04.1: [8086:2f21] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.272051] pci 0000:00:04.1: reg 0x10: [mem 0x39ffff28000-0x39ffff2bfff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.272147] pci 0000:00:04.2: [8086:2f22] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.272155] pci 0000:00:04.2: reg 0x10: [mem 0x39ffff24000-0x39ffff27fff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.272252] pci 0000:00:04.3: [8086:2f23] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.272259] pci 0000:00:04.3: reg 0x10: [mem 0x39ffff20000-0x39ffff23fff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.272358] pci 0000:00:04.4: [8086:2f24] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.272365] pci 0000:00:04.4: reg 0x10: [mem 0x39ffff1c000-0x39ffff1ffff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.272463] pci 0000:00:04.5: [8086:2f25] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.272471] pci 0000:00:04.5: reg 0x10: [mem 0x39ffff18000-0x39ffff1bfff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.272569] pci 0000:00:04.6: [8086:2f26] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.272577] pci 0000:00:04.6: reg 0x10: [mem 0x39ffff14000-0x39ffff17fff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.272673] pci 0000:00:04.7: [8086:2f27] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.272681] pci 0000:00:04.7: reg 0x10: [mem 0x39ffff10000-0x39ffff13fff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.272776] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.272866] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.272963] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.273052] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Nov  9 18:23:33 node-2 kernel: [    1.273058] pci 0000:00:05.4: reg 0x10: [mem 0x95603000-0x95603fff]
Nov  9 18:23:33 node-2 kernel: [    1.273169] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Nov  9 18:23:33 node-2 kernel: [    1.273330] pci 0000:00:14.0: [8086:8d31] type 00 class 0x0c0330
Nov  9 18:23:33 node-2 kernel: [    1.273346] pci 0000:00:14.0: reg 0x10: [mem 0x39ffff00000-0x39ffff0ffff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.273396] pci 0000:00:14.0: PME# supported from D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.273476] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Nov  9 18:23:33 node-2 kernel: [    1.273495] pci 0000:00:1a.0: reg 0x10: [mem 0x95601000-0x956013ff]
Nov  9 18:23:33 node-2 kernel: [    1.273579] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.273656] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.273718] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.273795] pci 0000:00:1c.2: [8086:8d14] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.273857] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.273932] pci 0000:00:1c.4: [8086:8d18] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.273993] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.274070] pci 0000:00:1c.6: [8086:8d1c] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.274132] pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.274208] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.274274] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.274361] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Nov  9 18:23:33 node-2 kernel: [    1.274380] pci 0000:00:1d.0: reg 0x10: [mem 0x95600000-0x956003ff]
Nov  9 18:23:33 node-2 kernel: [    1.274464] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.274551] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Nov  9 18:23:33 node-2 kernel: [    1.274715] pci 0000:00:1f.3: [8086:8d22] type 00 class 0x0c0500
Nov  9 18:23:33 node-2 kernel: [    1.274729] pci 0000:00:1f.3: reg 0x10: [mem 0x39ffff31000-0x39ffff310ff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.274748] pci 0000:00:1f.3: reg 0x20: [io  0x4000-0x401f]
Nov  9 18:23:33 node-2 kernel: [    1.274905] pci 0000:00:01.0: PCI bridge to [bus 02]
Nov  9 18:23:33 node-2 kernel: [    1.274941] pci 0000:00:01.1: PCI bridge to [bus 05]
Nov  9 18:23:33 node-2 kernel: [    1.274990] pci 0000:06:00.0: [14e4:16a2] type 00 class 0x020000
Nov  9 18:23:33 node-2 kernel: [    1.275002] pci 0000:06:00.0: reg 0x10: [mem 0x94000000-0x947fffff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.275011] pci 0000:06:00.0: reg 0x18: [mem 0x94800000-0x94ffffff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.275020] pci 0000:06:00.0: reg 0x20: [mem 0x95010000-0x9501ffff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.275027] pci 0000:06:00.0: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.275060] pci 0000:06:00.0: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.275112] pci 0000:06:00.1: [14e4:16a2] type 00 class 0x020000
Nov  9 18:23:33 node-2 kernel: [    1.275123] pci 0000:06:00.1: reg 0x10: [mem 0x93000000-0x937fffff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.275132] pci 0000:06:00.1: reg 0x18: [mem 0x93800000-0x93ffffff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.275141] pci 0000:06:00.1: reg 0x20: [mem 0x95000000-0x9500ffff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.275148] pci 0000:06:00.1: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.275181] pci 0000:06:00.1: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.282267] pci 0000:00:02.0: PCI bridge to [bus 06]
Nov  9 18:23:33 node-2 kernel: [    1.282277] pci 0000:00:02.0:   bridge window [mem 0x93000000-0x950fffff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.282327] pci 0000:00:02.1: PCI bridge to [bus 0b]
Nov  9 18:23:33 node-2 kernel: [    1.282405] pci 0000:07:00.0: [103c:3239] type 00 class 0x010400
Nov  9 18:23:33 node-2 kernel: [    1.282420] pci 0000:07:00.0: reg 0x10: [mem 0x95400000-0x954fffff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.282432] pci 0000:07:00.0: reg 0x18: [mem 0x95500000-0x955003ff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.282440] pci 0000:07:00.0: reg 0x20: [io  0x3000-0x30ff]
Nov  9 18:23:33 node-2 kernel: [    1.282455] pci 0000:07:00.0: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.282494] pci 0000:07:00.0: PME# supported from D0 D1 D3hot
Nov  9 18:23:33 node-2 kernel: [    1.290263] pci 0000:00:02.2: PCI bridge to [bus 07]
Nov  9 18:23:33 node-2 kernel: [    1.290269] pci 0000:00:02.2:   bridge window [io  0x3000-0x3fff]
Nov  9 18:23:33 node-2 kernel: [    1.290273] pci 0000:00:02.2:   bridge window [mem 0x95400000-0x955fffff]
Nov  9 18:23:33 node-2 kernel: [    1.290332] pci 0000:00:02.3: PCI bridge to [bus 0c]
Nov  9 18:23:33 node-2 kernel: [    1.290499] pci 0000:08:00.0: [8086:10f8] type 00 class 0x020000
Nov  9 18:23:33 node-2 kernel: [    1.290507] pci 0000:08:00.0: reg 0x10: [mem 0x95200000-0x952fffff]
Nov  9 18:23:33 node-2 kernel: [    1.290516] pci 0000:08:00.0: reg 0x18: [io  0x2020-0x203f]
Nov  9 18:23:33 node-2 kernel: [    1.290522] pci 0000:08:00.0: reg 0x1c: [mem 0x95304000-0x95307fff]
Nov  9 18:23:33 node-2 kernel: [    1.290536] pci 0000:08:00.0: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.290564] pci 0000:08:00.0: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.290586] pci 0000:08:00.0: reg 0x184: [mem 0x39fffe00000-0x39fffe03fff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.290596] pci 0000:08:00.0: reg 0x190: [mem 0x39fffd00000-0x39fffd03fff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.290646] pci 0000:08:00.1: [8086:10f8] type 00 class 0x020000
Nov  9 18:23:33 node-2 kernel: [    1.290653] pci 0000:08:00.1: reg 0x10: [mem 0x95100000-0x951fffff]
Nov  9 18:23:33 node-2 kernel: [    1.290663] pci 0000:08:00.1: reg 0x18: [io  0x2000-0x201f]
Nov  9 18:23:33 node-2 kernel: [    1.290668] pci 0000:08:00.1: reg 0x1c: [mem 0x95300000-0x95303fff]
Nov  9 18:23:33 node-2 kernel: [    1.290682] pci 0000:08:00.1: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.290710] pci 0000:08:00.1: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.290729] pci 0000:08:00.1: reg 0x184: [mem 0x39fffc00000-0x39fffc03fff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.290739] pci 0000:08:00.1: reg 0x190: [mem 0x39fffb00000-0x39fffb03fff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.298277] pci 0000:00:03.0: PCI bridge to [bus 08]
Nov  9 18:23:33 node-2 kernel: [    1.298283] pci 0000:00:03.0:   bridge window [io  0x2000-0x2fff]
Nov  9 18:23:33 node-2 kernel: [    1.298287] pci 0000:00:03.0:   bridge window [mem 0x95100000-0x953fffff]
Nov  9 18:23:33 node-2 kernel: [    1.298293] pci 0000:00:03.0:   bridge window [mem 0x39fffb00000-0x39fffefffff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.298343] pci 0000:00:03.1: PCI bridge to [bus 0d]
Nov  9 18:23:33 node-2 kernel: [    1.298400] pci 0000:00:03.2: PCI bridge to [bus 0e]
Nov  9 18:23:33 node-2 kernel: [    1.298463] pci 0000:00:03.3: PCI bridge to [bus 0f]
Nov  9 18:23:33 node-2 kernel: [    1.298514] pci 0000:00:1c.0: PCI bridge to [bus 10]
Nov  9 18:23:33 node-2 kernel: [    1.298580] pci 0000:01:00.0: [103c:3306] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.298598] pci 0000:01:00.0: reg 0x10: [io  0x1200-0x12ff]
Nov  9 18:23:33 node-2 kernel: [    1.298610] pci 0000:01:00.0: reg 0x14: [mem 0x92a8d000-0x92a8d1ff]
Nov  9 18:23:33 node-2 kernel: [    1.298622] pci 0000:01:00.0: reg 0x18: [io  0x1100-0x11ff]
Nov  9 18:23:33 node-2 kernel: [    1.298779] pci 0000:01:00.1: [102b:0533] type 00 class 0x030000
Nov  9 18:23:33 node-2 kernel: [    1.298796] pci 0000:01:00.1: reg 0x10: [mem 0x91000000-0x91ffffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.298808] pci 0000:01:00.1: reg 0x14: [mem 0x92a88000-0x92a8bfff]
Nov  9 18:23:33 node-2 kernel: [    1.298821] pci 0000:01:00.1: reg 0x18: [mem 0x92000000-0x927fffff]
Nov  9 18:23:33 node-2 kernel: [    1.298973] pci 0000:01:00.2: [103c:3307] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.298990] pci 0000:01:00.2: reg 0x10: [io  0x1000-0x10ff]
Nov  9 18:23:33 node-2 kernel: [    1.299002] pci 0000:01:00.2: reg 0x14: [mem 0x92a8c000-0x92a8c0ff]
Nov  9 18:23:33 node-2 kernel: [    1.299015] pci 0000:01:00.2: reg 0x18: [mem 0x92900000-0x929fffff]
Nov  9 18:23:33 node-2 kernel: [    1.299027] pci 0000:01:00.2: reg 0x1c: [mem 0x92a00000-0x92a7ffff]
Nov  9 18:23:33 node-2 kernel: [    1.299040] pci 0000:01:00.2: reg 0x20: [mem 0x92a80000-0x92a87fff]
Nov  9 18:23:33 node-2 kernel: [    1.299052] pci 0000:01:00.2: reg 0x24: [mem 0x92800000-0x928fffff]
Nov  9 18:23:33 node-2 kernel: [    1.299065] pci 0000:01:00.2: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.299124] pci 0000:01:00.2: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.299177] pci 0000:01:00.4: [103c:3300] type 00 class 0x0c0300
Nov  9 18:23:33 node-2 kernel: [    1.299238] pci 0000:01:00.4: reg 0x20: [io  0x1300-0x131f]
Nov  9 18:23:33 node-2 kernel: [    1.306291] pci 0000:00:1c.2: PCI bridge to [bus 01]
Nov  9 18:23:33 node-2 kernel: [    1.306298] pci 0000:00:1c.2:   bridge window [io  0x1000-0x1fff]
Nov  9 18:23:33 node-2 kernel: [    1.306302] pci 0000:00:1c.2:   bridge window [mem 0x90000000-0x92afffff]
Nov  9 18:23:33 node-2 kernel: [    1.306374] pci 0000:00:1c.4: PCI bridge to [bus 11]
Nov  9 18:23:33 node-2 kernel: [    1.306444] pci 0000:00:1c.6: PCI bridge to [bus 12]
Nov  9 18:23:33 node-2 kernel: [    1.306511] pci 0000:00:1c.7: PCI bridge to [bus 13]
Nov  9 18:23:33 node-2 kernel: [    1.306572] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Nov  9 18:23:33 node-2 kernel: [    1.306724] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
Nov  9 18:23:33 node-2 kernel: [    1.306774] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
Nov  9 18:23:33 node-2 kernel: [    1.306819] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
Nov  9 18:23:33 node-2 kernel: [    1.306864] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
Nov  9 18:23:33 node-2 kernel: [    1.306909] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
Nov  9 18:23:33 node-2 kernel: [    1.306955] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
Nov  9 18:23:33 node-2 kernel: [    1.307000] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
Nov  9 18:23:33 node-2 kernel: [    1.307046] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
Nov  9 18:23:33 node-2 kernel: [    1.307217] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Nov  9 18:23:33 node-2 kernel: [    1.307221] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  9 18:23:33 node-2 kernel: [    1.307288] acpi PNP0A08:01: _OSC: platform does not support [AER]
Nov  9 18:23:33 node-2 kernel: [    1.307346] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME PCIeCapability]
Nov  9 18:23:33 node-2 kernel: [    1.307349] acpi PNP0A08:01: FADT indicates ASPM is unsupported, using BIOS configuration
Nov  9 18:23:33 node-2 kernel: [    1.307428] PCI host bridge to bus 0000:80
Nov  9 18:23:33 node-2 kernel: [    1.307430] pci_bus 0000:80: root bus resource [bus 80-fe]
Nov  9 18:23:33 node-2 kernel: [    1.307432] pci_bus 0000:80: root bus resource [io  0xa000-0xffff]
Nov  9 18:23:33 node-2 kernel: [    1.307434] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Nov  9 18:23:33 node-2 kernel: [    1.307436] pci_bus 0000:80: root bus resource [mem 0x3a000000000-0x3bfffffffff]
Nov  9 18:23:33 node-2 kernel: [    1.307446] pci 0000:80:00.0: [8086:2f01] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.307487] pci 0000:80:00.0: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.307534] pci 0000:80:01.0: [8086:2f02] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.307574] pci 0000:80:01.0: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.307597] pci 0000:80:01.0: System wakeup disabled by ACPI
Nov  9 18:23:33 node-2 kernel: [    1.307622] pci 0000:80:01.1: [8086:2f03] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.307661] pci 0000:80:01.1: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.307684] pci 0000:80:01.1: System wakeup disabled by ACPI
Nov  9 18:23:33 node-2 kernel: [    1.307712] pci 0000:80:02.0: [8086:2f04] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.307751] pci 0000:80:02.0: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.307776] pci 0000:80:02.0: System wakeup disabled by ACPI
Nov  9 18:23:33 node-2 kernel: [    1.307798] pci 0000:80:02.1: [8086:2f05] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.307837] pci 0000:80:02.1: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.307882] pci 0000:80:02.2: [8086:2f06] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.307921] pci 0000:80:02.2: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.307943] pci 0000:80:02.2: System wakeup disabled by ACPI
Nov  9 18:23:33 node-2 kernel: [    1.307967] pci 0000:80:02.3: [8086:2f07] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.308006] pci 0000:80:02.3: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.308052] pci 0000:80:03.0: [8086:2f08] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.308091] pci 0000:80:03.0: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.308114] pci 0000:80:03.0: System wakeup disabled by ACPI
Nov  9 18:23:33 node-2 kernel: [    1.308138] pci 0000:80:03.1: [8086:2f09] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.308177] pci 0000:80:03.1: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.308220] pci 0000:80:03.2: [8086:2f0a] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.308259] pci 0000:80:03.2: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.308299] pci 0000:80:03.3: [8086:2f0b] type 01 class 0x060400
Nov  9 18:23:33 node-2 kernel: [    1.308338] pci 0000:80:03.3: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.308380] pci 0000:80:04.0: [8086:2f20] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.308389] pci 0000:80:04.0: reg 0x10: [mem 0x3bffff1c000-0x3bffff1ffff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.308459] pci 0000:80:04.1: [8086:2f21] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.308468] pci 0000:80:04.1: reg 0x10: [mem 0x3bffff18000-0x3bffff1bfff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.308539] pci 0000:80:04.2: [8086:2f22] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.308548] pci 0000:80:04.2: reg 0x10: [mem 0x3bffff14000-0x3bffff17fff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.308618] pci 0000:80:04.3: [8086:2f23] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.308626] pci 0000:80:04.3: reg 0x10: [mem 0x3bffff10000-0x3bffff13fff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.308696] pci 0000:80:04.4: [8086:2f24] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.308704] pci 0000:80:04.4: reg 0x10: [mem 0x3bffff0c000-0x3bffff0ffff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.308773] pci 0000:80:04.5: [8086:2f25] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.308782] pci 0000:80:04.5: reg 0x10: [mem 0x3bffff08000-0x3bffff0bfff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.308850] pci 0000:80:04.6: [8086:2f26] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.308859] pci 0000:80:04.6: reg 0x10: [mem 0x3bffff04000-0x3bffff07fff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.308931] pci 0000:80:04.7: [8086:2f27] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.308939] pci 0000:80:04.7: reg 0x10: [mem 0x3bffff00000-0x3bffff03fff 64bit]
Nov  9 18:23:33 node-2 kernel: [    1.309017] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.309075] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.309145] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Nov  9 18:23:33 node-2 kernel: [    1.309206] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Nov  9 18:23:33 node-2 kernel: [    1.309212] pci 0000:80:05.4: reg 0x10: [mem 0xc8300000-0xc8300fff]
Nov  9 18:23:33 node-2 kernel: [    1.309321] pci 0000:80:00.0: PCI bridge to [bus 8d]
Nov  9 18:23:33 node-2 kernel: [    1.309360] pci 0000:80:01.0: PCI bridge to [bus 81]
Nov  9 18:23:33 node-2 kernel: [    1.309396] pci 0000:80:01.1: PCI bridge to [bus 82]
Nov  9 18:23:33 node-2 kernel: [    1.309429] pci 0000:80:02.0: PCI bridge to [bus 83]
Nov  9 18:23:33 node-2 kernel: [    1.309465] pci 0000:80:02.1: PCI bridge to [bus 84]
Nov  9 18:23:33 node-2 kernel: [    1.309498] pci 0000:80:02.2: PCI bridge to [bus 85]
Nov  9 18:23:33 node-2 kernel: [    1.309532] pci 0000:80:02.3: PCI bridge to [bus 86]
Nov  9 18:23:33 node-2 kernel: [    1.309630] pci 0000:87:00.0: [8086:10f8] type 00 class 0x020000
Nov  9 18:23:33 node-2 kernel: [    1.309639] pci 0000:87:00.0: reg 0x10: [mem 0xc8100000-0xc81fffff]
Nov  9 18:23:33 node-2 kernel: [    1.309649] pci 0000:87:00.0: reg 0x18: [io  0xa020-0xa03f]
Nov  9 18:23:33 node-2 kernel: [    1.309655] pci 0000:87:00.0: reg 0x1c: [mem 0xc8204000-0xc8207fff]
Nov  9 18:23:33 node-2 kernel: [    1.309670] pci 0000:87:00.0: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.309702] pci 0000:87:00.0: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.309725] pci 0000:87:00.0: reg 0x184: [mem 0x3bfffe00000-0x3bfffe03fff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.309736] pci 0000:87:00.0: reg 0x190: [mem 0x3bfffd00000-0x3bfffd03fff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.309781] pci 0000:87:00.1: [8086:10f8] type 00 class 0x020000
Nov  9 18:23:33 node-2 kernel: [    1.309789] pci 0000:87:00.1: reg 0x10: [mem 0xc8000000-0xc80fffff]
Nov  9 18:23:33 node-2 kernel: [    1.309800] pci 0000:87:00.1: reg 0x18: [io  0xa000-0xa01f]
Nov  9 18:23:33 node-2 kernel: [    1.309806] pci 0000:87:00.1: reg 0x1c: [mem 0xc8200000-0xc8203fff]
Nov  9 18:23:33 node-2 kernel: [    1.309821] pci 0000:87:00.1: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.309851] pci 0000:87:00.1: PME# supported from D0 D3hot D3cold
Nov  9 18:23:33 node-2 kernel: [    1.309872] pci 0000:87:00.1: reg 0x184: [mem 0x3bfffc00000-0x3bfffc03fff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.309883] pci 0000:87:00.1: reg 0x190: [mem 0x3bfffb00000-0x3bfffb03fff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.314287] pci 0000:80:03.0: PCI bridge to [bus 87]
Nov  9 18:23:33 node-2 kernel: [    1.314294] pci 0000:80:03.0:   bridge window [io  0xa000-0xafff]
Nov  9 18:23:33 node-2 kernel: [    1.314298] pci 0000:80:03.0:   bridge window [mem 0xc8000000-0xc82fffff]
Nov  9 18:23:33 node-2 kernel: [    1.314304] pci 0000:80:03.0:   bridge window [mem 0x3bfffb00000-0x3bfffefffff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.314361] pci 0000:80:03.1: PCI bridge to [bus 8a]
Nov  9 18:23:33 node-2 kernel: [    1.314417] pci 0000:80:03.2: PCI bridge to [bus 8b]
Nov  9 18:23:33 node-2 kernel: [    1.314481] pci 0000:80:03.3: PCI bridge to [bus 8c]
Nov  9 18:23:33 node-2 kernel: [    1.314531] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Nov  9 18:23:33 node-2 kernel: [    1.314718] ACPI: Enabled 9 GPEs in block 00 to 3F
Nov  9 18:23:33 node-2 kernel: [    1.314724] ACPI: \_SB_.UNC0: notify handler is installed
Nov  9 18:23:33 node-2 kernel: [    1.314726] ACPI: \_SB_.UNC1: notify handler is installed
Nov  9 18:23:33 node-2 kernel: [    1.314745] ACPI: \_SB_.PCI0: notify handler is installed
Nov  9 18:23:33 node-2 kernel: [    1.314786] ACPI: \_SB_.PCI1: notify handler is installed
Nov  9 18:23:33 node-2 kernel: [    1.314794] Found 4 acpi root devices
Nov  9 18:23:33 node-2 kernel: [    1.314908] vgaarb: setting as boot device: PCI:0000:01:00.1
Nov  9 18:23:33 node-2 kernel: [    1.314910] vgaarb: device added: PCI:0000:01:00.1,decodes=io+mem,owns=io+mem,locks=none
Nov  9 18:23:33 node-2 kernel: [    1.314915] vgaarb: loaded
Nov  9 18:23:33 node-2 kernel: [    1.314917] vgaarb: bridge control possible 0000:01:00.1
Nov  9 18:23:33 node-2 kernel: [    1.315065] SCSI subsystem initialized
Nov  9 18:23:33 node-2 kernel: [    1.315207] libata version 3.00 loaded.
Nov  9 18:23:33 node-2 kernel: [    1.315223] ACPI: bus type USB registered
Nov  9 18:23:33 node-2 kernel: [    1.315240] usbcore: registered new interface driver usbfs
Nov  9 18:23:33 node-2 kernel: [    1.315246] usbcore: registered new interface driver hub
Nov  9 18:23:33 node-2 kernel: [    1.315281] usbcore: registered new device driver usb
Nov  9 18:23:33 node-2 kernel: [    1.315594] PCI: Using ACPI for IRQ routing
Nov  9 18:23:33 node-2 kernel: [    1.319481] PCI: pci_cache_line_size set to 64 bytes
Nov  9 18:23:33 node-2 kernel: [    1.319700] e820: reserve RAM buffer [mem 0x00094000-0x0009ffff]
Nov  9 18:23:33 node-2 kernel: [    1.319701] e820: reserve RAM buffer [mem 0x5ae24000-0x5bffffff]
Nov  9 18:23:33 node-2 kernel: [    1.319702] e820: reserve RAM buffer [mem 0x790ff000-0x7bffffff]
Nov  9 18:23:33 node-2 kernel: [    1.319703] e820: reserve RAM buffer [mem 0x7b800000-0x7bffffff]
Nov  9 18:23:33 node-2 kernel: [    1.319802] NetLabel: Initializing
Nov  9 18:23:33 node-2 kernel: [    1.319804] NetLabel:  domain hash size = 128
Nov  9 18:23:33 node-2 kernel: [    1.319805] NetLabel:  protocols = UNLABELED CIPSOv4
Nov  9 18:23:33 node-2 kernel: [    1.319819] NetLabel:  unlabeled traffic allowed by default
Nov  9 18:23:33 node-2 kernel: [    1.319884] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Nov  9 18:23:33 node-2 kernel: [    1.319889] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Nov  9 18:23:33 node-2 kernel: [    1.322031] Switched to clocksource hpet
Nov  9 18:23:33 node-2 kernel: [    1.327254] AppArmor: AppArmor Filesystem Enabled
Nov  9 18:23:33 node-2 kernel: [    1.327269] pnp: PnP ACPI init
Nov  9 18:23:33 node-2 kernel: [    1.327280] ACPI: bus type PNP registered
Nov  9 18:23:33 node-2 kernel: [    1.327434] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Nov  9 18:23:33 node-2 kernel: [    1.327557] pnp 00:01: [dma 4]
Nov  9 18:23:33 node-2 kernel: [    1.327576] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Nov  9 18:23:33 node-2 kernel: [    1.327602] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov  9 18:23:33 node-2 kernel: [    1.327629] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Nov  9 18:23:33 node-2 kernel: [    1.327651] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Nov  9 18:23:33 node-2 kernel: [    1.327700] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Nov  9 18:23:33 node-2 kernel: [    1.327780] system 00:06: [io  0x0500-0x053f] has been reserved
Nov  9 18:23:33 node-2 kernel: [    1.327783] system 00:06: [io  0x0400-0x047f] has been reserved
Nov  9 18:23:33 node-2 kernel: [    1.327785] system 00:06: [io  0x0540-0x057f] has been reserved
Nov  9 18:23:33 node-2 kernel: [    1.327787] system 00:06: [io  0x0600-0x061f] has been reserved
Nov  9 18:23:33 node-2 kernel: [    1.327789] system 00:06: [io  0x0880-0x0883] has been reserved
Nov  9 18:23:33 node-2 kernel: [    1.327791] system 00:06: [io  0x0800-0x081f] has been reserved
Nov  9 18:23:33 node-2 kernel: [    1.327794] system 00:06: [mem 0xfed1c000-0xfed3ffff] has been reserved
Nov  9 18:23:33 node-2 kernel: [    1.327796] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Nov  9 18:23:33 node-2 kernel: [    1.327799] system 00:06: [mem 0xff000000-0xffffffff] could not be reserved
Nov  9 18:23:33 node-2 kernel: [    1.327801] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Nov  9 18:23:33 node-2 kernel: [    1.327803] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Nov  9 18:23:33 node-2 kernel: [    1.327805] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Nov  9 18:23:33 node-2 kernel: [    1.327807] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Nov  9 18:23:33 node-2 kernel: [    1.327810] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov  9 18:23:33 node-2 kernel: [    1.327832] pnp 00:07: Plug and Play ACPI device, IDs IPI0001 (active)
Nov  9 18:23:33 node-2 kernel: [    1.327865] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Nov  9 18:23:33 node-2 kernel: [    1.327890] pnp 00:09: Plug and Play ACPI device, IDs PNP0501 (active)
Nov  9 18:23:33 node-2 kernel: [    1.327974] pnp: PnP ACPI: found 10 devices
Nov  9 18:23:33 node-2 kernel: [    1.327976] ACPI: bus type PNP unregistered
Nov  9 18:23:33 node-2 kernel: [    1.334552] pci 0000:00:02.0: BAR 14: assigned [mem 0x92b00000-0x92bfffff]
Nov  9 18:23:33 node-2 kernel: [    1.334556] pci 0000:00:02.2: BAR 15: assigned [mem 0x92c00000-0x92cfffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.334559] pci 0000:00:1c.2: BAR 15: assigned [mem 0x92d00000-0x92dfffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.334561] pci 0000:00:01.0: PCI bridge to [bus 02]
Nov  9 18:23:33 node-2 kernel: [    1.334567] pci 0000:00:01.1: PCI bridge to [bus 05]
Nov  9 18:23:33 node-2 kernel: [    1.334574] pci 0000:06:00.0: BAR 6: assigned [mem 0x95080000-0x950fffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.334577] pci 0000:06:00.1: BAR 6: assigned [mem 0x92b00000-0x92b7ffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.334579] pci 0000:00:02.0: PCI bridge to [bus 06]
Nov  9 18:23:33 node-2 kernel: [    1.334582] pci 0000:00:02.0:   bridge window [mem 0x92b00000-0x92bfffff]
Nov  9 18:23:33 node-2 kernel: [    1.334585] pci 0000:00:02.0:   bridge window [mem 0x93000000-0x950fffff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.334589] pci 0000:00:02.1: PCI bridge to [bus 0b]
Nov  9 18:23:33 node-2 kernel: [    1.334596] pci 0000:07:00.0: BAR 6: assigned [mem 0x92c00000-0x92c7ffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.334598] pci 0000:00:02.2: PCI bridge to [bus 07]
Nov  9 18:23:33 node-2 kernel: [    1.334600] pci 0000:00:02.2:   bridge window [io  0x3000-0x3fff]
Nov  9 18:23:33 node-2 kernel: [    1.334603] pci 0000:00:02.2:   bridge window [mem 0x95400000-0x955fffff]
Nov  9 18:23:33 node-2 kernel: [    1.334606] pci 0000:00:02.2:   bridge window [mem 0x92c00000-0x92cfffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.334610] pci 0000:00:02.3: PCI bridge to [bus 0c]
Nov  9 18:23:33 node-2 kernel: [    1.334617] pci 0000:08:00.0: BAR 6: assigned [mem 0x95380000-0x953fffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.334620] pci 0000:08:00.1: BAR 6: can't assign mem pref (size 0x80000)
Nov  9 18:23:33 node-2 kernel: [    1.334622] pci 0000:00:03.0: PCI bridge to [bus 08]
Nov  9 18:23:33 node-2 kernel: [    1.334624] pci 0000:00:03.0:   bridge window [io  0x2000-0x2fff]
Nov  9 18:23:33 node-2 kernel: [    1.334628] pci 0000:00:03.0:   bridge window [mem 0x95100000-0x953fffff]
Nov  9 18:23:33 node-2 kernel: [    1.334631] pci 0000:00:03.0:   bridge window [mem 0x39fffb00000-0x39fffefffff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.334635] pci 0000:00:03.1: PCI bridge to [bus 0d]
Nov  9 18:23:33 node-2 kernel: [    1.334641] pci 0000:00:03.2: PCI bridge to [bus 0e]
Nov  9 18:23:33 node-2 kernel: [    1.334647] pci 0000:00:03.3: PCI bridge to [bus 0f]
Nov  9 18:23:33 node-2 kernel: [    1.334653] pci 0000:00:1c.0: PCI bridge to [bus 10]
Nov  9 18:23:33 node-2 kernel: [    1.334663] pci 0000:01:00.2: BAR 6: assigned [mem 0x92d00000-0x92d0ffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.334665] pci 0000:00:1c.2: PCI bridge to [bus 01]
Nov  9 18:23:33 node-2 kernel: [    1.334667] pci 0000:00:1c.2:   bridge window [io  0x1000-0x1fff]
Nov  9 18:23:33 node-2 kernel: [    1.334672] pci 0000:00:1c.2:   bridge window [mem 0x90000000-0x92afffff]
Nov  9 18:23:33 node-2 kernel: [    1.334675] pci 0000:00:1c.2:   bridge window [mem 0x92d00000-0x92dfffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.334680] pci 0000:00:1c.4: PCI bridge to [bus 11]
Nov  9 18:23:33 node-2 kernel: [    1.334689] pci 0000:00:1c.6: PCI bridge to [bus 12]
Nov  9 18:23:33 node-2 kernel: [    1.334699] pci 0000:00:1c.7: PCI bridge to [bus 13]
Nov  9 18:23:33 node-2 kernel: [    1.334708] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Nov  9 18:23:33 node-2 kernel: [    1.334710] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Nov  9 18:23:33 node-2 kernel: [    1.334711] pci_bus 0000:00: resource 6 [io  0x03b0-0x03bb]
Nov  9 18:23:33 node-2 kernel: [    1.334712] pci_bus 0000:00: resource 7 [io  0x03c0-0x03df]
Nov  9 18:23:33 node-2 kernel: [    1.334713] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Nov  9 18:23:33 node-2 kernel: [    1.334715] pci_bus 0000:00: resource 9 [io  0x1000-0x9fff]
Nov  9 18:23:33 node-2 kernel: [    1.334716] pci_bus 0000:00: resource 10 [mem 0x90000000-0xc7ffbfff]
Nov  9 18:23:33 node-2 kernel: [    1.334717] pci_bus 0000:00: resource 11 [mem 0x38000000000-0x39fffffffff]
Nov  9 18:23:33 node-2 kernel: [    1.334719] pci_bus 0000:06: resource 1 [mem 0x92b00000-0x92bfffff]
Nov  9 18:23:33 node-2 kernel: [    1.334720] pci_bus 0000:06: resource 2 [mem 0x93000000-0x950fffff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.334721] pci_bus 0000:07: resource 0 [io  0x3000-0x3fff]
Nov  9 18:23:33 node-2 kernel: [    1.334723] pci_bus 0000:07: resource 1 [mem 0x95400000-0x955fffff]
Nov  9 18:23:33 node-2 kernel: [    1.334724] pci_bus 0000:07: resource 2 [mem 0x92c00000-0x92cfffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.334725] pci_bus 0000:08: resource 0 [io  0x2000-0x2fff]
Nov  9 18:23:33 node-2 kernel: [    1.334726] pci_bus 0000:08: resource 1 [mem 0x95100000-0x953fffff]
Nov  9 18:23:33 node-2 kernel: [    1.334728] pci_bus 0000:08: resource 2 [mem 0x39fffb00000-0x39fffefffff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.334729] pci_bus 0000:01: resource 0 [io  0x1000-0x1fff]
Nov  9 18:23:33 node-2 kernel: [    1.334730] pci_bus 0000:01: resource 1 [mem 0x90000000-0x92afffff]
Nov  9 18:23:33 node-2 kernel: [    1.334731] pci_bus 0000:01: resource 2 [mem 0x92d00000-0x92dfffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.334771] pci 0000:80:00.0: PCI bridge to [bus 8d]
Nov  9 18:23:33 node-2 kernel: [    1.334777] pci 0000:80:01.0: PCI bridge to [bus 81]
Nov  9 18:23:33 node-2 kernel: [    1.334784] pci 0000:80:01.1: PCI bridge to [bus 82]
Nov  9 18:23:33 node-2 kernel: [    1.334790] pci 0000:80:02.0: PCI bridge to [bus 83]
Nov  9 18:23:33 node-2 kernel: [    1.334796] pci 0000:80:02.1: PCI bridge to [bus 84]
Nov  9 18:23:33 node-2 kernel: [    1.334803] pci 0000:80:02.2: PCI bridge to [bus 85]
Nov  9 18:23:33 node-2 kernel: [    1.334809] pci 0000:80:02.3: PCI bridge to [bus 86]
Nov  9 18:23:33 node-2 kernel: [    1.334816] pci 0000:87:00.0: BAR 6: assigned [mem 0xc8280000-0xc82fffff pref]
Nov  9 18:23:33 node-2 kernel: [    1.334818] pci 0000:87:00.1: BAR 6: can't assign mem pref (size 0x80000)
Nov  9 18:23:33 node-2 kernel: [    1.334820] pci 0000:80:03.0: PCI bridge to [bus 87]
Nov  9 18:23:33 node-2 kernel: [    1.334822] pci 0000:80:03.0:   bridge window [io  0xa000-0xafff]
Nov  9 18:23:33 node-2 kernel: [    1.334826] pci 0000:80:03.0:   bridge window [mem 0xc8000000-0xc82fffff]
Nov  9 18:23:33 node-2 kernel: [    1.334829] pci 0000:80:03.0:   bridge window [mem 0x3bfffb00000-0x3bfffefffff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.334833] pci 0000:80:03.1: PCI bridge to [bus 8a]
Nov  9 18:23:33 node-2 kernel: [    1.334839] pci 0000:80:03.2: PCI bridge to [bus 8b]
Nov  9 18:23:33 node-2 kernel: [    1.334846] pci 0000:80:03.3: PCI bridge to [bus 8c]
Nov  9 18:23:33 node-2 kernel: [    1.334852] pci_bus 0000:80: resource 4 [io  0xa000-0xffff]
Nov  9 18:23:33 node-2 kernel: [    1.334853] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Nov  9 18:23:33 node-2 kernel: [    1.334855] pci_bus 0000:80: resource 6 [mem 0x3a000000000-0x3bfffffffff]
Nov  9 18:23:33 node-2 kernel: [    1.334856] pci_bus 0000:87: resource 0 [io  0xa000-0xafff]
Nov  9 18:23:33 node-2 kernel: [    1.334857] pci_bus 0000:87: resource 1 [mem 0xc8000000-0xc82fffff]
Nov  9 18:23:33 node-2 kernel: [    1.334859] pci_bus 0000:87: resource 2 [mem 0x3bfffb00000-0x3bfffefffff 64bit pref]
Nov  9 18:23:33 node-2 kernel: [    1.334904] NET: Registered protocol family 2
Nov  9 18:23:33 node-2 kernel: [    1.335431] TCP established hash table entries: 524288 (order: 10, 4194304 bytes)
Nov  9 18:23:33 node-2 kernel: [    1.336120] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Nov  9 18:23:33 node-2 kernel: [    1.336283] TCP: Hash tables configured (established 524288 bind 65536)
Nov  9 18:23:33 node-2 kernel: [    1.336321] TCP: reno registered
Nov  9 18:23:33 node-2 kernel: [    1.336453] UDP hash table entries: 65536 (order: 9, 2097152 bytes)
Nov  9 18:23:33 node-2 kernel: [    1.336874] UDP-Lite hash table entries: 65536 (order: 9, 2097152 bytes)
Nov  9 18:23:33 node-2 kernel: [    1.337382] NET: Registered protocol family 1
Nov  9 18:23:33 node-2 kernel: [    1.582226] pci 0000:01:00.1: Video device with shadowed ROM
Nov  9 18:23:33 node-2 kernel: [    1.582603] PCI: CLS 64 bytes, default 64
Nov  9 18:23:33 node-2 kernel: [    1.582682] Trying to unpack rootfs image as initramfs...
Nov  9 18:23:33 node-2 kernel: [    2.141732] Freeing initrd memory: 20388K (ffff88003581e000 - ffff880036c07000)
Nov  9 18:23:33 node-2 kernel: [    2.141832] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Nov  9 18:23:33 node-2 kernel: [    2.141838] software IO TLB [mem 0x750ff000-0x790ff000] (64MB) mapped at [ffff8800750ff000-ffff8800790fefff]
Nov  9 18:23:33 node-2 kernel: [    2.143950] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.143963] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.143983] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.143999] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144015] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144031] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144047] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144063] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144079] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144095] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144112] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144128] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144148] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144168] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144188] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144206] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144223] microcode: CPU16 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144240] microcode: CPU17 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144258] microcode: CPU18 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144275] microcode: CPU19 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144292] microcode: CPU20 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144310] microcode: CPU21 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144328] microcode: CPU22 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144346] microcode: CPU23 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144362] microcode: CPU24 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144378] microcode: CPU25 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144394] microcode: CPU26 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144407] microcode: CPU27 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144421] microcode: CPU28 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144435] microcode: CPU29 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144448] microcode: CPU30 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144462] microcode: CPU31 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144475] microcode: CPU32 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144489] microcode: CPU33 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144503] microcode: CPU34 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144516] microcode: CPU35 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144531] microcode: CPU36 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144546] microcode: CPU37 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144563] microcode: CPU38 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144578] microcode: CPU39 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144593] microcode: CPU40 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144607] microcode: CPU41 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144622] microcode: CPU42 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144637] microcode: CPU43 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144651] microcode: CPU44 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144667] microcode: CPU45 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144682] microcode: CPU46 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144697] microcode: CPU47 sig=0x306f2, pf=0x1, revision=0x2e
Nov  9 18:23:33 node-2 kernel: [    2.144812] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Nov  9 18:23:33 node-2 kernel: [    2.144820] Scanning for low memory corruption every 60 seconds
Nov  9 18:23:33 node-2 kernel: [    2.145946] Initialise system trusted keyring
Nov  9 18:23:33 node-2 kernel: [    2.146088] audit: initializing netlink socket (disabled)
Nov  9 18:23:33 node-2 kernel: [    2.146126] type=2000 audit(1478715675.924:1): initialized
Nov  9 18:23:33 node-2 kernel: [    2.199972] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov  9 18:23:33 node-2 kernel: [    2.206214] zbud: loaded
Nov  9 18:23:33 node-2 kernel: [    2.206510] VFS: Disk quotas dquot_6.5.2
Nov  9 18:23:33 node-2 kernel: [    2.206618] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Nov  9 18:23:33 node-2 kernel: [    2.207559] fuse init (API version 7.22)
Nov  9 18:23:33 node-2 kernel: [    2.207717] msgmni has been set to 32768
Nov  9 18:23:33 node-2 kernel: [    2.207844] Key type big_key registered
Nov  9 18:23:33 node-2 kernel: [    2.208754] Key type asymmetric registered
Nov  9 18:23:33 node-2 kernel: [    2.208758] Asymmetric key parser 'x509' registered
Nov  9 18:23:33 node-2 kernel: [    2.208816] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov  9 18:23:33 node-2 kernel: [    2.209004] io scheduler noop registered
Nov  9 18:23:33 node-2 kernel: [    2.209007] io scheduler deadline registered (default)
Nov  9 18:23:33 node-2 kernel: [    2.209061] io scheduler cfq registered
Nov  9 18:23:33 node-2 kernel: [    2.209925] pcieport 0000:00:01.0: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.209931] pcieport 0000:00:01.0: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.209981] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.210261] pcieport 0000:00:01.1: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.210265] pcieport 0000:00:01.1: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.210298] pcieport 0000:00:01.1: irq 91 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.210564] pcieport 0000:00:02.0: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.210569] pcieport 0000:00:02.0: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.210600] pcieport 0000:00:02.0: irq 92 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.210857] pcieport 0000:00:02.1: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.210861] pcieport 0000:00:02.1: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.210892] pcieport 0000:00:02.1: irq 93 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.211153] pcieport 0000:00:02.2: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.211157] pcieport 0000:00:02.2: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.211188] pcieport 0000:00:02.2: irq 94 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.211443] pcieport 0000:00:02.3: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.211447] pcieport 0000:00:02.3: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.211478] pcieport 0000:00:02.3: irq 95 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.211739] pcieport 0000:00:03.0: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.211743] pcieport 0000:00:03.0: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.211775] pcieport 0000:00:03.0: irq 96 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.212031] pcieport 0000:00:03.1: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.212035] pcieport 0000:00:03.1: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.212066] pcieport 0000:00:03.1: irq 97 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.212327] pcieport 0000:00:03.2: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.212331] pcieport 0000:00:03.2: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.212362] pcieport 0000:00:03.2: irq 98 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.212622] pcieport 0000:00:03.3: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.212626] pcieport 0000:00:03.3: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.212657] pcieport 0000:00:03.3: irq 99 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.212977] pcieport 0000:00:1c.0: irq 100 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.213075] pcieport 0000:00:1c.2: irq 101 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.213383] pcieport 0000:00:1c.4: irq 102 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.213700] pcieport 0000:00:1c.6: irq 103 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.214040] pcieport 0000:00:1c.7: irq 104 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.214291] pcieport 0000:80:00.0: irq 105 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.214509] pcieport 0000:80:01.0: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.214517] pcieport 0000:80:01.0: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.214553] pcieport 0000:80:01.0: irq 106 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.214680] pcieport 0000:80:01.1: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.214685] pcieport 0000:80:01.1: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.214718] pcieport 0000:80:01.1: irq 107 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.214842] pcieport 0000:80:02.0: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.214846] pcieport 0000:80:02.0: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.214880] pcieport 0000:80:02.0: irq 108 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.214997] pcieport 0000:80:02.1: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.215002] pcieport 0000:80:02.1: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.215042] pcieport 0000:80:02.1: irq 109 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.215165] pcieport 0000:80:02.2: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.215169] pcieport 0000:80:02.2: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.215202] pcieport 0000:80:02.2: irq 110 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.215316] pcieport 0000:80:02.3: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.215320] pcieport 0000:80:02.3: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.215352] pcieport 0000:80:02.3: irq 111 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.215472] pcieport 0000:80:03.0: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.215477] pcieport 0000:80:03.0: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.215510] pcieport 0000:80:03.0: irq 112 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.215624] pcieport 0000:80:03.1: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.215629] pcieport 0000:80:03.1: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.215661] pcieport 0000:80:03.1: irq 113 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.215779] pcieport 0000:80:03.2: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.215784] pcieport 0000:80:03.2: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.215816] pcieport 0000:80:03.2: irq 114 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.215928] pcieport 0000:80:03.3: can't derive routing for PCI INT A
Nov  9 18:23:33 node-2 kernel: [    2.215933] pcieport 0000:80:03.3: PCI INT A: no GSI
Nov  9 18:23:33 node-2 kernel: [    2.215965] pcieport 0000:80:03.3: irq 115 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    2.216102] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216112] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216134] pcieport 0000:00:01.1: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216139] pcie_pme 0000:00:01.1:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216160] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216165] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216168] pci 0000:06:00.1: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216174] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216193] pcieport 0000:00:02.1: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216199] pcie_pme 0000:00:02.1:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216217] pcieport 0000:00:02.2: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216222] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216227] pcie_pme 0000:00:02.2:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216247] pcieport 0000:00:02.3: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216253] pcie_pme 0000:00:02.3:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216279] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216284] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216287] pci 0000:08:00.1: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216293] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216312] pcieport 0000:00:03.1: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216318] pcie_pme 0000:00:03.1:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216337] pcieport 0000:00:03.2: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216342] pcie_pme 0000:00:03.2:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216372] pcieport 0000:00:03.3: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216377] pcie_pme 0000:00:03.3:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216399] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216405] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216426] pcieport 0000:00:1c.2: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216430] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216434] pci 0000:01:00.1: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216438] pci 0000:01:00.2: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216442] pci 0000:01:00.4: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216448] pcie_pme 0000:00:1c.2:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216467] pcieport 0000:00:1c.4: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216473] pcie_pme 0000:00:1c.4:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216493] pcieport 0000:00:1c.6: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216499] pcie_pme 0000:00:1c.6:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216519] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216525] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216549] pcieport 0000:80:00.0: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216554] pcie_pme 0000:80:00.0:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216575] pcieport 0000:80:01.0: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216580] pcie_pme 0000:80:01.0:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216623] pcieport 0000:80:01.1: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216629] pcie_pme 0000:80:01.1:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216652] pcieport 0000:80:02.0: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216658] pcie_pme 0000:80:02.0:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216681] pcieport 0000:80:02.1: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216687] pcie_pme 0000:80:02.1:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216709] pcieport 0000:80:02.2: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216715] pcie_pme 0000:80:02.2:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216737] pcieport 0000:80:02.3: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216743] pcie_pme 0000:80:02.3:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216765] pcieport 0000:80:03.0: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216769] pci 0000:87:00.0: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216773] pci 0000:87:00.1: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216779] pcie_pme 0000:80:03.0:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216801] pcieport 0000:80:03.1: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216807] pcie_pme 0000:80:03.1:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216828] pcieport 0000:80:03.2: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216834] pcie_pme 0000:80:03.2:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216865] pcieport 0000:80:03.3: Signaling PME through PCIe PME interrupt
Nov  9 18:23:33 node-2 kernel: [    2.216871] pcie_pme 0000:80:03.3:pcie01: service driver pcie_pme loaded
Nov  9 18:23:33 node-2 kernel: [    2.216911] ioapic: probe of 0000:00:05.4 failed with error -22
Nov  9 18:23:33 node-2 kernel: [    2.216948] ioapic: probe of 0000:80:05.4 failed with error -22
Nov  9 18:23:33 node-2 kernel: [    2.216960] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov  9 18:23:33 node-2 kernel: [    2.216985] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov  9 18:23:33 node-2 kernel: [    2.217092] vesafb: mode is 640x480x32, linelength=2560, pages=0
Nov  9 18:23:33 node-2 kernel: [    2.217095] vesafb: scrolling: redraw
Nov  9 18:23:33 node-2 kernel: [    2.217099] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Nov  9 18:23:33 node-2 kernel: [    2.439520] vesafb: framebuffer at 0x91000000, mapped to 0xffffc9001ce80000, using 1216k, total 1216k
Nov  9 18:23:33 node-2 kernel: [    2.452493] Console: switching to colour frame buffer device 80x30
Nov  9 18:23:33 node-2 kernel: [    2.465349] fb0: VESA VGA frame buffer device
Nov  9 18:23:33 node-2 kernel: [    2.465644] intel_idle: MWAIT substates: 0x2120
Nov  9 18:23:33 node-2 kernel: [    2.465646] intel_idle: v0.4 model 0x3F
Nov  9 18:23:33 node-2 kernel: [    2.465648] intel_idle: lapic_timer_reliable_states 0xffffffff
Nov  9 18:23:33 node-2 kernel: [    2.467162] ipmi message handler version 39.2
Nov  9 18:23:33 node-2 kernel: [    2.467584] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
Nov  9 18:23:33 node-2 kernel: [    2.468026] ACPI: Power Button [PWRF]
Nov  9 18:23:33 node-2 kernel: [    2.474485] ERST: Error Record Serialization Table (ERST) support is initialized.
Nov  9 18:23:33 node-2 kernel: [    2.485628] pstore: Registered erst as persistent store backend
Nov  9 18:23:33 node-2 kernel: [    2.492022] GHES: APEI firmware first mode is enabled by WHEA _OSC.
Nov  9 18:23:33 node-2 kernel: [    2.498614] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Nov  9 18:23:33 node-2 kernel: [    2.525951] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Nov  9 18:23:33 node-2 kernel: [    2.560481] 00:09: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Nov  9 18:23:33 node-2 kernel: [    2.577837] Linux agpgart interface v0.103
Nov  9 18:23:33 node-2 kernel: [    2.588368] brd: module loaded
Nov  9 18:23:33 node-2 kernel: [    2.597280] loop: module loaded
Nov  9 18:23:33 node-2 kernel: [    2.605868] libphy: Fixed MDIO Bus: probed
Nov  9 18:23:33 node-2 kernel: [    2.613807] tun: Universal TUN/TAP device driver, 1.6
Nov  9 18:23:33 node-2 kernel: [    2.621916] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov  9 18:23:33 node-2 kernel: [    2.630079] PPP generic driver version 2.4.2
Nov  9 18:23:33 node-2 kernel: [    2.638528] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov  9 18:23:33 node-2 kernel: [    2.646981] ehci-pci: EHCI PCI platform driver
Nov  9 18:23:33 node-2 kernel: [    2.655860] ehci-pci 0000:00:1a.0: EHCI Host Controller
Nov  9 18:23:33 node-2 kernel: [    2.664092] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Nov  9 18:23:33 node-2 kernel: [    2.680501] ehci-pci 0000:00:1a.0: debug port 2
Nov  9 18:23:33 node-2 kernel: [    2.692640] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Nov  9 18:23:33 node-2 kernel: [    2.692692] ehci-pci 0000:00:1a.0: irq 18, io mem 0x95601000
Nov  9 18:23:33 node-2 kernel: [    2.709777] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Nov  9 18:23:33 node-2 kernel: [    2.717781] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov  9 18:23:33 node-2 kernel: [    2.725740] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  9 18:23:33 node-2 kernel: [    2.741419] usb usb1: Product: EHCI Host Controller
Nov  9 18:23:33 node-2 kernel: [    2.749213] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov  9 18:23:33 node-2 kernel: [    2.757130] usb usb1: SerialNumber: 0000:00:1a.0
Nov  9 18:23:33 node-2 kernel: [    2.765045] hub 1-0:1.0: USB hub found
Nov  9 18:23:33 node-2 kernel: [    2.772609] hub 1-0:1.0: 2 ports detected
Nov  9 18:23:33 node-2 kernel: [    2.780441] ehci-pci 0000:00:1d.0: EHCI Host Controller
Nov  9 18:23:33 node-2 kernel: [    2.787887] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Nov  9 18:23:33 node-2 kernel: [    2.802300] ehci-pci 0000:00:1d.0: debug port 2
Nov  9 18:23:33 node-2 kernel: [    2.813311] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Nov  9 18:23:33 node-2 kernel: [    2.813321] ehci-pci 0000:00:1d.0: irq 18, io mem 0x95600000
Nov  9 18:23:33 node-2 kernel: [    2.829800] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Nov  9 18:23:33 node-2 kernel: [    2.836801] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Nov  9 18:23:33 node-2 kernel: [    2.843843] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  9 18:23:33 node-2 kernel: [    2.857935] usb usb2: Product: EHCI Host Controller
Nov  9 18:23:33 node-2 kernel: [    2.865254] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov  9 18:23:33 node-2 kernel: [    2.872673] usb usb2: SerialNumber: 0000:00:1d.0
Nov  9 18:23:33 node-2 kernel: [    2.880183] hub 2-0:1.0: USB hub found
Nov  9 18:23:33 node-2 kernel: [    2.887329] hub 2-0:1.0: 2 ports detected
Nov  9 18:23:33 node-2 kernel: [    2.894406] ehci-platform: EHCI generic platform driver
Nov  9 18:23:33 node-2 kernel: [    2.901431] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Nov  9 18:23:33 node-2 kernel: [    2.908478] ohci-pci: OHCI PCI platform driver
Nov  9 18:23:33 node-2 kernel: [    2.915519] ohci-platform: OHCI generic platform driver
Nov  9 18:23:33 node-2 kernel: [    2.922375] uhci_hcd: USB Universal Host Controller Interface driver
Nov  9 18:23:33 node-2 kernel: [    2.929616] uhci_hcd 0000:01:00.4: UHCI Host Controller
Nov  9 18:23:33 node-2 kernel: [    2.936758] uhci_hcd 0000:01:00.4: new USB bus registered, assigned bus number 3
Nov  9 18:23:33 node-2 kernel: [    2.951118] uhci_hcd 0000:01:00.4: port count misdetected? forcing to 2 ports
Nov  9 18:23:33 node-2 kernel: [    2.958523] uhci_hcd 0000:01:00.4: irq 19, io base 0x00001300
Nov  9 18:23:33 node-2 kernel: [    2.965802] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
Nov  9 18:23:33 node-2 kernel: [    2.973133] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  9 18:23:33 node-2 kernel: [    2.987694] usb usb3: Product: UHCI Host Controller
Nov  9 18:23:33 node-2 kernel: [    2.995186] usb usb3: Manufacturer: Linux 3.13.0-100-generic uhci_hcd
Nov  9 18:23:33 node-2 kernel: [    3.002913] usb usb3: SerialNumber: 0000:01:00.4
Nov  9 18:23:33 node-2 kernel: [    3.010691] hub 3-0:1.0: USB hub found
Nov  9 18:23:33 node-2 kernel: [    3.018227] hub 3-0:1.0: 2 ports detected
Nov  9 18:23:33 node-2 kernel: [    3.026030] xhci_hcd 0000:00:14.0: xHCI Host Controller
Nov  9 18:23:33 node-2 kernel: [    3.033463] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
Nov  9 18:23:33 node-2 kernel: [    3.049520] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
Nov  9 18:23:33 node-2 kernel: [    3.049579] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
Nov  9 18:23:33 node-2 kernel: [    3.057318] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  9 18:23:33 node-2 kernel: [    3.072665] usb usb4: Product: xHCI Host Controller
Nov  9 18:23:33 node-2 kernel: [    3.080278] usb usb4: Manufacturer: Linux 3.13.0-100-generic xhci_hcd
Nov  9 18:23:33 node-2 kernel: [    3.087919] usb usb4: SerialNumber: 0000:00:14.0
Nov  9 18:23:33 node-2 kernel: [    3.095716] hub 4-0:1.0: USB hub found
Nov  9 18:23:33 node-2 kernel: [    3.103254] hub 4-0:1.0: 15 ports detected
Nov  9 18:23:33 node-2 kernel: [    3.111939] xhci_hcd 0000:00:14.0: xHCI Host Controller
Nov  9 18:23:33 node-2 kernel: [    3.119598] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 5
Nov  9 18:23:33 node-2 kernel: [    3.121824] usb 1-1: new high-speed USB device number 2 using ehci-pci
Nov  9 18:23:33 node-2 kernel: [    3.142813] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003
Nov  9 18:23:33 node-2 kernel: [    3.150797] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  9 18:23:33 node-2 kernel: [    3.166281] usb usb5: Product: xHCI Host Controller
Nov  9 18:23:33 node-2 kernel: [    3.174019] usb usb5: Manufacturer: Linux 3.13.0-100-generic xhci_hcd
Nov  9 18:23:33 node-2 kernel: [    3.181826] usb usb5: SerialNumber: 0000:00:14.0
Nov  9 18:23:33 node-2 kernel: [    3.189521] tsc: Refined TSC clocksource calibration: 2497.107 MHz
Nov  9 18:23:33 node-2 kernel: [    3.197618] hub 5-0:1.0: USB hub found
Nov  9 18:23:33 node-2 kernel: [    3.205181] hub 5-0:1.0: 6 ports detected
Nov  9 18:23:33 node-2 kernel: [    3.213894] i8042: PNP: No PS/2 controller found. Probing ports directly.
Nov  9 18:23:33 node-2 kernel: [    3.223271] serio: i8042 KBD port at 0x60,0x64 irq 1
Nov  9 18:23:33 node-2 kernel: [    3.230883] serio: i8042 AUX port at 0x60,0x64 irq 12
Nov  9 18:23:33 node-2 kernel: [    3.238455] mousedev: PS/2 mouse device common for all mice
Nov  9 18:23:33 node-2 kernel: [    3.246117] rtc_cmos 00:02: RTC can wake from S4
Nov  9 18:23:33 node-2 kernel: [    3.253810] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Nov  9 18:23:33 node-2 kernel: [    3.261458] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov  9 18:23:33 node-2 kernel: [    3.274593] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Nov  9 18:23:33 node-2 kernel: [    3.274596] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  9 18:23:33 node-2 kernel: [    3.275363] hub 1-1:1.0: USB hub found
Nov  9 18:23:33 node-2 kernel: [    3.275574] hub 1-1:1.0: 6 ports detected
Nov  9 18:23:33 node-2 kernel: [    3.306834] device-mapper: uevent: version 1.0.3
Nov  9 18:23:33 node-2 kernel: [    3.314374] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Nov  9 18:23:33 node-2 kernel: [    3.329587] ledtrig-cpu: registered to indicate activity on CPUs
Nov  9 18:23:33 node-2 kernel: [    3.337721] TCP: cubic registered
Nov  9 18:23:33 node-2 kernel: [    3.345789] NET: Registered protocol family 10
Nov  9 18:23:33 node-2 kernel: [    3.353925] NET: Registered protocol family 17
Nov  9 18:23:33 node-2 kernel: [    3.361353] Key type dns_resolver registered
Nov  9 18:23:33 node-2 kernel: [    3.370426] Loading compiled-in X.509 certificates
Nov  9 18:23:33 node-2 kernel: [    3.379148] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Nov  9 18:23:33 node-2 kernel: [    3.389801] usb 2-1: new high-speed USB device number 2 using ehci-pci
Nov  9 18:23:33 node-2 kernel: [    3.401224] registered taskstats version 1
Nov  9 18:23:33 node-2 kernel: [    3.417141] Key type trusted registered
Nov  9 18:23:33 node-2 kernel: [    3.430030] Key type encrypted registered
Nov  9 18:23:33 node-2 kernel: [    3.437214] AppArmor: AppArmor sha1 policy hashing enabled
Nov  9 18:23:33 node-2 kernel: [    3.444734] IMA: No TPM chip found, activating TPM-bypass!
Nov  9 18:23:33 node-2 kernel: [    3.454214] regulator-dummy: disabling
Nov  9 18:23:33 node-2 kernel: [    3.461605]   Magic number: 8:439:392
Nov  9 18:23:33 node-2 kernel: [    3.468664] thermal cooling_device7: hash matches
Nov  9 18:23:33 node-2 kernel: [    3.476113] acpi ACPI0007:0f: hash matches
Nov  9 18:23:33 node-2 kernel: [    3.483388] memory memory672: hash matches
Nov  9 18:23:33 node-2 kernel: [    3.490818] rtc_cmos 00:02: setting system clock to 2016-11-09 18:21:18 UTC (1478715678)
Nov  9 18:23:33 node-2 kernel: [    3.506001] pcc-cpufreq: (v1.10.00) driver loaded with frequency limits: 1200 MHz, 2500 MHz
Nov  9 18:23:33 node-2 kernel: [    3.523270] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Nov  9 18:23:33 node-2 kernel: [    3.525115] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Nov  9 18:23:33 node-2 kernel: [    3.525116] EDD information not available.
Nov  9 18:23:33 node-2 kernel: [    3.525323] PM: Hibernation image not present or could not be loaded.
Nov  9 18:23:33 node-2 kernel: [    3.546647] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  9 18:23:33 node-2 kernel: [    3.547709] hub 2-1:1.0: USB hub found
Nov  9 18:23:33 node-2 kernel: [    3.547902] hub 2-1:1.0: 8 ports detected
Nov  9 18:23:33 node-2 kernel: [    3.570910] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Nov  9 18:23:33 node-2 kernel: [    3.586029] Write protecting the kernel read-only data: 12288k
Nov  9 18:23:33 node-2 kernel: [    3.594475] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Nov  9 18:23:33 node-2 kernel: [    3.611344] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Nov  9 18:23:33 node-2 kernel: [    3.654712] device-mapper: multipath: version 1.6.0 loaded
Nov  9 18:23:33 node-2 kernel: [    3.665510] systemd-udevd[442]: starting version 204
Nov  9 18:23:33 node-2 kernel: [    3.705482] md: linear personality registered for level -1
Nov  9 18:23:33 node-2 kernel: [    3.717965] usb 4-3: new high-speed USB device number 2 using xhci_hcd
Nov  9 18:23:33 node-2 kernel: [    3.722659] hpsa: module verification failed: signature and/or  required key missing - tainting kernel
Nov  9 18:23:33 node-2 kernel: [    3.736611] usb 4-3: New USB device found, idVendor=0424, idProduct=2660
Nov  9 18:23:33 node-2 kernel: [    3.736613] usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  9 18:23:33 node-2 kernel: [    3.740397] hub 4-3:1.0: USB hub found
Nov  9 18:23:33 node-2 kernel: [    3.740688] hub 4-3:1.0: 2 ports detected
Nov  9 18:23:33 node-2 kernel: [    3.785172] HP HPSA Driver (v 3.4.12-110)
Nov  9 18:23:33 node-2 kernel: [    3.794349] hpsa 0000:07:00.0: MSI-X capable controller
Nov  9 18:23:33 node-2 kernel: [    3.803478] hpsa 0000:07:00.0: irq 116 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    3.803484] hpsa 0000:07:00.0: irq 117 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    3.803489] hpsa 0000:07:00.0: irq 118 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    3.803501] hpsa 0000:07:00.0: irq 119 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    3.803521] hpsa 0000:07:00.0: Using 4 reply queue(s)
Nov  9 18:23:33 node-2 kernel: [    3.812353] pps_core: LinuxPPS API ver. 1 registered
Nov  9 18:23:33 node-2 kernel: [    3.812471] Physical aborts supported: yes
Nov  9 18:23:33 node-2 kernel: [    3.812473] Logical aborts supported: no
Nov  9 18:23:33 node-2 kernel: [    3.812473] HP SSD Smart Path aborts supported: yes
Nov  9 18:23:33 node-2 kernel: [    3.827933] hpsa 0000:07:00.0: hpsa0: <0x3239> at IRQ 116 using DAC
Nov  9 18:23:33 node-2 kernel: [    3.854885] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Nov  9 18:23:33 node-2 kernel: [    3.870696] bft2_offset = 0x8f4
Nov  9 18:23:33 node-2 kernel: [    3.880395] md: multipath personality registered for level -4
Nov  9 18:23:33 node-2 kernel: [    3.888059] scsi0 : hpsa
Nov  9 18:23:33 node-2 kernel: [    3.897190] bnx2x: Broadcom NetXtreme II 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.78.17-0 (2013/04/11)
Nov  9 18:23:33 node-2 kernel: [    3.906965] hpsa 0000:07:00.0: added scsi 0:3:0:0: RAID              HP      P244br          RAID-UNKNOWN SSDSmartPathCap- En- Exp=4 qd=1024
Nov  9 18:23:33 node-2 kernel: [    3.906979] hpsa 0000:07:00.0: added scsi 0:2:0:0: Direct-Access     HP       EG0600JEMCV      RAID-UNKNOWN SSDSmartPathCap- En- Exp=2 qd=58
Nov  9 18:23:33 node-2 kernel: [    3.907015] hpsa 0000:07:00.0: added scsi 0:2:1:0: Direct-Access     HP       EG0600JEMCV      RAID-UNKNOWN SSDSmartPathCap- En- Exp=2 qd=58
Nov  9 18:23:33 node-2 kernel: [    3.907082] hpsa 0000:07:00.0: added scsi 0:0:0:0: Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=4 qd=1024
Nov  9 18:23:33 node-2 kernel: [    3.910580] scsi 0:3:0:0: RAID              HP       P244br           3.00 PQ: 0 ANSI: 5
Nov  9 18:23:33 node-2 kernel: [    3.912615] scsi 0:0:0:0: Direct-Access     HP       LOGICAL VOLUME   3.00 PQ: 0 ANSI: 5
Nov  9 18:23:33 node-2 kernel: [    3.918205] scsi 0:3:0:0: Attached scsi generic sg0 type 12
Nov  9 18:23:33 node-2 kernel: [    3.924500] sd 0:0:0:0: Attached scsi generic sg1 type 0
Nov  9 18:23:33 node-2 kernel: [    3.930929] sd 0:0:0:0: [sda] 2344114096 512-byte logical blocks: (1.20 TB/1.09 TiB)
Nov  9 18:23:33 node-2 kernel: [    3.933379] sd 0:0:0:0: [sda] Write Protect is off
Nov  9 18:23:33 node-2 kernel: [    3.933438] sd 0:0:0:0: [sda] Mode Sense: 73 00 00 08
Nov  9 18:23:33 node-2 kernel: [    3.939321] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Nov  9 18:23:33 node-2 kernel: [    3.982400]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Nov  9 18:23:33 node-2 kernel: [    4.011821] sd 0:0:0:0: [sda] Attached SCSI disk
Nov  9 18:23:33 node-2 kernel: [    4.092912] bnx2x 0000:06:00.0: msix capability found
Nov  9 18:23:33 node-2 kernel: [    4.102141] PTP clock support registered
Nov  9 18:23:33 node-2 kernel: [    4.103594] bnx2x 0000:06:00.0: part number 0-0-0-0
Nov  9 18:23:33 node-2 kernel: [    4.119766] md: raid0 personality registered for level 0
Nov  9 18:23:33 node-2 kernel: [    4.130164] dca service started, version 1.12.1
Nov  9 18:23:33 node-2 kernel: [    4.139403] md: raid1 personality registered for level 1
Nov  9 18:23:33 node-2 kernel: [    4.148628] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 3.15.1-k
Nov  9 18:23:33 node-2 kernel: [    4.166040] ixgbe: Copyright (c) 1999-2013 Intel Corporation.
Nov  9 18:23:33 node-2 kernel: [    4.241558] raid6: sse2x1    7248 MB/s
Nov  9 18:23:33 node-2 kernel: [    4.317519] raid6: sse2x2    7788 MB/s
Nov  9 18:23:33 node-2 kernel: [    4.393526] raid6: sse2x4    8086 MB/s
Nov  9 18:23:33 node-2 kernel: [    4.469528] raid6: avx2x1   11895 MB/s
Nov  9 18:23:33 node-2 kernel: [    4.541498] raid6: avx2x2   15066 MB/s
Nov  9 18:23:33 node-2 kernel: [    4.613481] raid6: avx2x4   17010 MB/s
Nov  9 18:23:33 node-2 kernel: [    4.620712] raid6: using algorithm avx2x4 (17010 MB/s)
Nov  9 18:23:33 node-2 kernel: [    4.627869] raid6: using avx2x2 recovery algorithm
Nov  9 18:23:33 node-2 kernel: [    4.634822] Switched to clocksource tsc
Nov  9 18:23:33 node-2 kernel: [    4.634910] bnx2x 0000:06:00.0: irq 120 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.634963] bnx2x 0000:06:00.0: irq 121 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.635016] bnx2x 0000:06:00.0: irq 122 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.635046] bnx2x 0000:06:00.0: irq 123 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.635082] bnx2x 0000:06:00.0: irq 124 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.635126] bnx2x 0000:06:00.0: irq 125 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.635173] bnx2x 0000:06:00.0: irq 126 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.635223] bnx2x 0000:06:00.0: irq 127 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.635261] bnx2x 0000:06:00.0: irq 128 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.635314] bnx2x 0000:06:00.0: irq 129 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.636179] bnx2x 0000:06:00.1: msix capability found
Nov  9 18:23:33 node-2 kernel: [    4.637059] bnx2x 0000:06:00.1: part number 0-0-0-0
Nov  9 18:23:33 node-2 kernel: [    4.656152] xor: automatically using best checksumming function:
Nov  9 18:23:33 node-2 kernel: [    4.668876] ixgbe 0000:08:00.0: irq 130 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668882] ixgbe 0000:08:00.0: irq 131 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668887] ixgbe 0000:08:00.0: irq 132 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668896] ixgbe 0000:08:00.0: irq 133 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668901] ixgbe 0000:08:00.0: irq 134 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668905] ixgbe 0000:08:00.0: irq 135 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668910] ixgbe 0000:08:00.0: irq 136 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668914] ixgbe 0000:08:00.0: irq 137 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668919] ixgbe 0000:08:00.0: irq 138 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668923] ixgbe 0000:08:00.0: irq 139 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668928] ixgbe 0000:08:00.0: irq 140 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668933] ixgbe 0000:08:00.0: irq 141 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668937] ixgbe 0000:08:00.0: irq 142 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668942] ixgbe 0000:08:00.0: irq 143 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668946] ixgbe 0000:08:00.0: irq 144 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668951] ixgbe 0000:08:00.0: irq 145 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668955] ixgbe 0000:08:00.0: irq 146 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668960] ixgbe 0000:08:00.0: irq 147 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668964] ixgbe 0000:08:00.0: irq 148 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668973] ixgbe 0000:08:00.0: irq 149 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668978] ixgbe 0000:08:00.0: irq 150 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668982] ixgbe 0000:08:00.0: irq 151 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668986] ixgbe 0000:08:00.0: irq 152 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668991] ixgbe 0000:08:00.0: irq 153 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.668995] ixgbe 0000:08:00.0: irq 154 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669000] ixgbe 0000:08:00.0: irq 155 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669004] ixgbe 0000:08:00.0: irq 156 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669009] ixgbe 0000:08:00.0: irq 157 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669017] ixgbe 0000:08:00.0: irq 158 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669021] ixgbe 0000:08:00.0: irq 159 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669026] ixgbe 0000:08:00.0: irq 160 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669030] ixgbe 0000:08:00.0: irq 161 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669035] ixgbe 0000:08:00.0: irq 162 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669039] ixgbe 0000:08:00.0: irq 163 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669043] ixgbe 0000:08:00.0: irq 164 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669053] ixgbe 0000:08:00.0: irq 165 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669057] ixgbe 0000:08:00.0: irq 166 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669064] ixgbe 0000:08:00.0: irq 167 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669068] ixgbe 0000:08:00.0: irq 168 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669073] ixgbe 0000:08:00.0: irq 169 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669077] ixgbe 0000:08:00.0: irq 170 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669082] ixgbe 0000:08:00.0: irq 171 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669086] ixgbe 0000:08:00.0: irq 172 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669091] ixgbe 0000:08:00.0: irq 173 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669095] ixgbe 0000:08:00.0: irq 174 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669100] ixgbe 0000:08:00.0: irq 175 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669104] ixgbe 0000:08:00.0: irq 176 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669109] ixgbe 0000:08:00.0: irq 177 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669113] ixgbe 0000:08:00.0: irq 178 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.669198] ixgbe 0000:08:00.0: Multiqueue Enabled: Rx Queue count = 48, Tx Queue count = 48
Nov  9 18:23:33 node-2 kernel: [    4.682893] ixgbe 0000:08:00.0: PCI Express bandwidth of 32GT/s available
Nov  9 18:23:33 node-2 kernel: [    4.689919] ixgbe 0000:08:00.0: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Nov  9 18:23:33 node-2 kernel: [    4.697387] ixgbe 0000:08:00.0: MAC: 2, PHY: 1, PBA No: G43498-012
Nov  9 18:23:33 node-2 kernel: [    4.701533]    avx       : 28669.000 MB/sec
Nov  9 18:23:33 node-2 kernel: [    4.711242] ixgbe 0000:08:00.0: 5c:b9:01:8b:a1:1c
Nov  9 18:23:33 node-2 kernel: [    4.718859] async_tx: api initialized (async)
Nov  9 18:23:33 node-2 kernel: [    4.730504] md: raid6 personality registered for level 6
Nov  9 18:23:33 node-2 kernel: [    4.737189] md: raid5 personality registered for level 5
Nov  9 18:23:33 node-2 kernel: [    4.743595] md: raid4 personality registered for level 4
Nov  9 18:23:33 node-2 kernel: [    4.753513] md: raid10 personality registered for level 10
Nov  9 18:23:33 node-2 kernel: [    4.753546] ixgbe 0000:08:00.0: Intel(R) 10 Gigabit Network Connection
Nov  9 18:23:33 node-2 kernel: [    4.761504] bnx2x 0000:06:00.1: irq 179 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.761557] bnx2x 0000:06:00.1: irq 180 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.761609] bnx2x 0000:06:00.1: irq 181 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.761654] bnx2x 0000:06:00.1: irq 182 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.761703] bnx2x 0000:06:00.1: irq 183 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.761733] bnx2x 0000:06:00.1: irq 184 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.761766] bnx2x 0000:06:00.1: irq 185 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.761803] bnx2x 0000:06:00.1: irq 186 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.761844] bnx2x 0000:06:00.1: irq 187 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.761883] bnx2x 0000:06:00.1: irq 188 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.810051] random: lvm urandom read with 29 bits of entropy available
Nov  9 18:23:33 node-2 kernel: [    4.824406] multipathd (691): /proc/691/oom_adj is deprecated, please use /proc/691/oom_score_adj instead.
Nov  9 18:23:33 node-2 kernel: [    4.866004] ixgbe 0000:08:00.1: irq 189 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866010] ixgbe 0000:08:00.1: irq 190 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866015] ixgbe 0000:08:00.1: irq 191 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866023] ixgbe 0000:08:00.1: irq 192 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866027] ixgbe 0000:08:00.1: irq 193 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866032] ixgbe 0000:08:00.1: irq 194 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866036] ixgbe 0000:08:00.1: irq 195 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866041] ixgbe 0000:08:00.1: irq 196 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866045] ixgbe 0000:08:00.1: irq 197 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866049] ixgbe 0000:08:00.1: irq 198 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866059] ixgbe 0000:08:00.1: irq 199 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866063] ixgbe 0000:08:00.1: irq 200 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866067] ixgbe 0000:08:00.1: irq 201 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866072] ixgbe 0000:08:00.1: irq 202 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866076] ixgbe 0000:08:00.1: irq 203 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866080] ixgbe 0000:08:00.1: irq 204 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866085] ixgbe 0000:08:00.1: irq 205 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866089] ixgbe 0000:08:00.1: irq 206 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866093] ixgbe 0000:08:00.1: irq 207 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866097] ixgbe 0000:08:00.1: irq 208 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866102] ixgbe 0000:08:00.1: irq 209 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866106] ixgbe 0000:08:00.1: irq 210 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866113] ixgbe 0000:08:00.1: irq 211 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866117] ixgbe 0000:08:00.1: irq 212 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866121] ixgbe 0000:08:00.1: irq 213 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866126] ixgbe 0000:08:00.1: irq 214 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866134] ixgbe 0000:08:00.1: irq 215 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866139] ixgbe 0000:08:00.1: irq 216 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866143] ixgbe 0000:08:00.1: irq 217 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866148] ixgbe 0000:08:00.1: irq 218 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866152] ixgbe 0000:08:00.1: irq 219 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866157] ixgbe 0000:08:00.1: irq 220 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866161] ixgbe 0000:08:00.1: irq 221 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866165] ixgbe 0000:08:00.1: irq 222 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866169] ixgbe 0000:08:00.1: irq 223 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866173] ixgbe 0000:08:00.1: irq 224 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866177] ixgbe 0000:08:00.1: irq 225 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866181] ixgbe 0000:08:00.1: irq 226 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866186] ixgbe 0000:08:00.1: irq 227 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866190] ixgbe 0000:08:00.1: irq 228 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866194] ixgbe 0000:08:00.1: irq 229 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866198] ixgbe 0000:08:00.1: irq 230 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866205] ixgbe 0000:08:00.1: irq 231 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866209] ixgbe 0000:08:00.1: irq 232 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866213] ixgbe 0000:08:00.1: irq 233 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866220] ixgbe 0000:08:00.1: irq 234 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866224] ixgbe 0000:08:00.1: irq 235 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866229] ixgbe 0000:08:00.1: irq 236 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866233] ixgbe 0000:08:00.1: irq 237 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    4.866328] ixgbe 0000:08:00.1: Multiqueue Enabled: Rx Queue count = 48, Tx Queue count = 48
Nov  9 18:23:33 node-2 kernel: [    4.882894] ixgbe 0000:08:00.1: PCI Express bandwidth of 32GT/s available
Nov  9 18:23:33 node-2 kernel: [    4.891467] ixgbe 0000:08:00.1: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Nov  9 18:23:33 node-2 kernel: [    4.900358] ixgbe 0000:08:00.1: MAC: 2, PHY: 1, PBA No: G43498-012
Nov  9 18:23:33 node-2 kernel: [    4.909042] ixgbe 0000:08:00.1: 5c:b9:01:8b:a1:1d
Nov  9 18:23:33 node-2 kernel: [    4.943792] bio: create slab <bio-1> at 1
Nov  9 18:23:33 node-2 kernel: [    4.955069] ixgbe 0000:08:00.1: Intel(R) 10 Gigabit Network Connection
Nov  9 18:23:33 node-2 kernel: [    5.053395] ixgbe 0000:87:00.0: irq 238 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053406] ixgbe 0000:87:00.0: irq 239 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053411] ixgbe 0000:87:00.0: irq 240 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053415] ixgbe 0000:87:00.0: irq 241 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053420] ixgbe 0000:87:00.0: irq 242 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053424] ixgbe 0000:87:00.0: irq 243 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053429] ixgbe 0000:87:00.0: irq 244 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053433] ixgbe 0000:87:00.0: irq 245 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053438] ixgbe 0000:87:00.0: irq 246 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053442] ixgbe 0000:87:00.0: irq 247 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053446] ixgbe 0000:87:00.0: irq 248 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053451] ixgbe 0000:87:00.0: irq 249 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053455] ixgbe 0000:87:00.0: irq 250 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053459] ixgbe 0000:87:00.0: irq 251 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053464] ixgbe 0000:87:00.0: irq 252 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053468] ixgbe 0000:87:00.0: irq 253 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053472] ixgbe 0000:87:00.0: irq 254 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053481] ixgbe 0000:87:00.0: irq 255 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053488] ixgbe 0000:87:00.0: irq 256 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053492] ixgbe 0000:87:00.0: irq 257 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053497] ixgbe 0000:87:00.0: irq 258 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053501] ixgbe 0000:87:00.0: irq 259 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053510] ixgbe 0000:87:00.0: irq 260 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053514] ixgbe 0000:87:00.0: irq 261 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053519] ixgbe 0000:87:00.0: irq 262 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053525] ixgbe 0000:87:00.0: irq 263 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053529] ixgbe 0000:87:00.0: irq 264 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053534] ixgbe 0000:87:00.0: irq 265 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053538] ixgbe 0000:87:00.0: irq 266 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053542] ixgbe 0000:87:00.0: irq 267 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053547] ixgbe 0000:87:00.0: irq 268 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053551] ixgbe 0000:87:00.0: irq 269 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053556] ixgbe 0000:87:00.0: irq 270 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053560] ixgbe 0000:87:00.0: irq 271 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053564] ixgbe 0000:87:00.0: irq 272 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053568] ixgbe 0000:87:00.0: irq 273 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053572] ixgbe 0000:87:00.0: irq 274 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053577] ixgbe 0000:87:00.0: irq 275 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053581] ixgbe 0000:87:00.0: irq 276 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053585] ixgbe 0000:87:00.0: irq 277 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053590] ixgbe 0000:87:00.0: irq 278 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053603] ixgbe 0000:87:00.0: irq 279 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053612] ixgbe 0000:87:00.0: irq 280 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053622] ixgbe 0000:87:00.0: irq 281 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053631] ixgbe 0000:87:00.0: irq 282 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053640] ixgbe 0000:87:00.0: irq 283 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053649] ixgbe 0000:87:00.0: irq 284 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053658] ixgbe 0000:87:00.0: irq 285 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053667] ixgbe 0000:87:00.0: irq 286 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.053759] ixgbe 0000:87:00.0: Multiqueue Enabled: Rx Queue count = 48, Tx Queue count = 48
Nov  9 18:23:33 node-2 kernel: [    5.070557] ixgbe 0000:87:00.0: PCI Express bandwidth of 32GT/s available
Nov  9 18:23:33 node-2 kernel: [    5.079116] ixgbe 0000:87:00.0: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Nov  9 18:23:33 node-2 kernel: [    5.087953] ixgbe 0000:87:00.0: MAC: 2, PHY: 1, PBA No: G43498-012
Nov  9 18:23:33 node-2 kernel: [    5.096451] ixgbe 0000:87:00.0: 5c:b9:01:8b:a0:f0
Nov  9 18:23:33 node-2 kernel: [    5.144504] ixgbe 0000:87:00.0: Intel(R) 10 Gigabit Network Connection
Nov  9 18:23:33 node-2 kernel: [    5.245445] ixgbe 0000:87:00.1: irq 287 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245456] ixgbe 0000:87:00.1: irq 288 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245465] ixgbe 0000:87:00.1: irq 289 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245477] ixgbe 0000:87:00.1: irq 290 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245487] ixgbe 0000:87:00.1: irq 291 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245496] ixgbe 0000:87:00.1: irq 292 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245505] ixgbe 0000:87:00.1: irq 293 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245514] ixgbe 0000:87:00.1: irq 294 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245530] ixgbe 0000:87:00.1: irq 295 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245539] ixgbe 0000:87:00.1: irq 296 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245548] ixgbe 0000:87:00.1: irq 297 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245557] ixgbe 0000:87:00.1: irq 298 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245567] ixgbe 0000:87:00.1: irq 299 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245576] ixgbe 0000:87:00.1: irq 300 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245586] ixgbe 0000:87:00.1: irq 301 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245595] ixgbe 0000:87:00.1: irq 302 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245605] ixgbe 0000:87:00.1: irq 303 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245614] ixgbe 0000:87:00.1: irq 304 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245623] ixgbe 0000:87:00.1: irq 305 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245632] ixgbe 0000:87:00.1: irq 306 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245641] ixgbe 0000:87:00.1: irq 307 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245650] ixgbe 0000:87:00.1: irq 308 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245660] ixgbe 0000:87:00.1: irq 309 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245669] ixgbe 0000:87:00.1: irq 310 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245683] ixgbe 0000:87:00.1: irq 311 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245693] ixgbe 0000:87:00.1: irq 312 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245702] ixgbe 0000:87:00.1: irq 313 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245711] ixgbe 0000:87:00.1: irq 314 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245720] ixgbe 0000:87:00.1: irq 315 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245730] ixgbe 0000:87:00.1: irq 316 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245739] ixgbe 0000:87:00.1: irq 317 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245753] ixgbe 0000:87:00.1: irq 318 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245762] ixgbe 0000:87:00.1: irq 319 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245771] ixgbe 0000:87:00.1: irq 320 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245780] ixgbe 0000:87:00.1: irq 321 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245789] ixgbe 0000:87:00.1: irq 322 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245798] ixgbe 0000:87:00.1: irq 323 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245807] ixgbe 0000:87:00.1: irq 324 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245816] ixgbe 0000:87:00.1: irq 325 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245825] ixgbe 0000:87:00.1: irq 326 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245836] ixgbe 0000:87:00.1: irq 327 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245845] ixgbe 0000:87:00.1: irq 328 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245854] ixgbe 0000:87:00.1: irq 329 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245863] ixgbe 0000:87:00.1: irq 330 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245872] ixgbe 0000:87:00.1: irq 331 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245881] ixgbe 0000:87:00.1: irq 332 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245890] ixgbe 0000:87:00.1: irq 333 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245899] ixgbe 0000:87:00.1: irq 334 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245908] ixgbe 0000:87:00.1: irq 335 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [    5.245997] ixgbe 0000:87:00.1: Multiqueue Enabled: Rx Queue count = 48, Tx Queue count = 48
Nov  9 18:23:33 node-2 kernel: [    5.263743] ixgbe 0000:87:00.1: PCI Express bandwidth of 32GT/s available
Nov  9 18:23:33 node-2 kernel: [    5.272858] ixgbe 0000:87:00.1: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Nov  9 18:23:33 node-2 kernel: [    5.282179] ixgbe 0000:87:00.1: MAC: 2, PHY: 1, PBA No: G43498-012
Nov  9 18:23:33 node-2 kernel: [    5.291206] ixgbe 0000:87:00.1: 5c:b9:01:8b:a0:f1
Nov  9 18:23:33 node-2 kernel: [    5.335457] ixgbe 0000:87:00.1: Intel(R) 10 Gigabit Network Connection
Nov  9 18:23:33 node-2 kernel: [    6.199589] random: nonblocking pool is initialized
Nov  9 18:23:33 node-2 kernel: [    6.333976] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Nov  9 18:23:33 node-2 kernel: [    6.837499] init: plymouth-upstart-bridge main process (901) terminated with status 1
Nov  9 18:23:33 node-2 kernel: [    6.853738] init: plymouth-upstart-bridge main process ended, respawning
Nov  9 18:23:33 node-2 kernel: [    7.013412] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Nov  9 18:23:33 node-2 kernel: [    7.061626] Adding 4194300k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:4194300k FS
Nov  9 18:23:33 node-2 kernel: [    7.102985] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Nov  9 18:23:33 node-2 kernel: [    7.131827] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Nov  9 18:23:33 node-2 kernel: [    7.209088] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Nov  9 18:23:33 node-2 kernel: [    7.349339] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Nov  9 18:23:33 node-2 kernel: [    7.380058] XFS (dm-1): Mounting Filesystem
Nov  9 18:23:33 node-2 kernel: [    7.692233] XFS (dm-1): Ending clean mount
Nov  9 18:23:33 node-2 kernel: [    7.736158] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Nov  9 18:23:33 node-2 kernel: [    7.792936] XFS (dm-2): Mounting Filesystem
Nov  9 18:23:33 node-2 kernel: [    7.932434] XFS (dm-2): Ending clean mount
Nov  9 18:23:33 node-2 kernel: [    8.038175] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Nov  9 18:23:33 node-2 kernel: [    9.658065] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov  9 18:23:33 node-2 kernel: [    9.676425] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov  9 18:23:33 node-2 kernel: [    9.764702] dm-0: WRITE SAME failed. Manually zeroing.
Nov  9 18:23:33 node-2 kernel: [    9.869135] systemd-udevd[1132]: starting version 204
Nov  9 18:23:33 node-2 kernel: [   10.023210] wmi: Mapper loaded
Nov  9 18:23:33 node-2 kernel: [   10.033916] power_meter ACPI000D:00: Found ACPI power meter.
Nov  9 18:23:33 node-2 kernel: [   10.033948] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Nov  9 18:23:33 node-2 kernel: [   10.049123] IPMI System Interface driver.
Nov  9 18:23:33 node-2 kernel: [   10.049251] ipmi_si: probing via ACPI
Nov  9 18:23:33 node-2 kernel: [   10.049266] ipmi_si 00:07: [io  0x0ca2-0x0ca3] regsize 1 spacing 1 irq 0
Nov  9 18:23:33 node-2 kernel: [   10.049267] ipmi_si: Adding ACPI-specified kcs state machine
Nov  9 18:23:33 node-2 kernel: [   10.049304] ipmi_si: probing via SMBIOS
Nov  9 18:23:33 node-2 kernel: [   10.049306] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Nov  9 18:23:33 node-2 kernel: [   10.049307] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Nov  9 18:23:33 node-2 kernel: [   10.049309] ipmi_si: probing via SPMI
Nov  9 18:23:33 node-2 kernel: [   10.049311] ipmi_si: SPMI: io 0xca3 regsize 1 spacing 1 irq 0
Nov  9 18:23:33 node-2 kernel: [   10.049312] ipmi_si: Adding SPMI-specified kcs state machine
Nov  9 18:23:33 node-2 kernel: [   10.049314] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Nov  9 18:23:33 node-2 kernel: [   10.071504] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Nov  9 18:23:33 node-2 kernel: [   10.075474] ioatdma: Intel(R) QuickData Technology Driver 4.00
Nov  9 18:23:33 node-2 kernel: [   10.075845] ioatdma 0000:00:04.0: irq 336 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [   10.076836] ioatdma 0000:00:04.1: irq 337 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [   10.077626] ioatdma 0000:00:04.2: irq 338 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [   10.078436] ioatdma 0000:00:04.3: irq 339 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [   10.079037] ioatdma 0000:00:04.4: irq 340 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [   10.080256] ioatdma 0000:00:04.5: irq 341 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [   10.080847] ioatdma 0000:00:04.6: irq 342 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [   10.081198] ioatdma 0000:00:04.7: irq 343 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [   10.081712] ioatdma 0000:80:04.0: irq 344 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [   10.082723] ioatdma 0000:80:04.1: irq 345 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [   10.083374] ioatdma 0000:80:04.2: irq 346 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [   10.083887] ioatdma 0000:80:04.3: irq 347 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [   10.084364] ioatdma 0000:80:04.4: irq 348 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [   10.084730] ioatdma 0000:80:04.5: irq 349 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [   10.085128] ioatdma 0000:80:04.6: irq 350 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [   10.085533] ioatdma 0000:80:04.7: irq 351 for MSI/MSI-X
Nov  9 18:23:33 node-2 kernel: [   10.104552] systemd-udevd[1155]: renamed network interface eth2 to eno50
Nov  9 18:23:33 node-2 kernel: [   10.120530] systemd-udevd[1154]: renamed network interface eth0 to eno49
Nov  9 18:23:33 node-2 kernel: [   10.156594] systemd-udevd[1159]: renamed network interface eth3 to ens1f1
Nov  9 18:23:33 node-2 kernel: [   10.183450] systemd-udevd[1175]: renamed network interface eth5 to ens2f1
Nov  9 18:23:33 node-2 kernel: [   10.228559] systemd-udevd[1158]: renamed network interface eth1 to ens1f0
Nov  9 18:23:33 node-2 kernel: [   10.238117] ipmi_si 00:07: Found new BMC (man_id: 0x00000b, prod_id: 0x2020, dev_id: 0x13)
Nov  9 18:23:33 node-2 kernel: [   10.238125] ipmi_si 00:07: IPMI kcs interface initialized
Nov  9 18:23:33 node-2 kernel: [   10.240558] systemd-udevd[1174]: renamed network interface eth4 to ens2f0
Nov  9 18:23:33 node-2 kernel: [   10.567488] type=1400 audit(1478715685.573:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1511 comm="apparmor_parser"
Nov  9 18:23:33 node-2 kernel: [   10.567668] type=1400 audit(1478715685.573:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1511 comm="apparmor_parser"
Nov  9 18:23:33 node-2 kernel: [   10.567818] type=1400 audit(1478715685.573:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1511 comm="apparmor_parser"
Nov  9 18:23:33 node-2 kernel: [   10.590400] type=1400 audit(1478715685.597:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1494 comm="apparmor_parser"
Nov  9 18:23:33 node-2 kernel: [   10.590567] type=1400 audit(1478715685.597:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1494 comm="apparmor_parser"
Nov  9 18:23:33 node-2 kernel: [   10.590714] type=1400 audit(1478715685.597:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1494 comm="apparmor_parser"
Nov  9 18:23:33 node-2 kernel: [   10.591280] type=1400 audit(1478715685.597:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1416 comm="apparmor_parser"
Nov  9 18:23:33 node-2 kernel: [   10.591450] type=1400 audit(1478715685.597:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1416 comm="apparmor_parser"
Nov  9 18:23:33 node-2 kernel: [   10.591604] type=1400 audit(1478715685.597:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1416 comm="apparmor_parser"
Nov  9 18:23:33 node-2 kernel: [   10.593144] type=1400 audit(1478715685.601:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1415 comm="apparmor_parser"
Nov  9 18:23:33 node-2 kernel: [   11.147455] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov  9 18:23:33 node-2 kernel: [   11.147858] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov  9 18:23:33 node-2 kernel: [   11.869515] bnx2x 0000:06:00.0 eno49: using MSI-X  IRQs: sp 120  fp[0] 122 ... fp[7] 129
Nov  9 18:23:33 node-2 kernel: [   12.016246] IPv6: ADDRCONF(NETDEV_UP): eno49: link is not ready
Nov  9 18:23:33 node-2 kernel: [   14.367715] bnx2x 0000:06:00.0 eno49: NIC Link is Up, 10000 Mbps full duplex, Flow control: ON - receive & transmit
Nov  9 18:23:33 node-2 kernel: [   14.367738] IPv6: ADDRCONF(NETDEV_CHANGE): eno49: link becomes ready
Nov  9 18:23:33 node-2 kernel: [   20.041780] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Nov  9 18:23:33 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Nov  9 18:23:34 node-2 failsafe: Failsafe of 120 seconds reached.
Nov  9 18:23:34 node-2 kernel: [  139.633467] init: failsafe main process (8901) killed by TERM signal
Nov  9 18:23:34 node-2 dbus[8936]: [system] AppArmor D-Bus mediation is enabled
Nov  9 18:23:34 node-2 kernel: [  139.897729] audit_printk_skb: 54 callbacks suppressed
Nov  9 18:23:34 node-2 kernel: [  139.897732] type=1400 audit(1478715814.891:30): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=9027 comm="apparmor_parser"
Nov  9 18:23:34 node-2 kernel: [  139.897864] type=1400 audit(1478715814.891:31): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=9026 comm="apparmor_parser"
Nov  9 18:23:34 node-2 kernel: [  139.897869] type=1400 audit(1478715814.891:32): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=9026 comm="apparmor_parser"
Nov  9 18:23:34 node-2 kernel: [  139.897873] type=1400 audit(1478715814.891:33): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=9026 comm="apparmor_parser"
Nov  9 18:23:34 node-2 kernel: [  139.898132] type=1400 audit(1478715814.891:34): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=9026 comm="apparmor_parser"
Nov  9 18:23:34 node-2 kernel: [  139.898134] type=1400 audit(1478715814.891:35): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=9026 comm="apparmor_parser"
Nov  9 18:23:34 node-2 kernel: [  139.898280] type=1400 audit(1478715814.891:36): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=9026 comm="apparmor_parser"
Nov  9 18:23:34 node-2 kernel: [  139.972318] type=1400 audit(1478715814.967:37): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=9029 comm="apparmor_parser"
Nov  9 18:23:35 node-2 cron[9058]: (CRON) INFO (pidfile fd = 3)
Nov  9 18:23:35 node-2 anacron[9077]: Anacron 2.3 started on 2016-11-09
Nov  9 18:23:35 node-2 cron[9092]: (CRON) STARTUP (fork ok)
Nov  9 18:23:35 node-2 anacron[9077]: Will run job `cron.daily' in 5 min.
Nov  9 18:23:35 node-2 anacron[9077]: Will run job `cron.weekly' in 10 min.
Nov  9 18:23:35 node-2 anacron[9077]: Will run job `cron.monthly' in 15 min.
Nov  9 18:23:35 node-2 anacron[9077]: Jobs will be executed sequentially
Nov  9 18:23:35 node-2 multipathd: path checkers start up
Nov  9 18:23:35 node-2 cron[9092]: (CRON) INFO (Running @reboot jobs)
Nov  9 18:23:35 node-2 postfix/master[9234]: daemon started -- version 2.11.0, configuration /etc/postfix
Nov  9 18:23:53 node-2 puppet-agent[9465]: Reopening log files
Nov  9 18:23:55 node-2 puppet-agent[9465]: Could not request certificate: Connection refused - connect(2)
Nov  9 18:24:01 node-2 CRON[9687]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Nov  9 18:24:23 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  9 18:24:23 node-2 nailgun-agent: D, [2016-11-09T18:24:01.404500 #9690] DEBUG -- : Sleep for 22 seconds before sending request
Nov  9 18:24:23 node-2 nailgun-agent: I, [2016-11-09T18:24:23.420509 #9690]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov  9 18:24:30 node-2 puppet-user[9617]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Nov  9 18:24:30 node-2 puppet-user[9617]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.03 seconds
Nov  9 18:24:32 node-2 puppet-user[9617]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Nov  9 18:24:32 node-2 puppet-user[9617]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Nov  9 18:24:32 node-2 puppet-user[9617]: Finished catalog run in 1.87 seconds
Nov  9 18:24:39 node-2 nailgun-agent: D, [2016-11-09T18:24:39.003705 #9690] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Nov  9 18:24:41 node-2 kernel: [  206.938720] init: plymouth-upstart-bridge main process ended, respawning
Nov  9 18:24:42 node-2 puppet-agent[9465]: Could not run: SIGTERM
Nov  9 18:24:42 node-2 kernel: [  207.269390] ip_tables: (C) 2000-2006 Netfilter Core Team
Nov  9 18:24:42 node-2 ec2: 
Nov  9 18:24:42 node-2 ec2: #############################################################
Nov  9 18:24:42 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Nov  9 18:24:42 node-2 ec2: 1024 2c:ca:34:ae:14:99:60:3b:c6:12:91:ec:1e:f6:a0:5e  root@node-2.opnfvericsson.se (DSA)
Nov  9 18:24:42 node-2 ec2: 256 9a:b3:c3:ac:9a:b8:9a:fe:2f:36:de:95:ec:4a:31:b3  root@node-2.opnfvericsson.se (ECDSA)
Nov  9 18:24:42 node-2 ec2: 256 e0:e8:bb:4c:8b:39:96:cc:17:d7:bd:e8:04:e7:9d:84  root@node-2.opnfvericsson.se (ED25519)
Nov  9 18:24:42 node-2 ec2: 2048 f5:c4:4a:fc:6b:5e:98:56:f0:a9:5e:5f:e6:c7:fb:76  root@node-2.opnfvericsson.se (RSA)
Nov  9 18:24:42 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Nov  9 18:24:42 node-2 ec2: #############################################################
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.107391 #9690] DEBUG -- : Trying to find block devices
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.107634 #9690] DEBUG -- : Found block device: sda
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.107742 #9690] DEBUG -- : Block device info: {"size"=>"2344114096", "removable"=>"0", "model"=>"LOGICAL VOLUME", "rev"=>"3.00", "state"=>"running", "timeout"=>"30", "vendor"=>"HP"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.107802 #9690] DEBUG -- : Trying to get list of physical devices
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.108118 #9690] DEBUG -- : Getting udev properties for device: sda
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.112431 #9690] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3600508b1001c20c8b0029cbb680ee556 /dev/disk/by-id/wwn-0x600508b1001c20c8b0029cbb680ee556 /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"=>"PDZVU0RLM9A24V", "ID_SERIAL"=>"3600508b1001c20c8b0029cbb680ee556", "ID_SERIAL_SHORT"=>"600508b1001c20c8b0029cbb680ee556", "ID_TYPE"=>"disk", "ID_VENDOR"=>"HP", "ID_VENDOR_ENC"=>"HP\\x20\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x600508b1001c20c8", "ID_WWN_VENDOR_EXTENSION"=>"0xb0029cbb680ee556", "ID_WWN_WITH_EXTENSION"=>"0x600508b1001c20c8b0029cbb680ee556", "M
Nov  9 18:25:01 node-2 nailgun-agent: AJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"20531", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.112512 #9690] DEBUG -- : Trying to find out if device sda is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.112630 #9690] DEBUG -- : Device sda removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.112679 #9690] DEBUG -- : Device sda seems to be appropriate
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.113854 #9690] DEBUG -- : Getting udev properties for device: dm-0
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.117860 #9690] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-IfwxBo1aiiXctctseD11iDycjLYLOPJ3I1uuPpC0uYuCyemdOhpHyeK4cWloZHRU /dev/disk/by-uuid/d9f37881-6324-47a2-b31d-41746614aacd /dev/mapper/mongo-mongodb /dev/mongo/mongodb", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"mongodb", "DM_NAME"=>"mongo-mongodb", "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-IfwxBo1aiiXctctseD11iDycjLYLOPJ3I1uuPpC0uYuCyemdOhpHyeK4cWloZHRU", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d9f37881-6324-47a2-b31d-41746614aacd", "ID_FS_UUID_ENC"=>"d9f37881-6324-47a2-b31d-41746614aacd", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"22
Nov  9 18:25:01 node-2 nailgun-agent: 170", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.117940 #9690] DEBUG -- : Trying to find out if device dm-0 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.118029 #9690] DEBUG -- : Device dm-0 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.118073 #9690] DEBUG -- : Device dm-0 seems to be appropriate
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.118119 #9690] DEBUG -- : Getting udev properties for device: dm-1
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.122285 #9690] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-pW7KeQliqAOuyKTVbmPd6I6pJoGXQ95d3KX9AfM0Vh54MYST536ndUHQ0E09geiE /dev/disk/by-uuid/b9681ad1-01ea-473b-91de-77086ff3c6b4 /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "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-pW7KeQliqAOuyKTVbmPd6I6pJoGXQ95d3KX9AfM0Vh54MYST536ndUHQ0E09geiE", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b9681ad1-01ea-473b-91de-77086ff3c6b4", "ID_FS_UUID_ENC"=>"b9681ad1-01ea-473b-91de-77086ff3c6b4", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90148", "nomdmonddf"=>"1", "nomd
Nov  9 18:25:01 node-2 nailgun-agent: monisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.122367 #9690] DEBUG -- : Trying to find out if device dm-1 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.122459 #9690] DEBUG -- : Device dm-1 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.122502 #9690] DEBUG -- : Device dm-1 seems to be appropriate
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.122544 #9690] DEBUG -- : Getting udev properties for device: dm-2
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.126309 #9690] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-8DxTuFdujQm14QQdWBPfBZ0R3nBj2RRWT6ner93Us7S9OvEpAPGWHmuYNpeHNXZW /dev/disk/by-uuid/2a5e6cf2-4bab-4527-9f9f-1bbdbc5b4dff /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "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-8DxTuFdujQm14QQdWBPfBZ0R3nBj2RRWT6ner93Us7S9OvEpAPGWHmuYNpeHNXZW", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2a5e6cf2-4bab-4527-9f9f-1bbdbc5b4dff", "ID_FS_UUID_ENC"=>"2a5e6cf2-4bab-4527-9f9f-1bbdbc5b4dff", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"10
Nov  9 18:25:01 node-2 nailgun-agent: 617", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.126390 #9690] DEBUG -- : Trying to find out if device dm-2 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.126479 #9690] DEBUG -- : Device dm-2 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.126522 #9690] DEBUG -- : Device dm-2 seems to be appropriate
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.126568 #9690] DEBUG -- : Getting udev properties for device: dm-3
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.130386 #9690] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-7N8wB9KMlPa8pco9gVXQpa8GoFM6KwRh1pRpca9Ze52LVxwTRljR3j68JiE1I88s /dev/disk/by-uuid/92d8baeb-d35e-409a-b69a-87d0cb73d8db /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "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-7N8wB9KMlPa8pco9gVXQpa8GoFM6KwRh1pRpca9Ze52LVxwTRljR3j68JiE1I88s", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"92d8baeb-d35e-409a-b69a-87d0cb73d8db", "ID_FS_UUID_ENC"=>"92d8baeb-d35e-409a-b69a-87d0cb73d8db", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"21269", "nomdmond
Nov  9 18:25:01 node-2 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.130465 #9690] DEBUG -- : Trying to find out if device dm-3 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.130558 #9690] DEBUG -- : Device dm-3 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.130602 #9690] DEBUG -- : Device dm-3 seems to be appropriate
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.130647 #9690] DEBUG -- : Getting udev properties for device: dm-4
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.134463 #9690] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-tWqrVbcSLMvge6ux7mCwk9Q6iedfN0RPfL9DcaeI7YyKW05cEV7CP3GJibxJevpQ /dev/disk/by-uuid/0da97aac-38bf-486f-8cf6-1278590a4e02 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "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-tWqrVbcSLMvge6ux7mCwk9Q6iedfN0RPfL9DcaeI7YyKW05cEV7CP3GJibxJevpQ", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"0da97aac-38bf-486f-8cf6-1278590a4e02", "ID_FS_UUID_ENC"=>"0da97aac-38bf-486f-8cf6-1278590a4e02", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"20361", "nomdmonddf"=>"1", 
Nov  9 18:25:01 node-2 nailgun-agent: "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.134543 #9690] DEBUG -- : Trying to find out if device dm-4 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.134634 #9690] DEBUG -- : Device dm-4 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.134678 #9690] DEBUG -- : Device dm-4 seems to be appropriate
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.134725 #9690] DEBUG -- : Getting udev properties for device: dm-5
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.138883 #9690] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-N6dyjIMhpH8IcfxOslJVEH6bd9XOunVPpG1YsuO8R9LRYfRFSoVAHC3hSW8R0kAv /dev/disk/by-uuid/eed3d8cb-cc70-422e-b3a3-42005ac4da02 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "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-N6dyjIMhpH8IcfxOslJVEH6bd9XOunVPpG1YsuO8R9LRYfRFSoVAHC3hSW8R0kAv", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"eed3d8cb-cc70-422e-b3a3-42005ac4da02", "ID_FS_UUID_ENC"=>"eed3d8cb-cc70-422e-b3a3-42005ac4da02", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13428", "nomdmonddf"=>"1", "nomd
Nov  9 18:25:01 node-2 nailgun-agent: monisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.138960 #9690] DEBUG -- : Trying to find out if device dm-5 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.139052 #9690] DEBUG -- : Device dm-5 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.139098 #9690] DEBUG -- : Device dm-5 seems to be appropriate
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.139143 #9690] DEBUG -- : Getting udev properties for device: dm-6
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.143095 #9690] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-N6dyjIMhpH8IcfxOslJVEH6bd9XOunVPX2AEDsZ8TNDzpEeeknKrivuetMO2BDIf /dev/disk/by-uuid/619982fa-3cd5-4a67-b890-30828c0abb97 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-6", "DEVPATH"=>"/devices/virtual/block/dm-6", "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-N6dyjIMhpH8IcfxOslJVEH6bd9XOunVPX2AEDsZ8TNDzpEeeknKrivuetMO2BDIf", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"619982fa-3cd5-4a67-b890-30828c0abb97", "ID_FS_UUID_ENC"=>"619982fa-3cd5-4a67-b890-30828c0abb97", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14036", "nomdmonddf"=>"1", "nomdmonisw"
Nov  9 18:25:01 node-2 nailgun-agent: =>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.143172 #9690] DEBUG -- : Trying to find out if device dm-6 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.143264 #9690] DEBUG -- : Device dm-6 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.143305 #9690] DEBUG -- : Device dm-6 seems to be appropriate
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.143349 #9690] DEBUG -- : Getting udev properties for device: ram0
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.147021 #9690] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13878", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.147095 #9690] DEBUG -- : Trying to find out if device ram0 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.147189 #9690] DEBUG -- : Device ram0 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.147244 #9690] DEBUG -- : Getting udev properties for device: ram1
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.151121 #9690] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13888", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.151194 #9690] DEBUG -- : Trying to find out if device ram1 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.151284 #9690] DEBUG -- : Device ram1 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.151339 #9690] DEBUG -- : Getting udev properties for device: ram2
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.154883 #9690] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14362", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.154957 #9690] DEBUG -- : Trying to find out if device ram2 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.155056 #9690] DEBUG -- : Device ram2 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.155114 #9690] DEBUG -- : Getting udev properties for device: ram3
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.158838 #9690] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14381", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.158912 #9690] DEBUG -- : Trying to find out if device ram3 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.158999 #9690] DEBUG -- : Device ram3 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.159055 #9690] DEBUG -- : Getting udev properties for device: ram4
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.162824 #9690] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14395", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.162898 #9690] DEBUG -- : Trying to find out if device ram4 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.162988 #9690] DEBUG -- : Device ram4 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.163044 #9690] DEBUG -- : Getting udev properties for device: ram5
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.166585 #9690] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14409", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.166662 #9690] DEBUG -- : Trying to find out if device ram5 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.166756 #9690] DEBUG -- : Device ram5 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.166813 #9690] DEBUG -- : Getting udev properties for device: ram6
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.170319 #9690] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14425", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.170394 #9690] DEBUG -- : Trying to find out if device ram6 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.170485 #9690] DEBUG -- : Device ram6 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.170543 #9690] DEBUG -- : Getting udev properties for device: ram7
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.174451 #9690] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14439", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.174524 #9690] DEBUG -- : Trying to find out if device ram7 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.174616 #9690] DEBUG -- : Device ram7 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.174673 #9690] DEBUG -- : Getting udev properties for device: ram8
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.178070 #9690] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14458", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.178135 #9690] DEBUG -- : Trying to find out if device ram8 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.178216 #9690] DEBUG -- : Device ram8 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.178270 #9690] DEBUG -- : Getting udev properties for device: ram9
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.182489 #9690] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14476", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.182564 #9690] DEBUG -- : Trying to find out if device ram9 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.182658 #9690] DEBUG -- : Device ram9 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.182716 #9690] DEBUG -- : Getting udev properties for device: loop0
Nov  9 18:25:01 node-2 CRON[13024]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.187425 #9690] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13802", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.187501 #9690] DEBUG -- : Trying to find out if device loop0 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.187594 #9690] DEBUG -- : Device loop0 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.187654 #9690] DEBUG -- : Getting udev properties for device: loop1
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.191089 #9690] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13812", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.191180 #9690] DEBUG -- : Trying to find out if device loop1 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.191287 #9690] DEBUG -- : Device loop1 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.191350 #9690] DEBUG -- : Getting udev properties for device: loop2
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.194436 #9690] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13822", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.194512 #9690] DEBUG -- : Trying to find out if device loop2 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.194605 #9690] DEBUG -- : Device loop2 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.194662 #9690] DEBUG -- : Getting udev properties for device: loop3
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.198716 #9690] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13832", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.198792 #9690] DEBUG -- : Trying to find out if device loop3 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.198880 #9690] DEBUG -- : Device loop3 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.198939 #9690] DEBUG -- : Getting udev properties for device: loop4
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.202500 #9690] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13842", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.202574 #9690] DEBUG -- : Trying to find out if device loop4 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.202664 #9690] DEBUG -- : Device loop4 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.202720 #9690] DEBUG -- : Getting udev properties for device: loop5
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.206675 #9690] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13851", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.206750 #9690] DEBUG -- : Trying to find out if device loop5 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.206845 #9690] DEBUG -- : Device loop5 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.206903 #9690] DEBUG -- : Getting udev properties for device: loop6
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.210671 #9690] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13861", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.210751 #9690] DEBUG -- : Trying to find out if device loop6 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.210842 #9690] DEBUG -- : Device loop6 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.210899 #9690] DEBUG -- : Getting udev properties for device: loop7
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.214561 #9690] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13870", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.214634 #9690] DEBUG -- : Trying to find out if device loop7 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.214726 #9690] DEBUG -- : Device loop7 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.214780 #9690] DEBUG -- : Getting udev properties for device: ram10
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.218446 #9690] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13897", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.218522 #9690] DEBUG -- : Trying to find out if device ram10 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.218612 #9690] DEBUG -- : Device ram10 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.218670 #9690] DEBUG -- : Getting udev properties for device: ram11
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.222373 #9690] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13908", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.222447 #9690] DEBUG -- : Trying to find out if device ram11 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.222538 #9690] DEBUG -- : Device ram11 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.222593 #9690] DEBUG -- : Getting udev properties for device: ram12
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.226089 #9690] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13917", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.226166 #9690] DEBUG -- : Trying to find out if device ram12 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.226258 #9690] DEBUG -- : Device ram12 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.226319 #9690] DEBUG -- : Getting udev properties for device: ram13
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.229813 #9690] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13930", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.229895 #9690] DEBUG -- : Trying to find out if device ram13 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.229992 #9690] DEBUG -- : Device ram13 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.230050 #9690] DEBUG -- : Getting udev properties for device: ram14
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.233565 #9690] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14085", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.233684 #9690] DEBUG -- : Trying to find out if device ram14 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.233785 #9690] DEBUG -- : Device ram14 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.233844 #9690] DEBUG -- : Getting udev properties for device: ram15
Nov  9 18:25:01 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.237395 #9690] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14105", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.237470 #9690] DEBUG -- : Trying to find out if device ram15 is removable or not
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.237562 #9690] DEBUG -- : Device ram15 removable parameter: "0"
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.237675 #9690] 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-0x600508b1001c20c8b0029cbb680ee556", "disk/by-id/scsi-3600508b1001c20c8b0029cbb680ee556"], :removable=>"0"}]
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.237722 #9690] DEBUG -- : Block device seems to be physical data storage: sda
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.237820 #9690] DEBUG -- : Found block device: dm-0
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.237865 #9690] DEBUG -- : Block device info: {"size"=>"1071538176", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.237906 #9690] DEBUG -- : Found block device: dm-1
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.237944 #9690] DEBUG -- : Block device info: {"size"=>"1071538176", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.237973 #9690] DEBUG -- : Found block device: dm-2
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238004 #9690] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238036 #9690] DEBUG -- : Found block device: dm-3
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238065 #9690] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238091 #9690] DEBUG -- : Found block device: dm-4
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238117 #9690] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238145 #9690] DEBUG -- : Found block device: dm-5
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238175 #9690] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238202 #9690] DEBUG -- : Found block device: dm-6
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238231 #9690] DEBUG -- : Block device info: {"size"=>"8388608", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238260 #9690] DEBUG -- : Found block device: ram0
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238294 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238322 #9690] DEBUG -- : Found block device: ram1
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238353 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238381 #9690] DEBUG -- : Found block device: ram2
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238413 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238438 #9690] DEBUG -- : Found block device: ram3
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238470 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238497 #9690] DEBUG -- : Found block device: ram4
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238528 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238553 #9690] DEBUG -- : Found block device: ram5
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238584 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238611 #9690] DEBUG -- : Found block device: ram6
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238644 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238672 #9690] DEBUG -- : Found block device: ram7
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238702 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238732 #9690] DEBUG -- : Found block device: ram8
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238763 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238787 #9690] DEBUG -- : Found block device: ram9
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238818 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238845 #9690] DEBUG -- : Found block device: loop0
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238875 #9690] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238900 #9690] DEBUG -- : Found block device: loop1
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238929 #9690] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238956 #9690] DEBUG -- : Found block device: loop2
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.238988 #9690] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239014 #9690] DEBUG -- : Found block device: loop3
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239044 #9690] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239072 #9690] DEBUG -- : Found block device: loop4
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239103 #9690] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239129 #9690] DEBUG -- : Found block device: loop5
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239159 #9690] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239186 #9690] DEBUG -- : Found block device: loop6
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239219 #9690] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239247 #9690] DEBUG -- : Found block device: loop7
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239276 #9690] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239303 #9690] DEBUG -- : Found block device: ram10
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239334 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239363 #9690] DEBUG -- : Found block device: ram11
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239394 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239421 #9690] DEBUG -- : Found block device: ram12
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239453 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239478 #9690] DEBUG -- : Found block device: ram13
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239511 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239537 #9690] DEBUG -- : Found block device: ram14
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239567 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239593 #9690] DEBUG -- : Found block device: ram15
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239624 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.239706 #9690] 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-0x600508b1001c20c8b0029cbb680ee556", "disk/by-id/scsi-3600508b1001c20c8b0029cbb680ee556"], :removable=>"0", :paths=>nil}]
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.358276 #9690] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Nov  9 18:25:01 node-2 nailgun-agent: D, [2016-11-09T18:25:01.358375 #9690] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Nov  9 18:25:04 node-2 multipathd: uevent trigger error
Nov  9 18:25:04 node-2 puppet-user[11711]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov  9 18:25:04 node-2 puppet-user[11711]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.11 seconds
Nov  9 18:25:05 node-2 puppet-user[11711]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Nov  9 18:25:05 node-2 puppet-user[11711]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Nov  9 18:25:05 node-2 puppet-user[11711]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Nov  9 18:25:05 node-2 puppet-user[11711]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Nov  9 18:25:05 node-2 puppet-user[11711]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Nov  9 18:25:05 node-2 puppet-user[11711]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Nov  9 18:25:05 node-2 puppet-user[11711]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Nov  9 18:25:05 node-2 puppet-user[11711]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Nov  9 18:25:05 node-2 puppet-user[11711]: Finished catalog run in 0.02 seconds
Nov  9 18:25:23 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.226937 #9690] DEBUG -- : Trying to find block devices
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227186 #9690] DEBUG -- : Found block device: sda
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227264 #9690] DEBUG -- : Block device info: {"size"=>"2344114096", "removable"=>"0", "model"=>"LOGICAL VOLUME", "rev"=>"3.00", "state"=>"running", "timeout"=>"30", "vendor"=>"HP"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227317 #9690] DEBUG -- : Block device seems to be physical data storage: sda
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227377 #9690] DEBUG -- : Found block device: dm-0
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227418 #9690] DEBUG -- : Block device info: {"size"=>"1071538176", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227453 #9690] DEBUG -- : Found block device: dm-1
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227483 #9690] DEBUG -- : Block device info: {"size"=>"1071538176", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227512 #9690] DEBUG -- : Found block device: dm-2
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227544 #9690] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227573 #9690] DEBUG -- : Found block device: dm-3
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227609 #9690] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227635 #9690] DEBUG -- : Found block device: dm-4
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227668 #9690] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227693 #9690] DEBUG -- : Found block device: dm-5
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227723 #9690] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227753 #9690] DEBUG -- : Found block device: dm-6
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227784 #9690] DEBUG -- : Block device info: {"size"=>"8388608", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227813 #9690] DEBUG -- : Found block device: ram0
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227845 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227873 #9690] DEBUG -- : Found block device: ram1
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227905 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227931 #9690] DEBUG -- : Found block device: ram2
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227962 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.227986 #9690] DEBUG -- : Found block device: ram3
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228019 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228047 #9690] DEBUG -- : Found block device: ram4
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228078 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228108 #9690] DEBUG -- : Found block device: ram5
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228137 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228166 #9690] DEBUG -- : Found block device: ram6
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228199 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228228 #9690] DEBUG -- : Found block device: ram7
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228263 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228294 #9690] DEBUG -- : Found block device: ram8
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228327 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228356 #9690] DEBUG -- : Found block device: ram9
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228389 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228417 #9690] DEBUG -- : Found block device: loop0
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228449 #9690] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228477 #9690] DEBUG -- : Found block device: loop1
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228513 #9690] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228542 #9690] DEBUG -- : Found block device: loop2
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228571 #9690] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228595 #9690] DEBUG -- : Found block device: loop3
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228627 #9690] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228654 #9690] DEBUG -- : Found block device: loop4
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228685 #9690] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228711 #9690] DEBUG -- : Found block device: loop5
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228742 #9690] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228768 #9690] DEBUG -- : Found block device: loop6
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228802 #9690] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228829 #9690] DEBUG -- : Found block device: loop7
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228862 #9690] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228888 #9690] DEBUG -- : Found block device: ram10
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228917 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228944 #9690] DEBUG -- : Found block device: ram11
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.228973 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.229003 #9690] DEBUG -- : Found block device: ram12
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.229032 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.229056 #9690] DEBUG -- : Found block device: ram13
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.229088 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.229116 #9690] DEBUG -- : Found block device: ram14
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.229147 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.229173 #9690] DEBUG -- : Found block device: ram15
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.229204 #9690] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.229284 #9690] 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-0x600508b1001c20c8b0029cbb680ee556", "disk/by-id/scsi-3600508b1001c20c8b0029cbb680ee556"], :removable=>"0", :paths=>nil}]
Nov  9 18:25:23 node-2 nailgun-agent: D, [2016-11-09T18:25:23.430134 #9690] DEBUG -- : Response: status: 200 body: {"id": 2}
Nov  9 18:25:23 node-2 nailgun-agent: I, [2016-11-09T18:25:23.430564 #9690]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Nov  9 18:25:37 node-2 puppet-user[13662]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Nov  9 18:25:37 node-2 puppet-user[13662]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.10 seconds
Nov  9 18:25:37 node-2 puppet-user[13662]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Nov  9 18:25:37 node-2 puppet-user[13662]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Nov  9 18:25:37 node-2 puppet-user[13662]: Finished catalog run in 0.02 seconds
Nov  9 18:26:01 node-2 CRON[15647]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Nov  9 18:26:10 node-2 puppet-user[15113]: (Scope(Class[main])) MODULAR: configuration_symlink
Nov  9 18:26:10 node-2 puppet-user[15113]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.04 seconds
Nov  9 18:26:10 node-2 puppet-user[15113]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Nov  9 18:26:10 node-2 puppet-user[15113]: Finished catalog run in 0.03 seconds
Nov  9 18:26:26 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  9 18:26:26 node-2 nailgun-agent: I, [2016-11-09T18:26:26.646631 #15650]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov  9 18:26:43 node-2 puppet-user[16378]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Nov  9 18:26:43 node-2 puppet-user[16378]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.21 seconds
Nov  9 18:26:43 node-2 puppet-user[16378]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Nov  9 18:26:43 node-2 puppet-user[16378]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-kvm-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-kvm-0.9/]/returns) executed successfully
Nov  9 18:26:43 node-2 puppet-user[16378]: Finished catalog run in 0.42 seconds
Nov  9 18:27:01 node-2 CRON[18212]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Nov  9 18:27:04 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  9 18:27:04 node-2 nailgun-agent: I, [2016-11-09T18:27:04.728046 #15650]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Nov  9 18:27:15 node-2 puppet-user[17798]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Nov  9 18:27:16 node-2 puppet-user[17798]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.27 seconds
Nov  9 18:27:16 node-2 puppet-user[17798]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Nov  9 18:27:16 node-2 puppet-user[17798]: (/Stage[main]/Apt/File[preferences]/ensure) created
Nov  9 18:27:16 node-2 puppet-user[17798]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-kvm-0.9.0]/Apt::Setting[list-fuel-plugin-kvm-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-kvm-0.9.0.list]/ensure) created
Nov  9 18:27:16 node-2 puppet-user[17798]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Nov  9 18:27:16 node-2 puppet-user[17798]: Finished catalog run in 0.13 seconds
Nov  9 18:27:48 node-2 puppet-user[19361]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Nov  9 18:27:49 node-2 puppet-user[19361]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.18 seconds
Nov  9 18:27:49 node-2 puppet-user[19361]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Nov  9 18:27:49 node-2 kernel: [  394.262690] nr_pdflush_threads exported in /proc is scheduled for removal
Nov  9 18:27:49 node-2 kernel: [  394.262762] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Nov  9 18:27:49 node-2 puppet-user[19361]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Nov  9 18:27:49 node-2 puppet-user[19361]: Finished catalog run in 0.11 seconds
Nov  9 18:28:01 node-2 CRON[20798]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Nov  9 18:28:09 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  9 18:28:09 node-2 nailgun-agent: I, [2016-11-09T18:28:09.925352 #20801]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov  9 18:28:23 node-2 puppet-user[20558]: (Scope(Class[main])) MODULAR: sync_time
Nov  9 18:28:23 node-2 puppet-user[20558]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.04 seconds
Nov  9 18:28:23 node-2 ntpdate[21849]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Nov  9 18:28:29 node-2 ntpdate[21849]: adjust time server 10.20.0.2 offset 0.001103 sec
Nov  9 18:28:29 node-2 puppet-user[20558]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Nov  9 18:28:29 node-2 puppet-user[20558]: Finished catalog run in 6.15 seconds
Nov  9 18:28:35 node-2 anacron[9077]: Job `cron.daily' started
Nov  9 18:28:35 node-2 anacron[22243]: Updated timestamp for job `cron.daily' to 2016-11-09
Nov  9 18:28:37 node-2 anacron[9077]: Job `cron.daily' terminated
Nov  9 18:28:48 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  9 18:28:48 node-2 nailgun-agent: I, [2016-11-09T18:28:48.209255 #20801]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Nov  9 18:29:01 node-2 CRON[23837]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Nov  9 18:29:01 node-2 puppet-user[22115]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov  9 18:29:01 node-2 puppet-user[22115]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.10 seconds
Nov  9 18:29:02 node-2 puppet-user[22115]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Nov  9 18:29:02 node-2 puppet-user[22115]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-kvm"]'
Nov  9 18:29:02 node-2 puppet-user[22115]: Finished catalog run in 0.04 seconds
Nov  9 18:29:18 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  9 18:29:18 node-2 nailgun-agent: I, [2016-11-09T18:29:18.433931 #23840]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov  9 18:29:34 node-2 puppet-user[24155]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Nov  9 18:29:34 node-2 puppet-user[24155]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.51 seconds
Nov  9 18:29:35 node-2 puppet-user[24155]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Nov  9 18:29:35 node-2 puppet-user[24155]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Nov  9 18:29:35 node-2 puppet-user[24155]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Nov  9 18:29:35 node-2 puppet-user[24155]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Nov  9 18:29:35 node-2 puppet-user[24155]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Nov  9 18:29:35 node-2 puppet-user[24155]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Nov  9 18:29:35 node-2 puppet-user[24155]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Nov  9 18:29:35 node-2 puppet-user[24155]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Nov  9 18:29:35 node-2 puppet-user[24155]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Nov  9 18:29:35 node-2 puppet-user[24155]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Nov  9 18:29:35 node-2 puppet-user[24155]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Nov  9 18:29:35 node-2 puppet-user[24155]: Finished catalog run in 0.63 seconds
Nov  9 18:29:56 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  9 18:29:56 node-2 nailgun-agent: I, [2016-11-09T18:29:56.365237 #23840]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Nov  9 18:30:01 node-2 CRON[26343]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Nov  9 18:30:07 node-2 puppet-user[25546]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Nov  9 18:30:08 node-2 puppet-user[25546]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.14 seconds
Nov  9 18:30:09 node-2 puppet-user[25546]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Nov  9 18:30:16 node-2 puppet-user[25546]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Nov  9 18:30:16 node-2 puppet-user[25546]: Finished catalog run in 8.12 seconds
Nov  9 18:30:17 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  9 18:30:17 node-2 nailgun-agent: I, [2016-11-09T18:30:17.587999 #26346]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov  9 18:30:48 node-2 puppet-user[28301]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Nov  9 18:30:49 node-2 puppet-user[28301]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.61 seconds
Nov  9 18:30:49 node-2 puppet-user[28301]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Nov  9 18:30:49 node-2 puppet-user[28301]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Nov  9 18:30:49 node-2 puppet-user[28301]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Nov  9 18:30:49 node-2 puppet-user[28301]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Nov  9 18:30:49 node-2 puppet-user[28301]: Finished catalog run in 0.03 seconds
Nov  9 18:30:55 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  9 18:30:55 node-2 nailgun-agent: I, [2016-11-09T18:30:55.621897 #26346]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Nov  9 18:31:01 node-2 CRON[30244]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Nov  9 18:31:21 node-2 puppet-user[29694]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Nov  9 18:31:22 node-2 puppet-user[29694]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.76 seconds
Nov  9 18:31:22 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Nov  9 18:31:22 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Nov  9 18:31:22 node-2 crontab[31218]: (root) LIST (root)
Nov  9 18:31:22 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Nov  9 18:31:22 node-2 crontab[31219]: (root) REPLACE (root)
Nov  9 18:31:22 node-2 puppet-user[29694]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Nov  9 18:31:23 node-2 puppet-user[29694]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Nov  9 18:31:23 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8874" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 18:31:23 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Nov  9 18:31:56 node-2 multipathd: uevent trigger error
<27>Nov  9 18:31:56 node-2 multipathd: uevent trigger error
<27>Nov  9 18:31:56 node-2 multipathd: uevent trigger error
<27>Nov  9 18:31:56 node-2 multipathd: uevent trigger error
<27>Nov  9 18:31:56 node-2 multipathd: uevent trigger error
<27>Nov  9 18:31:56 node-2 multipathd: uevent trigger error
<27>Nov  9 18:32:34 node-2 multipathd: uevent trigger error
<27>Nov  9 18:32:34 node-2 multipathd: uevent trigger error
<27>Nov  9 18:32:34 node-2 multipathd: uevent trigger error
<27>Nov  9 18:32:34 node-2 multipathd: uevent trigger error
<27>Nov  9 18:32:34 node-2 multipathd: uevent trigger error
<27>Nov  9 18:33:27 node-2 ntpdate[42890]: no servers can be used, exiting
<27>Nov  9 18:34:31 node-2 multipathd: uevent trigger error
<27>Nov  9 18:34:31 node-2 multipathd: uevent trigger error
<27>Nov  9 18:34:31 node-2 multipathd: uevent trigger error
<27>Nov  9 18:34:31 node-2 multipathd: uevent trigger error
<27>Nov  9 18:34:31 node-2 multipathd: uevent trigger error
<27>Nov  9 18:35:05 node-2 multipathd: uevent trigger error
<27>Nov  9 18:35:05 node-2 multipathd: uevent trigger error
<27>Nov  9 18:35:05 node-2 multipathd: uevent trigger error
<27>Nov  9 18:35:05 node-2 multipathd: uevent trigger error
<27>Nov  9 18:35:05 node-2 multipathd: uevent trigger error
<27>Nov  9 18:35:47 node-2 multipathd: uevent trigger error
<27>Nov  9 18:35:47 node-2 multipathd: uevent trigger error
<27>Nov  9 18:35:47 node-2 multipathd: uevent trigger error
<27>Nov  9 18:35:47 node-2 multipathd: uevent trigger error
<27>Nov  9 18:35:47 node-2 multipathd: uevent trigger error
<27>Nov  9 18:35:47 node-2 multipathd: uevent trigger error
<27>Nov  9 18:35:50 node-2 multipathd: uevent trigger error
<27>Nov  9 18:35:50 node-2 multipathd: uevent trigger error
<27>Nov  9 18:35:50 node-2 multipathd: uevent trigger error
<27>Nov  9 18:35:50 node-2 multipathd: uevent trigger error
<27>Nov  9 18:35:50 node-2 multipathd: uevent trigger error
<27>Nov  9 18:36:27 node-2 multipathd: uevent trigger error
<27>Nov  9 18:36:27 node-2 multipathd: uevent trigger error
<27>Nov  9 18:36:27 node-2 multipathd: uevent trigger error
<27>Nov  9 18:36:27 node-2 multipathd: uevent trigger error
<27>Nov  9 18:36:27 node-2 multipathd: uevent trigger error
<27>Nov  9 18:36:35 node-2 multipathd: uevent trigger error
<27>Nov  9 18:36:35 node-2 multipathd: uevent trigger error
<27>Nov  9 18:36:35 node-2 multipathd: uevent trigger error
<27>Nov  9 18:36:35 node-2 multipathd: uevent trigger error
<27>Nov  9 18:36:35 node-2 multipathd: uevent trigger error
<27>Nov  9 18:36:38 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  9 18:36:38 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  9 18:36:45 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  9 18:36:45 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  9 18:36:50 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  9 18:37:00 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  9 18:37:00 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  9 18:37:08 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:08 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:08 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:08 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:08 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:08 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:08 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:18 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:18 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:18 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:18 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:18 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:41 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:41 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:41 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:41 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:41 node-2 multipathd: uevent trigger error
<129>Nov  9 18:37:43 node-2 haproxy[21580]: 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>Nov  9 18:37:44 node-2 haproxy[21584]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:37:45 node-2 haproxy[21584]: 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>Nov  9 18:37:45 node-2 haproxy[21584]: proxy mysqld has no server available!
<27>Nov  9 18:37:47 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:47 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:47 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:47 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:47 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:47 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:51 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:51 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:51 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:51 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:51 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:51 node-2 multipathd: uevent trigger error
<129>Nov  9 18:37:53 node-2 haproxy[24379]: 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>Nov  9 18:37:54 node-2 haproxy[24383]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:37:54 node-2 haproxy[24383]: 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>Nov  9 18:37:54 node-2 haproxy[24383]: proxy mysqld has no server available!
<129>Nov  9 18:37:54 node-2 haproxy[24383]: 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>Nov  9 18:37:55 node-2 haproxy[24383]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:37:55 node-2 haproxy[24383]: 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>Nov  9 18:37:55 node-2 haproxy[24383]: proxy object-storage has no server available!
<27>Nov  9 18:37:57 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:57 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:57 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:57 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:57 node-2 multipathd: uevent trigger error
<27>Nov  9 18:37:57 node-2 multipathd: uevent trigger error
<129>Nov  9 18:38:00 node-2 haproxy[25937]: 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>Nov  9 18:38:00 node-2 haproxy[25937]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:00 node-2 haproxy[25937]: 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>Nov  9 18:38:00 node-2 haproxy[25937]: proxy neutron has no server available!
<129>Nov  9 18:38:00 node-2 haproxy[25937]: 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>Nov  9 18:38:00 node-2 haproxy[25937]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:01 node-2 haproxy[25941]: 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>Nov  9 18:38:01 node-2 haproxy[25941]: proxy mysqld has no server available!
<129>Nov  9 18:38:01 node-2 haproxy[25941]: 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>Nov  9 18:38:01 node-2 haproxy[25941]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:01 node-2 haproxy[25941]: 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>Nov  9 18:38:01 node-2 haproxy[25941]: proxy object-storage has no server available!
<27>Nov  9 18:38:03 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:03 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:03 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:03 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:03 node-2 multipathd: uevent trigger error
<129>Nov  9 18:38:06 node-2 haproxy[27498]: 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>Nov  9 18:38:06 node-2 haproxy[27498]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:06 node-2 haproxy[27498]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:06 node-2 haproxy[27498]: proxy keystone-1 has no server available!
<129>Nov  9 18:38:06 node-2 haproxy[27498]: 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>Nov  9 18:38:06 node-2 haproxy[27498]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:06 node-2 haproxy[27498]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:06 node-2 haproxy[27498]: proxy keystone-2 has no server available!
<129>Nov  9 18:38:06 node-2 haproxy[27498]: 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>Nov  9 18:38:06 node-2 haproxy[27498]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:07 node-2 haproxy[27502]: 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>Nov  9 18:38:07 node-2 haproxy[27502]: proxy neutron has no server available!
<129>Nov  9 18:38:07 node-2 haproxy[27502]: 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>Nov  9 18:38:07 node-2 haproxy[27502]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:07 node-2 haproxy[27502]: 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>Nov  9 18:38:07 node-2 haproxy[27502]: proxy mysqld has no server available!
<129>Nov  9 18:38:07 node-2 haproxy[27502]: 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>Nov  9 18:38:07 node-2 haproxy[27502]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:07 node-2 haproxy[27502]: 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>Nov  9 18:38:07 node-2 haproxy[27502]: proxy object-storage has no server available!
<27>Nov  9 18:38:09 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:09 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:09 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:09 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:09 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:09 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:09 node-2 multipathd: uevent trigger error
<129>Nov  9 18:38:11 node-2 haproxy[29019]: 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>Nov  9 18:38:11 node-2 haproxy[29019]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:12 node-2 haproxy[29023]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:12 node-2 haproxy[29023]: proxy keystone-1 has no server available!
<129>Nov  9 18:38:12 node-2 haproxy[29023]: 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>Nov  9 18:38:12 node-2 haproxy[29023]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:12 node-2 haproxy[29023]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:12 node-2 haproxy[29023]: proxy keystone-2 has no server available!
<129>Nov  9 18:38:12 node-2 haproxy[29023]: 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>Nov  9 18:38:12 node-2 haproxy[29023]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:12 node-2 haproxy[29023]: 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>Nov  9 18:38:12 node-2 haproxy[29023]: proxy neutron has no server available!
<129>Nov  9 18:38:12 node-2 haproxy[29023]: 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>Nov  9 18:38:12 node-2 haproxy[29023]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:13 node-2 haproxy[29023]: 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>Nov  9 18:38:13 node-2 haproxy[29023]: proxy mysqld has no server available!
<129>Nov  9 18:38:13 node-2 haproxy[29023]: 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>Nov  9 18:38:13 node-2 haproxy[29023]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:13 node-2 haproxy[29023]: 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>Nov  9 18:38:13 node-2 haproxy[29023]: proxy object-storage has no server available!
<129>Nov  9 18:38:13 node-2 haproxy[29023]: 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>Nov  9 18:38:13 node-2 haproxy[29023]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:13 node-2 haproxy[29023]: 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>Nov  9 18:38:13 node-2 haproxy[29023]: proxy aodh has no server available!
<27>Nov  9 18:38:15 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:15 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:15 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:15 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:15 node-2 multipathd: uevent trigger error
<129>Nov  9 18:38:17 node-2 haproxy[30647]: 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>Nov  9 18:38:18 node-2 haproxy[30651]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:18 node-2 haproxy[30651]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:18 node-2 haproxy[30651]: proxy keystone-1 has no server available!
<129>Nov  9 18:38:18 node-2 haproxy[30651]: 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>Nov  9 18:38:18 node-2 haproxy[30651]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:18 node-2 haproxy[30651]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:18 node-2 haproxy[30651]: proxy keystone-2 has no server available!
<129>Nov  9 18:38:18 node-2 haproxy[30651]: 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>Nov  9 18:38:18 node-2 haproxy[30651]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:18 node-2 haproxy[30651]: 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>Nov  9 18:38:18 node-2 haproxy[30651]: proxy neutron has no server available!
<129>Nov  9 18:38:18 node-2 haproxy[30651]: 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>Nov  9 18:38:18 node-2 haproxy[30651]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:18 node-2 haproxy[30651]: 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>Nov  9 18:38:18 node-2 haproxy[30651]: proxy mysqld has no server available!
<129>Nov  9 18:38:19 node-2 haproxy[30651]: 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>Nov  9 18:38:19 node-2 haproxy[30651]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:19 node-2 haproxy[30651]: 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>Nov  9 18:38:19 node-2 haproxy[30651]: proxy object-storage has no server available!
<129>Nov  9 18:38:19 node-2 haproxy[30651]: 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>Nov  9 18:38:19 node-2 haproxy[30651]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:19 node-2 haproxy[30651]: 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>Nov  9 18:38:19 node-2 haproxy[30651]: proxy aodh has no server available!
<129>Nov  9 18:38:19 node-2 haproxy[30651]: 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>Nov  9 18:38:19 node-2 haproxy[30651]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:19 node-2 haproxy[30651]: 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>Nov  9 18:38:19 node-2 haproxy[30651]: proxy ceilometer has no server available!
<27>Nov  9 18:38:21 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:21 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:21 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:21 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:21 node-2 multipathd: uevent trigger error
<129>Nov  9 18:38:23 node-2 haproxy[32193]: 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>Nov  9 18:38:23 node-2 haproxy[32193]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:23 node-2 haproxy[32193]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:23 node-2 haproxy[32193]: proxy keystone-1 has no server available!
<129>Nov  9 18:38:23 node-2 haproxy[32193]: 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>Nov  9 18:38:24 node-2 haproxy[32197]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:24 node-2 haproxy[32197]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:24 node-2 haproxy[32197]: proxy keystone-2 has no server available!
<129>Nov  9 18:38:24 node-2 haproxy[32197]: 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>Nov  9 18:38:24 node-2 haproxy[32197]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:24 node-2 haproxy[32197]: 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>Nov  9 18:38:24 node-2 haproxy[32197]: proxy neutron has no server available!
<129>Nov  9 18:38:24 node-2 haproxy[32197]: 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>Nov  9 18:38:24 node-2 haproxy[32197]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:24 node-2 haproxy[32197]: 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>Nov  9 18:38:24 node-2 haproxy[32197]: proxy mysqld has no server available!
<129>Nov  9 18:38:24 node-2 haproxy[32197]: 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>Nov  9 18:38:24 node-2 haproxy[32197]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:25 node-2 haproxy[32197]: 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>Nov  9 18:38:25 node-2 haproxy[32197]: proxy object-storage has no server available!
<129>Nov  9 18:38:25 node-2 haproxy[32197]: 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>Nov  9 18:38:25 node-2 haproxy[32197]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:25 node-2 haproxy[32197]: 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>Nov  9 18:38:25 node-2 haproxy[32197]: proxy aodh has no server available!
<129>Nov  9 18:38:25 node-2 haproxy[32197]: 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>Nov  9 18:38:25 node-2 haproxy[32197]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:25 node-2 haproxy[32197]: 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>Nov  9 18:38:25 node-2 haproxy[32197]: proxy ceilometer has no server available!
<27>Nov  9 18:38:26 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:26 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:26 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:27 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:27 node-2 multipathd: uevent trigger error
<129>Nov  9 18:38:29 node-2 haproxy[33645]: 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>Nov  9 18:38:29 node-2 haproxy[33645]: 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>Nov  9 18:38:29 node-2 haproxy[33645]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:29 node-2 haproxy[33645]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:29 node-2 haproxy[33645]: proxy keystone-1 has no server available!
<129>Nov  9 18:38:29 node-2 haproxy[33645]: 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>Nov  9 18:38:29 node-2 haproxy[33645]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:29 node-2 haproxy[33645]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:29 node-2 haproxy[33645]: proxy keystone-2 has no server available!
<129>Nov  9 18:38:29 node-2 haproxy[33645]: 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>Nov  9 18:38:29 node-2 haproxy[33645]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:30 node-2 haproxy[33652]: 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>Nov  9 18:38:30 node-2 haproxy[33652]: proxy neutron has no server available!
<129>Nov  9 18:38:30 node-2 haproxy[33652]: 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>Nov  9 18:38:30 node-2 haproxy[33652]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:30 node-2 haproxy[33652]: 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>Nov  9 18:38:30 node-2 haproxy[33652]: proxy mysqld has no server available!
<129>Nov  9 18:38:30 node-2 haproxy[33652]: 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>Nov  9 18:38:30 node-2 haproxy[33652]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:30 node-2 haproxy[33652]: 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>Nov  9 18:38:30 node-2 haproxy[33652]: proxy object-storage has no server available!
<129>Nov  9 18:38:30 node-2 haproxy[33652]: 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>Nov  9 18:38:30 node-2 haproxy[33652]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:30 node-2 haproxy[33652]: 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>Nov  9 18:38:30 node-2 haproxy[33652]: proxy aodh has no server available!
<129>Nov  9 18:38:30 node-2 haproxy[33652]: 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>Nov  9 18:38:30 node-2 haproxy[33652]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:31 node-2 haproxy[33652]: 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>Nov  9 18:38:31 node-2 haproxy[33652]: proxy ceilometer has no server available!
<27>Nov  9 18:38:32 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:32 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:32 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:32 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:32 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:32 node-2 multipathd: uevent trigger error
<129>Nov  9 18:38:34 node-2 haproxy[35211]: 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>Nov  9 18:38:35 node-2 haproxy[35215]: 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>Nov  9 18:38:35 node-2 haproxy[35215]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:35 node-2 haproxy[35215]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:35 node-2 haproxy[35215]: proxy keystone-1 has no server available!
<129>Nov  9 18:38:35 node-2 haproxy[35215]: 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>Nov  9 18:38:35 node-2 haproxy[35215]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:35 node-2 haproxy[35215]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:35 node-2 haproxy[35215]: proxy keystone-2 has no server available!
<129>Nov  9 18:38:35 node-2 haproxy[35215]: 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>Nov  9 18:38:35 node-2 haproxy[35215]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:35 node-2 haproxy[35215]: 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>Nov  9 18:38:35 node-2 haproxy[35215]: proxy glance-api has no server available!
<129>Nov  9 18:38:35 node-2 haproxy[35215]: 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>Nov  9 18:38:35 node-2 haproxy[35215]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:35 node-2 haproxy[35215]: 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>Nov  9 18:38:35 node-2 haproxy[35215]: proxy glance-glare has no server available!
<129>Nov  9 18:38:35 node-2 haproxy[35215]: 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>Nov  9 18:38:35 node-2 haproxy[35215]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:36 node-2 haproxy[35215]: 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>Nov  9 18:38:36 node-2 haproxy[35215]: proxy neutron has no server available!
<129>Nov  9 18:38:36 node-2 haproxy[35215]: 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>Nov  9 18:38:36 node-2 haproxy[35215]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:36 node-2 haproxy[35215]: 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>Nov  9 18:38:36 node-2 haproxy[35215]: proxy glance-registry has no server available!
<129>Nov  9 18:38:36 node-2 haproxy[35215]: 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>Nov  9 18:38:36 node-2 haproxy[35215]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:36 node-2 haproxy[35215]: 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>Nov  9 18:38:36 node-2 haproxy[35215]: proxy mysqld has no server available!
<129>Nov  9 18:38:36 node-2 haproxy[35215]: 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>Nov  9 18:38:36 node-2 haproxy[35215]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:36 node-2 haproxy[35215]: 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>Nov  9 18:38:36 node-2 haproxy[35215]: proxy object-storage has no server available!
<129>Nov  9 18:38:36 node-2 haproxy[35215]: 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>Nov  9 18:38:36 node-2 haproxy[35215]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:36 node-2 haproxy[35215]: 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>Nov  9 18:38:36 node-2 haproxy[35215]: proxy aodh has no server available!
<129>Nov  9 18:38:36 node-2 haproxy[35215]: 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>Nov  9 18:38:36 node-2 haproxy[35215]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:36 node-2 haproxy[35215]: 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>Nov  9 18:38:36 node-2 haproxy[35215]: proxy ceilometer has no server available!
<27>Nov  9 18:38:38 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:38 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:38 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:38 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:38 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:38 node-2 multipathd: uevent trigger error
<129>Nov  9 18:38:41 node-2 haproxy[37084]: 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>Nov  9 18:38:41 node-2 haproxy[37084]: 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>Nov  9 18:38:41 node-2 haproxy[37084]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:41 node-2 haproxy[37084]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:41 node-2 haproxy[37084]: proxy keystone-1 has no server available!
<129>Nov  9 18:38:41 node-2 haproxy[37084]: 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>Nov  9 18:38:41 node-2 haproxy[37084]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:41 node-2 haproxy[37084]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:41 node-2 haproxy[37084]: proxy keystone-2 has no server available!
<129>Nov  9 18:38:41 node-2 haproxy[37084]: 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>Nov  9 18:38:41 node-2 haproxy[37084]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:41 node-2 haproxy[37084]: 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>Nov  9 18:38:41 node-2 haproxy[37084]: proxy nova-api has no server available!
<129>Nov  9 18:38:41 node-2 haproxy[37084]: 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>Nov  9 18:38:41 node-2 haproxy[37084]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:41 node-2 haproxy[37084]: 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>Nov  9 18:38:41 node-2 haproxy[37084]: proxy nova-metadata-api has no server available!
<129>Nov  9 18:38:41 node-2 haproxy[37084]: 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>Nov  9 18:38:41 node-2 haproxy[37084]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:42 node-2 haproxy[37091]: 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>Nov  9 18:38:42 node-2 haproxy[37091]: proxy glance-api has no server available!
<129>Nov  9 18:38:42 node-2 haproxy[37091]: 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>Nov  9 18:38:42 node-2 haproxy[37091]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:42 node-2 haproxy[37091]: 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>Nov  9 18:38:42 node-2 haproxy[37091]: proxy glance-glare has no server available!
<129>Nov  9 18:38:42 node-2 haproxy[37091]: 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>Nov  9 18:38:42 node-2 haproxy[37091]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:42 node-2 haproxy[37091]: 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>Nov  9 18:38:42 node-2 haproxy[37091]: proxy neutron has no server available!
<129>Nov  9 18:38:42 node-2 haproxy[37091]: 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>Nov  9 18:38:42 node-2 haproxy[37091]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:42 node-2 haproxy[37091]: 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>Nov  9 18:38:42 node-2 haproxy[37091]: proxy glance-registry has no server available!
<129>Nov  9 18:38:42 node-2 haproxy[37091]: 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>Nov  9 18:38:42 node-2 haproxy[37091]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:42 node-2 haproxy[37091]: 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>Nov  9 18:38:42 node-2 haproxy[37091]: proxy mysqld has no server available!
<129>Nov  9 18:38:42 node-2 haproxy[37091]: 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>Nov  9 18:38:42 node-2 haproxy[37091]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:42 node-2 haproxy[37091]: 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>Nov  9 18:38:42 node-2 haproxy[37091]: proxy object-storage has no server available!
<129>Nov  9 18:38:42 node-2 haproxy[37091]: 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>Nov  9 18:38:42 node-2 haproxy[37091]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:42 node-2 haproxy[37091]: 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>Nov  9 18:38:42 node-2 haproxy[37091]: proxy aodh has no server available!
<129>Nov  9 18:38:42 node-2 haproxy[37091]: 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>Nov  9 18:38:42 node-2 haproxy[37091]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:43 node-2 haproxy[37091]: 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>Nov  9 18:38:43 node-2 haproxy[37091]: proxy ceilometer has no server available!
<129>Nov  9 18:38:43 node-2 haproxy[37091]: 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>Nov  9 18:38:43 node-2 haproxy[37091]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:43 node-2 haproxy[37091]: 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>Nov  9 18:38:43 node-2 haproxy[37091]: proxy nova-novncproxy has no server available!
<27>Nov  9 18:38:45 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:45 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:45 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:45 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:45 node-2 multipathd: uevent trigger error
<129>Nov  9 18:38:47 node-2 haproxy[38618]: 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>Nov  9 18:38:47 node-2 haproxy[38618]: 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>Nov  9 18:38:47 node-2 haproxy[38618]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:47 node-2 haproxy[38618]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:47 node-2 haproxy[38618]: proxy keystone-1 has no server available!
<129>Nov  9 18:38:47 node-2 haproxy[38618]: 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>Nov  9 18:38:47 node-2 haproxy[38618]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:47 node-2 haproxy[38618]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:47 node-2 haproxy[38618]: proxy keystone-2 has no server available!
<129>Nov  9 18:38:47 node-2 haproxy[38618]: 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>Nov  9 18:38:47 node-2 haproxy[38618]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:47 node-2 haproxy[38618]: 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>Nov  9 18:38:47 node-2 haproxy[38618]: proxy nova-api has no server available!
<129>Nov  9 18:38:47 node-2 haproxy[38618]: 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>Nov  9 18:38:47 node-2 haproxy[38618]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:48 node-2 haproxy[38628]: 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>Nov  9 18:38:48 node-2 haproxy[38628]: proxy nova-metadata-api has no server available!
<129>Nov  9 18:38:48 node-2 haproxy[38628]: 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>Nov  9 18:38:48 node-2 haproxy[38628]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:48 node-2 haproxy[38628]: 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>Nov  9 18:38:48 node-2 haproxy[38628]: proxy cinder-api has no server available!
<129>Nov  9 18:38:48 node-2 haproxy[38628]: 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>Nov  9 18:38:48 node-2 haproxy[38628]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:48 node-2 haproxy[38628]: 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>Nov  9 18:38:48 node-2 haproxy[38628]: proxy glance-api has no server available!
<129>Nov  9 18:38:48 node-2 haproxy[38628]: 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>Nov  9 18:38:48 node-2 haproxy[38628]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:48 node-2 haproxy[38628]: 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>Nov  9 18:38:48 node-2 haproxy[38628]: proxy glance-glare has no server available!
<129>Nov  9 18:38:48 node-2 haproxy[38628]: 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>Nov  9 18:38:48 node-2 haproxy[38628]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:48 node-2 haproxy[38628]: 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>Nov  9 18:38:48 node-2 haproxy[38628]: proxy neutron has no server available!
<129>Nov  9 18:38:48 node-2 haproxy[38628]: 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>Nov  9 18:38:48 node-2 haproxy[38628]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:48 node-2 haproxy[38628]: 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>Nov  9 18:38:48 node-2 haproxy[38628]: proxy glance-registry has no server available!
<129>Nov  9 18:38:48 node-2 haproxy[38628]: 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>Nov  9 18:38:48 node-2 haproxy[38628]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:48 node-2 haproxy[38628]: 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>Nov  9 18:38:48 node-2 haproxy[38628]: proxy mysqld has no server available!
<129>Nov  9 18:38:48 node-2 haproxy[38628]: 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>Nov  9 18:38:48 node-2 haproxy[38628]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:48 node-2 haproxy[38628]: 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>Nov  9 18:38:48 node-2 haproxy[38628]: proxy object-storage has no server available!
<129>Nov  9 18:38:48 node-2 haproxy[38628]: 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>Nov  9 18:38:49 node-2 haproxy[38628]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:49 node-2 haproxy[38628]: 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>Nov  9 18:38:49 node-2 haproxy[38628]: proxy aodh has no server available!
<129>Nov  9 18:38:49 node-2 haproxy[38628]: 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>Nov  9 18:38:49 node-2 haproxy[38628]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:49 node-2 haproxy[38628]: 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>Nov  9 18:38:49 node-2 haproxy[38628]: proxy ceilometer has no server available!
<129>Nov  9 18:38:49 node-2 haproxy[38628]: 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>Nov  9 18:38:49 node-2 haproxy[38628]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:49 node-2 haproxy[38628]: 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>Nov  9 18:38:49 node-2 haproxy[38628]: proxy nova-novncproxy has no server available!
<27>Nov  9 18:38:50 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:50 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:50 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:50 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:50 node-2 multipathd: uevent trigger error
<129>Nov  9 18:38:53 node-2 haproxy[40184]: 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>Nov  9 18:38:53 node-2 haproxy[40184]: 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>Nov  9 18:38:53 node-2 haproxy[40184]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:53 node-2 haproxy[40184]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:53 node-2 haproxy[40184]: proxy keystone-1 has no server available!
<129>Nov  9 18:38:53 node-2 haproxy[40184]: 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>Nov  9 18:38:53 node-2 haproxy[40184]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:54 node-2 haproxy[40193]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  9 18:38:54 node-2 haproxy[40193]: proxy keystone-2 has no server available!
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: proxy nova-api has no server available!
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: proxy nova-metadata-api has no server available!
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: proxy cinder-api has no server available!
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: proxy glance-api has no server available!
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: proxy glance-glare has no server available!
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: proxy neutron has no server available!
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: proxy glance-registry has no server available!
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: proxy mysqld has no server available!
<129>Nov  9 18:38:54 node-2 haproxy[40193]: 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>Nov  9 18:38:54 node-2 haproxy[40193]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:55 node-2 haproxy[40193]: 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>Nov  9 18:38:55 node-2 haproxy[40193]: proxy object-storage has no server available!
<129>Nov  9 18:38:55 node-2 haproxy[40193]: 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>Nov  9 18:38:55 node-2 haproxy[40193]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:55 node-2 haproxy[40193]: 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>Nov  9 18:38:55 node-2 haproxy[40193]: proxy aodh has no server available!
<129>Nov  9 18:38:55 node-2 haproxy[40193]: 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>Nov  9 18:38:55 node-2 haproxy[40193]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:55 node-2 haproxy[40193]: 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>Nov  9 18:38:55 node-2 haproxy[40193]: proxy ceilometer has no server available!
<129>Nov  9 18:38:55 node-2 haproxy[40193]: 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>Nov  9 18:38:55 node-2 haproxy[40193]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:55 node-2 haproxy[40193]: 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>Nov  9 18:38:55 node-2 haproxy[40193]: proxy heat-api has no server available!
<129>Nov  9 18:38:55 node-2 haproxy[40193]: 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>Nov  9 18:38:55 node-2 haproxy[40193]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:55 node-2 haproxy[40193]: 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>Nov  9 18:38:55 node-2 haproxy[40193]: proxy heat-api-cfn has no server available!
<129>Nov  9 18:38:55 node-2 haproxy[40193]: 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>Nov  9 18:38:55 node-2 haproxy[40193]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:55 node-2 haproxy[40193]: 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>Nov  9 18:38:55 node-2 haproxy[40193]: proxy heat-api-cloudwatch has no server available!
<129>Nov  9 18:38:55 node-2 haproxy[40193]: 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>Nov  9 18:38:55 node-2 haproxy[40193]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 18:38:55 node-2 haproxy[40193]: 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>Nov  9 18:38:55 node-2 haproxy[40193]: proxy nova-novncproxy has no server available!
<27>Nov  9 18:38:57 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:57 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:57 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:57 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:57 node-2 multipathd: uevent trigger error
<27>Nov  9 18:38:57 node-2 multipathd: uevent trigger error
<27>Nov  9 18:39:01 node-2 multipathd: uevent trigger error
<27>Nov  9 18:39:01 node-2 multipathd: uevent trigger error
<27>Nov  9 18:39:01 node-2 multipathd: uevent trigger error
<27>Nov  9 18:39:01 node-2 multipathd: uevent trigger error
<27>Nov  9 18:39:01 node-2 multipathd: uevent trigger error
<27>Nov  9 18:39:01 node-2 multipathd: uevent trigger error
<27>Nov  9 18:39:06 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Nov  9 18:39:27 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>Nov  9 18:39:29 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Nov  9 18:39:59 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 18:40:03 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  9 18:40:23 node-2 multipathd: uevent trigger error
<27>Nov  9 18:40:24 node-2 multipathd: uevent trigger error
<27>Nov  9 18:40:24 node-2 multipathd: uevent trigger error
<27>Nov  9 18:40:24 node-2 multipathd: uevent trigger error
<27>Nov  9 18:40:24 node-2 multipathd: uevent trigger error
<27>Nov  9 18:42:41 node-2 multipathd: uevent trigger error
<27>Nov  9 18:42:41 node-2 multipathd: uevent trigger error
<27>Nov  9 18:42:41 node-2 multipathd: uevent trigger error
<27>Nov  9 18:42:41 node-2 multipathd: uevent trigger error
<27>Nov  9 18:42:41 node-2 multipathd: uevent trigger error
<27>Nov  9 18:42:46 node-2 multipathd: uevent trigger error
<27>Nov  9 18:42:46 node-2 multipathd: uevent trigger error
<27>Nov  9 18:42:46 node-2 multipathd: uevent trigger error
<27>Nov  9 18:42:46 node-2 multipathd: uevent trigger error
<27>Nov  9 18:42:46 node-2 multipathd: uevent trigger error
<27>Nov  9 18:42:46 node-2 multipathd: uevent trigger error
<27>Nov  9 18:42:51 node-2 multipathd: uevent trigger error
<27>Nov  9 18:42:51 node-2 multipathd: uevent trigger error
<27>Nov  9 18:42:51 node-2 multipathd: uevent trigger error
<27>Nov  9 18:42:51 node-2 multipathd: uevent trigger error
<27>Nov  9 18:42:51 node-2 multipathd: uevent trigger error
<27>Nov  9 18:43:01 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 18:43:04 node-2 multipathd: uevent trigger error
<27>Nov  9 18:43:04 node-2 multipathd: uevent trigger error
<27>Nov  9 18:43:04 node-2 multipathd: uevent trigger error
<27>Nov  9 18:43:04 node-2 multipathd: uevent trigger error
<27>Nov  9 18:43:04 node-2 multipathd: uevent trigger error
<43>Nov  9 18:43:04 node-2 apache2_error [Wed Nov 09 18:42:56.339158 2016] [mpm_event:notice] [pid 36063:tid 139974898493312] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  9 18:43:04 node-2 apache2_error [Wed Nov 09 18:42:56.339301 2016] [core:notice] [pid 36063:tid 139974898493312] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov  9 18:43:04 node-2 apache2_error [Wed Nov 09 18:42:58.656475 2016] [mpm_event:notice] [pid 36063:tid 139974898493312] AH00491: caught SIGTERM, shutting down
<43>Nov  9 18:43:04 node-2 apache2_error [Wed Nov 09 18:42:59.755122 2016] [mpm_worker:notice] [pid 37133:tid 140137625851776] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  9 18:43:04 node-2 apache2_error [Wed Nov 09 18:42:59.755165 2016] [core:notice] [pid 37133:tid 140137625851776] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  9 18:43:08 node-2 multipathd: uevent trigger error
<27>Nov  9 18:43:08 node-2 multipathd: uevent trigger error
<27>Nov  9 18:43:08 node-2 multipathd: uevent trigger error
<27>Nov  9 18:43:08 node-2 multipathd: uevent trigger error
<27>Nov  9 18:43:08 node-2 multipathd: uevent trigger error
<43>Nov  9 18:43:44 node-2 apache2_error [Wed Nov 09 18:43:39.091480 2016] [mpm_worker:notice] [pid 37133:tid 140137625851776] AH00295: caught SIGTERM, shutting down
<43>Nov  9 18:43:44 node-2 apache2_error [Wed Nov 09 18:43:39.863993 2016] [mpm_worker:notice] [pid 47407:tid 140715278968704] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  9 18:43:44 node-2 apache2_error [Wed Nov 09 18:43:39.864027 2016] [core:notice] [pid 47407:tid 140715278968704] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov  9 18:44:24 node-2 apache2_error [Wed Nov 09 18:44:16.638221 2016] [mpm_worker:notice] [pid 47407:tid 140715278968704] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  9 18:44:24 node-2 apache2_error [Wed Nov 09 18:44:16.834286 2016] [mpm_worker:warn] [pid 47407:tid 140715278968704] AH00317: MaxRequestWorkers of 12881 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 12875
<43>Nov  9 18:44:24 node-2 apache2_error [Wed Nov 09 18:44:16.839244 2016] [mpm_worker:notice] [pid 47407:tid 140715278968704] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  9 18:44:24 node-2 apache2_error [Wed Nov 09 18:44:16.839272 2016] [core:notice] [pid 47407:tid 140715278968704] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  9 18:45:16 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:16 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:16 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:16 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:16 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:16 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:21 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:21 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:21 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:21 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:21 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:21 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:39 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:39 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:39 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:39 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:39 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:39 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:59 node-2 multipathd: uevent trigger error
<27>Nov  9 18:45:59 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:00 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:00 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:00 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:02 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 18:46:05 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:05 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:05 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:05 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:05 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:05 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:25 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:25 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:25 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:25 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:25 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:46 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:46 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:46 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:46 node-2 multipathd: uevent trigger error
<27>Nov  9 18:46:46 node-2 multipathd: uevent trigger error
<27>Nov  9 18:47:32 node-2 multipathd: uevent trigger error
<27>Nov  9 18:47:32 node-2 multipathd: uevent trigger error
<27>Nov  9 18:47:32 node-2 multipathd: uevent trigger error
<27>Nov  9 18:47:32 node-2 multipathd: uevent trigger error
<27>Nov  9 18:47:32 node-2 multipathd: uevent trigger error
<27>Nov  9 18:48:35 node-2 multipathd: uevent trigger error
<27>Nov  9 18:48:35 node-2 multipathd: uevent trigger error
<27>Nov  9 18:48:35 node-2 multipathd: uevent trigger error
<27>Nov  9 18:48:35 node-2 multipathd: uevent trigger error
<27>Nov  9 18:48:35 node-2 multipathd: uevent trigger error
<27>Nov  9 18:48:35 node-2 multipathd: uevent trigger error
<27>Nov  9 18:49:04 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 18:49:09 node-2 multipathd: uevent trigger error
<27>Nov  9 18:49:09 node-2 multipathd: uevent trigger error
<27>Nov  9 18:49:09 node-2 multipathd: uevent trigger error
<27>Nov  9 18:49:09 node-2 multipathd: uevent trigger error
<27>Nov  9 18:49:09 node-2 multipathd: uevent trigger error
<27>Nov  9 18:49:09 node-2 multipathd: uevent trigger error
<27>Nov  9 18:49:35 node-2 multipathd: uevent trigger error
<27>Nov  9 18:49:35 node-2 multipathd: uevent trigger error
<27>Nov  9 18:49:35 node-2 multipathd: uevent trigger error
<27>Nov  9 18:49:35 node-2 multipathd: uevent trigger error
<27>Nov  9 18:49:35 node-2 multipathd: uevent trigger error
<27>Nov  9 18:49:41 node-2 multipathd: uevent trigger error
<27>Nov  9 18:49:41 node-2 multipathd: uevent trigger error
<27>Nov  9 18:49:41 node-2 multipathd: uevent trigger error
<27>Nov  9 18:49:41 node-2 multipathd: uevent trigger error
<27>Nov  9 18:49:41 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:00 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:00 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:00 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:00 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:00 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:06 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 18:52:19 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:19 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:19 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:19 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:19 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:19 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:25 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:25 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:25 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:25 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:25 node-2 multipathd: uevent trigger error
<27>Nov  9 18:52:25 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:05 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:05 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:05 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:05 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:05 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:11 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:11 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:11 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:11 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:11 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:40 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:40 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:40 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:40 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:40 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:52 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:52 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:52 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:52 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:52 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:52 node-2 multipathd: uevent trigger error
<27>Nov  9 18:53:59 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Nov  9 18:53:59 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Nov  9 18:53:59 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Nov  9 18:54:00 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Nov  9 18:54:00 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Nov  9 18:54:00 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:00 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:01 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:01 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:01 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:16 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:16 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:16 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:16 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:16 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:34 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:34 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:34 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:34 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:34 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:48 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:48 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:48 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:48 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:48 node-2 multipathd: uevent trigger error
<27>Nov  9 18:54:48 node-2 multipathd: uevent trigger error
<27>Nov  9 18:55:08 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 18:56:55 node-2 multipathd: uevent trigger error
<27>Nov  9 18:56:55 node-2 multipathd: uevent trigger error
<27>Nov  9 18:56:55 node-2 multipathd: uevent trigger error
<27>Nov  9 18:56:55 node-2 multipathd: uevent trigger error
<27>Nov  9 18:56:55 node-2 multipathd: uevent trigger error
<27>Nov  9 18:56:55 node-2 multipathd: uevent trigger error
<27>Nov  9 18:57:24 node-2 multipathd: uevent trigger error
<27>Nov  9 18:57:24 node-2 multipathd: uevent trigger error
<27>Nov  9 18:57:24 node-2 multipathd: uevent trigger error
<27>Nov  9 18:57:24 node-2 multipathd: uevent trigger error
<27>Nov  9 18:57:30 node-2 multipathd: uevent trigger error
<27>Nov  9 18:57:30 node-2 multipathd: uevent trigger error
<27>Nov  9 18:57:30 node-2 multipathd: uevent trigger error
<27>Nov  9 18:57:30 node-2 multipathd: uevent trigger error
<27>Nov  9 18:57:30 node-2 multipathd: uevent trigger error
<27>Nov  9 18:57:53 node-2 multipathd: uevent trigger error
<27>Nov  9 18:57:54 node-2 multipathd: uevent trigger error
<27>Nov  9 18:57:54 node-2 multipathd: uevent trigger error
<27>Nov  9 18:57:54 node-2 multipathd: uevent trigger error
<27>Nov  9 18:57:54 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:06 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:06 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:06 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:06 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:06 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:10 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 18:58:11 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:11 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:11 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:11 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:11 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:15 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:15 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:15 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:15 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:15 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:22 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:22 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:22 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:22 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:22 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:50 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:50 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:50 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:50 node-2 multipathd: uevent trigger error
<27>Nov  9 18:58:50 node-2 multipathd: uevent trigger error
<27>Nov  9 18:59:36 node-2 multipathd: uevent trigger error
<27>Nov  9 18:59:36 node-2 multipathd: uevent trigger error
<27>Nov  9 18:59:36 node-2 multipathd: uevent trigger error
<27>Nov  9 18:59:36 node-2 multipathd: uevent trigger error
<27>Nov  9 18:59:36 node-2 multipathd: uevent trigger error
<27>Nov  9 18:59:51 node-2 multipathd: uevent trigger error
<27>Nov  9 18:59:51 node-2 multipathd: uevent trigger error
<27>Nov  9 18:59:51 node-2 multipathd: uevent trigger error
<27>Nov  9 18:59:51 node-2 multipathd: uevent trigger error
<27>Nov  9 18:59:51 node-2 multipathd: uevent trigger error
<11>Nov  9 19:00:03 node-2 liberasurecode[4760]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:03 node-2 liberasurecode[4760]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:03 node-2 liberasurecode[4760]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:03 node-2 liberasurecode[4760]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:03 node-2 liberasurecode[4789]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:03 node-2 liberasurecode[4789]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:03 node-2 liberasurecode[4789]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:03 node-2 liberasurecode[4789]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:04 node-2 liberasurecode[5165]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:04 node-2 liberasurecode[5165]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:04 node-2 liberasurecode[5165]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:04 node-2 liberasurecode[5165]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:06 node-2 liberasurecode[5715]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:06 node-2 liberasurecode[5715]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:06 node-2 liberasurecode[5715]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:06 node-2 liberasurecode[5715]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:06 node-2 liberasurecode[5751]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:06 node-2 liberasurecode[5751]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:06 node-2 liberasurecode[5751]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:06 node-2 liberasurecode[5751]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:06 node-2 liberasurecode[5796]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:06 node-2 liberasurecode[5796]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:06 node-2 liberasurecode[5796]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:06 node-2 liberasurecode[5796]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:07 node-2 liberasurecode[5858]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:07 node-2 liberasurecode[5858]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:07 node-2 liberasurecode[5858]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:07 node-2 liberasurecode[5858]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:07 node-2 liberasurecode[5880]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:07 node-2 liberasurecode[5880]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:07 node-2 liberasurecode[5880]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:07 node-2 liberasurecode[5880]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:07 node-2 liberasurecode[5892]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:07 node-2 liberasurecode[5892]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:07 node-2 liberasurecode[5892]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:07 node-2 liberasurecode[5892]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:07 node-2 liberasurecode[5913]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:07 node-2 liberasurecode[5913]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:07 node-2 liberasurecode[5913]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:07 node-2 liberasurecode[5913]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:29 node-2 liberasurecode[6887]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:29 node-2 liberasurecode[6887]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:29 node-2 liberasurecode[6887]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:00:29 node-2 liberasurecode[6887]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  9 19:00:41 node-2 multipathd: uevent trigger error
<27>Nov  9 19:00:41 node-2 multipathd: uevent trigger error
<27>Nov  9 19:00:41 node-2 multipathd: uevent trigger error
<27>Nov  9 19:00:41 node-2 multipathd: uevent trigger error
<27>Nov  9 19:00:41 node-2 multipathd: uevent trigger error
<27>Nov  9 19:01:12 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Nov  9 19:01:16 node-2 apache2_error [Wed Nov 09 19:01:11.781440 2016] [mpm_worker:notice] [pid 47407:tid 140715278968704] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  9 19:01:16 node-2 apache2_error [Wed Nov 09 19:01:11.976535 2016] [mpm_worker:warn] [pid 47407:tid 140715278968704] AH00317: MaxRequestWorkers of 12881 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 12875
<43>Nov  9 19:01:16 node-2 apache2_error [Wed Nov 09 19:01:11.981450 2016] [mpm_worker:notice] [pid 47407:tid 140715278968704] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  9 19:01:16 node-2 apache2_error [Wed Nov 09 19:01:11.981485 2016] [core:notice] [pid 47407:tid 140715278968704] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  9 19:01:54 node-2 multipathd: uevent trigger error
<27>Nov  9 19:01:54 node-2 multipathd: uevent trigger error
<27>Nov  9 19:01:54 node-2 multipathd: uevent trigger error
<27>Nov  9 19:01:54 node-2 multipathd: uevent trigger error
<27>Nov  9 19:01:54 node-2 multipathd: uevent trigger error
<43>Nov  9 19:01:56 node-2 apache2_error [Wed Nov 09 19:01:49.488744 2016] [mpm_worker:notice] [pid 47407:tid 140715278968704] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  9 19:01:56 node-2 apache2_error [Wed Nov 09 19:01:49.873629 2016] [mpm_worker:warn] [pid 47407:tid 140715278968704] AH00317: MaxRequestWorkers of 12881 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 12875
<43>Nov  9 19:01:56 node-2 apache2_error [Wed Nov 09 19:01:49.882633 2016] [mpm_worker:notice] [pid 47407:tid 140715278968704] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  9 19:01:56 node-2 apache2_error [Wed Nov 09 19:01:49.882662 2016] [core:notice] [pid 47407:tid 140715278968704] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  9 19:02:02 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:02 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:02 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:02 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:02 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:42 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:42 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:42 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:42 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:42 node-2 multipathd: uevent trigger error
<43>Nov  9 19:02:46 node-2 apache2_error [Wed Nov 09 19:02:37.423342 2016] [mpm_worker:notice] [pid 47407:tid 140715278968704] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  9 19:02:46 node-2 apache2_error [Wed Nov 09 19:02:37.621477 2016] [mpm_worker:warn] [pid 47407:tid 140715278968704] AH00317: MaxRequestWorkers of 12881 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 12875
<43>Nov  9 19:02:46 node-2 apache2_error [Wed Nov 09 19:02:37.629700 2016] [mpm_worker:notice] [pid 47407:tid 140715278968704] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  9 19:02:46 node-2 apache2_error [Wed Nov 09 19:02:37.629718 2016] [core:notice] [pid 47407:tid 140715278968704] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  9 19:02:49 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:49 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:49 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:49 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:49 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:55 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:55 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:55 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:55 node-2 multipathd: uevent trigger error
<27>Nov  9 19:02:55 node-2 multipathd: uevent trigger error
<27>Nov  9 19:03:05 node-2 multipathd: uevent trigger error
<27>Nov  9 19:03:05 node-2 multipathd: uevent trigger error
<27>Nov  9 19:03:05 node-2 multipathd: uevent trigger error
<27>Nov  9 19:03:05 node-2 multipathd: uevent trigger error
<27>Nov  9 19:03:05 node-2 multipathd: uevent trigger error
<27>Nov  9 19:03:21 node-2 multipathd: uevent trigger error
<27>Nov  9 19:03:21 node-2 multipathd: uevent trigger error
<27>Nov  9 19:03:21 node-2 multipathd: uevent trigger error
<27>Nov  9 19:03:21 node-2 multipathd: uevent trigger error
<27>Nov  9 19:03:21 node-2 multipathd: uevent trigger error
<27>Nov  9 19:03:46 node-2 multipathd: uevent trigger error
<27>Nov  9 19:03:51 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Nov  9 19:04:01 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:01 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:01 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:01 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:01 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:06 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:06 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:06 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:06 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:06 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:12 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:12 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:12 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:12 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:12 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:18 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:18 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:18 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:18 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:18 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:30 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:30 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:30 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:30 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:30 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:36 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:36 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:36 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:36 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:36 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:42 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:42 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:42 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:42 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:42 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:55 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:55 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:56 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:56 node-2 multipathd: uevent trigger error
<27>Nov  9 19:04:56 node-2 multipathd: uevent trigger error
<11>Nov  9 19:05:02 node-2 liberasurecode[24283]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:05:02 node-2 liberasurecode[24283]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:05:02 node-2 liberasurecode[24283]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 19:05:02 node-2 liberasurecode[24283]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  9 19:05:02 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:02 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:02 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:02 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:02 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:16 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:16 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:16 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:16 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:16 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:21 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:21 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:21 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:21 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:22 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:27 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:27 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:27 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:27 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:27 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:32 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:32 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:32 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:32 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:32 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:32 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:38 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:38 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:38 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:38 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:38 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:44 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:44 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:44 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:44 node-2 multipathd: uevent trigger error
<27>Nov  9 19:05:44 node-2 multipathd: uevent trigger error
