Oct 29 08:44:39 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8826" x-info="http://www.rsyslog.com"] start
Oct 29 08:44:39 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 29 08:44:39 node-2 rsyslogd: rsyslogd's groupid changed to 104
Oct 29 08:44:39 node-2 rsyslogd: rsyslogd's userid changed to 101
Oct 29 08:44:39 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 29 08:44:39 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 29 08:44:39 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 29 08:44:39 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)
Oct 29 08:44:39 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=ff37ac73-7ac9-4aca-9a48-3984eed9d826 nomdmonddf nomdmonisw
Oct 29 08:44:39 node-2 kernel: [    0.000000] KERNEL supported cpus:
Oct 29 08:44:39 node-2 kernel: [    0.000000]   Intel GenuineIntel
Oct 29 08:44:39 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Oct 29 08:44:39 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Oct 29 08:44:39 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 29 08:44:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000093fff] usable
Oct 29 08:44:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000094000-0x000000000009ffff] reserved
Oct 29 08:44:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 29 08:44:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000005ae23fff] usable
Oct 29 08:44:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000005ae24000-0x000000005bae3fff] reserved
Oct 29 08:44:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000005bae4000-0x00000000790fefff] usable
Oct 29 08:44:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000790ff000-0x00000000791fefff] reserved
Oct 29 08:44:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000791ff000-0x000000007b5fefff] ACPI NVS
Oct 29 08:44:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007b5ff000-0x000000007b7fefff] ACPI data
Oct 29 08:44:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007b7ff000-0x000000007b7fffff] usable
Oct 29 08:44:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007b800000-0x000000008fffffff] reserved
Oct 29 08:44:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff800000-0x00000000ffffffff] reserved
Oct 29 08:44:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000207fffffff] usable
Oct 29 08:44:39 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 29 08:44:39 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 29 08:44:39 node-2 kernel: [    0.000000] DMI: HP ProLiant BL460c Gen9, BIOS I36 05/06/2015
Oct 29 08:44:39 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 29 08:44:39 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 29 08:44:39 node-2 kernel: [    0.000000] No AGP bridge found
Oct 29 08:44:39 node-2 kernel: [    0.000000] e820: last_pfn = 0x2080000 max_arch_pfn = 0x400000000
Oct 29 08:44:39 node-2 kernel: [    0.000000] MTRR default type: write-back
Oct 29 08:44:39 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 29 08:44:39 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Oct 29 08:44:39 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 29 08:44:39 node-2 kernel: [    0.000000]   C0000-DFFFF write-protect
Oct 29 08:44:39 node-2 kernel: [    0.000000]   E0000-EFFFF uncachable
Oct 29 08:44:39 node-2 kernel: [    0.000000]   F0000-FFFFF write-protect
Oct 29 08:44:39 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 29 08:44:39 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 29 08:44:39 node-2 kernel: [    0.000000]   1 base 002080000000 mask 3FFF80000000 uncachable
Oct 29 08:44:39 node-2 kernel: [    0.000000]   2 base 008000000000 mask 3F8000000000 uncachable
Oct 29 08:44:39 node-2 kernel: [    0.000000]   3 base 010000000000 mask 3F0000000000 uncachable
Oct 29 08:44:39 node-2 kernel: [    0.000000]   4 base 038000000000 mask 3FC000000000 uncachable
Oct 29 08:44:39 node-2 kernel: [    0.000000]   5 base 00007C000000 mask 3FFFFC000000 uncachable
Oct 29 08:44:39 node-2 kernel: [    0.000000]   6 base 00007FC00000 mask 3FFFFFC00000 uncachable
Oct 29 08:44:39 node-2 kernel: [    0.000000]   7 disabled
Oct 29 08:44:39 node-2 kernel: [    0.000000]   8 disabled
Oct 29 08:44:39 node-2 kernel: [    0.000000]   9 disabled
Oct 29 08:44:39 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 29 08:44:39 node-2 kernel: [    0.000000] e820: last_pfn = 0x7b800 max_arch_pfn = 0x400000000
Oct 29 08:44:39 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 29 08:44:39 node-2 kernel: [    0.000000] Base memory trampoline at [ffff88000008e000] 8e000 size 24576
Oct 29 08:44:39 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Oct 29 08:44:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 29 08:44:39 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 29 08:44:39 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 29 08:44:39 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 29 08:44:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x207fe00000-0x207fffffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]  [mem 0x207fe00000-0x207fffffff] page 1G
Oct 29 08:44:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x207c000000-0x207fdfffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]  [mem 0x207c000000-0x207fdfffff] page 1G
Oct 29 08:44:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x2000000000-0x207bffffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]  [mem 0x2000000000-0x207bffffff] page 1G
Oct 29 08:44:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x1000000000-0x1fffffffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]  [mem 0x1000000000-0x1fffffffff] page 1G
Oct 29 08:44:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x5ae23fff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 29 08:44:39 node-2 kernel: [    0.000000]  [mem 0x00200000-0x5adfffff] page 2M
Oct 29 08:44:39 node-2 kernel: [    0.000000]  [mem 0x5ae00000-0x5ae23fff] page 4k
Oct 29 08:44:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x5bae4000-0x790fefff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]  [mem 0x5bae4000-0x5bbfffff] page 4k
Oct 29 08:44:39 node-2 kernel: [    0.000000]  [mem 0x5bc00000-0x78ffffff] page 2M
Oct 29 08:44:39 node-2 kernel: [    0.000000]  [mem 0x79000000-0x790fefff] page 4k
Oct 29 08:44:39 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 29 08:44:39 node-2 kernel: [    0.000000] BRK [0x01fe6000, 0x01fe6fff] PGTABLE
Oct 29 08:44:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7b7ff000-0x7b7fffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]  [mem 0x7b7ff000-0x7b7fffff] page 4k
Oct 29 08:44:39 node-2 kernel: [    0.000000] BRK [0x01fe7000, 0x01fe7fff] PGTABLE
Oct 29 08:44:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0xfffffffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]  [mem 0x100000000-0xfffffffff] page 1G
Oct 29 08:44:39 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f4f00 000024 (v02 HP    )
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: XSDT 000000007b7e8188 0000EC (v01 HP     ProLiant 00000001      01000013)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: FACP 000000007b7f6000 00010C (v05 HP     ProLiant 00000001 HP   00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: DSDT 000000007b7dd000 00AE48 (v02 HP     DSDT     00000002 HPAG 00020000)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: FACS 000000007b52b000 000040
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: UEFI 000000007b539000 000042 (v01 HP     ProLiant 00000002      01000013)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: MCEJ 000000007b7fc000 000130 (v01 HP     ProLiant 00000001 INTL 0100000D)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: SSDT 000000007b7fb000 000064 (v02 HP     SpsNvs   00000002 INTL 20130328)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: HEST 000000007b7fa000 0000A8 (v01 HP     ProLiant 00000001 INTL 00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: BERT 000000007b7f9000 000030 (v01 HP     ProLiant 00000001 INTL 00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: ERST 000000007b7f8000 000230 (v01 HP     ProLiant 00000001 INTL 00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: EINJ 000000007b7f7000 000150 (v01 HP     ProLiant 00000001 INTL 00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: HPET 000000007b7f5000 000038 (v01 HP     ProLiant 00000001 HP   00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: PMCT 000000007b7f4000 000064 (v01 HP     ProLiant 00000001 HP   00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: WDDT 000000007b7f3000 000040 (v01 HP     ProLiant 00000001 HP   00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: APIC 000000007b7f2000 0005AA (v03 HP     ProLiant 00000001 HP   00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: MCFG 000000007b7f1000 00003C (v01 HP     ProLiant 00000001 HP   00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: SLIT 000000007b7f0000 000030 (v01 HP     ProLiant 00000001 HP   00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: SRAT 000000007b7ef000 000500 (v03 HP     ProLiant 00000001 HP   00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: SPMI 000000007b7ee000 000041 (v05 HP     ProLiant 00000001 HP   00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: RASF 000000007b7ed000 000030 (v01 HP     ProLiant 00000001 HP   00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: SPCR 000000007b7ec000 000050 (v01 HP     ProLiant 00000001 HP   00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: MSCT 000000007b7eb000 000064 (v01 HP     ProLiant 00000001 HP   00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: BDAT 000000007b7ea000 000030 (v01 HP     ProLiant 00000001 HP   00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: PCCT 000000007b7e9000 00006E (v01 HP     ProLiant 00000001 HP   00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: SSDT 000000007b7d6000 0062CE (v02 HP     PCISSDT  00000002 HPAG 00020000)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: SSDT 000000007b7d5000 0001CB (v02 HP     TIMESSDT 00000002 HPAG 00020000)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: SSDT 000000007b7d4000 0002F2 (v01 HP         pmab 00000001 INTL 20130328)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: DMAR 000000007b7fd000 000300 (v01 INTEL  INTEL ID 00000001    ? 00000001)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0000 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0002 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0004 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0006 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0008 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x000a -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0010 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0012 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0014 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0016 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0018 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x001a -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0020 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0022 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0024 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0026 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0028 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x002a -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0030 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0032 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0034 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0036 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0038 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x003a -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0001 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0003 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0005 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0007 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0009 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x000b -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0011 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0013 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0015 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0017 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0019 -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x001b -> Node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0021 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0023 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0025 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0027 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0029 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x002b -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0031 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0033 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0035 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0037 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x0039 -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x003b -> Node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x107fffffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x1080000000-0x207fffffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 29 08:44:39 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x107fffffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x107fffb000-0x107fffffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x1080000000-0x207fffffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x207fff8000-0x207fffcfff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0041ffffff] PMD -> [ffff88103fe00000-ffff88107fdfffff] on node 0
Oct 29 08:44:39 node-2 kernel: [    0.000000]  [ffffea0042000000-ffffea0081ffffff] PMD -> [ffff88203f600000-ffff88207f5fffff] on node 1
Oct 29 08:44:39 node-2 kernel: [    0.000000] Zone ranges:
Oct 29 08:44:39 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x207fffffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000] Movable zone start for each node
Oct 29 08:44:39 node-2 kernel: [    0.000000] Early memory node ranges
Oct 29 08:44:39 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x00093fff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x5ae23fff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]   node   0: [mem 0x5bae4000-0x790fefff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]   node   0: [mem 0x7b7ff000-0x7b7fffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x107fffffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000]   node   1: [mem 0x1080000000-0x207fffffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000] On node 0 totalpages: 16745427
Oct 29 08:44:39 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 29 08:44:39 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 29 08:44:39 node-2 kernel: [    0.000000]   DMA zone: 3987 pages, LIFO batch:0
Oct 29 08:44:39 node-2 kernel: [    0.000000]   DMA32 zone: 7633 pages used for memmap
Oct 29 08:44:39 node-2 kernel: [    0.000000]   DMA32 zone: 488512 pages, LIFO batch:31
Oct 29 08:44:39 node-2 kernel: [    0.000000]   Normal zone: 253952 pages used for memmap
Oct 29 08:44:39 node-2 kernel: [    0.000000]   Normal zone: 16252928 pages, LIFO batch:31
Oct 29 08:44:39 node-2 kernel: [    0.000000] On node 1 totalpages: 16777216
Oct 29 08:44:39 node-2 kernel: [    0.000000]   Normal zone: 262144 pages used for memmap
Oct 29 08:44:39 node-2 kernel: [    0.000000]   Normal zone: 16777216 pages, LIFO batch:31
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x00] uid[0x00] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x02] uid[0x02] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x04] uid[0x04] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x06] uid[0x06] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x08] uid[0x08] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x0a] uid[0x0a] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x10] uid[0x10] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x12] uid[0x12] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x14] uid[0x14] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x16] uid[0x16] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x18] uid[0x18] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x1a] uid[0x1a] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x20] uid[0x20] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x22] uid[0x22] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x24] uid[0x24] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x26] uid[0x26] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x28] uid[0x28] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x2a] uid[0x2a] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x30] uid[0x30] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x32] uid[0x32] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x34] uid[0x34] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x36] uid[0x36] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x38] uid[0x38] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x3a] uid[0x3a] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x01] uid[0x01] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x03] uid[0x03] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x05] uid[0x05] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x07] uid[0x07] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x09] uid[0x09] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x0b] uid[0x0b] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x11] uid[0x11] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x13] uid[0x13] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x15] uid[0x15] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x17] uid[0x17] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x19] uid[0x19] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x1b] uid[0x1b] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x21] uid[0x21] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x23] uid[0x23] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x25] uid[0x25] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x27] uid[0x27] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x29] uid[0x29] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x2b] uid[0x2b] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x31] uid[0x31] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x33] uid[0x33] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x35] uid[0x35] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x37] uid[0x37] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x39] uid[0x39] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC (apic_id[0x3b] uid[0x3b] enabled)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x00] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x01] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x02] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x03] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x04] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x05] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x06] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x07] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x08] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x09] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x0a] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x0b] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x10] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x11] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x12] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x13] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x14] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x15] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x16] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x17] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x18] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x19] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x1a] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x1b] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x20] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x21] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x22] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x23] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x24] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x25] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x26] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x27] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x28] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x29] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x2a] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x2b] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x30] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x31] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x32] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x33] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x34] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x35] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x36] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x37] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x38] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x39] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x3a] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: X2APIC_NMI (uid[0x3b] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 29 08:44:39 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 29 08:44:39 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 29 08:44:39 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 29 08:44:39 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 29 08:44:39 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 29 08:44:39 node-2 kernel: [    0.000000] smpboot: Allowing 48 CPUs, 0 hotplug CPUs
Oct 29 08:44:39 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 29 08:44:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x00094000-0x0009ffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x5ae24000-0x5bae3fff]
Oct 29 08:44:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x790ff000-0x791fefff]
Oct 29 08:44:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x791ff000-0x7b5fefff]
Oct 29 08:44:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7b5ff000-0x7b7fefff]
Oct 29 08:44:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7b800000-0x8fffffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xff7fffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff800000-0xffffffff]
Oct 29 08:44:39 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xff7fffff] available for PCI devices
Oct 29 08:44:39 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 29 08:44:39 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:48 nr_node_ids:2
Oct 29 08:44:39 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88103fa00000 s81536 r8192 d20864 u131072
Oct 29 08:44:39 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u131072 alloc=1*2097152
Oct 29 08:44:39 node-2 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 08 09 10 11 24 25 26 27 
Oct 29 08:44:39 node-2 kernel: [    0.000000] pcpu-alloc: [0] 28 29 30 31 32 33 34 35 -- -- -- -- -- -- -- -- 
Oct 29 08:44:39 node-2 kernel: [    0.000000] pcpu-alloc: [1] 12 13 14 15 16 17 18 19 20 21 22 23 36 37 38 39 
Oct 29 08:44:39 node-2 kernel: [    0.000000] pcpu-alloc: [1] 40 41 42 43 44 45 46 47 -- -- -- -- -- -- -- -- 
Oct 29 08:44:39 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 32998829
Oct 29 08:44:39 node-2 kernel: [    0.000000] Policy zone: Normal
Oct 29 08:44:39 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=ff37ac73-7ac9-4aca-9a48-3984eed9d826 nomdmonddf nomdmonisw
Oct 29 08:44:39 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 29 08:44:39 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 29 08:44:39 node-2 kernel: [    0.000000] Checking aperture...
Oct 29 08:44:39 node-2 kernel: [    0.000000] No AGP bridge found
Oct 29 08:44:39 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 29 08:44:39 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 29 08:44:39 node-2 kernel: [    0.000000] Memory: 131884968K/134090572K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 2205604K reserved)
Oct 29 08:44:39 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=48, Nodes=2
Oct 29 08:44:39 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 29 08:44:39 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 29 08:44:39 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=48.
Oct 29 08:44:39 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 29 08:44:39 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-47.
Oct 29 08:44:39 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1880 16
Oct 29 08:44:39 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 29 08:44:39 node-2 kernel: [    0.000000] console [tty0] enabled
Oct 29 08:44:39 node-2 kernel: [    0.000000] allocated 536870912 bytes of page_cgroup
Oct 29 08:44:39 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 29 08:44:39 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 29 08:44:39 node-2 kernel: [    0.000000] hpet clockevent registered
Oct 29 08:44:39 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 29 08:44:39 node-2 kernel: [    0.004000] tsc: Detected 2497.208 MHz processor
Oct 29 08:44:39 node-2 kernel: [    0.000026] Calibrating delay loop (skipped), value calculated using timer frequency.. 4994.41 BogoMIPS (lpj=9988832)
Oct 29 08:44:39 node-2 kernel: [    0.000034] pid_max: default: 49152 minimum: 384
Oct 29 08:44:39 node-2 kernel: [    0.000197] Security Framework initialized
Oct 29 08:44:39 node-2 kernel: [    0.000288] AppArmor: AppArmor initialized
Oct 29 08:44:39 node-2 kernel: [    0.000291] Yama: becoming mindful.
Oct 29 08:44:39 node-2 kernel: [    0.015829] Dentry cache hash table entries: 16777216 (order: 15, 134217728 bytes)
Oct 29 08:44:39 node-2 kernel: [    0.061940] Inode-cache hash table entries: 8388608 (order: 14, 67108864 bytes)
Oct 29 08:44:39 node-2 kernel: [    0.081447] Mount-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 29 08:44:39 node-2 kernel: [    0.081701] Mountpoint-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 29 08:44:39 node-2 kernel: [    0.083243] Initializing cgroup subsys memory
Oct 29 08:44:39 node-2 kernel: [    0.083272] Initializing cgroup subsys devices
Oct 29 08:44:39 node-2 kernel: [    0.083277] Initializing cgroup subsys freezer
Oct 29 08:44:39 node-2 kernel: [    0.083281] Initializing cgroup subsys blkio
Oct 29 08:44:39 node-2 kernel: [    0.083286] Initializing cgroup subsys perf_event
Oct 29 08:44:39 node-2 kernel: [    0.083302] Initializing cgroup subsys hugetlb
Oct 29 08:44:39 node-2 kernel: [    0.083361] CPU: Physical Processor ID: 0
Oct 29 08:44:39 node-2 kernel: [    0.083365] CPU: Processor Core ID: 0
Oct 29 08:44:39 node-2 kernel: [    0.084908] mce: CPU supports 22 MCE banks
Oct 29 08:44:39 node-2 kernel: [    0.084987] CPU0: Thermal monitoring enabled (TM1)
Oct 29 08:44:39 node-2 kernel: [    0.084993] process: using mwait in idle threads
Oct 29 08:44:39 node-2 kernel: [    0.085001] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 29 08:44:39 node-2 kernel: [    0.085001] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 29 08:44:39 node-2 kernel: [    0.085001] tlb_flushall_shift: 6
Oct 29 08:44:39 node-2 kernel: [    0.085233] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 29 08:44:39 node-2 kernel: [    0.087108] ACPI: Core revision 20131115
Oct 29 08:44:39 node-2 kernel: [    0.094029] ACPI: All ACPI Tables successfully acquired
Oct 29 08:44:39 node-2 kernel: [    0.094259] ftrace: allocating 28622 entries in 112 pages
Oct 29 08:44:39 node-2 kernel: [    0.117971] dmar: Host address width 46
Oct 29 08:44:39 node-2 kernel: [    0.117977] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 29 08:44:39 node-2 kernel: [    0.117988] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020df
Oct 29 08:44:39 node-2 kernel: [    0.117993] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 29 08:44:39 node-2 kernel: [    0.118002] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020df
Oct 29 08:44:39 node-2 kernel: [    0.118007] dmar: RMRR base: 0x00000079171000 end: 0x00000079173fff
Oct 29 08:44:39 node-2 kernel: [    0.118011] dmar: RMRR base: 0x000000791ed000 end: 0x000000791f0fff
Oct 29 08:44:39 node-2 kernel: [    0.118014] dmar: RMRR base: 0x000000791dd000 end: 0x000000791ecfff
Oct 29 08:44:39 node-2 kernel: [    0.118017] dmar: RMRR base: 0x000000791ca000 end: 0x000000791dafff
Oct 29 08:44:39 node-2 kernel: [    0.118020] dmar: RMRR base: 0x000000791db000 end: 0x000000791dcfff
Oct 29 08:44:39 node-2 kernel: [    0.118023] dmar: RMRR base: 0x0000005ae24000 end: 0x0000005ae63fff
Oct 29 08:44:39 node-2 kernel: [    0.118162] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 29 08:44:39 node-2 kernel: [    0.118166] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 29 08:44:39 node-2 kernel: [    0.118169] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 29 08:44:39 node-2 kernel: [    0.118172] HPET id 0 under DRHD base 0xc7ffc000
Oct 29 08:44:39 node-2 kernel: [    0.119000] Enabled IRQ remapping in x2apic mode
Oct 29 08:44:39 node-2 kernel: [    0.119003] Enabling x2apic
Oct 29 08:44:39 node-2 kernel: [    0.119006] Enabled x2apic
Oct 29 08:44:39 node-2 kernel: [    0.119013] Switched APIC routing to cluster x2apic.
Oct 29 08:44:39 node-2 kernel: [    0.119785] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 29 08:44:39 node-2 kernel: [    0.159626] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 29 08:44:39 node-2 kernel: [    0.159640] TSC deadline timer enabled
Oct 29 08:44:39 node-2 kernel: [    0.159669] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Broken BIOS detected, complain to your hardware vendor.
Oct 29 08:44:39 node-2 kernel: [    0.159683] [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 38d is 330)
Oct 29 08:44:39 node-2 kernel: [    0.159687] Intel PMU driver.
Oct 29 08:44:39 node-2 kernel: [    0.159692] ... version:                3
Oct 29 08:44:39 node-2 kernel: [    0.159694] ... bit width:              48
Oct 29 08:44:39 node-2 kernel: [    0.159697] ... generic registers:      4
Oct 29 08:44:39 node-2 kernel: [    0.159700] ... value mask:             0000ffffffffffff
Oct 29 08:44:39 node-2 kernel: [    0.159703] ... max period:             0000ffffffffffff
Oct 29 08:44:39 node-2 kernel: [    0.159705] ... fixed-purpose events:   3
Oct 29 08:44:39 node-2 kernel: [    0.159708] ... event mask:             000000070000000f
Oct 29 08:44:39 node-2 kernel: [    0.165026] x86: Booting SMP configuration:
Oct 29 08:44:39 node-2 kernel: [    0.182458] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 29 08:44:39 node-2 kernel: [    0.165031] .... node  #0, CPUs:        #1  #2  #3  #4  #5  #6  #7  #8  #9 #10 #11
Oct 29 08:44:39 node-2 kernel: [    0.340334] .... node  #1, CPUs:   #12 #13 #14 #15 #16 #17 #18 #19 #20 #21 #22 #23
Oct 29 08:44:39 node-2 kernel: [    0.629039] .... node  #0, CPUs:   #24 #25 #26 #27 #28 #29 #30 #31 #32 #33 #34 #35
Oct 29 08:44:39 node-2 kernel: [    0.808987] .... node  #1, CPUs:   #36 #37 #38 #39 #40 #41 #42 #43 #44 #45 #46 #47
Oct 29 08:44:39 node-2 kernel: [    1.001115] x86: Booted up 2 nodes, 48 CPUs
Oct 29 08:44:39 node-2 kernel: [    1.001120] smpboot: Total of 48 processors activated (239771.01 BogoMIPS)
Oct 29 08:44:39 node-2 kernel: [    1.194857] devtmpfs: initialized
Oct 29 08:44:39 node-2 kernel: [    1.203695] EVM: security.selinux
Oct 29 08:44:39 node-2 kernel: [    1.203697] EVM: security.SMACK64
Oct 29 08:44:39 node-2 kernel: [    1.203699] EVM: security.ima
Oct 29 08:44:39 node-2 kernel: [    1.203700] EVM: security.capability
Oct 29 08:44:39 node-2 kernel: [    1.203776] PM: Registering ACPI NVS region [mem 0x791ff000-0x7b5fefff] (37748736 bytes)
Oct 29 08:44:39 node-2 kernel: [    1.205162] pinctrl core: initialized pinctrl subsystem
Oct 29 08:44:39 node-2 kernel: [    1.205235] regulator-dummy: no parameters
Oct 29 08:44:39 node-2 kernel: [    1.205267] RTC time:  8:42:23, date: 10/29/16
Oct 29 08:44:39 node-2 kernel: [    1.205326] NET: Registered protocol family 16
Oct 29 08:44:39 node-2 kernel: [    1.205438] cpuidle: using governor ladder
Oct 29 08:44:39 node-2 kernel: [    1.205440] cpuidle: using governor menu
Oct 29 08:44:39 node-2 kernel: [    1.205488] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Oct 29 08:44:39 node-2 kernel: [    1.205490] ACPI: bus type PCI registered
Oct 29 08:44:39 node-2 kernel: [    1.205493] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 29 08:44:39 node-2 kernel: [    1.205570] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 29 08:44:39 node-2 kernel: [    1.205574] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 29 08:44:39 node-2 kernel: [    1.224591] PCI: Using configuration type 1 for base access
Oct 29 08:44:39 node-2 kernel: [    1.227327] bio: create slab <bio-0> at 0
Oct 29 08:44:39 node-2 kernel: [    1.227868] ACPI: Added _OSI(Module Device)
Oct 29 08:44:39 node-2 kernel: [    1.227871] ACPI: Added _OSI(Processor Device)
Oct 29 08:44:39 node-2 kernel: [    1.227872] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 29 08:44:39 node-2 kernel: [    1.227874] ACPI: Added _OSI(Processor Aggregator Device)
Oct 29 08:44:39 node-2 kernel: [    1.236206] ACPI: Interpreter enabled
Oct 29 08:44:39 node-2 kernel: [    1.236212] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 29 08:44:39 node-2 kernel: [    1.236216] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 29 08:44:39 node-2 kernel: [    1.236220] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 29 08:44:39 node-2 kernel: [    1.236223] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S4_] (20131115/hwxface-580)
Oct 29 08:44:39 node-2 kernel: [    1.236229] ACPI: (supports S0 S5)
Oct 29 08:44:39 node-2 kernel: [    1.236230] ACPI: Using IOAPIC for interrupt routing
Oct 29 08:44:39 node-2 kernel: [    1.236269] HEST: Table parsing has been initialized.
Oct 29 08:44:39 node-2 kernel: [    1.236273] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 29 08:44:39 node-2 kernel: [    1.236465] ACPI: No dock devices found.
Oct 29 08:44:39 node-2 kernel: [    1.244020] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 29 08:44:39 node-2 kernel: [    1.244026] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 29 08:44:39 node-2 kernel: [    1.244031] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 29 08:44:39 node-2 kernel: [    1.244057] PCI host bridge to bus 0000:7f
Oct 29 08:44:39 node-2 kernel: [    1.244060] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 29 08:44:39 node-2 kernel: [    1.244069] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244113] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244151] pci 0000:7f:09.0: [8086:2f90] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244183] pci 0000:7f:09.3: [8086:2f93] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244221] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244253] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 29 08:44:39 node-2 kernel: [    1.244286] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 29 08:44:39 node-2 kernel: [    1.244319] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244351] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244380] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244410] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244439] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244468] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244498] pci 0000:7f:0c.6: [8086:2fe6] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244528] pci 0000:7f:0c.7: [8086:2fe7] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244556] pci 0000:7f:0d.0: [8086:2fe8] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244587] pci 0000:7f:0d.1: [8086:2fe9] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244617] pci 0000:7f:0d.2: [8086:2fea] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244647] pci 0000:7f:0d.3: [8086:2feb] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244679] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244709] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244739] pci 0000:7f:0f.2: [8086:2ffa] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244774] pci 0000:7f:0f.3: [8086:2ffb] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244806] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244838] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244869] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244900] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244928] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 29 08:44:39 node-2 kernel: [    1.244962] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.244992] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 29 08:44:39 node-2 kernel: [    1.245021] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245052] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245088] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 29 08:44:39 node-2 kernel: [    1.245120] pci 0000:7f:12.2: [8086:2f70] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245152] pci 0000:7f:12.4: [8086:2f60] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245185] pci 0000:7f:12.5: [8086:2f38] type 00 class 0x110100
Oct 29 08:44:39 node-2 kernel: [    1.245217] pci 0000:7f:12.6: [8086:2f78] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245251] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245285] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245317] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245353] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245388] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245420] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245452] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245488] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245523] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245557] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245593] pci 0000:7f:14.4: [8086:2fbc] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245629] pci 0000:7f:14.5: [8086:2fbd] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245663] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245697] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245729] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245769] pci 0000:7f:16.1: [8086:2f79] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245811] pci 0000:7f:16.2: [8086:2f6a] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245848] pci 0000:7f:16.3: [8086:2f6b] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245887] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245923] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.245960] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.246003] pci 0000:7f:17.1: [8086:2fd1] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.246041] pci 0000:7f:17.2: [8086:2fd2] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.246078] pci 0000:7f:17.3: [8086:2fd3] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.246115] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.246149] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.246181] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.246224] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.246265] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.246299] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.246332] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.246366] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.246408] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.246448] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.246484] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.246555] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 29 08:44:39 node-2 kernel: [    1.246559] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 29 08:44:39 node-2 kernel: [    1.246563] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 29 08:44:39 node-2 kernel: [    1.246586] PCI host bridge to bus 0000:ff
Oct 29 08:44:39 node-2 kernel: [    1.246588] pci_bus 0000:ff: root bus resource [bus ff]
Oct 29 08:44:39 node-2 kernel: [    1.251010] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251053] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251091] pci 0000:ff:09.0: [8086:2f90] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251129] pci 0000:ff:09.3: [8086:2f93] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251173] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251209] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 29 08:44:39 node-2 kernel: [    1.251244] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 29 08:44:39 node-2 kernel: [    1.251282] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251319] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251351] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251384] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251417] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251450] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251483] pci 0000:ff:0c.6: [8086:2fe6] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251517] pci 0000:ff:0c.7: [8086:2fe7] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251551] pci 0000:ff:0d.0: [8086:2fe8] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251585] pci 0000:ff:0d.1: [8086:2fe9] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251617] pci 0000:ff:0d.2: [8086:2fea] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251650] pci 0000:ff:0d.3: [8086:2feb] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251687] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251722] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251756] pci 0000:ff:0f.2: [8086:2ffa] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251789] pci 0000:ff:0f.3: [8086:2ffb] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251822] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251857] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251890] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251923] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.251956] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 29 08:44:39 node-2 kernel: [    1.251990] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252023] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 29 08:44:39 node-2 kernel: [    1.252057] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252092] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252136] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 29 08:44:39 node-2 kernel: [    1.252170] pci 0000:ff:12.2: [8086:2f70] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252206] pci 0000:ff:12.4: [8086:2f60] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252241] pci 0000:ff:12.5: [8086:2f38] type 00 class 0x110100
Oct 29 08:44:39 node-2 kernel: [    1.252276] pci 0000:ff:12.6: [8086:2f78] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252314] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252351] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252390] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252430] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252472] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252508] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252550] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252591] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252631] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252671] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252711] pci 0000:ff:14.4: [8086:2fbc] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252751] pci 0000:ff:14.5: [8086:2fbd] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252792] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252827] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252866] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252908] pci 0000:ff:16.1: [8086:2f79] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252950] pci 0000:ff:16.2: [8086:2f6a] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.252991] pci 0000:ff:16.3: [8086:2f6b] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253034] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253074] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253112] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253154] pci 0000:ff:17.1: [8086:2fd1] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253196] pci 0000:ff:17.2: [8086:2fd2] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253240] pci 0000:ff:17.3: [8086:2fd3] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253281] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253317] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253355] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253395] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253439] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253476] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253513] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253550] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253588] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253631] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.253671] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.254565] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 29 08:44:39 node-2 kernel: [    1.254570] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 29 08:44:39 node-2 kernel: [    1.254646] acpi PNP0A08:00: _OSC: platform does not support [AER]
Oct 29 08:44:39 node-2 kernel: [    1.254711] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME PCIeCapability]
Oct 29 08:44:39 node-2 kernel: [    1.254714] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
Oct 29 08:44:39 node-2 kernel: [    1.255014] acpi PNP0A08:00: ignoring host bridge window [mem 0x000c4000-0x000cbfff] (conflicts with Video ROM [mem 0x000c0000-0x000c7fff])
Oct 29 08:44:39 node-2 kernel: [    1.255264] PCI host bridge to bus 0000:00
Oct 29 08:44:39 node-2 kernel: [    1.255267] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 29 08:44:39 node-2 kernel: [    1.255269] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 29 08:44:39 node-2 kernel: [    1.255271] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 29 08:44:39 node-2 kernel: [    1.255273] pci_bus 0000:00: root bus resource [io  0x03b0-0x03bb]
Oct 29 08:44:39 node-2 kernel: [    1.255275] pci_bus 0000:00: root bus resource [io  0x03c0-0x03df]
Oct 29 08:44:39 node-2 kernel: [    1.255277] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 29 08:44:39 node-2 kernel: [    1.255279] pci_bus 0000:00: root bus resource [io  0x1000-0x9fff]
Oct 29 08:44:39 node-2 kernel: [    1.255281] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 29 08:44:39 node-2 kernel: [    1.255283] pci_bus 0000:00: root bus resource [mem 0x38000000000-0x39fffffffff]
Oct 29 08:44:39 node-2 kernel: [    1.255290] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 29 08:44:39 node-2 kernel: [    1.255394] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.255433] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.255489] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 29 08:44:39 node-2 kernel: [    1.255514] pci 0000:00:01.1: [8086:2f03] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.255550] pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.255631] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.255667] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.255721] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 29 08:44:39 node-2 kernel: [    1.255744] pci 0000:00:02.1: [8086:2f05] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.255780] pci 0000:00:02.1: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.255854] pci 0000:00:02.2: [8086:2f06] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.255890] pci 0000:00:02.2: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.255964] pci 0000:00:02.3: [8086:2f07] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.256000] pci 0000:00:02.3: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.256075] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.256111] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.256168] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 29 08:44:39 node-2 kernel: [    1.256192] pci 0000:00:03.1: [8086:2f09] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.256228] pci 0000:00:03.1: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.256302] pci 0000:00:03.2: [8086:2f0a] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.256338] pci 0000:00:03.2: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.256412] pci 0000:00:03.3: [8086:2f0b] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.256448] pci 0000:00:03.3: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.256529] pci 0000:00:04.0: [8086:2f20] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.256538] pci 0000:00:04.0: reg 0x10: [mem 0x39ffff2c000-0x39ffff2ffff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.256639] pci 0000:00:04.1: [8086:2f21] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.256647] pci 0000:00:04.1: reg 0x10: [mem 0x39ffff28000-0x39ffff2bfff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.256748] pci 0000:00:04.2: [8086:2f22] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.256756] pci 0000:00:04.2: reg 0x10: [mem 0x39ffff24000-0x39ffff27fff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.256857] pci 0000:00:04.3: [8086:2f23] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.256865] pci 0000:00:04.3: reg 0x10: [mem 0x39ffff20000-0x39ffff23fff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.256965] pci 0000:00:04.4: [8086:2f24] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.256973] pci 0000:00:04.4: reg 0x10: [mem 0x39ffff1c000-0x39ffff1ffff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.257074] pci 0000:00:04.5: [8086:2f25] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.257082] pci 0000:00:04.5: reg 0x10: [mem 0x39ffff18000-0x39ffff1bfff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.257183] pci 0000:00:04.6: [8086:2f26] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.257191] pci 0000:00:04.6: reg 0x10: [mem 0x39ffff14000-0x39ffff17fff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.257292] pci 0000:00:04.7: [8086:2f27] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.257299] pci 0000:00:04.7: reg 0x10: [mem 0x39ffff10000-0x39ffff13fff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.257398] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.257490] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.257592] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.257685] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 29 08:44:39 node-2 kernel: [    1.257691] pci 0000:00:05.4: reg 0x10: [mem 0x95603000-0x95603fff]
Oct 29 08:44:39 node-2 kernel: [    1.257802] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 29 08:44:39 node-2 kernel: [    1.257968] pci 0000:00:14.0: [8086:8d31] type 00 class 0x0c0330
Oct 29 08:44:39 node-2 kernel: [    1.257984] pci 0000:00:14.0: reg 0x10: [mem 0x39ffff00000-0x39ffff0ffff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.258034] pci 0000:00:14.0: PME# supported from D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.258117] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 29 08:44:39 node-2 kernel: [    1.258136] pci 0000:00:1a.0: reg 0x10: [mem 0x95601000-0x956013ff]
Oct 29 08:44:39 node-2 kernel: [    1.258221] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.258301] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.258363] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.258443] pci 0000:00:1c.2: [8086:8d14] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.258505] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.258583] pci 0000:00:1c.4: [8086:8d18] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.258645] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.258724] pci 0000:00:1c.6: [8086:8d1c] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.258787] pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.258865] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.258927] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.259016] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 29 08:44:39 node-2 kernel: [    1.259036] pci 0000:00:1d.0: reg 0x10: [mem 0x95600000-0x956003ff]
Oct 29 08:44:39 node-2 kernel: [    1.259120] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.259209] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 29 08:44:39 node-2 kernel: [    1.259376] pci 0000:00:1f.3: [8086:8d22] type 00 class 0x0c0500
Oct 29 08:44:39 node-2 kernel: [    1.259389] pci 0000:00:1f.3: reg 0x10: [mem 0x39ffff31000-0x39ffff310ff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.259408] pci 0000:00:1f.3: reg 0x20: [io  0x4000-0x401f]
Oct 29 08:44:39 node-2 kernel: [    1.259566] pci 0000:00:01.0: PCI bridge to [bus 02]
Oct 29 08:44:39 node-2 kernel: [    1.259602] pci 0000:00:01.1: PCI bridge to [bus 05]
Oct 29 08:44:39 node-2 kernel: [    1.259652] pci 0000:06:00.0: [14e4:16a2] type 00 class 0x020000
Oct 29 08:44:39 node-2 kernel: [    1.259664] pci 0000:06:00.0: reg 0x10: [mem 0x94000000-0x947fffff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.259674] pci 0000:06:00.0: reg 0x18: [mem 0x94800000-0x94ffffff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.259683] pci 0000:06:00.0: reg 0x20: [mem 0x95010000-0x9501ffff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.259689] pci 0000:06:00.0: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.259723] pci 0000:06:00.0: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.259778] pci 0000:06:00.1: [14e4:16a2] type 00 class 0x020000
Oct 29 08:44:39 node-2 kernel: [    1.259790] pci 0000:06:00.1: reg 0x10: [mem 0x93000000-0x937fffff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.259799] pci 0000:06:00.1: reg 0x18: [mem 0x93800000-0x93ffffff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.259808] pci 0000:06:00.1: reg 0x20: [mem 0x95000000-0x9500ffff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.259814] pci 0000:06:00.1: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.259848] pci 0000:06:00.1: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.267039] pci 0000:00:02.0: PCI bridge to [bus 06]
Oct 29 08:44:39 node-2 kernel: [    1.267050] pci 0000:00:02.0:   bridge window [mem 0x93000000-0x950fffff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.267107] pci 0000:00:02.1: PCI bridge to [bus 0b]
Oct 29 08:44:39 node-2 kernel: [    1.267184] pci 0000:07:00.0: [103c:3239] type 00 class 0x010400
Oct 29 08:44:39 node-2 kernel: [    1.267199] pci 0000:07:00.0: reg 0x10: [mem 0x95400000-0x954fffff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.267211] pci 0000:07:00.0: reg 0x18: [mem 0x95500000-0x955003ff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.267220] pci 0000:07:00.0: reg 0x20: [io  0x3000-0x30ff]
Oct 29 08:44:39 node-2 kernel: [    1.267234] pci 0000:07:00.0: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.267273] pci 0000:07:00.0: PME# supported from D0 D1 D3hot
Oct 29 08:44:39 node-2 kernel: [    1.275036] pci 0000:00:02.2: PCI bridge to [bus 07]
Oct 29 08:44:39 node-2 kernel: [    1.275042] pci 0000:00:02.2:   bridge window [io  0x3000-0x3fff]
Oct 29 08:44:39 node-2 kernel: [    1.275047] pci 0000:00:02.2:   bridge window [mem 0x95400000-0x955fffff]
Oct 29 08:44:39 node-2 kernel: [    1.275103] pci 0000:00:02.3: PCI bridge to [bus 0c]
Oct 29 08:44:39 node-2 kernel: [    1.275258] pci 0000:08:00.0: [8086:10f8] type 00 class 0x020000
Oct 29 08:44:39 node-2 kernel: [    1.275271] pci 0000:08:00.0: reg 0x10: [mem 0x95200000-0x952fffff]
Oct 29 08:44:39 node-2 kernel: [    1.275286] pci 0000:08:00.0: reg 0x18: [io  0x2020-0x203f]
Oct 29 08:44:39 node-2 kernel: [    1.275294] pci 0000:08:00.0: reg 0x1c: [mem 0x95304000-0x95307fff]
Oct 29 08:44:39 node-2 kernel: [    1.275322] pci 0000:08:00.0: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.275351] pci 0000:08:00.0: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.275374] pci 0000:08:00.0: reg 0x184: [mem 0x39fffe00000-0x39fffe03fff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.275383] pci 0000:08:00.0: reg 0x190: [mem 0x39fffd00000-0x39fffd03fff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.275431] pci 0000:08:00.1: [8086:10f8] type 00 class 0x020000
Oct 29 08:44:39 node-2 kernel: [    1.275439] pci 0000:08:00.1: reg 0x10: [mem 0x95100000-0x951fffff]
Oct 29 08:44:39 node-2 kernel: [    1.275449] pci 0000:08:00.1: reg 0x18: [io  0x2000-0x201f]
Oct 29 08:44:39 node-2 kernel: [    1.275454] pci 0000:08:00.1: reg 0x1c: [mem 0x95300000-0x95303fff]
Oct 29 08:44:39 node-2 kernel: [    1.275469] pci 0000:08:00.1: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.275497] pci 0000:08:00.1: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.275517] pci 0000:08:00.1: reg 0x184: [mem 0x39fffc00000-0x39fffc03fff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.275526] pci 0000:08:00.1: reg 0x190: [mem 0x39fffb00000-0x39fffb03fff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.283043] pci 0000:00:03.0: PCI bridge to [bus 08]
Oct 29 08:44:39 node-2 kernel: [    1.283049] pci 0000:00:03.0:   bridge window [io  0x2000-0x2fff]
Oct 29 08:44:39 node-2 kernel: [    1.283053] pci 0000:00:03.0:   bridge window [mem 0x95100000-0x953fffff]
Oct 29 08:44:39 node-2 kernel: [    1.283059] pci 0000:00:03.0:   bridge window [mem 0x39fffb00000-0x39fffefffff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.283108] pci 0000:00:03.1: PCI bridge to [bus 0d]
Oct 29 08:44:39 node-2 kernel: [    1.283169] pci 0000:00:03.2: PCI bridge to [bus 0e]
Oct 29 08:44:39 node-2 kernel: [    1.283201] pci 0000:00:03.3: PCI bridge to [bus 0f]
Oct 29 08:44:39 node-2 kernel: [    1.283252] pci 0000:00:1c.0: PCI bridge to [bus 10]
Oct 29 08:44:39 node-2 kernel: [    1.283322] pci 0000:01:00.0: [103c:3306] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.283340] pci 0000:01:00.0: reg 0x10: [io  0x1200-0x12ff]
Oct 29 08:44:39 node-2 kernel: [    1.283352] pci 0000:01:00.0: reg 0x14: [mem 0x92a8d000-0x92a8d1ff]
Oct 29 08:44:39 node-2 kernel: [    1.283365] pci 0000:01:00.0: reg 0x18: [io  0x1100-0x11ff]
Oct 29 08:44:39 node-2 kernel: [    1.283522] pci 0000:01:00.1: [102b:0533] type 00 class 0x030000
Oct 29 08:44:39 node-2 kernel: [    1.283540] pci 0000:01:00.1: reg 0x10: [mem 0x91000000-0x91ffffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.283552] pci 0000:01:00.1: reg 0x14: [mem 0x92a88000-0x92a8bfff]
Oct 29 08:44:39 node-2 kernel: [    1.283565] pci 0000:01:00.1: reg 0x18: [mem 0x92000000-0x927fffff]
Oct 29 08:44:39 node-2 kernel: [    1.283716] pci 0000:01:00.2: [103c:3307] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.283733] pci 0000:01:00.2: reg 0x10: [io  0x1000-0x10ff]
Oct 29 08:44:39 node-2 kernel: [    1.283745] pci 0000:01:00.2: reg 0x14: [mem 0x92a8c000-0x92a8c0ff]
Oct 29 08:44:39 node-2 kernel: [    1.283758] pci 0000:01:00.2: reg 0x18: [mem 0x92900000-0x929fffff]
Oct 29 08:44:39 node-2 kernel: [    1.283770] pci 0000:01:00.2: reg 0x1c: [mem 0x92a00000-0x92a7ffff]
Oct 29 08:44:39 node-2 kernel: [    1.283783] pci 0000:01:00.2: reg 0x20: [mem 0x92a80000-0x92a87fff]
Oct 29 08:44:39 node-2 kernel: [    1.283795] pci 0000:01:00.2: reg 0x24: [mem 0x92800000-0x928fffff]
Oct 29 08:44:39 node-2 kernel: [    1.283808] pci 0000:01:00.2: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.283867] pci 0000:01:00.2: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.283921] pci 0000:01:00.4: [103c:3300] type 00 class 0x0c0300
Oct 29 08:44:39 node-2 kernel: [    1.283983] pci 0000:01:00.4: reg 0x20: [io  0x1300-0x131f]
Oct 29 08:44:39 node-2 kernel: [    1.291058] pci 0000:00:1c.2: PCI bridge to [bus 01]
Oct 29 08:44:39 node-2 kernel: [    1.291065] pci 0000:00:1c.2:   bridge window [io  0x1000-0x1fff]
Oct 29 08:44:39 node-2 kernel: [    1.291069] pci 0000:00:1c.2:   bridge window [mem 0x90000000-0x92afffff]
Oct 29 08:44:39 node-2 kernel: [    1.291141] pci 0000:00:1c.4: PCI bridge to [bus 11]
Oct 29 08:44:39 node-2 kernel: [    1.291211] pci 0000:00:1c.6: PCI bridge to [bus 12]
Oct 29 08:44:39 node-2 kernel: [    1.291284] pci 0000:00:1c.7: PCI bridge to [bus 13]
Oct 29 08:44:39 node-2 kernel: [    1.291372] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 29 08:44:39 node-2 kernel: [    1.291621] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
Oct 29 08:44:39 node-2 kernel: [    1.291672] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
Oct 29 08:44:39 node-2 kernel: [    1.291719] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
Oct 29 08:44:39 node-2 kernel: [    1.291765] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
Oct 29 08:44:39 node-2 kernel: [    1.291812] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
Oct 29 08:44:39 node-2 kernel: [    1.291859] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
Oct 29 08:44:39 node-2 kernel: [    1.291906] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
Oct 29 08:44:39 node-2 kernel: [    1.291953] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
Oct 29 08:44:39 node-2 kernel: [    1.292131] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 29 08:44:39 node-2 kernel: [    1.292135] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 29 08:44:39 node-2 kernel: [    1.292205] acpi PNP0A08:01: _OSC: platform does not support [AER]
Oct 29 08:44:39 node-2 kernel: [    1.292266] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME PCIeCapability]
Oct 29 08:44:39 node-2 kernel: [    1.292268] acpi PNP0A08:01: FADT indicates ASPM is unsupported, using BIOS configuration
Oct 29 08:44:39 node-2 kernel: [    1.292351] PCI host bridge to bus 0000:80
Oct 29 08:44:39 node-2 kernel: [    1.292353] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 29 08:44:39 node-2 kernel: [    1.292355] pci_bus 0000:80: root bus resource [io  0xa000-0xffff]
Oct 29 08:44:39 node-2 kernel: [    1.292357] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 29 08:44:39 node-2 kernel: [    1.292360] pci_bus 0000:80: root bus resource [mem 0x3a000000000-0x3bfffffffff]
Oct 29 08:44:39 node-2 kernel: [    1.292370] pci 0000:80:00.0: [8086:2f01] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.292411] pci 0000:80:00.0: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.292460] pci 0000:80:01.0: [8086:2f02] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.292500] pci 0000:80:01.0: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.292524] pci 0000:80:01.0: System wakeup disabled by ACPI
Oct 29 08:44:39 node-2 kernel: [    1.292549] pci 0000:80:01.1: [8086:2f03] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.292589] pci 0000:80:01.1: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.292612] pci 0000:80:01.1: System wakeup disabled by ACPI
Oct 29 08:44:39 node-2 kernel: [    1.292641] pci 0000:80:02.0: [8086:2f04] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.292680] pci 0000:80:02.0: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.292707] pci 0000:80:02.0: System wakeup disabled by ACPI
Oct 29 08:44:39 node-2 kernel: [    1.292729] pci 0000:80:02.1: [8086:2f05] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.292769] pci 0000:80:02.1: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.292814] pci 0000:80:02.2: [8086:2f06] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.292854] pci 0000:80:02.2: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.292877] pci 0000:80:02.2: System wakeup disabled by ACPI
Oct 29 08:44:39 node-2 kernel: [    1.292900] pci 0000:80:02.3: [8086:2f07] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.292940] pci 0000:80:02.3: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.292987] pci 0000:80:03.0: [8086:2f08] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.293028] pci 0000:80:03.0: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.293051] pci 0000:80:03.0: System wakeup disabled by ACPI
Oct 29 08:44:39 node-2 kernel: [    1.293079] pci 0000:80:03.1: [8086:2f09] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.293119] pci 0000:80:03.1: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.293163] pci 0000:80:03.2: [8086:2f0a] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.293204] pci 0000:80:03.2: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.293247] pci 0000:80:03.3: [8086:2f0b] type 01 class 0x060400
Oct 29 08:44:39 node-2 kernel: [    1.293287] pci 0000:80:03.3: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.293333] pci 0000:80:04.0: [8086:2f20] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.293342] pci 0000:80:04.0: reg 0x10: [mem 0x3bffff1c000-0x3bffff1ffff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.293415] pci 0000:80:04.1: [8086:2f21] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.293424] pci 0000:80:04.1: reg 0x10: [mem 0x3bffff18000-0x3bffff1bfff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.293498] pci 0000:80:04.2: [8086:2f22] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.293506] pci 0000:80:04.2: reg 0x10: [mem 0x3bffff14000-0x3bffff17fff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.293580] pci 0000:80:04.3: [8086:2f23] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.293589] pci 0000:80:04.3: reg 0x10: [mem 0x3bffff10000-0x3bffff13fff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.293663] pci 0000:80:04.4: [8086:2f24] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.293671] pci 0000:80:04.4: reg 0x10: [mem 0x3bffff0c000-0x3bffff0ffff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.293745] pci 0000:80:04.5: [8086:2f25] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.293753] pci 0000:80:04.5: reg 0x10: [mem 0x3bffff08000-0x3bffff0bfff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.293827] pci 0000:80:04.6: [8086:2f26] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.293835] pci 0000:80:04.6: reg 0x10: [mem 0x3bffff04000-0x3bffff07fff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.293910] pci 0000:80:04.7: [8086:2f27] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.293918] pci 0000:80:04.7: reg 0x10: [mem 0x3bffff00000-0x3bffff03fff 64bit]
Oct 29 08:44:39 node-2 kernel: [    1.293997] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.294065] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.294136] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 29 08:44:39 node-2 kernel: [    1.294197] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 29 08:44:39 node-2 kernel: [    1.294203] pci 0000:80:05.4: reg 0x10: [mem 0xc8300000-0xc8300fff]
Oct 29 08:44:39 node-2 kernel: [    1.294317] pci 0000:80:00.0: PCI bridge to [bus 8d]
Oct 29 08:44:39 node-2 kernel: [    1.294358] pci 0000:80:01.0: PCI bridge to [bus 81]
Oct 29 08:44:39 node-2 kernel: [    1.294395] pci 0000:80:01.1: PCI bridge to [bus 82]
Oct 29 08:44:39 node-2 kernel: [    1.294429] pci 0000:80:02.0: PCI bridge to [bus 83]
Oct 29 08:44:39 node-2 kernel: [    1.294465] pci 0000:80:02.1: PCI bridge to [bus 84]
Oct 29 08:44:39 node-2 kernel: [    1.294499] pci 0000:80:02.2: PCI bridge to [bus 85]
Oct 29 08:44:39 node-2 kernel: [    1.294535] pci 0000:80:02.3: PCI bridge to [bus 86]
Oct 29 08:44:39 node-2 kernel: [    1.294637] pci 0000:87:00.0: [8086:10f8] type 00 class 0x020000
Oct 29 08:44:39 node-2 kernel: [    1.294645] pci 0000:87:00.0: reg 0x10: [mem 0xc8100000-0xc81fffff]
Oct 29 08:44:39 node-2 kernel: [    1.294656] pci 0000:87:00.0: reg 0x18: [io  0xa020-0xa03f]
Oct 29 08:44:39 node-2 kernel: [    1.294662] pci 0000:87:00.0: reg 0x1c: [mem 0xc8204000-0xc8207fff]
Oct 29 08:44:39 node-2 kernel: [    1.294678] pci 0000:87:00.0: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.294709] pci 0000:87:00.0: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.294733] pci 0000:87:00.0: reg 0x184: [mem 0x3bfffe00000-0x3bfffe03fff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.294744] pci 0000:87:00.0: reg 0x190: [mem 0x3bfffd00000-0x3bfffd03fff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.294790] pci 0000:87:00.1: [8086:10f8] type 00 class 0x020000
Oct 29 08:44:39 node-2 kernel: [    1.294798] pci 0000:87:00.1: reg 0x10: [mem 0xc8000000-0xc80fffff]
Oct 29 08:44:39 node-2 kernel: [    1.294809] pci 0000:87:00.1: reg 0x18: [io  0xa000-0xa01f]
Oct 29 08:44:39 node-2 kernel: [    1.294815] pci 0000:87:00.1: reg 0x1c: [mem 0xc8200000-0xc8203fff]
Oct 29 08:44:39 node-2 kernel: [    1.294830] pci 0000:87:00.1: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.294861] pci 0000:87:00.1: PME# supported from D0 D3hot D3cold
Oct 29 08:44:39 node-2 kernel: [    1.294882] pci 0000:87:00.1: reg 0x184: [mem 0x3bfffc00000-0x3bfffc03fff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.294893] pci 0000:87:00.1: reg 0x190: [mem 0x3bfffb00000-0x3bfffb03fff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.299063] pci 0000:80:03.0: PCI bridge to [bus 87]
Oct 29 08:44:39 node-2 kernel: [    1.299067] pci 0000:80:03.0:   bridge window [io  0xa000-0xafff]
Oct 29 08:44:39 node-2 kernel: [    1.299069] pci 0000:80:03.0:   bridge window [mem 0xc8000000-0xc82fffff]
Oct 29 08:44:39 node-2 kernel: [    1.299073] pci 0000:80:03.0:   bridge window [mem 0x3bfffb00000-0x3bfffefffff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.299109] pci 0000:80:03.1: PCI bridge to [bus 8a]
Oct 29 08:44:39 node-2 kernel: [    1.299144] pci 0000:80:03.2: PCI bridge to [bus 8b]
Oct 29 08:44:39 node-2 kernel: [    1.299181] pci 0000:80:03.3: PCI bridge to [bus 8c]
Oct 29 08:44:39 node-2 kernel: [    1.299214] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 29 08:44:39 node-2 kernel: [    1.299314] ACPI: Enabled 9 GPEs in block 00 to 3F
Oct 29 08:44:39 node-2 kernel: [    1.299321] ACPI: \_SB_.UNC0: notify handler is installed
Oct 29 08:44:39 node-2 kernel: [    1.299323] ACPI: \_SB_.UNC1: notify handler is installed
Oct 29 08:44:39 node-2 kernel: [    1.299343] ACPI: \_SB_.PCI0: notify handler is installed
Oct 29 08:44:39 node-2 kernel: [    1.299386] ACPI: \_SB_.PCI1: notify handler is installed
Oct 29 08:44:39 node-2 kernel: [    1.299394] Found 4 acpi root devices
Oct 29 08:44:39 node-2 kernel: [    1.299517] vgaarb: setting as boot device: PCI:0000:01:00.1
Oct 29 08:44:39 node-2 kernel: [    1.299520] vgaarb: device added: PCI:0000:01:00.1,decodes=io+mem,owns=io+mem,locks=none
Oct 29 08:44:39 node-2 kernel: [    1.299525] vgaarb: loaded
Oct 29 08:44:39 node-2 kernel: [    1.299527] vgaarb: bridge control possible 0000:01:00.1
Oct 29 08:44:39 node-2 kernel: [    1.299680] SCSI subsystem initialized
Oct 29 08:44:39 node-2 kernel: [    1.299815] libata version 3.00 loaded.
Oct 29 08:44:39 node-2 kernel: [    1.299832] ACPI: bus type USB registered
Oct 29 08:44:39 node-2 kernel: [    1.299849] usbcore: registered new interface driver usbfs
Oct 29 08:44:39 node-2 kernel: [    1.299856] usbcore: registered new interface driver hub
Oct 29 08:44:39 node-2 kernel: [    1.299890] usbcore: registered new device driver usb
Oct 29 08:44:39 node-2 kernel: [    1.300197] PCI: Using ACPI for IRQ routing
Oct 29 08:44:39 node-2 kernel: [    1.304144] PCI: pci_cache_line_size set to 64 bytes
Oct 29 08:44:39 node-2 kernel: [    1.304369] e820: reserve RAM buffer [mem 0x00094000-0x0009ffff]
Oct 29 08:44:39 node-2 kernel: [    1.304371] e820: reserve RAM buffer [mem 0x5ae24000-0x5bffffff]
Oct 29 08:44:39 node-2 kernel: [    1.304372] e820: reserve RAM buffer [mem 0x790ff000-0x7bffffff]
Oct 29 08:44:39 node-2 kernel: [    1.304373] e820: reserve RAM buffer [mem 0x7b800000-0x7bffffff]
Oct 29 08:44:39 node-2 kernel: [    1.304487] NetLabel: Initializing
Oct 29 08:44:39 node-2 kernel: [    1.304489] NetLabel:  domain hash size = 128
Oct 29 08:44:39 node-2 kernel: [    1.304490] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 29 08:44:39 node-2 kernel: [    1.304505] NetLabel:  unlabeled traffic allowed by default
Oct 29 08:44:39 node-2 kernel: [    1.304574] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 29 08:44:39 node-2 kernel: [    1.304580] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 29 08:44:39 node-2 kernel: [    1.306739] Switched to clocksource hpet
Oct 29 08:44:39 node-2 kernel: [    1.312082] AppArmor: AppArmor Filesystem Enabled
Oct 29 08:44:39 node-2 kernel: [    1.312097] pnp: PnP ACPI init
Oct 29 08:44:39 node-2 kernel: [    1.312109] ACPI: bus type PNP registered
Oct 29 08:44:39 node-2 kernel: [    1.312268] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 29 08:44:39 node-2 kernel: [    1.312401] pnp 00:01: [dma 4]
Oct 29 08:44:39 node-2 kernel: [    1.312420] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 29 08:44:39 node-2 kernel: [    1.312447] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 29 08:44:39 node-2 kernel: [    1.312480] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 29 08:44:39 node-2 kernel: [    1.312521] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 29 08:44:39 node-2 kernel: [    1.312571] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 29 08:44:39 node-2 kernel: [    1.312655] system 00:06: [io  0x0500-0x053f] has been reserved
Oct 29 08:44:39 node-2 kernel: [    1.312658] system 00:06: [io  0x0400-0x047f] has been reserved
Oct 29 08:44:39 node-2 kernel: [    1.312660] system 00:06: [io  0x0540-0x057f] has been reserved
Oct 29 08:44:39 node-2 kernel: [    1.312662] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 29 08:44:39 node-2 kernel: [    1.312664] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 29 08:44:39 node-2 kernel: [    1.312666] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 29 08:44:39 node-2 kernel: [    1.312669] system 00:06: [mem 0xfed1c000-0xfed3ffff] has been reserved
Oct 29 08:44:39 node-2 kernel: [    1.312671] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 29 08:44:39 node-2 kernel: [    1.312674] system 00:06: [mem 0xff000000-0xffffffff] could not be reserved
Oct 29 08:44:39 node-2 kernel: [    1.312676] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 29 08:44:39 node-2 kernel: [    1.312678] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 29 08:44:39 node-2 kernel: [    1.312680] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 29 08:44:39 node-2 kernel: [    1.312682] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 29 08:44:39 node-2 kernel: [    1.312685] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 29 08:44:39 node-2 kernel: [    1.312708] pnp 00:07: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 29 08:44:39 node-2 kernel: [    1.312742] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 29 08:44:39 node-2 kernel: [    1.312767] pnp 00:09: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 29 08:44:39 node-2 kernel: [    1.312852] pnp: PnP ACPI: found 10 devices
Oct 29 08:44:39 node-2 kernel: [    1.312854] ACPI: bus type PNP unregistered
Oct 29 08:44:39 node-2 kernel: [    1.319484] pci 0000:00:02.0: BAR 14: assigned [mem 0x92b00000-0x92bfffff]
Oct 29 08:44:39 node-2 kernel: [    1.319489] pci 0000:00:02.2: BAR 15: assigned [mem 0x92c00000-0x92cfffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.319492] pci 0000:00:1c.2: BAR 15: assigned [mem 0x92d00000-0x92dfffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.319494] pci 0000:00:01.0: PCI bridge to [bus 02]
Oct 29 08:44:39 node-2 kernel: [    1.319501] pci 0000:00:01.1: PCI bridge to [bus 05]
Oct 29 08:44:39 node-2 kernel: [    1.319508] pci 0000:06:00.0: BAR 6: assigned [mem 0x95080000-0x950fffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.319510] pci 0000:06:00.1: BAR 6: assigned [mem 0x92b00000-0x92b7ffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.319513] pci 0000:00:02.0: PCI bridge to [bus 06]
Oct 29 08:44:39 node-2 kernel: [    1.319516] pci 0000:00:02.0:   bridge window [mem 0x92b00000-0x92bfffff]
Oct 29 08:44:39 node-2 kernel: [    1.319519] pci 0000:00:02.0:   bridge window [mem 0x93000000-0x950fffff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.319523] pci 0000:00:02.1: PCI bridge to [bus 0b]
Oct 29 08:44:39 node-2 kernel: [    1.319530] pci 0000:07:00.0: BAR 6: assigned [mem 0x92c00000-0x92c7ffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.319532] pci 0000:00:02.2: PCI bridge to [bus 07]
Oct 29 08:44:39 node-2 kernel: [    1.319535] pci 0000:00:02.2:   bridge window [io  0x3000-0x3fff]
Oct 29 08:44:39 node-2 kernel: [    1.319538] pci 0000:00:02.2:   bridge window [mem 0x95400000-0x955fffff]
Oct 29 08:44:39 node-2 kernel: [    1.319541] pci 0000:00:02.2:   bridge window [mem 0x92c00000-0x92cfffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.319545] pci 0000:00:02.3: PCI bridge to [bus 0c]
Oct 29 08:44:39 node-2 kernel: [    1.319552] pci 0000:08:00.0: BAR 6: assigned [mem 0x95380000-0x953fffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.319555] pci 0000:08:00.1: BAR 6: can't assign mem pref (size 0x80000)
Oct 29 08:44:39 node-2 kernel: [    1.319558] pci 0000:00:03.0: PCI bridge to [bus 08]
Oct 29 08:44:39 node-2 kernel: [    1.319560] pci 0000:00:03.0:   bridge window [io  0x2000-0x2fff]
Oct 29 08:44:39 node-2 kernel: [    1.319563] pci 0000:00:03.0:   bridge window [mem 0x95100000-0x953fffff]
Oct 29 08:44:39 node-2 kernel: [    1.319567] pci 0000:00:03.0:   bridge window [mem 0x39fffb00000-0x39fffefffff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.319571] pci 0000:00:03.1: PCI bridge to [bus 0d]
Oct 29 08:44:39 node-2 kernel: [    1.319577] pci 0000:00:03.2: PCI bridge to [bus 0e]
Oct 29 08:44:39 node-2 kernel: [    1.319583] pci 0000:00:03.3: PCI bridge to [bus 0f]
Oct 29 08:44:39 node-2 kernel: [    1.319589] pci 0000:00:1c.0: PCI bridge to [bus 10]
Oct 29 08:44:39 node-2 kernel: [    1.319599] pci 0000:01:00.2: BAR 6: assigned [mem 0x92d00000-0x92d0ffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.319602] pci 0000:00:1c.2: PCI bridge to [bus 01]
Oct 29 08:44:39 node-2 kernel: [    1.319604] pci 0000:00:1c.2:   bridge window [io  0x1000-0x1fff]
Oct 29 08:44:39 node-2 kernel: [    1.319609] pci 0000:00:1c.2:   bridge window [mem 0x90000000-0x92afffff]
Oct 29 08:44:39 node-2 kernel: [    1.319612] pci 0000:00:1c.2:   bridge window [mem 0x92d00000-0x92dfffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.319618] pci 0000:00:1c.4: PCI bridge to [bus 11]
Oct 29 08:44:39 node-2 kernel: [    1.319627] pci 0000:00:1c.6: PCI bridge to [bus 12]
Oct 29 08:44:39 node-2 kernel: [    1.319636] pci 0000:00:1c.7: PCI bridge to [bus 13]
Oct 29 08:44:39 node-2 kernel: [    1.319646] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 29 08:44:39 node-2 kernel: [    1.319648] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 29 08:44:39 node-2 kernel: [    1.319649] pci_bus 0000:00: resource 6 [io  0x03b0-0x03bb]
Oct 29 08:44:39 node-2 kernel: [    1.319650] pci_bus 0000:00: resource 7 [io  0x03c0-0x03df]
Oct 29 08:44:39 node-2 kernel: [    1.319651] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 29 08:44:39 node-2 kernel: [    1.319653] pci_bus 0000:00: resource 9 [io  0x1000-0x9fff]
Oct 29 08:44:39 node-2 kernel: [    1.319654] pci_bus 0000:00: resource 10 [mem 0x90000000-0xc7ffbfff]
Oct 29 08:44:39 node-2 kernel: [    1.319655] pci_bus 0000:00: resource 11 [mem 0x38000000000-0x39fffffffff]
Oct 29 08:44:39 node-2 kernel: [    1.319657] pci_bus 0000:06: resource 1 [mem 0x92b00000-0x92bfffff]
Oct 29 08:44:39 node-2 kernel: [    1.319658] pci_bus 0000:06: resource 2 [mem 0x93000000-0x950fffff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.319660] pci_bus 0000:07: resource 0 [io  0x3000-0x3fff]
Oct 29 08:44:39 node-2 kernel: [    1.319661] pci_bus 0000:07: resource 1 [mem 0x95400000-0x955fffff]
Oct 29 08:44:39 node-2 kernel: [    1.319662] pci_bus 0000:07: resource 2 [mem 0x92c00000-0x92cfffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.319664] pci_bus 0000:08: resource 0 [io  0x2000-0x2fff]
Oct 29 08:44:39 node-2 kernel: [    1.319665] pci_bus 0000:08: resource 1 [mem 0x95100000-0x953fffff]
Oct 29 08:44:39 node-2 kernel: [    1.319666] pci_bus 0000:08: resource 2 [mem 0x39fffb00000-0x39fffefffff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.319668] pci_bus 0000:01: resource 0 [io  0x1000-0x1fff]
Oct 29 08:44:39 node-2 kernel: [    1.319669] pci_bus 0000:01: resource 1 [mem 0x90000000-0x92afffff]
Oct 29 08:44:39 node-2 kernel: [    1.319671] pci_bus 0000:01: resource 2 [mem 0x92d00000-0x92dfffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.319712] pci 0000:80:00.0: PCI bridge to [bus 8d]
Oct 29 08:44:39 node-2 kernel: [    1.319718] pci 0000:80:01.0: PCI bridge to [bus 81]
Oct 29 08:44:39 node-2 kernel: [    1.319725] pci 0000:80:01.1: PCI bridge to [bus 82]
Oct 29 08:44:39 node-2 kernel: [    1.319732] pci 0000:80:02.0: PCI bridge to [bus 83]
Oct 29 08:44:39 node-2 kernel: [    1.319738] pci 0000:80:02.1: PCI bridge to [bus 84]
Oct 29 08:44:39 node-2 kernel: [    1.319745] pci 0000:80:02.2: PCI bridge to [bus 85]
Oct 29 08:44:39 node-2 kernel: [    1.319751] pci 0000:80:02.3: PCI bridge to [bus 86]
Oct 29 08:44:39 node-2 kernel: [    1.319759] pci 0000:87:00.0: BAR 6: assigned [mem 0xc8280000-0xc82fffff pref]
Oct 29 08:44:39 node-2 kernel: [    1.319761] pci 0000:87:00.1: BAR 6: can't assign mem pref (size 0x80000)
Oct 29 08:44:39 node-2 kernel: [    1.319763] pci 0000:80:03.0: PCI bridge to [bus 87]
Oct 29 08:44:39 node-2 kernel: [    1.319766] pci 0000:80:03.0:   bridge window [io  0xa000-0xafff]
Oct 29 08:44:39 node-2 kernel: [    1.319769] pci 0000:80:03.0:   bridge window [mem 0xc8000000-0xc82fffff]
Oct 29 08:44:39 node-2 kernel: [    1.319772] pci 0000:80:03.0:   bridge window [mem 0x3bfffb00000-0x3bfffefffff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.319776] pci 0000:80:03.1: PCI bridge to [bus 8a]
Oct 29 08:44:39 node-2 kernel: [    1.319783] pci 0000:80:03.2: PCI bridge to [bus 8b]
Oct 29 08:44:39 node-2 kernel: [    1.319789] pci 0000:80:03.3: PCI bridge to [bus 8c]
Oct 29 08:44:39 node-2 kernel: [    1.319796] pci_bus 0000:80: resource 4 [io  0xa000-0xffff]
Oct 29 08:44:39 node-2 kernel: [    1.319797] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 29 08:44:39 node-2 kernel: [    1.319799] pci_bus 0000:80: resource 6 [mem 0x3a000000000-0x3bfffffffff]
Oct 29 08:44:39 node-2 kernel: [    1.319800] pci_bus 0000:87: resource 0 [io  0xa000-0xafff]
Oct 29 08:44:39 node-2 kernel: [    1.319802] pci_bus 0000:87: resource 1 [mem 0xc8000000-0xc82fffff]
Oct 29 08:44:39 node-2 kernel: [    1.319803] pci_bus 0000:87: resource 2 [mem 0x3bfffb00000-0x3bfffefffff 64bit pref]
Oct 29 08:44:39 node-2 kernel: [    1.319849] NET: Registered protocol family 2
Oct 29 08:44:39 node-2 kernel: [    1.320402] TCP established hash table entries: 524288 (order: 10, 4194304 bytes)
Oct 29 08:44:39 node-2 kernel: [    1.321113] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 29 08:44:39 node-2 kernel: [    1.321280] TCP: Hash tables configured (established 524288 bind 65536)
Oct 29 08:44:39 node-2 kernel: [    1.321321] TCP: reno registered
Oct 29 08:44:39 node-2 kernel: [    1.321456] UDP hash table entries: 65536 (order: 9, 2097152 bytes)
Oct 29 08:44:39 node-2 kernel: [    1.321891] UDP-Lite hash table entries: 65536 (order: 9, 2097152 bytes)
Oct 29 08:44:39 node-2 kernel: [    1.322408] NET: Registered protocol family 1
Oct 29 08:44:39 node-2 kernel: [    1.554935] pci 0000:01:00.1: Video device with shadowed ROM
Oct 29 08:44:39 node-2 kernel: [    1.555343] PCI: CLS 64 bytes, default 64
Oct 29 08:44:39 node-2 kernel: [    1.555429] Trying to unpack rootfs image as initramfs...
Oct 29 08:44:39 node-2 kernel: [    2.123043] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Oct 29 08:44:39 node-2 kernel: [    2.123133] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 29 08:44:39 node-2 kernel: [    2.123139] software IO TLB [mem 0x750ff000-0x790ff000] (64MB) mapped at [ffff8800750ff000-ffff8800790fefff]
Oct 29 08:44:39 node-2 kernel: [    2.125218] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125231] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125254] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125270] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125286] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125302] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125318] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125334] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125350] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125366] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125383] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125400] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125419] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125440] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125465] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125483] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125501] microcode: CPU16 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125518] microcode: CPU17 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125536] microcode: CPU18 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125553] microcode: CPU19 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125571] microcode: CPU20 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125588] microcode: CPU21 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125606] microcode: CPU22 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125624] microcode: CPU23 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125641] microcode: CPU24 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125657] microcode: CPU25 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125676] microcode: CPU26 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125690] microcode: CPU27 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125703] microcode: CPU28 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125717] microcode: CPU29 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125731] microcode: CPU30 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125744] microcode: CPU31 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125758] microcode: CPU32 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125771] microcode: CPU33 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125785] microcode: CPU34 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125799] microcode: CPU35 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125813] microcode: CPU36 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125829] microcode: CPU37 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125849] microcode: CPU38 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125864] microcode: CPU39 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125879] microcode: CPU40 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125894] microcode: CPU41 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125908] microcode: CPU42 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125923] microcode: CPU43 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125937] microcode: CPU44 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125953] microcode: CPU45 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125968] microcode: CPU46 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.125982] microcode: CPU47 sig=0x306f2, pf=0x1, revision=0x2e
Oct 29 08:44:39 node-2 kernel: [    2.126101] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 29 08:44:39 node-2 kernel: [    2.126109] Scanning for low memory corruption every 60 seconds
Oct 29 08:44:39 node-2 kernel: [    2.127246] Initialise system trusted keyring
Oct 29 08:44:39 node-2 kernel: [    2.127386] audit: initializing netlink socket (disabled)
Oct 29 08:44:39 node-2 kernel: [    2.127424] type=2000 audit(1477730543.896:1): initialized
Oct 29 08:44:39 node-2 kernel: [    2.181446] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 29 08:44:39 node-2 kernel: [    2.188013] zbud: loaded
Oct 29 08:44:39 node-2 kernel: [    2.188309] VFS: Disk quotas dquot_6.5.2
Oct 29 08:44:39 node-2 kernel: [    2.188418] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 29 08:44:39 node-2 kernel: [    2.189354] fuse init (API version 7.22)
Oct 29 08:44:39 node-2 kernel: [    2.189505] msgmni has been set to 32768
Oct 29 08:44:39 node-2 kernel: [    2.189630] Key type big_key registered
Oct 29 08:44:39 node-2 kernel: [    2.190543] Key type asymmetric registered
Oct 29 08:44:39 node-2 kernel: [    2.190547] Asymmetric key parser 'x509' registered
Oct 29 08:44:39 node-2 kernel: [    2.190614] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 29 08:44:39 node-2 kernel: [    2.190805] io scheduler noop registered
Oct 29 08:44:39 node-2 kernel: [    2.190809] io scheduler deadline registered (default)
Oct 29 08:44:39 node-2 kernel: [    2.190865] io scheduler cfq registered
Oct 29 08:44:39 node-2 kernel: [    2.191708] pcieport 0000:00:01.0: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.191714] pcieport 0000:00:01.0: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.191805] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.192083] pcieport 0000:00:01.1: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.192087] pcieport 0000:00:01.1: PCI INT A: no GSI
Oct 29 08:44:39 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 29 08:44:39 node-2 kernel: [    2.192120] pcieport 0000:00:01.1: irq 91 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.192387] pcieport 0000:00:02.0: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.192391] pcieport 0000:00:02.0: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.192423] pcieport 0000:00:02.0: irq 92 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.192680] pcieport 0000:00:02.1: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.192684] pcieport 0000:00:02.1: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.192715] pcieport 0000:00:02.1: irq 93 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.192978] pcieport 0000:00:02.2: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.192982] pcieport 0000:00:02.2: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.193013] pcieport 0000:00:02.2: irq 94 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.193268] pcieport 0000:00:02.3: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.193272] pcieport 0000:00:02.3: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.193303] pcieport 0000:00:02.3: irq 95 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.193564] pcieport 0000:00:03.0: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.193569] pcieport 0000:00:03.0: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.193601] pcieport 0000:00:03.0: irq 96 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.193856] pcieport 0000:00:03.1: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.193860] pcieport 0000:00:03.1: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.193891] pcieport 0000:00:03.1: irq 97 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.194151] pcieport 0000:00:03.2: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.194155] pcieport 0000:00:03.2: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.194186] pcieport 0000:00:03.2: irq 98 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.194447] pcieport 0000:00:03.3: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.194451] pcieport 0000:00:03.3: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.194482] pcieport 0000:00:03.3: irq 99 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.194802] pcieport 0000:00:1c.0: irq 100 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.194902] pcieport 0000:00:1c.2: irq 101 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.195213] pcieport 0000:00:1c.4: irq 102 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.195520] pcieport 0000:00:1c.6: irq 103 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.195820] pcieport 0000:00:1c.7: irq 104 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.196057] pcieport 0000:80:00.0: irq 105 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.196282] pcieport 0000:80:01.0: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.196289] pcieport 0000:80:01.0: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.196326] pcieport 0000:80:01.0: irq 106 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.196457] pcieport 0000:80:01.1: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.196462] pcieport 0000:80:01.1: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.196495] pcieport 0000:80:01.1: irq 107 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.196623] pcieport 0000:80:02.0: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.196628] pcieport 0000:80:02.0: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.196661] pcieport 0000:80:02.0: irq 108 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.196778] pcieport 0000:80:02.1: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.196782] pcieport 0000:80:02.1: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.196814] pcieport 0000:80:02.1: irq 109 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.196936] pcieport 0000:80:02.2: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.196941] pcieport 0000:80:02.2: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.196973] pcieport 0000:80:02.2: irq 110 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.197089] pcieport 0000:80:02.3: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.197093] pcieport 0000:80:02.3: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.197125] pcieport 0000:80:02.3: irq 111 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.197246] pcieport 0000:80:03.0: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.197251] pcieport 0000:80:03.0: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.197284] pcieport 0000:80:03.0: irq 112 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.197400] pcieport 0000:80:03.1: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.197404] pcieport 0000:80:03.1: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.197436] pcieport 0000:80:03.1: irq 113 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.197556] pcieport 0000:80:03.2: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.197561] pcieport 0000:80:03.2: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.197593] pcieport 0000:80:03.2: irq 114 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.197707] pcieport 0000:80:03.3: can't derive routing for PCI INT A
Oct 29 08:44:39 node-2 kernel: [    2.197712] pcieport 0000:80:03.3: PCI INT A: no GSI
Oct 29 08:44:39 node-2 kernel: [    2.197743] pcieport 0000:80:03.3: irq 115 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    2.197882] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.197892] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.197914] pcieport 0000:00:01.1: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.197920] pcie_pme 0000:00:01.1:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.197940] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.197945] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.197949] pci 0000:06:00.1: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.197954] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.197974] pcieport 0000:00:02.1: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.197979] pcie_pme 0000:00:02.1:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.197998] pcieport 0000:00:02.2: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198002] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198008] pcie_pme 0000:00:02.2:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198028] pcieport 0000:00:02.3: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198034] pcie_pme 0000:00:02.3:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198061] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198065] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198069] pci 0000:08:00.1: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198074] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198093] pcieport 0000:00:03.1: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198099] pcie_pme 0000:00:03.1:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198118] pcieport 0000:00:03.2: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198124] pcie_pme 0000:00:03.2:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198154] pcieport 0000:00:03.3: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198160] pcie_pme 0000:00:03.3:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198182] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198188] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198208] pcieport 0000:00:1c.2: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198212] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198216] pci 0000:01:00.1: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198220] pci 0000:01:00.2: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198224] pci 0000:01:00.4: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198230] pcie_pme 0000:00:1c.2:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198249] pcieport 0000:00:1c.4: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198256] pcie_pme 0000:00:1c.4:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198276] pcieport 0000:00:1c.6: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198282] pcie_pme 0000:00:1c.6:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198302] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198308] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198331] pcieport 0000:80:00.0: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198337] pcie_pme 0000:80:00.0:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198359] pcieport 0000:80:01.0: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198364] pcie_pme 0000:80:01.0:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198407] pcieport 0000:80:01.1: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198413] pcie_pme 0000:80:01.1:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198436] pcieport 0000:80:02.0: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198442] pcie_pme 0000:80:02.0:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198465] pcieport 0000:80:02.1: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198471] pcie_pme 0000:80:02.1:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198492] pcieport 0000:80:02.2: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198498] pcie_pme 0000:80:02.2:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198520] pcieport 0000:80:02.3: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198526] pcie_pme 0000:80:02.3:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198549] pcieport 0000:80:03.0: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198553] pci 0000:87:00.0: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198569] pci 0000:87:00.1: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198575] pcie_pme 0000:80:03.0:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198599] pcieport 0000:80:03.1: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198605] pcie_pme 0000:80:03.1:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198635] pcieport 0000:80:03.2: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198641] pcie_pme 0000:80:03.2:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198676] pcieport 0000:80:03.3: Signaling PME through PCIe PME interrupt
Oct 29 08:44:39 node-2 kernel: [    2.198682] pcie_pme 0000:80:03.3:pcie01: service driver pcie_pme loaded
Oct 29 08:44:39 node-2 kernel: [    2.198722] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 29 08:44:39 node-2 kernel: [    2.198761] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 29 08:44:39 node-2 kernel: [    2.198772] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 29 08:44:39 node-2 kernel: [    2.198796] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 29 08:44:39 node-2 kernel: [    2.198904] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 29 08:44:39 node-2 kernel: [    2.198907] vesafb: scrolling: redraw
Oct 29 08:44:39 node-2 kernel: [    2.198911] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 29 08:44:39 node-2 kernel: [    2.422592] vesafb: framebuffer at 0x91000000, mapped to 0xffffc9001ce80000, using 1216k, total 1216k
Oct 29 08:44:39 node-2 kernel: [    2.435372] Console: switching to colour frame buffer device 80x30
Oct 29 08:44:39 node-2 kernel: [    2.448315] fb0: VESA VGA frame buffer device
Oct 29 08:44:39 node-2 kernel: [    2.448609] intel_idle: MWAIT substates: 0x2120
Oct 29 08:44:39 node-2 kernel: [    2.448611] intel_idle: v0.4 model 0x3F
Oct 29 08:44:39 node-2 kernel: [    2.448613] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 29 08:44:39 node-2 kernel: [    2.450113] ipmi message handler version 39.2
Oct 29 08:44:39 node-2 kernel: [    2.450533] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
Oct 29 08:44:39 node-2 kernel: [    2.450974] ACPI: Power Button [PWRF]
Oct 29 08:44:39 node-2 kernel: [    2.457407] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 29 08:44:39 node-2 kernel: [    2.468539] pstore: Registered erst as persistent store backend
Oct 29 08:44:39 node-2 kernel: [    2.474881] GHES: APEI firmware first mode is enabled by WHEA _OSC.
Oct 29 08:44:39 node-2 kernel: [    2.481455] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 29 08:44:39 node-2 kernel: [    2.508770] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 29 08:44:39 node-2 kernel: [    2.543300] 00:09: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 29 08:44:39 node-2 kernel: [    2.560559] Linux agpgart interface v0.103
Oct 29 08:44:39 node-2 kernel: [    2.571043] brd: module loaded
Oct 29 08:44:39 node-2 kernel: [    2.580780] loop: module loaded
Oct 29 08:44:39 node-2 kernel: [    2.589275] libphy: Fixed MDIO Bus: probed
Oct 29 08:44:39 node-2 kernel: [    2.597146] tun: Universal TUN/TAP device driver, 1.6
Oct 29 08:44:39 node-2 kernel: [    2.605211] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 29 08:44:39 node-2 kernel: [    2.613304] PPP generic driver version 2.4.2
Oct 29 08:44:39 node-2 kernel: [    2.621647] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 29 08:44:39 node-2 kernel: [    2.630081] ehci-pci: EHCI PCI platform driver
Oct 29 08:44:39 node-2 kernel: [    2.638995] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 29 08:44:39 node-2 kernel: [    2.647315] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 29 08:44:39 node-2 kernel: [    2.663838] ehci-pci 0000:00:1a.0: debug port 2
Oct 29 08:44:39 node-2 kernel: [    2.676279] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 29 08:44:39 node-2 kernel: [    2.676331] ehci-pci 0000:00:1a.0: irq 18, io mem 0x95601000
Oct 29 08:44:39 node-2 kernel: [    2.694485] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 29 08:44:39 node-2 kernel: [    2.702520] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 29 08:44:39 node-2 kernel: [    2.710535] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 29 08:44:39 node-2 kernel: [    2.726344] usb usb1: Product: EHCI Host Controller
Oct 29 08:44:39 node-2 kernel: [    2.734166] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 29 08:44:39 node-2 kernel: [    2.742170] usb usb1: SerialNumber: 0000:00:1a.0
Oct 29 08:44:39 node-2 kernel: [    2.750151] hub 1-0:1.0: USB hub found
Oct 29 08:44:39 node-2 kernel: [    2.757791] hub 1-0:1.0: 2 ports detected
Oct 29 08:44:39 node-2 kernel: [    2.765686] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 29 08:44:39 node-2 kernel: [    2.773171] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 29 08:44:39 node-2 kernel: [    2.787655] ehci-pci 0000:00:1d.0: debug port 2
Oct 29 08:44:39 node-2 kernel: [    2.798721] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 29 08:44:39 node-2 kernel: [    2.798732] ehci-pci 0000:00:1d.0: irq 18, io mem 0x95600000
Oct 29 08:44:39 node-2 kernel: [    2.814503] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 29 08:44:39 node-2 kernel: [    2.821576] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 29 08:44:39 node-2 kernel: [    2.828675] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 29 08:44:39 node-2 kernel: [    2.842850] usb usb2: Product: EHCI Host Controller
Oct 29 08:44:39 node-2 kernel: [    2.850219] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 29 08:44:39 node-2 kernel: [    2.857685] usb usb2: SerialNumber: 0000:00:1d.0
Oct 29 08:44:39 node-2 kernel: [    2.865188] hub 2-0:1.0: USB hub found
Oct 29 08:44:39 node-2 kernel: [    2.872383] hub 2-0:1.0: 2 ports detected
Oct 29 08:44:39 node-2 kernel: [    2.879502] ehci-platform: EHCI generic platform driver
Oct 29 08:44:39 node-2 kernel: [    2.886524] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 29 08:44:39 node-2 kernel: [    2.893642] ohci-pci: OHCI PCI platform driver
Oct 29 08:44:39 node-2 kernel: [    2.900884] ohci-platform: OHCI generic platform driver
Oct 29 08:44:39 node-2 kernel: [    2.907871] uhci_hcd: USB Universal Host Controller Interface driver
Oct 29 08:44:39 node-2 kernel: [    2.915145] uhci_hcd 0000:01:00.4: UHCI Host Controller
Oct 29 08:44:39 node-2 kernel: [    2.922561] uhci_hcd 0000:01:00.4: new USB bus registered, assigned bus number 3
Oct 29 08:44:39 node-2 kernel: [    2.936800] uhci_hcd 0000:01:00.4: port count misdetected? forcing to 2 ports
Oct 29 08:44:39 node-2 kernel: [    2.944218] uhci_hcd 0000:01:00.4: irq 19, io base 0x00001300
Oct 29 08:44:39 node-2 kernel: [    2.951649] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
Oct 29 08:44:39 node-2 kernel: [    2.959141] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 29 08:44:39 node-2 kernel: [    2.973654] usb usb3: Product: UHCI Host Controller
Oct 29 08:44:39 node-2 kernel: [    2.981104] usb usb3: Manufacturer: Linux 3.13.0-100-generic uhci_hcd
Oct 29 08:44:39 node-2 kernel: [    2.988819] usb usb3: SerialNumber: 0000:01:00.4
Oct 29 08:44:39 node-2 kernel: [    2.996568] hub 3-0:1.0: USB hub found
Oct 29 08:44:39 node-2 kernel: [    3.004129] hub 3-0:1.0: 2 ports detected
Oct 29 08:44:39 node-2 kernel: [    3.011993] xhci_hcd 0000:00:14.0: xHCI Host Controller
Oct 29 08:44:39 node-2 kernel: [    3.019515] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
Oct 29 08:44:39 node-2 kernel: [    3.035559] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
Oct 29 08:44:39 node-2 kernel: [    3.035614] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
Oct 29 08:44:39 node-2 kernel: [    3.043323] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 29 08:44:39 node-2 kernel: [    3.058674] usb usb4: Product: xHCI Host Controller
Oct 29 08:44:39 node-2 kernel: [    3.066350] usb usb4: Manufacturer: Linux 3.13.0-100-generic xhci_hcd
Oct 29 08:44:39 node-2 kernel: [    3.074068] usb usb4: SerialNumber: 0000:00:14.0
Oct 29 08:44:39 node-2 kernel: [    3.081948] hub 4-0:1.0: USB hub found
Oct 29 08:44:39 node-2 kernel: [    3.089555] hub 4-0:1.0: 15 ports detected
Oct 29 08:44:39 node-2 kernel: [    3.098280] xhci_hcd 0000:00:14.0: xHCI Host Controller
Oct 29 08:44:39 node-2 kernel: [    3.105918] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 5
Oct 29 08:44:39 node-2 kernel: [    3.106548] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 29 08:44:39 node-2 kernel: [    3.129090] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003
Oct 29 08:44:39 node-2 kernel: [    3.137072] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 29 08:44:39 node-2 kernel: [    3.152812] usb usb5: Product: xHCI Host Controller
Oct 29 08:44:39 node-2 kernel: [    3.160602] usb usb5: Manufacturer: Linux 3.13.0-100-generic xhci_hcd
Oct 29 08:44:39 node-2 kernel: [    3.168469] usb usb5: SerialNumber: 0000:00:14.0
Oct 29 08:44:39 node-2 kernel: [    3.176512] tsc: Refined TSC clocksource calibration: 2497.106 MHz
Oct 29 08:44:39 node-2 kernel: [    3.184487] hub 5-0:1.0: USB hub found
Oct 29 08:44:39 node-2 kernel: [    3.192148] hub 5-0:1.0: 6 ports detected
Oct 29 08:44:39 node-2 kernel: [    3.202617] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 29 08:44:39 node-2 kernel: [    3.212144] serio: i8042 KBD port at 0x60,0x64 irq 1
Oct 29 08:44:39 node-2 kernel: [    3.219799] serio: i8042 AUX port at 0x60,0x64 irq 12
Oct 29 08:44:39 node-2 kernel: [    3.227556] mousedev: PS/2 mouse device common for all mice
Oct 29 08:44:39 node-2 kernel: [    3.235305] rtc_cmos 00:02: RTC can wake from S4
Oct 29 08:44:39 node-2 kernel: [    3.243084] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 29 08:44:39 node-2 kernel: [    3.250831] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 29 08:44:39 node-2 kernel: [    3.259459] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 29 08:44:39 node-2 kernel: [    3.259462] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 29 08:44:39 node-2 kernel: [    3.260489] hub 1-1:1.0: USB hub found
Oct 29 08:44:39 node-2 kernel: [    3.260830] hub 1-1:1.0: 6 ports detected
Oct 29 08:44:39 node-2 kernel: [    3.296728] device-mapper: uevent: version 1.0.3
Oct 29 08:44:39 node-2 kernel: [    3.304451] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 29 08:44:39 node-2 kernel: [    3.319569] ledtrig-cpu: registered to indicate activity on CPUs
Oct 29 08:44:39 node-2 kernel: [    3.327871] TCP: cubic registered
Oct 29 08:44:39 node-2 kernel: [    3.335950] NET: Registered protocol family 10
Oct 29 08:44:39 node-2 kernel: [    3.344192] NET: Registered protocol family 17
Oct 29 08:44:39 node-2 kernel: [    3.351636] Key type dns_resolver registered
Oct 29 08:44:39 node-2 kernel: [    3.360727] Loading compiled-in X.509 certificates
Oct 29 08:44:39 node-2 kernel: [    3.369484] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Oct 29 08:44:39 node-2 kernel: [    3.374560] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 29 08:44:39 node-2 kernel: [    3.391881] registered taskstats version 1
Oct 29 08:44:39 node-2 kernel: [    3.407862] Key type trusted registered
Oct 29 08:44:39 node-2 kernel: [    3.420914] Key type encrypted registered
Oct 29 08:44:39 node-2 kernel: [    3.428503] AppArmor: AppArmor sha1 policy hashing enabled
Oct 29 08:44:39 node-2 kernel: [    3.435817] IMA: No TPM chip found, activating TPM-bypass!
Oct 29 08:44:39 node-2 kernel: [    3.445445] regulator-dummy: disabling
Oct 29 08:44:39 node-2 kernel: [    3.452953]   Magic number: 4:735:726
Oct 29 08:44:39 node-2 kernel: [    3.460181] block loop6: hash matches
Oct 29 08:44:39 node-2 kernel: [    3.467495] pci 0000:01:00.1: hash matches
Oct 29 08:44:39 node-2 kernel: [    3.474963] memory memory444: hash matches
Oct 29 08:44:39 node-2 kernel: [    3.482416] rtc_cmos 00:02: setting system clock to 2016-10-29 08:42:26 UTC (1477730546)
Oct 29 08:44:39 node-2 kernel: [    3.497585] pcc-cpufreq: (v1.10.00) driver loaded with frequency limits: 1200 MHz, 2500 MHz
Oct 29 08:44:39 node-2 kernel: [    3.512556] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 29 08:44:39 node-2 kernel: [    3.520575] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 29 08:44:39 node-2 kernel: [    3.520576] EDD information not available.
Oct 29 08:44:39 node-2 kernel: [    3.520671] PM: Hibernation image not present or could not be loaded.
Oct 29 08:44:39 node-2 kernel: [    3.537644] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 29 08:44:39 node-2 kernel: [    3.545683] hub 2-1:1.0: USB hub found
Oct 29 08:44:39 node-2 kernel: [    3.546604] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 29 08:44:39 node-2 kernel: [    3.546605] Write protecting the kernel read-only data: 12288k
Oct 29 08:44:39 node-2 kernel: [    3.577170] hub 2-1:1.0: 8 ports detected
Oct 29 08:44:39 node-2 kernel: [    3.585311] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 29 08:44:39 node-2 kernel: [    3.602459] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 29 08:44:39 node-2 kernel: [    3.645977] device-mapper: multipath: version 1.6.0 loaded
Oct 29 08:44:39 node-2 kernel: [    3.656950] systemd-udevd[446]: starting version 204
Oct 29 08:44:39 node-2 kernel: [    3.696026] hpsa: module verification failed: signature and/or  required key missing - tainting kernel
Oct 29 08:44:39 node-2 kernel: [    3.705695] usb 4-3: new high-speed USB device number 2 using xhci_hcd
Oct 29 08:44:39 node-2 kernel: [    3.722610] HP HPSA Driver (v 3.4.12-110)
Oct 29 08:44:39 node-2 kernel: [    3.731303] usb 4-3: New USB device found, idVendor=0424, idProduct=2660
Oct 29 08:44:39 node-2 kernel: [    3.736383] hpsa 0000:07:00.0: MSI-X capable controller
Oct 29 08:44:39 node-2 kernel: [    3.737154] hpsa 0000:07:00.0: irq 116 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    3.737382] hpsa 0000:07:00.0: irq 117 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    3.737609] hpsa 0000:07:00.0: irq 118 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    3.737811] hpsa 0000:07:00.0: irq 119 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    3.737983] hpsa 0000:07:00.0: Using 4 reply queue(s)
Oct 29 08:44:39 node-2 kernel: [    3.738259] Physical aborts supported: yes
Oct 29 08:44:39 node-2 kernel: [    3.738259] Logical aborts supported: no
Oct 29 08:44:39 node-2 kernel: [    3.738259] HP SSD Smart Path aborts supported: yes
Oct 29 08:44:39 node-2 kernel: [    3.757277] hpsa 0000:07:00.0: hpsa0: <0x3239> at IRQ 116 using DAC
Oct 29 08:44:39 node-2 kernel: [    3.793091] usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 29 08:44:39 node-2 kernel: [    3.798144] hub 4-3:1.0: USB hub found
Oct 29 08:44:39 node-2 kernel: [    3.798997] hub 4-3:1.0: 2 ports detected
Oct 29 08:44:39 node-2 kernel: [    3.811314] pps_core: LinuxPPS API ver. 1 registered
Oct 29 08:44:39 node-2 kernel: [    3.811315] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Oct 29 08:44:39 node-2 kernel: [    3.820203] bnx2x: Broadcom NetXtreme II 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.78.17-0 (2013/04/11)
Oct 29 08:44:39 node-2 kernel: [    3.822444] bnx2x 0000:06:00.0: msix capability found
Oct 29 08:44:39 node-2 kernel: [    3.828416] bnx2x 0000:06:00.0: part number 0-0-0-0
Oct 29 08:44:39 node-2 kernel: [    3.834937] bft2_offset = 0x8f4
Oct 29 08:44:39 node-2 kernel: [    3.857622] scsi0 : hpsa
Oct 29 08:44:39 node-2 kernel: [    3.872932] PTP clock support registered
Oct 29 08:44:39 node-2 kernel: [    3.892577] hpsa 0000:07:00.0: added scsi 0:3:0:0: RAID              HP      P244br          RAID-UNKNOWN SSDSmartPathCap- En- Exp=4 qd=1024
Oct 29 08:44:39 node-2 kernel: [    3.892608] hpsa 0000:07:00.0: added scsi 0:2:0:0: Direct-Access     HP       EG0600JEMCV      RAID-UNKNOWN SSDSmartPathCap- En- Exp=2 qd=58
Oct 29 08:44:39 node-2 kernel: [    3.892618] hpsa 0000:07:00.0: added scsi 0:2:1:0: Direct-Access     HP       EG0600JEMCV      RAID-UNKNOWN SSDSmartPathCap- En- Exp=2 qd=58
Oct 29 08:44:39 node-2 kernel: [    3.892645] hpsa 0000:07:00.0: added scsi 0:0:0:0: Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=4 qd=1024
Oct 29 08:44:39 node-2 kernel: [    3.897911] scsi 0:3:0:0: RAID              HP       P244br           3.00 PQ: 0 ANSI: 5
Oct 29 08:44:39 node-2 kernel: [    3.900683] scsi 0:0:0:0: Direct-Access     HP       LOGICAL VOLUME   3.00 PQ: 0 ANSI: 5
Oct 29 08:44:39 node-2 kernel: [    3.908194] scsi 0:3:0:0: Attached scsi generic sg0 type 12
Oct 29 08:44:39 node-2 kernel: [    3.914585] dca service started, version 1.12.1
Oct 29 08:44:39 node-2 kernel: [    3.916426] sd 0:0:0:0: Attached scsi generic sg1 type 0
Oct 29 08:44:39 node-2 kernel: [    3.917444] sd 0:0:0:0: [sda] 2344114096 512-byte logical blocks: (1.20 TB/1.09 TiB)
Oct 29 08:44:39 node-2 kernel: [    3.921723] sd 0:0:0:0: [sda] Write Protect is off
Oct 29 08:44:39 node-2 kernel: [    3.921750] sd 0:0:0:0: [sda] Mode Sense: 73 00 00 08
Oct 29 08:44:39 node-2 kernel: [    3.923122] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Oct 29 08:44:39 node-2 kernel: [    3.955674]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Oct 29 08:44:39 node-2 kernel: [    3.964717] bnx2x 0000:06:00.0: irq 120 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    3.965010] bnx2x 0000:06:00.0: irq 121 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    3.965120] bnx2x 0000:06:00.0: irq 122 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    3.965271] bnx2x 0000:06:00.0: irq 123 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    3.965382] bnx2x 0000:06:00.0: irq 124 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    3.965642] bnx2x 0000:06:00.0: irq 125 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    3.965860] bnx2x 0000:06:00.0: irq 126 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    3.966074] bnx2x 0000:06:00.0: irq 127 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    3.966191] bnx2x 0000:06:00.0: irq 128 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    3.967128] bnx2x 0000:06:00.0: irq 129 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    3.988328] bnx2x 0000:06:00.1: msix capability found
Oct 29 08:44:39 node-2 kernel: [    3.990061] sd 0:0:0:0: [sda] Attached SCSI disk
Oct 29 08:44:39 node-2 kernel: [    3.993048] bnx2x 0000:06:00.1: part number 0-0-0-0
Oct 29 08:44:39 node-2 kernel: [    4.040302] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 3.15.1-k
Oct 29 08:44:39 node-2 kernel: [    4.040302] ixgbe: Copyright (c) 1999-2013 Intel Corporation.
Oct 29 08:44:39 node-2 kernel: [    4.112809] bnx2x 0000:06:00.1: irq 130 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.112876] bnx2x 0000:06:00.1: irq 131 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.113061] bnx2x 0000:06:00.1: irq 132 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.113170] bnx2x 0000:06:00.1: irq 133 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.113347] bnx2x 0000:06:00.1: irq 134 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.113455] bnx2x 0000:06:00.1: irq 135 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.113665] bnx2x 0000:06:00.1: irq 136 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.113815] bnx2x 0000:06:00.1: irq 137 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.113994] bnx2x 0000:06:00.1: irq 138 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.114143] bnx2x 0000:06:00.1: irq 139 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.144688] md: linear personality registered for level -1
Oct 29 08:44:39 node-2 kernel: [    4.155906] md: multipath personality registered for level -4
Oct 29 08:44:39 node-2 kernel: [    4.167234] md: raid0 personality registered for level 0
Oct 29 08:44:39 node-2 kernel: [    4.178715] md: raid1 personality registered for level 1
Oct 29 08:44:39 node-2 kernel: [    4.188694] Switched to clocksource tsc
Oct 29 08:44:39 node-2 kernel: [    4.188773] ixgbe 0000:08:00.0: irq 140 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.188830] ixgbe 0000:08:00.0: irq 141 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.188869] ixgbe 0000:08:00.0: irq 142 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.188911] ixgbe 0000:08:00.0: irq 143 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.188960] ixgbe 0000:08:00.0: irq 144 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189015] ixgbe 0000:08:00.0: irq 145 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189067] ixgbe 0000:08:00.0: irq 146 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189119] ixgbe 0000:08:00.0: irq 147 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189170] ixgbe 0000:08:00.0: irq 148 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189221] ixgbe 0000:08:00.0: irq 149 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189275] ixgbe 0000:08:00.0: irq 150 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189331] ixgbe 0000:08:00.0: irq 151 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189383] ixgbe 0000:08:00.0: irq 152 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189438] ixgbe 0000:08:00.0: irq 153 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189491] ixgbe 0000:08:00.0: irq 154 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189545] ixgbe 0000:08:00.0: irq 155 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189595] ixgbe 0000:08:00.0: irq 156 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189645] ixgbe 0000:08:00.0: irq 157 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189695] ixgbe 0000:08:00.0: irq 158 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189746] ixgbe 0000:08:00.0: irq 159 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189792] ixgbe 0000:08:00.0: irq 160 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189839] ixgbe 0000:08:00.0: irq 161 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189891] ixgbe 0000:08:00.0: irq 162 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189939] ixgbe 0000:08:00.0: irq 163 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.189990] ixgbe 0000:08:00.0: irq 164 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190044] ixgbe 0000:08:00.0: irq 165 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190092] ixgbe 0000:08:00.0: irq 166 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190140] ixgbe 0000:08:00.0: irq 167 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190188] ixgbe 0000:08:00.0: irq 168 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190243] ixgbe 0000:08:00.0: irq 169 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190292] ixgbe 0000:08:00.0: irq 170 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190341] ixgbe 0000:08:00.0: irq 171 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190392] ixgbe 0000:08:00.0: irq 172 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190442] ixgbe 0000:08:00.0: irq 173 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190490] ixgbe 0000:08:00.0: irq 174 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190538] ixgbe 0000:08:00.0: irq 175 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190585] ixgbe 0000:08:00.0: irq 176 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190634] ixgbe 0000:08:00.0: irq 177 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190682] ixgbe 0000:08:00.0: irq 178 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190731] ixgbe 0000:08:00.0: irq 179 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190781] ixgbe 0000:08:00.0: irq 180 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190827] ixgbe 0000:08:00.0: irq 181 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190868] ixgbe 0000:08:00.0: irq 182 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190900] ixgbe 0000:08:00.0: irq 183 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190927] ixgbe 0000:08:00.0: irq 184 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.190978] ixgbe 0000:08:00.0: irq 185 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.191020] ixgbe 0000:08:00.0: irq 186 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.191025] ixgbe 0000:08:00.0: irq 187 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.191058] ixgbe 0000:08:00.0: irq 188 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.191587] ixgbe 0000:08:00.0: Multiqueue Enabled: Rx Queue count = 48, Tx Queue count = 48
Oct 29 08:44:39 node-2 kernel: [    4.191741] ixgbe 0000:08:00.0: PCI Express bandwidth of 32GT/s available
Oct 29 08:44:39 node-2 kernel: [    4.191742] ixgbe 0000:08:00.0: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Oct 29 08:44:39 node-2 kernel: [    4.192145] ixgbe 0000:08:00.0: MAC: 2, PHY: 1, PBA No: G43498-012
Oct 29 08:44:39 node-2 kernel: [    4.192146] ixgbe 0000:08:00.0: 5c:b9:01:8b:a1:1c
Oct 29 08:44:39 node-2 kernel: [    4.236091] ixgbe 0000:08:00.0: Intel(R) 10 Gigabit Network Connection
Oct 29 08:44:39 node-2 kernel: [    4.322203] raid6: sse2x1    9322 MB/s
Oct 29 08:44:39 node-2 kernel: [    4.352328] ixgbe 0000:08:00.1: irq 189 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352336] ixgbe 0000:08:00.1: irq 190 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352342] ixgbe 0000:08:00.1: irq 191 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352347] ixgbe 0000:08:00.1: irq 192 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352353] ixgbe 0000:08:00.1: irq 193 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352358] ixgbe 0000:08:00.1: irq 194 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352363] ixgbe 0000:08:00.1: irq 195 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352368] ixgbe 0000:08:00.1: irq 196 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352373] ixgbe 0000:08:00.1: irq 197 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352378] ixgbe 0000:08:00.1: irq 198 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352383] ixgbe 0000:08:00.1: irq 199 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352388] ixgbe 0000:08:00.1: irq 200 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352393] ixgbe 0000:08:00.1: irq 201 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352399] ixgbe 0000:08:00.1: irq 202 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352406] ixgbe 0000:08:00.1: irq 203 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352411] ixgbe 0000:08:00.1: irq 204 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352416] ixgbe 0000:08:00.1: irq 205 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352421] ixgbe 0000:08:00.1: irq 206 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352426] ixgbe 0000:08:00.1: irq 207 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352432] ixgbe 0000:08:00.1: irq 208 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352437] ixgbe 0000:08:00.1: irq 209 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352443] ixgbe 0000:08:00.1: irq 210 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352448] ixgbe 0000:08:00.1: irq 211 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352453] ixgbe 0000:08:00.1: irq 212 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352458] ixgbe 0000:08:00.1: irq 213 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352464] ixgbe 0000:08:00.1: irq 214 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352469] ixgbe 0000:08:00.1: irq 215 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352474] ixgbe 0000:08:00.1: irq 216 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352479] ixgbe 0000:08:00.1: irq 217 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352486] ixgbe 0000:08:00.1: irq 218 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352493] ixgbe 0000:08:00.1: irq 219 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352498] ixgbe 0000:08:00.1: irq 220 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352503] ixgbe 0000:08:00.1: irq 221 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352511] ixgbe 0000:08:00.1: irq 222 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352516] ixgbe 0000:08:00.1: irq 223 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352521] ixgbe 0000:08:00.1: irq 224 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352527] ixgbe 0000:08:00.1: irq 225 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352532] ixgbe 0000:08:00.1: irq 226 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352537] ixgbe 0000:08:00.1: irq 227 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352542] ixgbe 0000:08:00.1: irq 228 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352547] ixgbe 0000:08:00.1: irq 229 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352552] ixgbe 0000:08:00.1: irq 230 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352557] ixgbe 0000:08:00.1: irq 231 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352562] ixgbe 0000:08:00.1: irq 232 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352567] ixgbe 0000:08:00.1: irq 233 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352573] ixgbe 0000:08:00.1: irq 234 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352579] ixgbe 0000:08:00.1: irq 235 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352584] ixgbe 0000:08:00.1: irq 236 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352590] ixgbe 0000:08:00.1: irq 237 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.352681] ixgbe 0000:08:00.1: Multiqueue Enabled: Rx Queue count = 48, Tx Queue count = 48
Oct 29 08:44:39 node-2 kernel: [    4.368760] ixgbe 0000:08:00.1: PCI Express bandwidth of 32GT/s available
Oct 29 08:44:39 node-2 kernel: [    4.377004] ixgbe 0000:08:00.1: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Oct 29 08:44:39 node-2 kernel: [    4.385683] ixgbe 0000:08:00.1: MAC: 2, PHY: 1, PBA No: G43498-012
Oct 29 08:44:39 node-2 kernel: [    4.393958] ixgbe 0000:08:00.1: 5c:b9:01:8b:a1:1d
Oct 29 08:44:39 node-2 kernel: [    4.394215] raid6: sse2x2    4541 MB/s
Oct 29 08:44:39 node-2 kernel: [    4.413158] random: lvm urandom read with 33 bits of entropy available
Oct 29 08:44:39 node-2 kernel: [    4.445092] ixgbe 0000:08:00.1: Intel(R) 10 Gigabit Network Connection
Oct 29 08:44:39 node-2 kernel: [    4.462169] raid6: sse2x4   10454 MB/s
Oct 29 08:44:39 node-2 kernel: [    4.538172] raid6: avx2x1   20491 MB/s
Oct 29 08:44:39 node-2 kernel: [    4.546414] ixgbe 0000:87:00.0: irq 238 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546420] ixgbe 0000:87:00.0: irq 239 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546436] ixgbe 0000:87:00.0: irq 240 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546445] ixgbe 0000:87:00.0: irq 241 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546449] ixgbe 0000:87:00.0: irq 242 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546454] ixgbe 0000:87:00.0: irq 243 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546458] ixgbe 0000:87:00.0: irq 244 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546463] ixgbe 0000:87:00.0: irq 245 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546468] ixgbe 0000:87:00.0: irq 246 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546472] ixgbe 0000:87:00.0: irq 247 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546477] ixgbe 0000:87:00.0: irq 248 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546481] ixgbe 0000:87:00.0: irq 249 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546485] ixgbe 0000:87:00.0: irq 250 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546490] ixgbe 0000:87:00.0: irq 251 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546494] ixgbe 0000:87:00.0: irq 252 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546498] ixgbe 0000:87:00.0: irq 253 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546503] ixgbe 0000:87:00.0: irq 254 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546507] ixgbe 0000:87:00.0: irq 255 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546512] ixgbe 0000:87:00.0: irq 256 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546521] ixgbe 0000:87:00.0: irq 257 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546525] ixgbe 0000:87:00.0: irq 258 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546530] ixgbe 0000:87:00.0: irq 259 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546534] ixgbe 0000:87:00.0: irq 260 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546538] ixgbe 0000:87:00.0: irq 261 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546543] ixgbe 0000:87:00.0: irq 262 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546547] ixgbe 0000:87:00.0: irq 263 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546556] ixgbe 0000:87:00.0: irq 264 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546560] ixgbe 0000:87:00.0: irq 265 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546564] ixgbe 0000:87:00.0: irq 266 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546569] ixgbe 0000:87:00.0: irq 267 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546573] ixgbe 0000:87:00.0: irq 268 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546577] ixgbe 0000:87:00.0: irq 269 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546582] ixgbe 0000:87:00.0: irq 270 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546586] ixgbe 0000:87:00.0: irq 271 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546591] ixgbe 0000:87:00.0: irq 272 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546597] ixgbe 0000:87:00.0: irq 273 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546601] ixgbe 0000:87:00.0: irq 274 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546606] ixgbe 0000:87:00.0: irq 275 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546610] ixgbe 0000:87:00.0: irq 276 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546614] ixgbe 0000:87:00.0: irq 277 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546619] ixgbe 0000:87:00.0: irq 278 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546628] ixgbe 0000:87:00.0: irq 279 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546637] ixgbe 0000:87:00.0: irq 280 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546646] ixgbe 0000:87:00.0: irq 281 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546655] ixgbe 0000:87:00.0: irq 282 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546664] ixgbe 0000:87:00.0: irq 283 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546673] ixgbe 0000:87:00.0: irq 284 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546682] ixgbe 0000:87:00.0: irq 285 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546691] ixgbe 0000:87:00.0: irq 286 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.546928] ixgbe 0000:87:00.0: Multiqueue Enabled: Rx Queue count = 48, Tx Queue count = 48
Oct 29 08:44:39 node-2 kernel: [    4.563270] ixgbe 0000:87:00.0: PCI Express bandwidth of 32GT/s available
Oct 29 08:44:39 node-2 kernel: [    4.571577] ixgbe 0000:87:00.0: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Oct 29 08:44:39 node-2 kernel: [    4.580146] ixgbe 0000:87:00.0: MAC: 2, PHY: 1, PBA No: G43498-012
Oct 29 08:44:39 node-2 kernel: [    4.588190] ixgbe 0000:87:00.0: 5c:b9:01:8b:a0:f0
Oct 29 08:44:39 node-2 kernel: [    4.614121] raid6: avx2x2   23431 MB/s
Oct 29 08:44:39 node-2 kernel: [    4.631650] ixgbe 0000:87:00.0: Intel(R) 10 Gigabit Network Connection
Oct 29 08:44:39 node-2 kernel: [    4.686131] raid6: avx2x4   27183 MB/s
Oct 29 08:44:39 node-2 kernel: [    4.694272] raid6: using algorithm avx2x4 (27183 MB/s)
Oct 29 08:44:39 node-2 kernel: [    4.702413] raid6: using avx2x2 recovery algorithm
Oct 29 08:44:39 node-2 kernel: [    4.711422] xor: automatically using best checksumming function:
Oct 29 08:44:39 node-2 kernel: [    4.712797] bio: create slab <bio-1> at 1
Oct 29 08:44:39 node-2 kernel: [    4.734281] ixgbe 0000:87:00.1: irq 287 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734292] ixgbe 0000:87:00.1: irq 288 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734302] ixgbe 0000:87:00.1: irq 289 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734311] ixgbe 0000:87:00.1: irq 290 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734321] ixgbe 0000:87:00.1: irq 291 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734330] ixgbe 0000:87:00.1: irq 292 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734339] ixgbe 0000:87:00.1: irq 293 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734348] ixgbe 0000:87:00.1: irq 294 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734357] ixgbe 0000:87:00.1: irq 295 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734366] ixgbe 0000:87:00.1: irq 296 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734375] ixgbe 0000:87:00.1: irq 297 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734384] ixgbe 0000:87:00.1: irq 298 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734393] ixgbe 0000:87:00.1: irq 299 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734401] ixgbe 0000:87:00.1: irq 300 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734412] ixgbe 0000:87:00.1: irq 301 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734421] ixgbe 0000:87:00.1: irq 302 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734430] ixgbe 0000:87:00.1: irq 303 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734439] ixgbe 0000:87:00.1: irq 304 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734448] ixgbe 0000:87:00.1: irq 305 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734457] ixgbe 0000:87:00.1: irq 306 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734466] ixgbe 0000:87:00.1: irq 307 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734476] ixgbe 0000:87:00.1: irq 308 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734485] ixgbe 0000:87:00.1: irq 309 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734494] ixgbe 0000:87:00.1: irq 310 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734502] ixgbe 0000:87:00.1: irq 311 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734511] ixgbe 0000:87:00.1: irq 312 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734520] ixgbe 0000:87:00.1: irq 313 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734529] ixgbe 0000:87:00.1: irq 314 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734538] ixgbe 0000:87:00.1: irq 315 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734550] ixgbe 0000:87:00.1: irq 316 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734562] ixgbe 0000:87:00.1: irq 317 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734570] ixgbe 0000:87:00.1: irq 318 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734580] ixgbe 0000:87:00.1: irq 319 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734592] ixgbe 0000:87:00.1: irq 320 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734604] ixgbe 0000:87:00.1: irq 321 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734613] ixgbe 0000:87:00.1: irq 322 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734622] ixgbe 0000:87:00.1: irq 323 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734631] ixgbe 0000:87:00.1: irq 324 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734640] ixgbe 0000:87:00.1: irq 325 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734649] ixgbe 0000:87:00.1: irq 326 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734658] ixgbe 0000:87:00.1: irq 327 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734667] ixgbe 0000:87:00.1: irq 328 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734676] ixgbe 0000:87:00.1: irq 329 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734685] ixgbe 0000:87:00.1: irq 330 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734694] ixgbe 0000:87:00.1: irq 331 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734703] ixgbe 0000:87:00.1: irq 332 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734712] ixgbe 0000:87:00.1: irq 333 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734721] ixgbe 0000:87:00.1: irq 334 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734730] ixgbe 0000:87:00.1: irq 335 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    4.734815] ixgbe 0000:87:00.1: Multiqueue Enabled: Rx Queue count = 48, Tx Queue count = 48
Oct 29 08:44:39 node-2 kernel: [    4.750933] ixgbe 0000:87:00.1: PCI Express bandwidth of 32GT/s available
Oct 29 08:44:39 node-2 kernel: [    4.759325] ixgbe 0000:87:00.1: (Speed:5.0GT/s, Width: x8, Encoding Loss:20%)
Oct 29 08:44:39 node-2 kernel: [    4.766110]    avx       : 28992.000 MB/sec
Oct 29 08:44:39 node-2 kernel: [    4.776406] ixgbe 0000:87:00.1: MAC: 2, PHY: 1, PBA No: G43498-012
Oct 29 08:44:39 node-2 kernel: [    4.784693] ixgbe 0000:87:00.1: 5c:b9:01:8b:a0:f1
Oct 29 08:44:39 node-2 kernel: [    4.792905] async_tx: api initialized (async)
Oct 29 08:44:39 node-2 kernel: [    4.805737] md: raid6 personality registered for level 6
Oct 29 08:44:39 node-2 kernel: [    4.813761] md: raid5 personality registered for level 5
Oct 29 08:44:39 node-2 kernel: [    4.821469] md: raid4 personality registered for level 4
Oct 29 08:44:39 node-2 kernel: [    4.828036] ixgbe 0000:87:00.1: Intel(R) 10 Gigabit Network Connection
Oct 29 08:44:39 node-2 kernel: [    4.841597] md: raid10 personality registered for level 10
Oct 29 08:44:39 node-2 kernel: [    4.907514] multipathd (715): /proc/715/oom_adj is deprecated, please use /proc/715/oom_score_adj instead.
Oct 29 08:44:39 node-2 kernel: [    5.686485] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 29 08:44:39 node-2 kernel: [    5.809994] random: nonblocking pool is initialized
Oct 29 08:44:39 node-2 kernel: [    6.168425] init: plymouth-upstart-bridge main process (879) terminated with status 1
Oct 29 08:44:39 node-2 kernel: [    6.184757] init: plymouth-upstart-bridge main process ended, respawning
Oct 29 08:44:39 node-2 kernel: [    6.197620] init: plymouth-upstart-bridge main process (890) terminated with status 1
Oct 29 08:44:39 node-2 kernel: [    6.214355] init: plymouth-upstart-bridge main process ended, respawning
Oct 29 08:44:39 node-2 kernel: [    6.311650] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct 29 08:44:39 node-2 kernel: [    6.322897] Adding 4194300k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:4194300k FS
Oct 29 08:44:39 node-2 kernel: [    6.366031] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 29 08:44:39 node-2 kernel: [    6.395278] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 29 08:44:39 node-2 kernel: [    6.545589] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 29 08:44:39 node-2 kernel: [    6.698337] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 29 08:44:39 node-2 kernel: [    6.744666] XFS (dm-0): Mounting Filesystem
Oct 29 08:44:39 node-2 kernel: [    6.986583] XFS (dm-0): Ending clean mount
Oct 29 08:44:39 node-2 kernel: [    7.055480] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct 29 08:44:39 node-2 kernel: [    7.093067] XFS (dm-1): Mounting Filesystem
Oct 29 08:44:39 node-2 kernel: [    7.318435] XFS (dm-1): Ending clean mount
Oct 29 08:44:39 node-2 kernel: [    8.701913] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 29 08:44:39 node-2 kernel: [    8.720107] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 29 08:44:39 node-2 kernel: [    8.859952] systemd-udevd[1107]: starting version 204
Oct 29 08:44:39 node-2 kernel: [    9.034433] wmi: Mapper loaded
Oct 29 08:44:39 node-2 kernel: [    9.035576] IPMI System Interface driver.
Oct 29 08:44:39 node-2 kernel: [    9.035630] ipmi_si: probing via ACPI
Oct 29 08:44:39 node-2 kernel: [    9.035652] ipmi_si 00:07: [io  0x0ca2-0x0ca3] regsize 1 spacing 1 irq 0
Oct 29 08:44:39 node-2 kernel: [    9.035654] ipmi_si: Adding ACPI-specified kcs state machine
Oct 29 08:44:39 node-2 kernel: [    9.035663] ipmi_si: probing via SMBIOS
Oct 29 08:44:39 node-2 kernel: [    9.035664] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 29 08:44:39 node-2 kernel: [    9.035665] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 29 08:44:39 node-2 kernel: [    9.035667] ipmi_si: probing via SPMI
Oct 29 08:44:39 node-2 kernel: [    9.035668] ipmi_si: SPMI: io 0xca3 regsize 1 spacing 1 irq 0
Oct 29 08:44:39 node-2 kernel: [    9.035669] ipmi_si: Adding SPMI-specified kcs state machine
Oct 29 08:44:39 node-2 kernel: [    9.035670] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 29 08:44:39 node-2 kernel: [    9.059730] power_meter ACPI000D:00: Found ACPI power meter.
Oct 29 08:44:39 node-2 kernel: [    9.059757] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 29 08:44:39 node-2 kernel: [    9.119239] ioatdma: Intel(R) QuickData Technology Driver 4.00
Oct 29 08:44:39 node-2 kernel: [    9.119309] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 29 08:44:39 node-2 kernel: [    9.119534] ioatdma 0000:00:04.0: irq 336 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    9.120097] ioatdma 0000:00:04.1: irq 337 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    9.120364] ioatdma 0000:00:04.2: irq 338 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    9.120631] ioatdma 0000:00:04.3: irq 339 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    9.120902] ioatdma 0000:00:04.4: irq 340 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    9.121172] ioatdma 0000:00:04.5: irq 341 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    9.121438] ioatdma 0000:00:04.6: irq 342 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    9.121699] ioatdma 0000:00:04.7: irq 343 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    9.122261] ioatdma 0000:80:04.0: irq 344 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    9.123721] ioatdma 0000:80:04.1: irq 345 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    9.124166] ioatdma 0000:80:04.2: irq 346 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    9.126522] ioatdma 0000:80:04.3: irq 347 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    9.126743] ioatdma 0000:80:04.4: irq 348 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    9.127295] ioatdma 0000:80:04.5: irq 349 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    9.127933] ioatdma 0000:80:04.6: irq 350 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    9.128484] ioatdma 0000:80:04.7: irq 351 for MSI/MSI-X
Oct 29 08:44:39 node-2 kernel: [    9.157438] systemd-udevd[1125]: renamed network interface eth0 to eno49
Oct 29 08:44:39 node-2 kernel: [    9.193458] systemd-udevd[1126]: renamed network interface eth1 to eno50
Oct 29 08:44:39 node-2 kernel: [    9.209439] systemd-udevd[1154]: renamed network interface eth5 to ens2f1
Oct 29 08:44:39 node-2 kernel: [    9.245430] systemd-udevd[1135]: renamed network interface eth3 to ens1f1
Oct 29 08:44:39 node-2 kernel: [    9.269495] systemd-udevd[1134]: renamed network interface eth2 to ens1f0
Oct 29 08:44:39 node-2 kernel: [    9.270515] ipmi_si 00:07: Found new BMC (man_id: 0x00000b, prod_id: 0x2020, dev_id: 0x13)
Oct 29 08:44:39 node-2 kernel: [    9.270528] ipmi_si 00:07: IPMI kcs interface initialized
Oct 29 08:44:39 node-2 kernel: [    9.293479] systemd-udevd[1152]: renamed network interface eth4 to ens2f0
Oct 29 08:44:39 node-2 kernel: [    9.579534] type=1400 audit(1477730552.595:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1467 comm="apparmor_parser"
Oct 29 08:44:39 node-2 kernel: [    9.579708] type=1400 audit(1477730552.595:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1467 comm="apparmor_parser"
Oct 29 08:44:39 node-2 kernel: [    9.579857] type=1400 audit(1477730552.595:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1467 comm="apparmor_parser"
Oct 29 08:44:39 node-2 kernel: [    9.579981] type=1400 audit(1477730552.595:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1478 comm="apparmor_parser"
Oct 29 08:44:39 node-2 kernel: [    9.580149] type=1400 audit(1477730552.595:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1478 comm="apparmor_parser"
Oct 29 08:44:39 node-2 kernel: [    9.580297] type=1400 audit(1477730552.595:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1478 comm="apparmor_parser"
Oct 29 08:44:39 node-2 kernel: [    9.581579] type=1400 audit(1477730552.599:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1497 comm="apparmor_parser"
Oct 29 08:44:39 node-2 kernel: [    9.581749] type=1400 audit(1477730552.599:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1497 comm="apparmor_parser"
Oct 29 08:44:39 node-2 kernel: [    9.581924] type=1400 audit(1477730552.599:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1497 comm="apparmor_parser"
Oct 29 08:44:39 node-2 kernel: [    9.581961] type=1400 audit(1477730552.599:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1468 comm="apparmor_parser"
Oct 29 08:44:39 node-2 kernel: [   10.215859] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 29 08:44:39 node-2 kernel: [   10.216279] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 29 08:44:39 node-2 kernel: [   10.918392] bnx2x 0000:06:00.0 eno49: using MSI-X  IRQs: sp 120  fp[0] 122 ... fp[7] 129
Oct 29 08:44:39 node-2 kernel: [   11.065098] IPv6: ADDRCONF(NETDEV_UP): eno49: link is not ready
Oct 29 08:44:39 node-2 kernel: [   13.148666] bnx2x 0000:06:00.0 eno49: NIC Link is Up, 10000 Mbps full duplex, Flow control: ON - receive & transmit
Oct 29 08:44:39 node-2 kernel: [   13.148687] IPv6: ADDRCONF(NETDEV_CHANGE): eno49: link becomes ready
Oct 29 08:44:39 node-2 kernel: [   18.869577] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 29 08:44:40 node-2 failsafe: Failsafe of 120 seconds reached.
Oct 29 08:44:40 node-2 kernel: [  138.205189] init: failsafe main process (8853) killed by TERM signal
Oct 29 08:44:40 node-2 dbus[8886]: [system] AppArmor D-Bus mediation is enabled
Oct 29 08:44:40 node-2 kernel: [  138.333195] audit_printk_skb: 54 callbacks suppressed
Oct 29 08:44:40 node-2 kernel: [  138.333197] type=1400 audit(1477730680.965:30): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8978 comm="apparmor_parser"
Oct 29 08:44:40 node-2 kernel: [  138.336511] type=1400 audit(1477730680.965:31): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8977 comm="apparmor_parser"
Oct 29 08:44:40 node-2 kernel: [  138.336623] type=1400 audit(1477730680.965:32): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8977 comm="apparmor_parser"
Oct 29 08:44:40 node-2 kernel: [  138.336661] type=1400 audit(1477730680.965:33): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8977 comm="apparmor_parser"
Oct 29 08:44:40 node-2 kernel: [  138.338558] type=1400 audit(1477730680.969:34): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8977 comm="apparmor_parser"
Oct 29 08:44:40 node-2 kernel: [  138.338560] type=1400 audit(1477730680.969:35): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8977 comm="apparmor_parser"
Oct 29 08:44:40 node-2 kernel: [  138.338703] type=1400 audit(1477730680.969:36): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8977 comm="apparmor_parser"
Oct 29 08:44:41 node-2 kernel: [  138.413880] type=1400 audit(1477730681.045:37): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8980 comm="apparmor_parser"
Oct 29 08:44:41 node-2 cron[9012]: (CRON) INFO (pidfile fd = 3)
Oct 29 08:44:41 node-2 cron[9050]: (CRON) STARTUP (fork ok)
Oct 29 08:44:41 node-2 anacron[9049]: Anacron 2.3 started on 2016-10-29
Oct 29 08:44:41 node-2 anacron[9049]: Will run job `cron.daily' in 5 min.
Oct 29 08:44:41 node-2 anacron[9049]: Will run job `cron.weekly' in 10 min.
Oct 29 08:44:41 node-2 anacron[9049]: Will run job `cron.monthly' in 15 min.
Oct 29 08:44:41 node-2 anacron[9049]: Jobs will be executed sequentially
Oct 29 08:44:41 node-2 cron[9050]: (CRON) INFO (Running @reboot jobs)
Oct 29 08:44:41 node-2 multipathd: path checkers start up
Oct 29 08:44:41 node-2 postfix/master[9191]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 29 08:44:59 node-2 puppet-agent[9495]: Reopening log files
Oct 29 08:45:00 node-2 puppet-agent[9495]: Could not request certificate: Connection refused - connect(2)
Oct 29 08:45:01 node-2 CRON[9535]: (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")
Oct 29 08:45:14 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 08:45:14 node-2 nailgun-agent: D, [2016-10-29T08:45:01.442126 #9538] DEBUG -- : Sleep for 13 seconds before sending request
Oct 29 08:45:14 node-2 nailgun-agent: I, [2016-10-29T08:45:14.458870 #9538]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 29 08:45:29 node-2 nailgun-agent: D, [2016-10-29T08:45:29.919247 #9538] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Oct 29 08:45:37 node-2 puppet-user[9585]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 29 08:45:37 node-2 puppet-user[9585]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.03 seconds
Oct 29 08:45:38 node-2 puppet-user[9585]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 29 08:45:38 node-2 puppet-user[9585]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 29 08:45:38 node-2 puppet-user[9585]: Finished catalog run in 0.97 seconds
Oct 29 08:45:43 node-2 kernel: [  200.828473] init: plymouth-upstart-bridge main process ended, respawning
Oct 29 08:45:43 node-2 puppet-agent[9495]: Could not run: SIGTERM
Oct 29 08:45:43 node-2 kernel: [  201.179084] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 29 08:45:43 node-2 ec2: 
Oct 29 08:45:43 node-2 ec2: #############################################################
Oct 29 08:45:43 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 29 08:45:43 node-2 ec2: 1024 2c:90:39:0b:69:2b:eb:bf:86:51:e4:c2:ff:95:6a:55  root@node-2.opnfvericsson.se (DSA)
Oct 29 08:45:43 node-2 ec2: 256 0d:66:46:a0:e0:32:96:dc:65:b9:9c:79:c9:0e:64:43  root@node-2.opnfvericsson.se (ECDSA)
Oct 29 08:45:43 node-2 ec2: 256 a8:94:ff:a0:26:4c:b1:bf:1b:d8:e0:a2:ee:5b:8e:77  root@node-2.opnfvericsson.se (ED25519)
Oct 29 08:45:43 node-2 ec2: 2048 84:d2:ce:8e:22:07:bd:73:ee:e6:ea:dc:14:82:04:1c  root@node-2.opnfvericsson.se (RSA)
Oct 29 08:45:43 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 29 08:45:43 node-2 ec2: #############################################################
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.543973 #9538] DEBUG -- : Trying to find block devices
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.544196 #9538] DEBUG -- : Found block device: sda
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.544294 #9538] DEBUG -- : Block device info: {"size"=>"2344114096", "removable"=>"0", "model"=>"LOGICAL VOLUME", "rev"=>"3.00", "state"=>"running", "timeout"=>"30", "vendor"=>"HP"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.544357 #9538] DEBUG -- : Trying to get list of physical devices
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.544675 #9538] DEBUG -- : Getting udev properties for device: sda
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.549146 #9538] 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
Oct 29 08:45:52 node-2 nailgun-agent: AJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"40482", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.549223 #9538] DEBUG -- : Trying to find out if device sda is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.549340 #9538] DEBUG -- : Device sda removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.549385 #9538] DEBUG -- : Device sda seems to be appropriate
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.550381 #9538] DEBUG -- : Getting udev properties for device: dm-0
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.554469 #9538] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-JBWxpr8O135MaLfta6IYNPmFkQ2VH1Jikygl2odg8n9Dygjw1IdN0KH4D9XOlIvq /dev/disk/by-uuid/2ab125fc-e082-456a-b581-661c1ff8af3e /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-JBWxpr8O135MaLfta6IYNPmFkQ2VH1Jikygl2odg8n9Dygjw1IdN0KH4D9XOlIvq", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2ab125fc-e082-456a-b581-661c1ff8af3e", "ID_FS_UUID_ENC"=>"2ab125fc-e082-456a-b581-661c1ff8af3e", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81755", "nomdmonddf"=>"1", "nomd
Oct 29 08:45:52 node-2 nailgun-agent: monisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.554543 #9538] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.554635 #9538] DEBUG -- : Device dm-0 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.554677 #9538] DEBUG -- : Device dm-0 seems to be appropriate
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.554722 #9538] DEBUG -- : Getting udev properties for device: dm-1
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.558635 #9538] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-5JrCYhyXgdVvg2Faxlrygqo0HIAwsAnB9qE4xaa75kScHhLH6PsPZHcq2ytgzr3v /dev/disk/by-uuid/11cf1734-6823-444d-9087-e055a389f877 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-5JrCYhyXgdVvg2Faxlrygqo0HIAwsAnB9qE4xaa75kScHhLH6PsPZHcq2ytgzr3v", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"11cf1734-6823-444d-9087-e055a389f877", "ID_FS_UUID_ENC"=>"11cf1734-6823-444d-9087-e055a389f877", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15
Oct 29 08:45:52 node-2 nailgun-agent: 660", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.558714 #9538] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.558832 #9538] DEBUG -- : Device dm-1 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.558881 #9538] DEBUG -- : Device dm-1 seems to be appropriate
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.558924 #9538] DEBUG -- : Getting udev properties for device: dm-2
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.562808 #9538] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-ARHvJgBJcFqTM3vdfXRQY933Nscs8xihpCmhOQ09ultSerPx80lNt8Mr8OfryijD /dev/disk/by-uuid/19556e4d-e0f6-4a9b-8050-6d6fe16f45cd /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-ARHvJgBJcFqTM3vdfXRQY933Nscs8xihpCmhOQ09ultSerPx80lNt8Mr8OfryijD", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"19556e4d-e0f6-4a9b-8050-6d6fe16f45cd", "ID_FS_UUID_ENC"=>"19556e4d-e0f6-4a9b-8050-6d6fe16f45cd", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3504", "nomdmondd
Oct 29 08:45:52 node-2 nailgun-agent: f"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.562888 #9538] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.562980 #9538] DEBUG -- : Device dm-2 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.563021 #9538] DEBUG -- : Device dm-2 seems to be appropriate
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.563062 #9538] DEBUG -- : Getting udev properties for device: dm-3
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.567032 #9538] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-BrIRVKAkTOxfMFs53jDJizBsZjYK5nnfay82yzDvLjFgnhnZlEUszwxO9WEg0ziO /dev/disk/by-uuid/1da0781f-535b-499f-b109-0a2bdbcc1ebb /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-BrIRVKAkTOxfMFs53jDJizBsZjYK5nnfay82yzDvLjFgnhnZlEUszwxO9WEg0ziO", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"1da0781f-535b-499f-b109-0a2bdbcc1ebb", "ID_FS_UUID_ENC"=>"1da0781f-535b-499f-b109-0a2bdbcc1ebb", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2453", "nomdmonddf"=>"1", "
Oct 29 08:45:52 node-2 nailgun-agent: nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.567109 #9538] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.567202 #9538] DEBUG -- : Device dm-3 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.567247 #9538] DEBUG -- : Device dm-3 seems to be appropriate
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.567286 #9538] DEBUG -- : Getting udev properties for device: dm-4
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.571489 #9538] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-F29vAhSPiphkBO1v376y4FcGKTGvymQqnDNwC3TdWUrP1ktwpF01c8M3hxf7YHpP /dev/disk/by-uuid/ff37ac73-7ac9-4aca-9a48-3984eed9d826 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-F29vAhSPiphkBO1v376y4FcGKTGvymQqnDNwC3TdWUrP1ktwpF01c8M3hxf7YHpP", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ff37ac73-7ac9-4aca-9a48-3984eed9d826", "ID_FS_UUID_ENC"=>"ff37ac73-7ac9-4aca-9a48-3984eed9d826", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18372", "nomdmonddf"=>"1", "nomd
Oct 29 08:45:52 node-2 nailgun-agent: monisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.571565 #9538] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.571658 #9538] DEBUG -- : Device dm-4 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.571702 #9538] DEBUG -- : Device dm-4 seems to be appropriate
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.571743 #9538] DEBUG -- : Getting udev properties for device: dm-5
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.575512 #9538] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-F29vAhSPiphkBO1v376y4FcGKTGvymQqhoFmPBrIPKi0VktCReLRKM55iDYDQJVV /dev/disk/by-uuid/2d2590ee-7e23-41f4-ad0f-c2d5a6d587a7 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-F29vAhSPiphkBO1v376y4FcGKTGvymQqhoFmPBrIPKi0VktCReLRKM55iDYDQJVV", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"2d2590ee-7e23-41f4-ad0f-c2d5a6d587a7", "ID_FS_UUID_ENC"=>"2d2590ee-7e23-41f4-ad0f-c2d5a6d587a7", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"19039", "nomdmonddf"=>"1", "nomdmonisw"
Oct 29 08:45:52 node-2 nailgun-agent: =>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.575586 #9538] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.575678 #9538] DEBUG -- : Device dm-5 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.575721 #9538] DEBUG -- : Device dm-5 seems to be appropriate
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.575761 #9538] DEBUG -- : Getting udev properties for device: ram0
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.579311 #9538] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28576", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.579392 #9538] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.579487 #9538] DEBUG -- : Device ram0 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.579543 #9538] DEBUG -- : Getting udev properties for device: ram1
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.583405 #9538] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28584", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.583479 #9538] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.583569 #9538] DEBUG -- : Device ram1 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.583625 #9538] DEBUG -- : Getting udev properties for device: ram2
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.587179 #9538] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28649", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.587255 #9538] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.587347 #9538] DEBUG -- : Device ram2 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.587401 #9538] DEBUG -- : Getting udev properties for device: ram3
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.590561 #9538] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28657", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.590640 #9538] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.590733 #9538] DEBUG -- : Device ram3 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.590816 #9538] DEBUG -- : Getting udev properties for device: ram4
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.594727 #9538] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28668", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.595063 #9538] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.595165 #9538] DEBUG -- : Device ram4 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.595217 #9538] DEBUG -- : Getting udev properties for device: ram5
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.598712 #9538] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28694", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.598804 #9538] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.598903 #9538] DEBUG -- : Device ram5 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.598959 #9538] DEBUG -- : Getting udev properties for device: ram6
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.602483 #9538] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28706", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.602558 #9538] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.602648 #9538] DEBUG -- : Device ram6 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.602704 #9538] DEBUG -- : Getting udev properties for device: ram7
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.607286 #9538] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28716", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.607345 #9538] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.607410 #9538] DEBUG -- : Device ram7 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.607453 #9538] DEBUG -- : Getting udev properties for device: ram8
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.611174 #9538] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28729", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.611221 #9538] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.611279 #9538] DEBUG -- : Device ram8 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.611317 #9538] DEBUG -- : Getting udev properties for device: ram9
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.615833 #9538] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"4028741", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.615914 #9538] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.616010 #9538] DEBUG -- : Device ram9 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.616070 #9538] DEBUG -- : Getting udev properties for device: loop0
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.620377 #9538] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28501", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.620454 #9538] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.620549 #9538] DEBUG -- : Device loop0 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.620607 #9538] DEBUG -- : Getting udev properties for device: loop1
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.624910 #9538] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28512", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.624989 #9538] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.625084 #9538] DEBUG -- : Device loop1 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.625143 #9538] DEBUG -- : Getting udev properties for device: loop2
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.629569 #9538] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28521", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.629646 #9538] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.629747 #9538] DEBUG -- : Device loop2 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.629805 #9538] DEBUG -- : Getting udev properties for device: loop3
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.633822 #9538] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28531", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.633900 #9538] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.633996 #9538] DEBUG -- : Device loop3 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.634056 #9538] DEBUG -- : Getting udev properties for device: loop4
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.638090 #9538] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28539", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.638172 #9538] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.638268 #9538] DEBUG -- : Device loop4 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.638325 #9538] DEBUG -- : Getting udev properties for device: loop5
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.642338 #9538] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28548", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.642416 #9538] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.642510 #9538] DEBUG -- : Device loop5 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.642565 #9538] DEBUG -- : Getting udev properties for device: loop6
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.646557 #9538] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28557", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.646633 #9538] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.646727 #9538] DEBUG -- : Device loop6 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.646796 #9538] DEBUG -- : Getting udev properties for device: loop7
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.651356 #9538] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28567", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.651431 #9538] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.651522 #9538] DEBUG -- : Device loop7 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.651575 #9538] DEBUG -- : Getting udev properties for device: ram10
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.655219 #9538] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28593", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.655295 #9538] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.655384 #9538] DEBUG -- : Device ram10 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.655438 #9538] DEBUG -- : Getting udev properties for device: ram11
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.659089 #9538] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28602", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.659165 #9538] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.659258 #9538] DEBUG -- : Device ram11 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.659312 #9538] DEBUG -- : Getting udev properties for device: ram12
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.663023 #9538] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28613", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.663101 #9538] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.663198 #9538] DEBUG -- : Device ram12 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.663254 #9538] DEBUG -- : Getting udev properties for device: ram13
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.667014 #9538] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28622", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.667092 #9538] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.667185 #9538] DEBUG -- : Device ram13 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.667241 #9538] DEBUG -- : Getting udev properties for device: ram14
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.670881 #9538] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28631", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.670960 #9538] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.671054 #9538] DEBUG -- : Device ram14 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.671109 #9538] DEBUG -- : Getting udev properties for device: ram15
Oct 29 08:45:52 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.674723 #9538] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28640", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.674814 #9538] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.674913 #9538] DEBUG -- : Device ram15 removable parameter: "0"
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675016 #9538] 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"}]
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675057 #9538] DEBUG -- : Block device seems to be physical data storage: sda
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675148 #9538] DEBUG -- : Found block device: dm-0
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675191 #9538] DEBUG -- : Block device info: {"size"=>"2143207424", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675230 #9538] DEBUG -- : Found block device: dm-1
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675265 #9538] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675293 #9538] DEBUG -- : Found block device: dm-2
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675330 #9538] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675359 #9538] DEBUG -- : Found block device: dm-3
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675392 #9538] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675420 #9538] DEBUG -- : Found block device: dm-4
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675452 #9538] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675483 #9538] DEBUG -- : Found block device: dm-5
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675514 #9538] DEBUG -- : Block device info: {"size"=>"8388608", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675541 #9538] DEBUG -- : Found block device: ram0
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675572 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675600 #9538] DEBUG -- : Found block device: ram1
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675632 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675659 #9538] DEBUG -- : Found block device: ram2
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675691 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675717 #9538] DEBUG -- : Found block device: ram3
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675750 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675776 #9538] DEBUG -- : Found block device: ram4
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675810 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675837 #9538] DEBUG -- : Found block device: ram5
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675866 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675891 #9538] DEBUG -- : Found block device: ram6
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675922 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675947 #9538] DEBUG -- : Found block device: ram7
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.675980 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676006 #9538] DEBUG -- : Found block device: ram8
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676034 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676063 #9538] DEBUG -- : Found block device: ram9
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676092 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676122 #9538] DEBUG -- : Found block device: loop0
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676152 #9538] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676183 #9538] DEBUG -- : Found block device: loop1
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676221 #9538] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676248 #9538] DEBUG -- : Found block device: loop2
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676278 #9538] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676309 #9538] DEBUG -- : Found block device: loop3
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676340 #9538] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676368 #9538] DEBUG -- : Found block device: loop4
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676398 #9538] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676427 #9538] DEBUG -- : Found block device: loop5
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676457 #9538] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676484 #9538] DEBUG -- : Found block device: loop6
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676517 #9538] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676543 #9538] DEBUG -- : Found block device: loop7
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676572 #9538] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676601 #9538] DEBUG -- : Found block device: ram10
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676634 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676664 #9538] DEBUG -- : Found block device: ram11
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676694 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676719 #9538] DEBUG -- : Found block device: ram12
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676751 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676783 #9538] DEBUG -- : Found block device: ram13
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676813 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676841 #9538] DEBUG -- : Found block device: ram14
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676870 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676897 #9538] DEBUG -- : Found block device: ram15
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.676927 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.677009 #9538] 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}]
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.794394 #9538] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Oct 29 08:45:52 node-2 nailgun-agent: D, [2016-10-29T08:45:52.794493 #9538] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct 29 08:46:01 node-2 CRON[12764]: (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")
Oct 29 08:46:10 node-2 multipathd: uevent trigger error
Oct 29 08:46:10 node-2 puppet-user[11648]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 29 08:46:10 node-2 puppet-user[11648]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.10 seconds
Oct 29 08:46:10 node-2 puppet-user[11648]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 29 08:46:10 node-2 puppet-user[11648]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 29 08:46:10 node-2 puppet-user[11648]: (/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"]'
Oct 29 08:46:10 node-2 puppet-user[11648]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 29 08:46:10 node-2 puppet-user[11648]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 29 08:46:10 node-2 puppet-user[11648]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 29 08:46:10 node-2 puppet-user[11648]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 29 08:46:10 node-2 puppet-user[11648]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 29 08:46:10 node-2 puppet-user[11648]: Finished catalog run in 0.03 seconds
Oct 29 08:46:15 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.081280 #9538] DEBUG -- : Trying to find block devices
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.081531 #9538] DEBUG -- : Found block device: sda
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.081612 #9538] DEBUG -- : Block device info: {"size"=>"2344114096", "removable"=>"0", "model"=>"LOGICAL VOLUME", "rev"=>"3.00", "state"=>"running", "timeout"=>"30", "vendor"=>"HP"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.081664 #9538] DEBUG -- : Block device seems to be physical data storage: sda
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.081723 #9538] DEBUG -- : Found block device: dm-0
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.081763 #9538] DEBUG -- : Block device info: {"size"=>"2143207424", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.081800 #9538] DEBUG -- : Found block device: dm-1
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.081830 #9538] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.081859 #9538] DEBUG -- : Found block device: dm-2
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.081892 #9538] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.081925 #9538] DEBUG -- : Found block device: dm-3
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.081958 #9538] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.081986 #9538] DEBUG -- : Found block device: dm-4
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082016 #9538] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082045 #9538] DEBUG -- : Found block device: dm-5
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082074 #9538] DEBUG -- : Block device info: {"size"=>"8388608", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082103 #9538] DEBUG -- : Found block device: ram0
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082135 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082163 #9538] DEBUG -- : Found block device: ram1
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082193 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082219 #9538] DEBUG -- : Found block device: ram2
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082249 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082276 #9538] DEBUG -- : Found block device: ram3
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082302 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082329 #9538] DEBUG -- : Found block device: ram4
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082362 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082392 #9538] DEBUG -- : Found block device: ram5
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082423 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082449 #9538] DEBUG -- : Found block device: ram6
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082480 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082509 #9538] DEBUG -- : Found block device: ram7
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082537 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082565 #9538] DEBUG -- : Found block device: ram8
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082592 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082618 #9538] DEBUG -- : Found block device: ram9
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082650 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082681 #9538] DEBUG -- : Found block device: loop0
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082711 #9538] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082738 #9538] DEBUG -- : Found block device: loop1
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082797 #9538] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082840 #9538] DEBUG -- : Found block device: loop2
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082869 #9538] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082899 #9538] DEBUG -- : Found block device: loop3
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082929 #9538] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082960 #9538] DEBUG -- : Found block device: loop4
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.082992 #9538] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083021 #9538] DEBUG -- : Found block device: loop5
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083052 #9538] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083077 #9538] DEBUG -- : Found block device: loop6
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083112 #9538] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083140 #9538] DEBUG -- : Found block device: loop7
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083168 #9538] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083194 #9538] DEBUG -- : Found block device: ram10
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083223 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083251 #9538] DEBUG -- : Found block device: ram11
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083286 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083312 #9538] DEBUG -- : Found block device: ram12
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083345 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083373 #9538] DEBUG -- : Found block device: ram13
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083404 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083434 #9538] DEBUG -- : Found block device: ram14
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083464 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083491 #9538] DEBUG -- : Found block device: ram15
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083517 #9538] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.083598 #9538] 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}]
Oct 29 08:46:15 node-2 nailgun-agent: D, [2016-10-29T08:46:15.279002 #9538] DEBUG -- : Response: status: 200 body: {"id": 2}
Oct 29 08:46:15 node-2 nailgun-agent: I, [2016-10-29T08:46:15.279389 #9538]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Oct 29 08:46:43 node-2 puppet-user[13489]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 29 08:46:43 node-2 puppet-user[13489]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.10 seconds
Oct 29 08:46:43 node-2 puppet-user[13489]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 29 08:46:43 node-2 puppet-user[13489]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 29 08:46:43 node-2 puppet-user[13489]: Finished catalog run in 0.02 seconds
Oct 29 08:47:01 node-2 CRON[15317]: (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")
Oct 29 08:47:12 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 08:47:12 node-2 nailgun-agent: I, [2016-10-29T08:47:12.509462 #15320]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 29 08:47:16 node-2 puppet-user[14923]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 29 08:47:16 node-2 puppet-user[14923]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.04 seconds
Oct 29 08:47:16 node-2 puppet-user[14923]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 29 08:47:16 node-2 puppet-user[14923]: Finished catalog run in 0.03 seconds
Oct 29 08:47:48 node-2 puppet-user[16217]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 29 08:47:49 node-2 puppet-user[16217]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.18 seconds
Oct 29 08:47:49 node-2 puppet-user[16217]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 29 08:47:50 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 08:47:50 node-2 nailgun-agent: I, [2016-10-29T08:47:50.491115 #15320]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Oct 29 08:47:51 node-2 puppet-user[16217]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Oct 29 08:47:51 node-2 puppet-user[16217]: Finished catalog run in 2.23 seconds
Oct 29 08:48:01 node-2 CRON[18127]: (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")
Oct 29 08:48:18 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 08:48:18 node-2 nailgun-agent: I, [2016-10-29T08:48:18.711611 #18130]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 29 08:48:23 node-2 puppet-user[17917]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 29 08:48:24 node-2 puppet-user[17917]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.28 seconds
Oct 29 08:48:24 node-2 puppet-user[17917]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 29 08:48:24 node-2 puppet-user[17917]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Oct 29 08:48:24 node-2 puppet-user[17917]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 29 08:48:24 node-2 puppet-user[17917]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 29 08:48:24 node-2 puppet-user[17917]: Finished catalog run in 0.12 seconds
Oct 29 08:48:56 node-2 puppet-user[19222]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 29 08:48:56 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 08:48:56 node-2 puppet-user[19222]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.19 seconds
Oct 29 08:48:56 node-2 nailgun-agent: I, [2016-10-29T08:48:56.938741 #18130]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Oct 29 08:48:57 node-2 puppet-user[19222]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 29 08:48:57 node-2 kernel: [  394.456295] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 29 08:48:57 node-2 kernel: [  394.456367] 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.
Oct 29 08:48:57 node-2 puppet-user[19222]: (/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'
Oct 29 08:48:57 node-2 puppet-user[19222]: Finished catalog run in 0.12 seconds
Oct 29 08:49:01 node-2 CRON[20863]: (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")
Oct 29 08:49:05 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 08:49:05 node-2 nailgun-agent: I, [2016-10-29T08:49:05.130695 #20866]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 29 08:49:30 node-2 puppet-user[20803]: (Scope(Class[main])) MODULAR: sync_time
Oct 29 08:49:30 node-2 puppet-user[20803]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.04 seconds
Oct 29 08:49:31 node-2 ntpdate[22149]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 29 08:49:37 node-2 ntpdate[22149]: adjust time server 10.20.0.2 offset 0.000994 sec
Oct 29 08:49:37 node-2 puppet-user[20803]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 29 08:49:37 node-2 puppet-user[20803]: Finished catalog run in 6.15 seconds
Oct 29 08:49:41 node-2 anacron[9049]: Job `cron.daily' started
Oct 29 08:49:41 node-2 anacron[22376]: Updated timestamp for job `cron.daily' to 2016-10-29
Oct 29 08:49:42 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 08:49:43 node-2 nailgun-agent: I, [2016-10-29T08:49:42.995354 #20866]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Oct 29 08:49:43 node-2 anacron[9049]: Job `cron.daily' terminated
Oct 29 08:50:01 node-2 CRON[23592]: (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")
Oct 29 08:50:10 node-2 puppet-user[22308]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 29 08:50:10 node-2 puppet-user[22308]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.10 seconds
Oct 29 08:50:10 node-2 puppet-user[22308]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 29 08:50:10 node-2 puppet-user[22308]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Oct 29 08:50:10 node-2 puppet-user[22308]: Finished catalog run in 0.06 seconds
Oct 29 08:50:13 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 08:50:13 node-2 nailgun-agent: I, [2016-10-29T08:50:13.216245 #23595]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 29 08:50:42 node-2 puppet-user[24323]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 29 08:50:43 node-2 puppet-user[24323]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.55 seconds
Oct 29 08:50:43 node-2 puppet-user[24323]: (/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
Oct 29 08:50:43 node-2 puppet-user[24323]: (/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
Oct 29 08:50:43 node-2 puppet-user[24323]: (/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
Oct 29 08:50:43 node-2 puppet-user[24323]: (/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
Oct 29 08:50:43 node-2 puppet-user[24323]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct 29 08:50:43 node-2 puppet-user[24323]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Oct 29 08:50:43 node-2 puppet-user[24323]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct 29 08:50:43 node-2 puppet-user[24323]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Oct 29 08:50:43 node-2 puppet-user[24323]: (/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
Oct 29 08:50:43 node-2 puppet-user[24323]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Oct 29 08:50:44 node-2 puppet-user[24323]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 29 08:50:44 node-2 puppet-user[24323]: Finished catalog run in 0.63 seconds
Oct 29 08:50:51 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 08:50:51 node-2 nailgun-agent: I, [2016-10-29T08:50:51.343489 #23595]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Oct 29 08:51:01 node-2 CRON[26329]: (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")
Oct 29 08:51:16 node-2 puppet-user[25712]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 29 08:51:16 node-2 puppet-user[25712]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.15 seconds
Oct 29 08:51:18 node-2 puppet-user[25712]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 29 08:51:20 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 08:51:20 node-2 nailgun-agent: I, [2016-10-29T08:51:20.539879 #26332]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 29 08:51:25 node-2 puppet-user[25712]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 29 08:51:25 node-2 puppet-user[25712]: Finished catalog run in 8.23 seconds
Oct 29 08:51:57 node-2 puppet-user[28479]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 29 08:51:58 node-2 puppet-user[28479]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.57 seconds
Oct 29 08:51:58 node-2 puppet-user[28479]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 29 08:51:58 node-2 puppet-user[28479]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 29 08:51:58 node-2 puppet-user[28479]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 29 08:51:58 node-2 puppet-user[28479]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 29 08:51:58 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 08:51:58 node-2 puppet-user[28479]: Finished catalog run in 0.05 seconds
Oct 29 08:51:58 node-2 nailgun-agent: I, [2016-10-29T08:51:58.805646 #26332]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Oct 29 08:52:01 node-2 CRON[30176]: (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")
Oct 29 08:52:30 node-2 puppet-user[30106]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 29 08:52:31 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 08:52:31 node-2 nailgun-agent: I, [2016-10-29T08:52:31.017215 #30179]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 29 08:52:31 node-2 puppet-user[30106]: Compiled catalog for node-2.opnfvericsson.se in environment production in 0.80 seconds
Oct 29 08:52:31 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 29 08:52:31 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 29 08:52:31 node-2 crontab[31374]: (root) LIST (root)
Oct 29 08:52:31 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 29 08:52:31 node-2 crontab[31375]: (root) REPLACE (root)
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/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
Oct 29 08:52:32 node-2 puppet-user[30106]: (/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
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/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
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/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
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/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
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/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
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/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
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/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
Oct 29 08:52:32 node-2 puppet-user[30106]: (/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
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 29 08:52:32 node-2 puppet-user[30106]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Oct 29 08:52:33 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8826" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 08:52:33 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 29 08:53:05 node-2 multipathd: uevent trigger error
<27>Oct 29 08:53:05 node-2 multipathd: uevent trigger error
<27>Oct 29 08:53:05 node-2 multipathd: uevent trigger error
<27>Oct 29 08:53:05 node-2 multipathd: uevent trigger error
<27>Oct 29 08:53:05 node-2 multipathd: uevent trigger error
<27>Oct 29 08:53:43 node-2 multipathd: uevent trigger error
<27>Oct 29 08:53:43 node-2 multipathd: uevent trigger error
<27>Oct 29 08:53:43 node-2 multipathd: uevent trigger error
<27>Oct 29 08:53:43 node-2 multipathd: uevent trigger error
<27>Oct 29 08:53:43 node-2 multipathd: uevent trigger error
<27>Oct 29 08:55:04 node-2 multipathd: uevent trigger error
<27>Oct 29 08:55:04 node-2 multipathd: uevent trigger error
<27>Oct 29 08:55:04 node-2 multipathd: uevent trigger error
<27>Oct 29 08:55:04 node-2 multipathd: uevent trigger error
<27>Oct 29 08:55:04 node-2 multipathd: uevent trigger error
<27>Oct 29 08:55:04 node-2 multipathd: uevent trigger error
<27>Oct 29 08:55:37 node-2 multipathd: uevent trigger error
<27>Oct 29 08:55:37 node-2 multipathd: uevent trigger error
<27>Oct 29 08:55:37 node-2 multipathd: uevent trigger error
<27>Oct 29 08:55:37 node-2 multipathd: uevent trigger error
<27>Oct 29 08:55:37 node-2 multipathd: uevent trigger error
<27>Oct 29 08:56:18 node-2 ntpdate[1757]: no servers can be used, exiting
<27>Oct 29 08:57:23 node-2 multipathd: uevent trigger error
<27>Oct 29 08:57:23 node-2 multipathd: uevent trigger error
<27>Oct 29 08:57:23 node-2 multipathd: uevent trigger error
<27>Oct 29 08:57:23 node-2 multipathd: uevent trigger error
<27>Oct 29 08:57:23 node-2 multipathd: uevent trigger error
<27>Oct 29 08:57:57 node-2 multipathd: uevent trigger error
<27>Oct 29 08:57:57 node-2 multipathd: uevent trigger error
<27>Oct 29 08:57:57 node-2 multipathd: uevent trigger error
<27>Oct 29 08:57:57 node-2 multipathd: uevent trigger error
<27>Oct 29 08:57:57 node-2 multipathd: uevent trigger error
<27>Oct 29 08:58:38 node-2 multipathd: uevent trigger error
<27>Oct 29 08:58:38 node-2 multipathd: uevent trigger error
<27>Oct 29 08:58:38 node-2 multipathd: uevent trigger error
<27>Oct 29 08:58:38 node-2 multipathd: uevent trigger error
<27>Oct 29 08:58:38 node-2 multipathd: uevent trigger error
<27>Oct 29 08:58:38 node-2 multipathd: uevent trigger error
<27>Oct 29 08:58:42 node-2 multipathd: uevent trigger error
<27>Oct 29 08:58:42 node-2 multipathd: uevent trigger error
<27>Oct 29 08:58:42 node-2 multipathd: uevent trigger error
<27>Oct 29 08:58:42 node-2 multipathd: uevent trigger error
<27>Oct 29 08:58:42 node-2 multipathd: uevent trigger error
<27>Oct 29 08:58:42 node-2 multipathd: uevent trigger error
<27>Oct 29 08:59:18 node-2 multipathd: uevent trigger error
<27>Oct 29 08:59:18 node-2 multipathd: uevent trigger error
<27>Oct 29 08:59:18 node-2 multipathd: uevent trigger error
<27>Oct 29 08:59:18 node-2 multipathd: uevent trigger error
<27>Oct 29 08:59:18 node-2 multipathd: uevent trigger error
<27>Oct 29 08:59:28 node-2 multipathd: uevent trigger error
<27>Oct 29 08:59:28 node-2 multipathd: uevent trigger error
<27>Oct 29 08:59:28 node-2 multipathd: uevent trigger error
<27>Oct 29 08:59:28 node-2 multipathd: uevent trigger error
<27>Oct 29 08:59:28 node-2 multipathd: uevent trigger error
<27>Oct 29 08:59:32 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 29 08:59:32 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 29 08:59:36 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 29 08:59:36 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 29 08:59:42 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 29 08:59:54 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 29 08:59:54 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 29 08:59:55 node-2 multipathd: uevent trigger error
<27>Oct 29 08:59:55 node-2 multipathd: uevent trigger error
<27>Oct 29 08:59:55 node-2 multipathd: uevent trigger error
<27>Oct 29 08:59:55 node-2 multipathd: uevent trigger error
<27>Oct 29 08:59:55 node-2 multipathd: uevent trigger error
<27>Oct 29 08:59:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:05 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:05 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:05 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:05 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:05 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:28 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:28 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:28 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:28 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:28 node-2 multipathd: uevent trigger error
<129>Oct 29 09:00:30 node-2 haproxy[27841]: 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>Oct 29 09:00:30 node-2 haproxy[27841]: 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>Oct 29 09:00:31 node-2 haproxy[27845]: 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>Oct 29 09:00:31 node-2 haproxy[27845]: proxy mysqld has no server available!
<27>Oct 29 09:00:34 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:34 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:34 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:34 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:34 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:38 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:38 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:38 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:38 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:38 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:38 node-2 multipathd: uevent trigger error
<129>Oct 29 09:00:40 node-2 haproxy[30713]: 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>Oct 29 09:00:41 node-2 haproxy[30717]: 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>Oct 29 09:00:41 node-2 haproxy[30717]: 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>Oct 29 09:00:41 node-2 haproxy[30717]: proxy mysqld has no server available!
<129>Oct 29 09:00:41 node-2 haproxy[30717]: 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>Oct 29 09:00:42 node-2 haproxy[30717]: 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>Oct 29 09:00:42 node-2 haproxy[30717]: 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>Oct 29 09:00:42 node-2 haproxy[30717]: proxy object-storage has no server available!
<27>Oct 29 09:00:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:44 node-2 multipathd: uevent trigger error
<129>Oct 29 09:00:46 node-2 haproxy[32248]: 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>Oct 29 09:00:46 node-2 haproxy[32248]: 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>Oct 29 09:00:46 node-2 haproxy[32248]: 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>Oct 29 09:00:46 node-2 haproxy[32248]: proxy neutron has no server available!
<129>Oct 29 09:00:47 node-2 haproxy[32252]: 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>Oct 29 09:00:47 node-2 haproxy[32252]: 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>Oct 29 09:00:47 node-2 haproxy[32252]: 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>Oct 29 09:00:47 node-2 haproxy[32252]: proxy mysqld has no server available!
<129>Oct 29 09:00:47 node-2 haproxy[32252]: 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>Oct 29 09:00:47 node-2 haproxy[32252]: 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>Oct 29 09:00:48 node-2 haproxy[32252]: 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>Oct 29 09:00:48 node-2 haproxy[32252]: proxy object-storage has no server available!
<27>Oct 29 09:00:49 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:49 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:49 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:49 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:49 node-2 multipathd: uevent trigger error
<129>Oct 29 09:00:52 node-2 haproxy[33794]: 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>Oct 29 09:00:52 node-2 haproxy[33794]: 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>Oct 29 09:00:52 node-2 haproxy[33794]: 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>Oct 29 09:00:52 node-2 haproxy[33794]: proxy keystone-1 has no server available!
<129>Oct 29 09:00:52 node-2 haproxy[33794]: 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>Oct 29 09:00:52 node-2 haproxy[33794]: 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>Oct 29 09:00:52 node-2 haproxy[33794]: 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>Oct 29 09:00:52 node-2 haproxy[33794]: proxy keystone-2 has no server available!
<129>Oct 29 09:00:52 node-2 haproxy[33794]: 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>Oct 29 09:00:53 node-2 haproxy[33798]: 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>Oct 29 09:00:53 node-2 haproxy[33798]: 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>Oct 29 09:00:53 node-2 haproxy[33798]: proxy neutron has no server available!
<129>Oct 29 09:00:53 node-2 haproxy[33798]: 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>Oct 29 09:00:53 node-2 haproxy[33798]: 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>Oct 29 09:00:53 node-2 haproxy[33798]: 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>Oct 29 09:00:53 node-2 haproxy[33798]: proxy mysqld has no server available!
<129>Oct 29 09:00:53 node-2 haproxy[33798]: 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>Oct 29 09:00:53 node-2 haproxy[33798]: 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>Oct 29 09:00:54 node-2 haproxy[33798]: 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>Oct 29 09:00:54 node-2 haproxy[33798]: proxy object-storage has no server available!
<27>Oct 29 09:00:56 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:56 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:56 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:56 node-2 multipathd: uevent trigger error
<27>Oct 29 09:00:56 node-2 multipathd: uevent trigger error
<129>Oct 29 09:00:58 node-2 haproxy[35318]: 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>Oct 29 09:00:58 node-2 haproxy[35318]: 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>Oct 29 09:00:58 node-2 haproxy[35318]: 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>Oct 29 09:00:58 node-2 haproxy[35318]: proxy keystone-1 has no server available!
<129>Oct 29 09:00:58 node-2 haproxy[35318]: 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>Oct 29 09:00:58 node-2 haproxy[35318]: 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>Oct 29 09:00:58 node-2 haproxy[35318]: 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>Oct 29 09:00:58 node-2 haproxy[35318]: proxy keystone-2 has no server available!
<129>Oct 29 09:00:58 node-2 haproxy[35318]: 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>Oct 29 09:00:58 node-2 haproxy[35318]: 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>Oct 29 09:00:59 node-2 haproxy[35324]: 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>Oct 29 09:00:59 node-2 haproxy[35324]: proxy neutron has no server available!
<129>Oct 29 09:00:59 node-2 haproxy[35324]: 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>Oct 29 09:00:59 node-2 haproxy[35324]: 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>Oct 29 09:00:59 node-2 haproxy[35324]: 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>Oct 29 09:00:59 node-2 haproxy[35324]: proxy mysqld has no server available!
<129>Oct 29 09:00:59 node-2 haproxy[35324]: 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>Oct 29 09:00:59 node-2 haproxy[35324]: 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>Oct 29 09:00:59 node-2 haproxy[35324]: 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>Oct 29 09:00:59 node-2 haproxy[35324]: proxy object-storage has no server available!
<129>Oct 29 09:00:59 node-2 haproxy[35324]: 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>Oct 29 09:00:59 node-2 haproxy[35324]: 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>Oct 29 09:01:00 node-2 haproxy[35324]: 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>Oct 29 09:01:00 node-2 haproxy[35324]: proxy aodh has no server available!
<27>Oct 29 09:01:02 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:02 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:02 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:02 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:02 node-2 multipathd: uevent trigger error
<129>Oct 29 09:01:04 node-2 haproxy[36837]: 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>Oct 29 09:01:04 node-2 haproxy[36837]: 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>Oct 29 09:01:04 node-2 haproxy[36837]: 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>Oct 29 09:01:04 node-2 haproxy[36837]: proxy keystone-1 has no server available!
<129>Oct 29 09:01:04 node-2 haproxy[36837]: 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>Oct 29 09:01:04 node-2 haproxy[36837]: 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>Oct 29 09:01:04 node-2 haproxy[36837]: 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>Oct 29 09:01:04 node-2 haproxy[36837]: proxy keystone-2 has no server available!
<129>Oct 29 09:01:04 node-2 haproxy[36837]: 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>Oct 29 09:01:05 node-2 haproxy[36844]: 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>Oct 29 09:01:05 node-2 haproxy[36844]: 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>Oct 29 09:01:05 node-2 haproxy[36844]: proxy neutron has no server available!
<129>Oct 29 09:01:05 node-2 haproxy[36844]: 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>Oct 29 09:01:05 node-2 haproxy[36844]: 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>Oct 29 09:01:05 node-2 haproxy[36844]: 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>Oct 29 09:01:05 node-2 haproxy[36844]: proxy mysqld has no server available!
<129>Oct 29 09:01:05 node-2 haproxy[36844]: 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>Oct 29 09:01:05 node-2 haproxy[36844]: 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>Oct 29 09:01:05 node-2 haproxy[36844]: 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>Oct 29 09:01:05 node-2 haproxy[36844]: proxy object-storage has no server available!
<129>Oct 29 09:01:05 node-2 haproxy[36844]: 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>Oct 29 09:01:05 node-2 haproxy[36844]: 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>Oct 29 09:01:06 node-2 haproxy[36844]: 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>Oct 29 09:01:06 node-2 haproxy[36844]: proxy aodh has no server available!
<129>Oct 29 09:01:06 node-2 haproxy[36844]: 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>Oct 29 09:01:06 node-2 haproxy[36844]: 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>Oct 29 09:01:06 node-2 haproxy[36844]: 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>Oct 29 09:01:06 node-2 haproxy[36844]: proxy ceilometer has no server available!
<27>Oct 29 09:01:08 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:08 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:08 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:08 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:08 node-2 multipathd: uevent trigger error
<129>Oct 29 09:01:10 node-2 haproxy[38292]: 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>Oct 29 09:01:10 node-2 haproxy[38292]: 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>Oct 29 09:01:10 node-2 haproxy[38292]: 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>Oct 29 09:01:10 node-2 haproxy[38292]: proxy keystone-1 has no server available!
<129>Oct 29 09:01:10 node-2 haproxy[38292]: 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>Oct 29 09:01:10 node-2 haproxy[38292]: 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>Oct 29 09:01:11 node-2 haproxy[38296]: 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>Oct 29 09:01:11 node-2 haproxy[38296]: proxy keystone-2 has no server available!
<129>Oct 29 09:01:11 node-2 haproxy[38296]: 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>Oct 29 09:01:11 node-2 haproxy[38296]: 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>Oct 29 09:01:11 node-2 haproxy[38296]: 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>Oct 29 09:01:11 node-2 haproxy[38296]: proxy neutron has no server available!
<129>Oct 29 09:01:11 node-2 haproxy[38296]: 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>Oct 29 09:01:11 node-2 haproxy[38296]: 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>Oct 29 09:01:11 node-2 haproxy[38296]: 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>Oct 29 09:01:11 node-2 haproxy[38296]: proxy mysqld has no server available!
<129>Oct 29 09:01:11 node-2 haproxy[38296]: 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>Oct 29 09:01:11 node-2 haproxy[38296]: 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>Oct 29 09:01:11 node-2 haproxy[38296]: 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>Oct 29 09:01:11 node-2 haproxy[38296]: proxy object-storage has no server available!
<129>Oct 29 09:01:11 node-2 haproxy[38296]: 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>Oct 29 09:01:12 node-2 haproxy[38296]: 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>Oct 29 09:01:12 node-2 haproxy[38296]: 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>Oct 29 09:01:12 node-2 haproxy[38296]: proxy aodh has no server available!
<129>Oct 29 09:01:12 node-2 haproxy[38296]: 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>Oct 29 09:01:12 node-2 haproxy[38296]: 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>Oct 29 09:01:12 node-2 haproxy[38296]: 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>Oct 29 09:01:12 node-2 haproxy[38296]: proxy ceilometer has no server available!
<27>Oct 29 09:01:14 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:14 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:14 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:14 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:14 node-2 multipathd: uevent trigger error
<129>Oct 29 09:01:16 node-2 haproxy[39910]: 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>Oct 29 09:01:16 node-2 haproxy[39910]: 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>Oct 29 09:01:16 node-2 haproxy[39910]: 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>Oct 29 09:01:16 node-2 haproxy[39910]: 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>Oct 29 09:01:16 node-2 haproxy[39910]: proxy keystone-1 has no server available!
<129>Oct 29 09:01:17 node-2 haproxy[39914]: 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>Oct 29 09:01:17 node-2 haproxy[39914]: 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>Oct 29 09:01:17 node-2 haproxy[39914]: 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>Oct 29 09:01:17 node-2 haproxy[39914]: proxy keystone-2 has no server available!
<129>Oct 29 09:01:17 node-2 haproxy[39914]: 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>Oct 29 09:01:17 node-2 haproxy[39914]: 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>Oct 29 09:01:17 node-2 haproxy[39914]: 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>Oct 29 09:01:17 node-2 haproxy[39914]: proxy neutron has no server available!
<129>Oct 29 09:01:17 node-2 haproxy[39914]: 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>Oct 29 09:01:17 node-2 haproxy[39914]: 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>Oct 29 09:01:17 node-2 haproxy[39914]: 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>Oct 29 09:01:17 node-2 haproxy[39914]: proxy mysqld has no server available!
<129>Oct 29 09:01:17 node-2 haproxy[39914]: 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>Oct 29 09:01:17 node-2 haproxy[39914]: 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>Oct 29 09:01:17 node-2 haproxy[39914]: 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>Oct 29 09:01:17 node-2 haproxy[39914]: proxy object-storage has no server available!
<129>Oct 29 09:01:18 node-2 haproxy[39914]: 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>Oct 29 09:01:18 node-2 haproxy[39914]: 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>Oct 29 09:01:18 node-2 haproxy[39914]: 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>Oct 29 09:01:18 node-2 haproxy[39914]: proxy aodh has no server available!
<129>Oct 29 09:01:18 node-2 haproxy[39914]: 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>Oct 29 09:01:18 node-2 haproxy[39914]: 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>Oct 29 09:01:18 node-2 haproxy[39914]: 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>Oct 29 09:01:18 node-2 haproxy[39914]: proxy ceilometer has no server available!
<27>Oct 29 09:01:19 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:19 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:20 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:20 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:20 node-2 multipathd: uevent trigger error
<129>Oct 29 09:01:22 node-2 haproxy[41498]: 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>Oct 29 09:01:22 node-2 haproxy[41498]: 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>Oct 29 09:01:22 node-2 haproxy[41498]: 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>Oct 29 09:01:22 node-2 haproxy[41498]: 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>Oct 29 09:01:22 node-2 haproxy[41498]: proxy keystone-1 has no server available!
<129>Oct 29 09:01:22 node-2 haproxy[41498]: 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>Oct 29 09:01:22 node-2 haproxy[41498]: 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>Oct 29 09:01:22 node-2 haproxy[41498]: 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>Oct 29 09:01:22 node-2 haproxy[41498]: proxy keystone-2 has no server available!
<129>Oct 29 09:01:23 node-2 haproxy[41502]: 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>Oct 29 09:01:23 node-2 haproxy[41502]: 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>Oct 29 09:01:23 node-2 haproxy[41502]: 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>Oct 29 09:01:23 node-2 haproxy[41502]: proxy glance-api has no server available!
<129>Oct 29 09:01:23 node-2 haproxy[41502]: 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>Oct 29 09:01:23 node-2 haproxy[41502]: 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>Oct 29 09:01:23 node-2 haproxy[41502]: 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>Oct 29 09:01:23 node-2 haproxy[41502]: proxy glance-glare has no server available!
<129>Oct 29 09:01:23 node-2 haproxy[41502]: 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>Oct 29 09:01:23 node-2 haproxy[41502]: 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>Oct 29 09:01:23 node-2 haproxy[41502]: 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>Oct 29 09:01:23 node-2 haproxy[41502]: proxy neutron has no server available!
<129>Oct 29 09:01:23 node-2 haproxy[41502]: 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>Oct 29 09:01:23 node-2 haproxy[41502]: 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>Oct 29 09:01:23 node-2 haproxy[41502]: 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>Oct 29 09:01:23 node-2 haproxy[41502]: proxy glance-registry has no server available!
<129>Oct 29 09:01:23 node-2 haproxy[41502]: 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>Oct 29 09:01:23 node-2 haproxy[41502]: 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>Oct 29 09:01:23 node-2 haproxy[41502]: 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>Oct 29 09:01:23 node-2 haproxy[41502]: proxy mysqld has no server available!
<129>Oct 29 09:01:23 node-2 haproxy[41502]: 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>Oct 29 09:01:24 node-2 haproxy[41502]: 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>Oct 29 09:01:24 node-2 haproxy[41502]: 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>Oct 29 09:01:24 node-2 haproxy[41502]: proxy object-storage has no server available!
<129>Oct 29 09:01:24 node-2 haproxy[41502]: 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>Oct 29 09:01:24 node-2 haproxy[41502]: 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>Oct 29 09:01:24 node-2 haproxy[41502]: 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>Oct 29 09:01:24 node-2 haproxy[41502]: proxy aodh has no server available!
<129>Oct 29 09:01:24 node-2 haproxy[41502]: 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>Oct 29 09:01:24 node-2 haproxy[41502]: 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>Oct 29 09:01:24 node-2 haproxy[41502]: 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>Oct 29 09:01:24 node-2 haproxy[41502]: proxy ceilometer has no server available!
<27>Oct 29 09:01:26 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:26 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:26 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:26 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:26 node-2 multipathd: uevent trigger error
<129>Oct 29 09:01:28 node-2 haproxy[43049]: 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>Oct 29 09:01:28 node-2 haproxy[43049]: 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>Oct 29 09:01:28 node-2 haproxy[43049]: 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>Oct 29 09:01:28 node-2 haproxy[43049]: 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>Oct 29 09:01:28 node-2 haproxy[43049]: proxy keystone-1 has no server available!
<129>Oct 29 09:01:28 node-2 haproxy[43049]: 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>Oct 29 09:01:28 node-2 haproxy[43049]: 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>Oct 29 09:01:28 node-2 haproxy[43049]: 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>Oct 29 09:01:28 node-2 haproxy[43049]: proxy keystone-2 has no server available!
<129>Oct 29 09:01:28 node-2 haproxy[43049]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: proxy nova-api has no server available!
<129>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: proxy nova-metadata-api has no server available!
<129>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: proxy glance-api has no server available!
<129>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: proxy glance-glare has no server available!
<129>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: proxy neutron has no server available!
<129>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: proxy glance-registry has no server available!
<129>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:29 node-2 haproxy[43053]: proxy mysqld has no server available!
<129>Oct 29 09:01:29 node-2 haproxy[43053]: 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>Oct 29 09:01:30 node-2 haproxy[43053]: 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>Oct 29 09:01:30 node-2 haproxy[43053]: 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>Oct 29 09:01:30 node-2 haproxy[43053]: proxy object-storage has no server available!
<129>Oct 29 09:01:30 node-2 haproxy[43053]: 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>Oct 29 09:01:30 node-2 haproxy[43053]: 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>Oct 29 09:01:30 node-2 haproxy[43053]: 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>Oct 29 09:01:30 node-2 haproxy[43053]: proxy aodh has no server available!
<129>Oct 29 09:01:30 node-2 haproxy[43053]: 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>Oct 29 09:01:30 node-2 haproxy[43053]: 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>Oct 29 09:01:30 node-2 haproxy[43053]: 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>Oct 29 09:01:30 node-2 haproxy[43053]: proxy ceilometer has no server available!
<129>Oct 29 09:01:30 node-2 haproxy[43053]: 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>Oct 29 09:01:30 node-2 haproxy[43053]: 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>Oct 29 09:01:30 node-2 haproxy[43053]: 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>Oct 29 09:01:30 node-2 haproxy[43053]: proxy nova-novncproxy has no server available!
<27>Oct 29 09:01:32 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:32 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:32 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:32 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:32 node-2 multipathd: uevent trigger error
<129>Oct 29 09:01:34 node-2 haproxy[44553]: 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>Oct 29 09:01:34 node-2 haproxy[44553]: 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>Oct 29 09:01:34 node-2 haproxy[44553]: 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>Oct 29 09:01:34 node-2 haproxy[44553]: 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>Oct 29 09:01:34 node-2 haproxy[44553]: proxy keystone-1 has no server available!
<129>Oct 29 09:01:34 node-2 haproxy[44553]: 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>Oct 29 09:01:34 node-2 haproxy[44553]: 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>Oct 29 09:01:34 node-2 haproxy[44553]: 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>Oct 29 09:01:34 node-2 haproxy[44553]: proxy keystone-2 has no server available!
<129>Oct 29 09:01:34 node-2 haproxy[44553]: 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>Oct 29 09:01:34 node-2 haproxy[44553]: 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>Oct 29 09:01:34 node-2 haproxy[44553]: 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>Oct 29 09:01:34 node-2 haproxy[44553]: proxy nova-api has no server available!
<129>Oct 29 09:01:34 node-2 haproxy[44553]: 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>Oct 29 09:01:34 node-2 haproxy[44553]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: proxy nova-metadata-api has no server available!
<129>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: proxy cinder-api has no server available!
<129>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: proxy glance-api has no server available!
<129>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: proxy glance-glare has no server available!
<129>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: proxy neutron has no server available!
<129>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: proxy glance-registry has no server available!
<129>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: proxy mysqld has no server available!
<129>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:35 node-2 haproxy[44557]: proxy object-storage has no server available!
<129>Oct 29 09:01:35 node-2 haproxy[44557]: 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>Oct 29 09:01:36 node-2 haproxy[44557]: 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>Oct 29 09:01:36 node-2 haproxy[44557]: 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>Oct 29 09:01:36 node-2 haproxy[44557]: proxy aodh has no server available!
<129>Oct 29 09:01:36 node-2 haproxy[44557]: 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>Oct 29 09:01:36 node-2 haproxy[44557]: 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>Oct 29 09:01:36 node-2 haproxy[44557]: 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>Oct 29 09:01:36 node-2 haproxy[44557]: proxy ceilometer has no server available!
<129>Oct 29 09:01:36 node-2 haproxy[44557]: 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>Oct 29 09:01:36 node-2 haproxy[44557]: 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>Oct 29 09:01:36 node-2 haproxy[44557]: 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>Oct 29 09:01:36 node-2 haproxy[44557]: proxy nova-novncproxy has no server available!
<27>Oct 29 09:01:37 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:37 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:37 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:37 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:37 node-2 multipathd: uevent trigger error
<129>Oct 29 09:01:40 node-2 haproxy[46387]: 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>Oct 29 09:01:40 node-2 haproxy[46387]: 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>Oct 29 09:01:40 node-2 haproxy[46387]: 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>Oct 29 09:01:40 node-2 haproxy[46387]: 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>Oct 29 09:01:40 node-2 haproxy[46387]: proxy keystone-1 has no server available!
<129>Oct 29 09:01:40 node-2 haproxy[46387]: 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>Oct 29 09:01:40 node-2 haproxy[46387]: 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>Oct 29 09:01:40 node-2 haproxy[46387]: 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>Oct 29 09:01:40 node-2 haproxy[46387]: proxy keystone-2 has no server available!
<129>Oct 29 09:01:40 node-2 haproxy[46387]: 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>Oct 29 09:01:40 node-2 haproxy[46387]: 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>Oct 29 09:01:40 node-2 haproxy[46387]: 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>Oct 29 09:01:40 node-2 haproxy[46387]: proxy nova-api has no server available!
<129>Oct 29 09:01:40 node-2 haproxy[46387]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: proxy nova-metadata-api has no server available!
<129>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: proxy cinder-api has no server available!
<129>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: proxy glance-api has no server available!
<129>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: proxy glance-glare has no server available!
<129>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: proxy neutron has no server available!
<129>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: proxy glance-registry has no server available!
<129>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: proxy mysqld has no server available!
<129>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: proxy object-storage has no server available!
<129>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:41 node-2 haproxy[46391]: proxy aodh has no server available!
<129>Oct 29 09:01:41 node-2 haproxy[46391]: 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>Oct 29 09:01:42 node-2 haproxy[46391]: 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>Oct 29 09:01:42 node-2 haproxy[46391]: 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>Oct 29 09:01:42 node-2 haproxy[46391]: proxy ceilometer has no server available!
<129>Oct 29 09:01:42 node-2 haproxy[46391]: 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>Oct 29 09:01:42 node-2 haproxy[46391]: 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>Oct 29 09:01:42 node-2 haproxy[46391]: 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>Oct 29 09:01:42 node-2 haproxy[46391]: proxy heat-api has no server available!
<129>Oct 29 09:01:42 node-2 haproxy[46391]: 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>Oct 29 09:01:42 node-2 haproxy[46391]: 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>Oct 29 09:01:42 node-2 haproxy[46391]: 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>Oct 29 09:01:42 node-2 haproxy[46391]: proxy heat-api-cfn has no server available!
<129>Oct 29 09:01:42 node-2 haproxy[46391]: 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>Oct 29 09:01:42 node-2 haproxy[46391]: 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>Oct 29 09:01:42 node-2 haproxy[46391]: 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>Oct 29 09:01:42 node-2 haproxy[46391]: proxy heat-api-cloudwatch has no server available!
<129>Oct 29 09:01:42 node-2 haproxy[46391]: 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>Oct 29 09:01:42 node-2 haproxy[46391]: 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>Oct 29 09:01:42 node-2 haproxy[46391]: 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>Oct 29 09:01:42 node-2 haproxy[46391]: proxy nova-novncproxy has no server available!
<27>Oct 29 09:01:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:48 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:48 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:48 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:48 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:48 node-2 multipathd: uevent trigger error
<27>Oct 29 09:01:53 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 29 09:02:08 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 29 09:02:11 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 29 09:02:14 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>Oct 29 09:02:16 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 29 09:03:11 node-2 multipathd: uevent trigger error
<27>Oct 29 09:03:11 node-2 multipathd: uevent trigger error
<27>Oct 29 09:03:11 node-2 multipathd: uevent trigger error
<27>Oct 29 09:03:11 node-2 multipathd: uevent trigger error
<27>Oct 29 09:03:11 node-2 multipathd: uevent trigger error
<27>Oct 29 09:03:11 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:15 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 29 09:05:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:34 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:34 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:34 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:34 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:34 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:39 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:39 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:39 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:39 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:39 node-2 multipathd: uevent trigger error
<43>Oct 29 09:05:44 node-2 apache2_error [Sat Oct 29 09:05:43.615293 2016] [mpm_event:notice] [pid 42407:tid 140328390506368] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 29 09:05:44 node-2 apache2_error [Sat Oct 29 09:05:43.615431 2016] [core:notice] [pid 42407:tid 140328390506368] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 29 09:05:52 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:52 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:52 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:52 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:52 node-2 multipathd: uevent trigger error
<43>Oct 29 09:05:54 node-2 apache2_error [Sat Oct 29 09:05:45.828389 2016] [mpm_event:notice] [pid 42407:tid 140328390506368] AH00491: caught SIGTERM, shutting down
<43>Oct 29 09:05:54 node-2 apache2_error [Sat Oct 29 09:05:46.915282 2016] [mpm_worker:notice] [pid 42966:tid 140587541976960] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 29 09:05:54 node-2 apache2_error [Sat Oct 29 09:05:46.915315 2016] [core:notice] [pid 42966:tid 140587541976960] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 29 09:05:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:59 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:59 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:59 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:59 node-2 multipathd: uevent trigger error
<27>Oct 29 09:05:59 node-2 multipathd: uevent trigger error
<43>Oct 29 09:06:34 node-2 apache2_error [Sat Oct 29 09:06:31.454962 2016] [mpm_worker:notice] [pid 42966:tid 140587541976960] AH00295: caught SIGTERM, shutting down
<43>Oct 29 09:06:34 node-2 apache2_error [Sat Oct 29 09:06:32.210777 2016] [mpm_worker:notice] [pid 6348:tid 139693449058176] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 29 09:06:34 node-2 apache2_error [Sat Oct 29 09:06:32.210805 2016] [core:notice] [pid 6348:tid 139693449058176] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 29 09:07:14 node-2 apache2_error [Sat Oct 29 09:07:06.536061 2016] [mpm_worker:notice] [pid 6348:tid 139693449058176] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 29 09:07:14 node-2 apache2_error [Sat Oct 29 09:07:06.732933 2016] [mpm_worker:warn] [pid 6348:tid 139693449058176] AH00317: MaxRequestWorkers of 12881 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 12875
<43>Oct 29 09:07:14 node-2 apache2_error [Sat Oct 29 09:07:06.736719 2016] [mpm_worker:notice] [pid 6348:tid 139693449058176] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 29 09:07:14 node-2 apache2_error [Sat Oct 29 09:07:06.736736 2016] [core:notice] [pid 6348:tid 139693449058176] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 29 09:08:06 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:06 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:06 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:06 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:06 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:11 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:11 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:11 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:11 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:11 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:16 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:16 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:16 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:16 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:16 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:17 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 29 09:08:34 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:34 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:34 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:34 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:34 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:08:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:09:01 node-2 multipathd: uevent trigger error
<27>Oct 29 09:09:01 node-2 multipathd: uevent trigger error
<27>Oct 29 09:09:01 node-2 multipathd: uevent trigger error
<27>Oct 29 09:09:01 node-2 multipathd: uevent trigger error
<27>Oct 29 09:09:01 node-2 multipathd: uevent trigger error
<27>Oct 29 09:09:22 node-2 multipathd: uevent trigger error
<27>Oct 29 09:09:22 node-2 multipathd: uevent trigger error
<27>Oct 29 09:09:22 node-2 multipathd: uevent trigger error
<27>Oct 29 09:09:22 node-2 multipathd: uevent trigger error
<27>Oct 29 09:09:22 node-2 multipathd: uevent trigger error
<27>Oct 29 09:10:02 node-2 multipathd: uevent trigger error
<27>Oct 29 09:10:02 node-2 multipathd: uevent trigger error
<27>Oct 29 09:10:02 node-2 multipathd: uevent trigger error
<27>Oct 29 09:10:02 node-2 multipathd: uevent trigger error
<27>Oct 29 09:10:02 node-2 multipathd: uevent trigger error
<27>Oct 29 09:11:04 node-2 multipathd: uevent trigger error
<27>Oct 29 09:11:04 node-2 multipathd: uevent trigger error
<27>Oct 29 09:11:04 node-2 multipathd: uevent trigger error
<27>Oct 29 09:11:04 node-2 multipathd: uevent trigger error
<27>Oct 29 09:11:04 node-2 multipathd: uevent trigger error
<27>Oct 29 09:11:19 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 29 09:11:37 node-2 multipathd: uevent trigger error
<27>Oct 29 09:11:37 node-2 multipathd: uevent trigger error
<27>Oct 29 09:11:38 node-2 multipathd: uevent trigger error
<27>Oct 29 09:11:38 node-2 multipathd: uevent trigger error
<27>Oct 29 09:11:38 node-2 multipathd: uevent trigger error
<27>Oct 29 09:12:04 node-2 multipathd: uevent trigger error
<27>Oct 29 09:12:04 node-2 multipathd: uevent trigger error
<27>Oct 29 09:12:04 node-2 multipathd: uevent trigger error
<27>Oct 29 09:12:04 node-2 multipathd: uevent trigger error
<27>Oct 29 09:12:04 node-2 multipathd: uevent trigger error
<27>Oct 29 09:12:10 node-2 multipathd: uevent trigger error
<27>Oct 29 09:12:10 node-2 multipathd: uevent trigger error
<27>Oct 29 09:12:10 node-2 multipathd: uevent trigger error
<27>Oct 29 09:12:10 node-2 multipathd: uevent trigger error
<27>Oct 29 09:12:10 node-2 multipathd: uevent trigger error
<27>Oct 29 09:14:21 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 29 09:14:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:14:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:14:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:14:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:14:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:14:47 node-2 multipathd: uevent trigger error
<27>Oct 29 09:14:47 node-2 multipathd: uevent trigger error
<27>Oct 29 09:14:47 node-2 multipathd: uevent trigger error
<27>Oct 29 09:14:47 node-2 multipathd: uevent trigger error
<27>Oct 29 09:14:47 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:00 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:00 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:00 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:00 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:00 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:00 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:06 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:06 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:06 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:06 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:06 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:17 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:17 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:17 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:17 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:17 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:56 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:56 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:56 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:56 node-2 multipathd: uevent trigger error
<27>Oct 29 09:15:56 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:02 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:02 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:02 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:02 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:02 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:08 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:08 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:08 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:08 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:08 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:37 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:37 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:37 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:37 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:37 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:49 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:49 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:49 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:49 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:49 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:55 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Oct 29 09:16:55 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Oct 29 09:16:55 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Oct 29 09:16:57 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Oct 29 09:16:57 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Oct 29 09:16:57 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:57 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:57 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:57 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:57 node-2 multipathd: uevent trigger error
<27>Oct 29 09:16:57 node-2 multipathd: uevent trigger error
<27>Oct 29 09:17:12 node-2 multipathd: uevent trigger error
<27>Oct 29 09:17:12 node-2 multipathd: uevent trigger error
<27>Oct 29 09:17:12 node-2 multipathd: uevent trigger error
<27>Oct 29 09:17:12 node-2 multipathd: uevent trigger error
<27>Oct 29 09:17:12 node-2 multipathd: uevent trigger error
<27>Oct 29 09:17:23 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 29 09:17:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:17:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:17:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:17:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:17:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:17:43 node-2 multipathd: uevent trigger error
<27>Oct 29 09:17:43 node-2 multipathd: uevent trigger error
<27>Oct 29 09:17:43 node-2 multipathd: uevent trigger error
<27>Oct 29 09:17:43 node-2 multipathd: uevent trigger error
<27>Oct 29 09:17:43 node-2 multipathd: uevent trigger error
<27>Oct 29 09:19:51 node-2 multipathd: uevent trigger error
<27>Oct 29 09:19:51 node-2 multipathd: uevent trigger error
<27>Oct 29 09:19:51 node-2 multipathd: uevent trigger error
<27>Oct 29 09:19:51 node-2 multipathd: uevent trigger error
<27>Oct 29 09:19:51 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:16 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:16 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:16 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:16 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:21 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:22 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:22 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:22 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:22 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:25 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 29 09:20:45 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:45 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:45 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:45 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:50 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:50 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:50 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:50 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:50 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:20:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:21:08 node-2 multipathd: uevent trigger error
<27>Oct 29 09:21:08 node-2 multipathd: uevent trigger error
<27>Oct 29 09:21:08 node-2 multipathd: uevent trigger error
<27>Oct 29 09:21:08 node-2 multipathd: uevent trigger error
<27>Oct 29 09:21:08 node-2 multipathd: uevent trigger error
<27>Oct 29 09:21:15 node-2 multipathd: uevent trigger error
<27>Oct 29 09:21:15 node-2 multipathd: uevent trigger error
<27>Oct 29 09:21:15 node-2 multipathd: uevent trigger error
<27>Oct 29 09:21:15 node-2 multipathd: uevent trigger error
<27>Oct 29 09:21:15 node-2 multipathd: uevent trigger error
<27>Oct 29 09:21:42 node-2 multipathd: uevent trigger error
<27>Oct 29 09:21:42 node-2 multipathd: uevent trigger error
<27>Oct 29 09:21:42 node-2 multipathd: uevent trigger error
<27>Oct 29 09:21:42 node-2 multipathd: uevent trigger error
<27>Oct 29 09:21:42 node-2 multipathd: uevent trigger error
<27>Oct 29 09:22:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:22:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:22:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:22:29 node-2 multipathd: uevent trigger error
<27>Oct 29 09:22:43 node-2 multipathd: uevent trigger error
<27>Oct 29 09:22:43 node-2 multipathd: uevent trigger error
<27>Oct 29 09:22:43 node-2 multipathd: uevent trigger error
<27>Oct 29 09:22:43 node-2 multipathd: uevent trigger error
<27>Oct 29 09:22:43 node-2 multipathd: uevent trigger error
<11>Oct 29 09:22:55 node-2 liberasurecode[12612]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:55 node-2 liberasurecode[12612]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:55 node-2 liberasurecode[12612]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:55 node-2 liberasurecode[12612]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:55 node-2 liberasurecode[12672]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:55 node-2 liberasurecode[12672]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:55 node-2 liberasurecode[12672]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:55 node-2 liberasurecode[12672]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:56 node-2 liberasurecode[13085]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:56 node-2 liberasurecode[13085]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:56 node-2 liberasurecode[13085]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:56 node-2 liberasurecode[13085]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:58 node-2 liberasurecode[13532]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:58 node-2 liberasurecode[13532]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:58 node-2 liberasurecode[13532]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:58 node-2 liberasurecode[13532]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:58 node-2 liberasurecode[13578]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:58 node-2 liberasurecode[13578]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:58 node-2 liberasurecode[13578]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:58 node-2 liberasurecode[13578]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:58 node-2 liberasurecode[13618]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:58 node-2 liberasurecode[13618]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:58 node-2 liberasurecode[13618]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:58 node-2 liberasurecode[13618]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:59 node-2 liberasurecode[13676]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:59 node-2 liberasurecode[13676]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:59 node-2 liberasurecode[13676]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:59 node-2 liberasurecode[13676]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:59 node-2 liberasurecode[13691]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:59 node-2 liberasurecode[13691]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:59 node-2 liberasurecode[13691]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:59 node-2 liberasurecode[13691]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:59 node-2 liberasurecode[13704]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:59 node-2 liberasurecode[13704]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:59 node-2 liberasurecode[13704]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:59 node-2 liberasurecode[13704]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:59 node-2 liberasurecode[13719]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:59 node-2 liberasurecode[13719]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:59 node-2 liberasurecode[13719]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:22:59 node-2 liberasurecode[13719]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 09:23:10 node-2 liberasurecode[14210]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:23:10 node-2 liberasurecode[14210]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:23:10 node-2 liberasurecode[14210]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:23:10 node-2 liberasurecode[14210]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 29 09:23:18 node-2 multipathd: uevent trigger error
<27>Oct 29 09:23:18 node-2 multipathd: uevent trigger error
<27>Oct 29 09:23:18 node-2 multipathd: uevent trigger error
<27>Oct 29 09:23:18 node-2 multipathd: uevent trigger error
<27>Oct 29 09:23:18 node-2 multipathd: uevent trigger error
<27>Oct 29 09:23:26 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 29 09:23:55 node-2 apache2_error [Sat Oct 29 09:23:47.593704 2016] [mpm_worker:notice] [pid 6348:tid 139693449058176] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 29 09:23:55 node-2 apache2_error [Sat Oct 29 09:23:47.979353 2016] [mpm_worker:warn] [pid 6348:tid 139693449058176] AH00317: MaxRequestWorkers of 12881 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 12875
<43>Oct 29 09:23:55 node-2 apache2_error [Sat Oct 29 09:23:47.985630 2016] [mpm_worker:notice] [pid 6348:tid 139693449058176] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 29 09:23:55 node-2 apache2_error [Sat Oct 29 09:23:47.985648 2016] [core:notice] [pid 6348:tid 139693449058176] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 29 09:24:25 node-2 apache2_error [Sat Oct 29 09:24:25.271564 2016] [mpm_worker:notice] [pid 6348:tid 139693449058176] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 29 09:24:25 node-2 apache2_error [Sat Oct 29 09:24:25.469535 2016] [mpm_worker:warn] [pid 6348:tid 139693449058176] AH00317: MaxRequestWorkers of 12881 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 12875
<43>Oct 29 09:24:25 node-2 apache2_error [Sat Oct 29 09:24:25.477514 2016] [mpm_worker:notice] [pid 6348:tid 139693449058176] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 29 09:24:25 node-2 apache2_error [Sat Oct 29 09:24:25.477536 2016] [core:notice] [pid 6348:tid 139693449058176] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 29 09:24:30 node-2 multipathd: uevent trigger error
<27>Oct 29 09:24:30 node-2 multipathd: uevent trigger error
<27>Oct 29 09:24:30 node-2 multipathd: uevent trigger error
<27>Oct 29 09:24:30 node-2 multipathd: uevent trigger error
<27>Oct 29 09:24:30 node-2 multipathd: uevent trigger error
<27>Oct 29 09:24:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:24:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:24:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:24:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:24:44 node-2 multipathd: uevent trigger error
<11>Oct 29 09:25:01 node-2 liberasurecode[34053]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:25:01 node-2 liberasurecode[34053]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:25:02 node-2 liberasurecode[34053]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:25:02 node-2 liberasurecode[34053]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 29 09:25:24 node-2 multipathd: uevent trigger error
<27>Oct 29 09:25:24 node-2 multipathd: uevent trigger error
<27>Oct 29 09:25:24 node-2 multipathd: uevent trigger error
<27>Oct 29 09:25:24 node-2 multipathd: uevent trigger error
<27>Oct 29 09:25:24 node-2 multipathd: uevent trigger error
<43>Oct 29 09:25:25 node-2 apache2_error [Sat Oct 29 09:25:19.263159 2016] [mpm_worker:notice] [pid 6348:tid 139693449058176] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 29 09:25:25 node-2 apache2_error [Sat Oct 29 09:25:19.650027 2016] [mpm_worker:warn] [pid 6348:tid 139693449058176] AH00317: MaxRequestWorkers of 12881 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 12875
<43>Oct 29 09:25:25 node-2 apache2_error [Sat Oct 29 09:25:19.658016 2016] [mpm_worker:notice] [pid 6348:tid 139693449058176] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 29 09:25:25 node-2 apache2_error [Sat Oct 29 09:25:19.658035 2016] [core:notice] [pid 6348:tid 139693449058176] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 29 09:25:31 node-2 multipathd: uevent trigger error
<27>Oct 29 09:25:31 node-2 multipathd: uevent trigger error
<27>Oct 29 09:25:31 node-2 multipathd: uevent trigger error
<27>Oct 29 09:25:31 node-2 multipathd: uevent trigger error
<27>Oct 29 09:25:31 node-2 multipathd: uevent trigger error
<27>Oct 29 09:25:38 node-2 multipathd: uevent trigger error
<27>Oct 29 09:25:38 node-2 multipathd: uevent trigger error
<27>Oct 29 09:25:38 node-2 multipathd: uevent trigger error
<27>Oct 29 09:25:38 node-2 multipathd: uevent trigger error
<27>Oct 29 09:25:38 node-2 multipathd: uevent trigger error
<27>Oct 29 09:26:01 node-2 multipathd: uevent trigger error
<27>Oct 29 09:26:01 node-2 multipathd: uevent trigger error
<27>Oct 29 09:26:01 node-2 multipathd: uevent trigger error
<27>Oct 29 09:26:01 node-2 multipathd: uevent trigger error
<27>Oct 29 09:26:01 node-2 multipathd: uevent trigger error
<27>Oct 29 09:26:24 node-2 multipathd: uevent trigger error
<27>Oct 29 09:26:33 node-2 multipathd: uevent trigger error
<27>Oct 29 09:26:33 node-2 multipathd: uevent trigger error
<27>Oct 29 09:26:33 node-2 multipathd: uevent trigger error
<27>Oct 29 09:26:33 node-2 multipathd: uevent trigger error
<27>Oct 29 09:26:33 node-2 multipathd: uevent trigger error
<27>Oct 29 09:26:34 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 29 09:26:38 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 29 09:26:47 node-2 multipathd: uevent trigger error
<27>Oct 29 09:26:47 node-2 multipathd: uevent trigger error
<27>Oct 29 09:26:47 node-2 multipathd: uevent trigger error
<27>Oct 29 09:26:47 node-2 multipathd: uevent trigger error
<27>Oct 29 09:26:47 node-2 multipathd: uevent trigger error
<27>Oct 29 09:27:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:27:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:27:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:27:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:27:44 node-2 multipathd: uevent trigger error
<11>Oct 29 09:30:01 node-2 liberasurecode[39838]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:30:01 node-2 liberasurecode[39838]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:30:01 node-2 liberasurecode[39838]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:30:01 node-2 liberasurecode[39838]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 29 09:30:39 node-2 multipathd: uevent trigger error
<27>Oct 29 09:30:39 node-2 multipathd: uevent trigger error
<27>Oct 29 09:30:39 node-2 multipathd: uevent trigger error
<27>Oct 29 09:30:39 node-2 multipathd: uevent trigger error
<27>Oct 29 09:30:39 node-2 multipathd: uevent trigger error
<27>Oct 29 09:30:45 node-2 multipathd: uevent trigger error
<27>Oct 29 09:30:45 node-2 multipathd: uevent trigger error
<27>Oct 29 09:30:45 node-2 multipathd: uevent trigger error
<27>Oct 29 09:30:45 node-2 multipathd: uevent trigger error
<27>Oct 29 09:30:45 node-2 multipathd: uevent trigger error
<27>Oct 29 09:30:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:30:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:30:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:30:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:30:55 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:07 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:07 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:07 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:07 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:07 node-2 multipathd: uevent trigger error
<129>Oct 29 09:31:15 node-2 haproxy[2852]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 09:31:15 node-2 haproxy[2852]: 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.
<27>Oct 29 09:31:24 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:24 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:24 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:24 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:24 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:30 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:30 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:30 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:30 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:44 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:50 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:50 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:50 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:50 node-2 multipathd: uevent trigger error
<27>Oct 29 09:31:50 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:04 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:04 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:05 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:05 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:05 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:17 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:17 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:17 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:17 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:17 node-2 multipathd: uevent trigger error
<129>Oct 29 09:32:24 node-2 haproxy[2852]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 29 09:32:32 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:32 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:32 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:32 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:32 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:37 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:37 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:37 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:37 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:37 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:43 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:43 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:43 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:43 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:43 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:48 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:48 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:48 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:48 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:48 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:53 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:53 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:53 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:53 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:59 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:59 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:59 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:59 node-2 multipathd: uevent trigger error
<27>Oct 29 09:32:59 node-2 multipathd: uevent trigger error
<11>Oct 29 09:35:01 node-2 liberasurecode[14106]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:35:01 node-2 liberasurecode[14106]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:35:01 node-2 liberasurecode[14106]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 09:35:01 node-2 liberasurecode[14106]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
