Jul 28 03:29:51 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8367" x-info="http://www.rsyslog.com"] start
Jul 28 03:29:51 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 28 03:29:51 node-4 rsyslogd: rsyslogd's groupid changed to 104
Jul 28 03:29:51 node-4 rsyslogd: rsyslogd's userid changed to 101
Jul 28 03:29:51 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 28 03:29:51 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 28 03:29:51 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 28 03:29:51 node-4 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 28 03:29:51 node-4 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=e3c97571-97d9-4932-92e3-59f8bed02a1a nomdmonddf nomdmonisw
Jul 28 03:29:51 node-4 kernel: [    0.000000] KERNEL supported cpus:
Jul 28 03:29:51 node-4 kernel: [    0.000000]   Intel GenuineIntel
Jul 28 03:29:51 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Jul 28 03:29:51 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Jul 28 03:29:51 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 28 03:29:51 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 28 03:29:51 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 28 03:29:51 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 28 03:29:51 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 28 03:29:51 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 28 03:29:51 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 28 03:29:51 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 28 03:29:51 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 28 03:29:51 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 28 03:29:51 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 28 03:29:51 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 28 03:29:51 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 28 03:29:51 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 28 03:29:51 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 28 03:29:51 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 28 03:29:51 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 28 03:29:51 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 28 03:29:51 node-4 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 28 03:29:51 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 28 03:29:51 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 28 03:29:51 node-4 kernel: [    0.000000] No AGP bridge found
Jul 28 03:29:51 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 28 03:29:51 node-4 kernel: [    0.000000] MTRR default type: write-back
Jul 28 03:29:51 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 28 03:29:51 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Jul 28 03:29:51 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 28 03:29:51 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 28 03:29:51 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 28 03:29:51 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 28 03:29:51 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 28 03:29:51 node-4 kernel: [    0.000000]   2 disabled
Jul 28 03:29:51 node-4 kernel: [    0.000000]   3 disabled
Jul 28 03:29:51 node-4 kernel: [    0.000000]   4 disabled
Jul 28 03:29:51 node-4 kernel: [    0.000000]   5 disabled
Jul 28 03:29:51 node-4 kernel: [    0.000000]   6 disabled
Jul 28 03:29:51 node-4 kernel: [    0.000000]   7 disabled
Jul 28 03:29:51 node-4 kernel: [    0.000000]   8 disabled
Jul 28 03:29:51 node-4 kernel: [    0.000000]   9 disabled
Jul 28 03:29:51 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 28 03:29:51 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 28 03:29:51 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 28 03:29:51 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 28 03:29:51 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 28 03:29:51 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Jul 28 03:29:51 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 28 03:29:51 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 28 03:29:51 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 28 03:29:51 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 28 03:29:51 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 28 03:29:51 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 28 03:29:51 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 28 03:29:51 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 28 03:29:51 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 28 03:29:51 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 28 03:29:51 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 28 03:29:51 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 28 03:29:51 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 28 03:29:51 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 28 03:29:51 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 28 03:29:51 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 28 03:29:51 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 28 03:29:51 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 28 03:29:51 node-4 kernel: [    0.000000] Zone ranges:
Jul 28 03:29:51 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] Movable zone start for each node
Jul 28 03:29:51 node-4 kernel: [    0.000000] Early memory node ranges
Jul 28 03:29:51 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 28 03:29:51 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 28 03:29:51 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 28 03:29:51 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 28 03:29:51 node-4 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 28 03:29:51 node-4 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 28 03:29:51 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 28 03:29:51 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 28 03:29:51 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 28 03:29:51 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 28 03:29:51 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 28 03:29:51 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 28 03:29:51 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 28 03:29:51 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 28 03:29:51 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 28 03:29:51 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 28 03:29:51 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 28 03:29:51 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 28 03:29:51 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 28 03:29:51 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 28 03:29:51 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 28 03:29:51 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 28 03:29:51 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 28 03:29:51 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 28 03:29:51 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 28 03:29:51 node-4 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 28 03:29:51 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 28 03:29:51 node-4 kernel: [    0.000000] Policy zone: Normal
Jul 28 03:29:51 node-4 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=e3c97571-97d9-4932-92e3-59f8bed02a1a nomdmonddf nomdmonisw
Jul 28 03:29:51 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 28 03:29:51 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 28 03:29:51 node-4 kernel: [    0.000000] Checking aperture...
Jul 28 03:29:51 node-4 kernel: [    0.000000] No AGP bridge found
Jul 28 03:29:51 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 28 03:29:51 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 28 03:29:51 node-4 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 28 03:29:51 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 28 03:29:51 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 28 03:29:51 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 28 03:29:51 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 28 03:29:51 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 28 03:29:51 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 28 03:29:51 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 28 03:29:51 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 28 03:29:51 node-4 kernel: [    0.000000] console [tty0] enabled
Jul 28 03:29:51 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 28 03:29:51 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 28 03:29:51 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 28 03:29:51 node-4 kernel: [    0.000000] hpet clockevent registered
Jul 28 03:29:51 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 28 03:29:51 node-4 kernel: [    0.004000] tsc: Detected 3492.266 MHz processor
Jul 28 03:29:51 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.53 BogoMIPS (lpj=13969064)
Jul 28 03:29:51 node-4 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 28 03:29:51 node-4 kernel: [    0.000044] Security Framework initialized
Jul 28 03:29:51 node-4 kernel: [    0.000061] AppArmor: AppArmor initialized
Jul 28 03:29:51 node-4 kernel: [    0.000062] Yama: becoming mindful.
Jul 28 03:29:51 node-4 kernel: [    0.001455] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 28 03:29:51 node-4 kernel: [    0.006311] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 28 03:29:51 node-4 kernel: [    0.008240] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 28 03:29:51 node-4 kernel: [    0.008267] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 28 03:29:51 node-4 kernel: [    0.008556] Initializing cgroup subsys memory
Jul 28 03:29:51 node-4 kernel: [    0.008564] Initializing cgroup subsys devices
Jul 28 03:29:51 node-4 kernel: [    0.008566] Initializing cgroup subsys freezer
Jul 28 03:29:51 node-4 kernel: [    0.008567] Initializing cgroup subsys blkio
Jul 28 03:29:51 node-4 kernel: [    0.008569] Initializing cgroup subsys perf_event
Jul 28 03:29:51 node-4 kernel: [    0.008571] Initializing cgroup subsys hugetlb
Jul 28 03:29:51 node-4 kernel: [    0.008591] CPU: Physical Processor ID: 0
Jul 28 03:29:51 node-4 kernel: [    0.008592] CPU: Processor Core ID: 0
Jul 28 03:29:51 node-4 kernel: [    0.008596] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 28 03:29:51 node-4 kernel: [    0.008596] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 28 03:29:51 node-4 kernel: [    0.009289] mce: CPU supports 22 MCE banks
Jul 28 03:29:51 node-4 kernel: [    0.009317] CPU0: Thermal monitoring enabled (TM1)
Jul 28 03:29:51 node-4 kernel: [    0.009337] process: using mwait in idle threads
Jul 28 03:29:51 node-4 kernel: [    0.009340] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 28 03:29:51 node-4 kernel: [    0.009340] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 28 03:29:51 node-4 kernel: [    0.009340] tlb_flushall_shift: 6
Jul 28 03:29:51 node-4 kernel: [    0.009428] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 28 03:29:51 node-4 kernel: [    0.010150] ACPI: Core revision 20131115
Jul 28 03:29:51 node-4 kernel: [    0.022834] ACPI: All ACPI Tables successfully acquired
Jul 28 03:29:51 node-4 kernel: [    0.022995] ftrace: allocating 28617 entries in 112 pages
Jul 28 03:29:51 node-4 kernel: [    0.031789] dmar: Host address width 46
Jul 28 03:29:51 node-4 kernel: [    0.031792] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 28 03:29:51 node-4 kernel: [    0.031798] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 28 03:29:51 node-4 kernel: [    0.031799] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 28 03:29:51 node-4 kernel: [    0.031803] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 28 03:29:51 node-4 kernel: [    0.031805] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 28 03:29:51 node-4 kernel: [    0.031806] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 28 03:29:51 node-4 kernel: [    0.031807] dmar: ATSR flags: 0x0
Jul 28 03:29:51 node-4 kernel: [    0.031808] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 28 03:29:51 node-4 kernel: [    0.031810] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 28 03:29:51 node-4 kernel: [    0.031926] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 28 03:29:51 node-4 kernel: [    0.031927] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 28 03:29:51 node-4 kernel: [    0.031928] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 28 03:29:51 node-4 kernel: [    0.031929] HPET id 0 under DRHD base 0xc7ffc000
Jul 28 03:29:51 node-4 kernel: [    0.031930] Your BIOS is broken and requested that x2apic be disabled.
Jul 28 03:29:51 node-4 kernel: [    0.031930] This will slightly decrease performance.
Jul 28 03:29:51 node-4 kernel: [    0.031930] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 28 03:29:51 node-4 kernel: [    0.032362] Enabled IRQ remapping in xapic mode
Jul 28 03:29:51 node-4 kernel: [    0.032363] x2apic not enabled, IRQ remapping is in xapic mode
Jul 28 03:29:51 node-4 kernel: [    0.032366] Switched APIC routing to physical flat.
Jul 28 03:29:51 node-4 kernel: [    0.032987] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 28 03:29:51 node-4 kernel: [    0.072640] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 28 03:29:51 node-4 kernel: [    0.072646] TSC deadline timer enabled
Jul 28 03:29:51 node-4 kernel: [    0.072654] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 28 03:29:51 node-4 kernel: [    0.072660] ... version:                3
Jul 28 03:29:51 node-4 kernel: [    0.072661] ... bit width:              48
Jul 28 03:29:51 node-4 kernel: [    0.072662] ... generic registers:      4
Jul 28 03:29:51 node-4 kernel: [    0.072663] ... value mask:             0000ffffffffffff
Jul 28 03:29:51 node-4 kernel: [    0.072664] ... max period:             0000ffffffffffff
Jul 28 03:29:51 node-4 kernel: [    0.072665] ... fixed-purpose events:   3
Jul 28 03:29:51 node-4 kernel: [    0.072665] ... event mask:             000000070000000f
Jul 28 03:29:51 node-4 kernel: [    0.074122] x86: Booting SMP configuration:
Jul 28 03:29:51 node-4 kernel: [    0.088350] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 28 03:29:51 node-4 kernel: [    0.074124] .... node  #0, CPUs:        #1  #2  #3
Jul 28 03:29:51 node-4 kernel: [    0.116271] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 28 03:29:51 node-4 kernel: [    0.270449] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 28 03:29:51 node-4 kernel: [    0.326077] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 28 03:29:51 node-4 kernel: [    0.382936] x86: Booted up 2 nodes, 16 CPUs
Jul 28 03:29:51 node-4 kernel: [    0.382939] smpboot: Total of 16 processors activated (111764.77 BogoMIPS)
Jul 28 03:29:51 node-4 kernel: [    0.406999] devtmpfs: initialized
Jul 28 03:29:51 node-4 kernel: [    0.410110] EVM: security.selinux
Jul 28 03:29:51 node-4 kernel: [    0.410111] EVM: security.SMACK64
Jul 28 03:29:51 node-4 kernel: [    0.410112] EVM: security.ima
Jul 28 03:29:51 node-4 kernel: [    0.410113] EVM: security.capability
Jul 28 03:29:51 node-4 kernel: [    0.410162] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 28 03:29:51 node-4 kernel: [    0.410831] pinctrl core: initialized pinctrl subsystem
Jul 28 03:29:51 node-4 kernel: [    0.410891] regulator-dummy: no parameters
Jul 28 03:29:51 node-4 kernel: [    0.410922] RTC time:  3:29:15, date: 07/28/16
Jul 28 03:29:51 node-4 kernel: [    0.410955] NET: Registered protocol family 16
Jul 28 03:29:51 node-4 kernel: [    0.411037] cpuidle: using governor ladder
Jul 28 03:29:51 node-4 kernel: [    0.411039] cpuidle: using governor menu
Jul 28 03:29:51 node-4 kernel: [    0.411072] ACPI: bus type PCI registered
Jul 28 03:29:51 node-4 kernel: [    0.411073] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 28 03:29:51 node-4 kernel: [    0.411118] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 28 03:29:51 node-4 kernel: [    0.411121] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 28 03:29:51 node-4 kernel: [    0.424853] PCI: Using configuration type 1 for base access
Jul 28 03:29:51 node-4 kernel: [    0.425856] bio: create slab <bio-0> at 0
Jul 28 03:29:51 node-4 kernel: [    0.426121] ACPI: Added _OSI(Module Device)
Jul 28 03:29:51 node-4 kernel: [    0.426122] ACPI: Added _OSI(Processor Device)
Jul 28 03:29:51 node-4 kernel: [    0.426123] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 28 03:29:51 node-4 kernel: [    0.426124] ACPI: Added _OSI(Processor Aggregator Device)
Jul 28 03:29:51 node-4 kernel: [    0.438813] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 28 03:29:51 node-4 kernel: [    0.449390] ACPI: Interpreter enabled
Jul 28 03:29:51 node-4 kernel: [    0.449395] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 28 03:29:51 node-4 kernel: [    0.449399] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 28 03:29:51 node-4 kernel: [    0.449402] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 28 03:29:51 node-4 kernel: [    0.449408] ACPI: (supports S0 S4 S5)
Jul 28 03:29:51 node-4 kernel: [    0.449410] ACPI: Using IOAPIC for interrupt routing
Jul 28 03:29:51 node-4 kernel: [    0.449456] HEST: Table parsing has been initialized.
Jul 28 03:29:51 node-4 kernel: [    0.449459] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 28 03:29:51 node-4 kernel: [    0.450032] ACPI: No dock devices found.
Jul 28 03:29:51 node-4 kernel: [    0.462083] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 28 03:29:51 node-4 kernel: [    0.462088] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 03:29:51 node-4 kernel: [    0.462091] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 28 03:29:51 node-4 kernel: [    0.462120] PCI host bridge to bus 0000:ff
Jul 28 03:29:51 node-4 kernel: [    0.462122] pci_bus 0000:ff: root bus resource [bus ff]
Jul 28 03:29:51 node-4 kernel: [    0.462130] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462169] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 28 03:29:51 node-4 kernel: [    0.462199] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462235] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462264] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 28 03:29:51 node-4 kernel: [    0.462294] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 28 03:29:51 node-4 kernel: [    0.462325] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462354] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462385] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462413] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462440] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462467] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462495] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462521] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462547] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462574] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462603] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462630] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462657] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 28 03:29:51 node-4 kernel: [    0.462685] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462711] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 28 03:29:51 node-4 kernel: [    0.462736] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462762] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462792] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 28 03:29:51 node-4 kernel: [    0.462827] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462858] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462887] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462918] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462949] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.462980] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463010] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463040] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463072] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463106] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463138] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463171] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463203] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463231] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463259] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463290] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463325] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463365] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463400] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463434] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463464] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463493] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463523] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463554] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463587] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463622] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463654] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463684] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463714] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463743] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463773] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463805] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463838] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463896] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 28 03:29:51 node-4 kernel: [    0.463899] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 03:29:51 node-4 kernel: [    0.463902] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 28 03:29:51 node-4 kernel: [    0.463920] PCI host bridge to bus 0000:7f
Jul 28 03:29:51 node-4 kernel: [    0.463921] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 28 03:29:51 node-4 kernel: [    0.463926] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.463954] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 28 03:29:51 node-4 kernel: [    0.463981] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464010] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464032] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 28 03:29:51 node-4 kernel: [    0.464056] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 28 03:29:51 node-4 kernel: [    0.464081] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464104] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464126] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464148] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464170] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464192] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464216] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464237] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464260] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464285] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464307] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464330] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464352] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 28 03:29:51 node-4 kernel: [    0.464375] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464397] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 28 03:29:51 node-4 kernel: [    0.464420] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464443] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464472] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 28 03:29:51 node-4 kernel: [    0.464504] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464530] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464556] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464583] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464608] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464634] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464659] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464687] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464711] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464737] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464764] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464791] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464820] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464847] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464873] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464903] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464928] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464955] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.464984] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.465012] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.465039] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.465066] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.465091] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.465119] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.465145] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.465172] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.465202] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.465228] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.465251] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.465277] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.465303] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.465333] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.465359] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.466615] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 28 03:29:51 node-4 kernel: [    0.466619] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 03:29:51 node-4 kernel: [    0.467751] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 28 03:29:51 node-4 kernel: [    0.468260] PCI host bridge to bus 0000:00
Jul 28 03:29:51 node-4 kernel: [    0.468262] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 28 03:29:51 node-4 kernel: [    0.468264] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 28 03:29:51 node-4 kernel: [    0.468265] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 28 03:29:51 node-4 kernel: [    0.468267] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 28 03:29:51 node-4 kernel: [    0.468268] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 28 03:29:51 node-4 kernel: [    0.468270] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 28 03:29:51 node-4 kernel: [    0.468271] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 28 03:29:51 node-4 kernel: [    0.468277] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 28 03:29:51 node-4 kernel: [    0.468359] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 28 03:29:51 node-4 kernel: [    0.468389] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 28 03:29:51 node-4 kernel: [    0.468431] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 28 03:29:51 node-4 kernel: [    0.468450] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 28 03:29:51 node-4 kernel: [    0.468480] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 28 03:29:51 node-4 kernel: [    0.468520] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 28 03:29:51 node-4 kernel: [    0.468539] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 28 03:29:51 node-4 kernel: [    0.468568] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 28 03:29:51 node-4 kernel: [    0.468608] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 28 03:29:51 node-4 kernel: [    0.468626] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.468697] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.468776] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.468851] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 28 03:29:51 node-4 kernel: [    0.468856] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 28 03:29:51 node-4 kernel: [    0.468941] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 28 03:29:51 node-4 kernel: [    0.469090] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 28 03:29:51 node-4 kernel: [    0.469108] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 28 03:29:51 node-4 kernel: [    0.469186] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 28 03:29:51 node-4 kernel: [    0.469241] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 28 03:29:51 node-4 kernel: [    0.469264] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 28 03:29:51 node-4 kernel: [    0.469319] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 28 03:29:51 node-4 kernel: [    0.469362] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 28 03:29:51 node-4 kernel: [    0.469391] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 28 03:29:51 node-4 kernel: [    0.469447] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 28 03:29:51 node-4 kernel: [    0.469489] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 28 03:29:51 node-4 kernel: [    0.469514] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 28 03:29:51 node-4 kernel: [    0.469532] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 28 03:29:51 node-4 kernel: [    0.469610] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 28 03:29:51 node-4 kernel: [    0.469659] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 28 03:29:51 node-4 kernel: [    0.469686] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 28 03:29:51 node-4 kernel: [    0.469931] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 28 03:29:51 node-4 kernel: [    0.469937] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 28 03:29:51 node-4 kernel: [    0.469943] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 28 03:29:51 node-4 kernel: [    0.469949] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 28 03:29:51 node-4 kernel: [    0.469956] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 28 03:29:51 node-4 kernel: [    0.469986] pci 0000:01:00.0: supports D1 D2
Jul 28 03:29:51 node-4 kernel: [    0.475611] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 28 03:29:51 node-4 kernel: [    0.475617] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 28 03:29:51 node-4 kernel: [    0.475621] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 28 03:29:51 node-4 kernel: [    0.475835] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 28 03:29:51 node-4 kernel: [    0.475868] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 28 03:29:51 node-4 kernel: [    0.483620] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 28 03:29:51 node-4 kernel: [    0.483626] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 28 03:29:51 node-4 kernel: [    0.483630] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 03:29:51 node-4 kernel: [    0.483704] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 28 03:29:51 node-4 kernel: [    0.483772] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 28 03:29:51 node-4 kernel: [    0.483848] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 28 03:29:51 node-4 kernel: [    0.483893] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 28 03:29:51 node-4 kernel: [    0.483897] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 03:29:51 node-4 kernel: [    0.483899] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 03:29:51 node-4 kernel: [    0.483951] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 28 03:29:51 node-4 kernel: [    0.484078] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 28 03:29:51 node-4 kernel: [    0.484132] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 28 03:29:51 node-4 kernel: [    0.484134] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 03:29:51 node-4 kernel: [    0.484136] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 03:29:51 node-4 kernel: [    0.484185] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 28 03:29:51 node-4 kernel: [    0.484304] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 28 03:29:51 node-4 kernel: [    0.484346] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 28 03:29:51 node-4 kernel: [    0.484466] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 28 03:29:51 node-4 kernel: [    0.484504] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 28 03:29:51 node-4 kernel: [    0.484624] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 28 03:29:51 node-4 kernel: [    0.484684] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 28 03:29:51 node-4 kernel: [    0.484809] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 28 03:29:51 node-4 kernel: [    0.484850] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 28 03:29:51 node-4 kernel: [    0.484853] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 03:29:51 node-4 kernel: [    0.484855] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 03:29:51 node-4 kernel: [    0.484918] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 28 03:29:51 node-4 kernel: [    0.484984] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 28 03:29:51 node-4 kernel: [    0.485038] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 28 03:29:51 node-4 kernel: [    0.485079] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 28 03:29:51 node-4 kernel: [    0.485159] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 28 03:29:51 node-4 kernel: [    0.485271] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 28 03:29:51 node-4 kernel: [    0.485273] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 03:29:51 node-4 kernel: [    0.485275] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 28 03:29:51 node-4 kernel: [    0.485335] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 28 03:29:51 node-4 kernel: [    0.485391] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 28 03:29:51 node-4 kernel: [    0.485439] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 28 03:29:51 node-4 kernel: [    0.485681] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 28 03:29:51 node-4 kernel: [    0.485685] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 28 03:29:51 node-4 kernel: [    0.485750] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 28 03:29:51 node-4 kernel: [    0.485807] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 28 03:29:51 node-4 kernel: [    0.485856] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 28 03:29:51 node-4 kernel: [    0.486065] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 28 03:29:51 node-4 kernel: [    0.486068] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 28 03:29:51 node-4 kernel: [    0.486131] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 28 03:29:51 node-4 kernel: [    0.486191] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 28 03:29:51 node-4 kernel: [    0.486243] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 28 03:29:51 node-4 kernel: [    0.486464] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 28 03:29:51 node-4 kernel: [    0.486467] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 28 03:29:51 node-4 kernel: [    0.486642] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 28 03:29:51 node-4 kernel: [    0.486681] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 28 03:29:51 node-4 kernel: [    0.486761] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 28 03:29:51 node-4 kernel: [    0.486780] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 28 03:29:51 node-4 kernel: [    0.486793] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 28 03:29:51 node-4 kernel: [    0.486806] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 28 03:29:51 node-4 kernel: [    0.486857] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 28 03:29:51 node-4 kernel: [    0.491627] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 28 03:29:51 node-4 kernel: [    0.491636] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 28 03:29:51 node-4 kernel: [    0.491683] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 28 03:29:51 node-4 kernel: [    0.492171] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 28 03:29:51 node-4 kernel: [    0.492175] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 03:29:51 node-4 kernel: [    0.492294] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 28 03:29:51 node-4 kernel: [    0.492403] PCI host bridge to bus 0000:80
Jul 28 03:29:51 node-4 kernel: [    0.492405] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 28 03:29:51 node-4 kernel: [    0.492406] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 28 03:29:51 node-4 kernel: [    0.492408] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 28 03:29:51 node-4 kernel: [    0.492416] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.492477] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.492544] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 28 03:29:51 node-4 kernel: [    0.492606] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 28 03:29:51 node-4 kernel: [    0.492611] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 28 03:29:51 node-4 kernel: [    0.492682] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 28 03:29:51 node-4 kernel: [    0.492978] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 28 03:29:51 node-4 kernel: [    0.493009] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 28 03:29:51 node-4 kernel: [    0.493039] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 28 03:29:51 node-4 kernel: [    0.493068] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 28 03:29:51 node-4 kernel: [    0.493097] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 03:29:51 node-4 kernel: [    0.493127] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 03:29:51 node-4 kernel: [    0.493157] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 03:29:51 node-4 kernel: [    0.493186] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 03:29:51 node-4 kernel: [    0.493271] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 28 03:29:51 node-4 kernel: [    0.493275] ACPI: \_SB_.UNC1: notify handler is installed
Jul 28 03:29:51 node-4 kernel: [    0.493276] ACPI: \_SB_.UNC0: notify handler is installed
Jul 28 03:29:51 node-4 kernel: [    0.493291] ACPI: \_SB_.PCI0: notify handler is installed
Jul 28 03:29:51 node-4 kernel: [    0.493344] ACPI: \_SB_.PCI1: notify handler is installed
Jul 28 03:29:51 node-4 kernel: [    0.493423] Found 4 acpi root devices
Jul 28 03:29:51 node-4 kernel: [    0.493532] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 28 03:29:51 node-4 kernel: [    0.493534] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 28 03:29:51 node-4 kernel: [    0.493536] vgaarb: loaded
Jul 28 03:29:51 node-4 kernel: [    0.493537] vgaarb: bridge control possible 0000:0c:00.0
Jul 28 03:29:51 node-4 kernel: [    0.493653] SCSI subsystem initialized
Jul 28 03:29:51 node-4 kernel: [    0.493717] libata version 3.00 loaded.
Jul 28 03:29:51 node-4 kernel: [    0.493733] ACPI: bus type USB registered
Jul 28 03:29:51 node-4 kernel: [    0.493743] usbcore: registered new interface driver usbfs
Jul 28 03:29:51 node-4 kernel: [    0.493748] usbcore: registered new interface driver hub
Jul 28 03:29:51 node-4 kernel: [    0.493771] usbcore: registered new device driver usb
Jul 28 03:29:51 node-4 kernel: [    0.493945] PCI: Using ACPI for IRQ routing
Jul 28 03:29:51 node-4 kernel: [    0.497556] PCI: pci_cache_line_size set to 64 bytes
Jul 28 03:29:51 node-4 kernel: [    0.497772] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 28 03:29:51 node-4 kernel: [    0.497773] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 28 03:29:51 node-4 kernel: [    0.497774] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 28 03:29:51 node-4 kernel: [    0.497839] NetLabel: Initializing
Jul 28 03:29:51 node-4 kernel: [    0.497841] NetLabel:  domain hash size = 128
Jul 28 03:29:51 node-4 kernel: [    0.497842] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 28 03:29:51 node-4 kernel: [    0.497852] NetLabel:  unlabeled traffic allowed by default
Jul 28 03:29:51 node-4 kernel: [    0.497907] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 28 03:29:51 node-4 kernel: [    0.497911] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 28 03:29:51 node-4 kernel: [    0.499968] Switched to clocksource hpet
Jul 28 03:29:51 node-4 kernel: [    0.503869] AppArmor: AppArmor Filesystem Enabled
Jul 28 03:29:51 node-4 kernel: [    0.503883] pnp: PnP ACPI init
Jul 28 03:29:51 node-4 kernel: [    0.503890] ACPI: bus type PNP registered
Jul 28 03:29:51 node-4 kernel: [    0.504011] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 28 03:29:51 node-4 kernel: [    0.504019] pnp 00:01: [dma 4]
Jul 28 03:29:51 node-4 kernel: [    0.504031] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 28 03:29:51 node-4 kernel: [    0.504057] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 28 03:29:51 node-4 kernel: [    0.504077] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 28 03:29:51 node-4 kernel: [    0.504094] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 28 03:29:51 node-4 kernel: [    0.504127] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 28 03:29:51 node-4 kernel: [    0.504178] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 28 03:29:51 node-4 kernel: [    0.504180] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 28 03:29:51 node-4 kernel: [    0.504182] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 28 03:29:51 node-4 kernel: [    0.504184] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 28 03:29:51 node-4 kernel: [    0.504185] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 28 03:29:51 node-4 kernel: [    0.504190] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 28 03:29:51 node-4 kernel: [    0.504192] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 28 03:29:51 node-4 kernel: [    0.504194] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 28 03:29:51 node-4 kernel: [    0.504195] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 28 03:29:51 node-4 kernel: [    0.504197] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 28 03:29:51 node-4 kernel: [    0.504198] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 28 03:29:51 node-4 kernel: [    0.504200] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 28 03:29:51 node-4 kernel: [    0.504201] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 28 03:29:51 node-4 kernel: [    0.504204] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 28 03:29:51 node-4 kernel: [    0.504287] pnp 00:07: [dma 0 disabled]
Jul 28 03:29:51 node-4 kernel: [    0.504316] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 28 03:29:51 node-4 kernel: [    0.504390] pnp 00:08: [dma 0 disabled]
Jul 28 03:29:51 node-4 kernel: [    0.504422] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 28 03:29:51 node-4 kernel: [    0.504473] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 28 03:29:51 node-4 kernel: [    0.504817] pnp: PnP ACPI: found 10 devices
Jul 28 03:29:51 node-4 kernel: [    0.504819] ACPI: bus type PNP unregistered
Jul 28 03:29:51 node-4 kernel: [    0.511120] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 28 03:29:51 node-4 kernel: [    0.511123] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 28 03:29:51 node-4 kernel: [    0.511126] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 28 03:29:51 node-4 kernel: [    0.511130] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 28 03:29:51 node-4 kernel: [    0.511132] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 03:29:51 node-4 kernel: [    0.511146] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 28 03:29:51 node-4 kernel: [    0.511175] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 28 03:29:51 node-4 kernel: [    0.511193] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 28 03:29:51 node-4 kernel: [    0.511222] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 28 03:29:51 node-4 kernel: [    0.511237] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 28 03:29:51 node-4 kernel: [    0.511266] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 28 03:29:51 node-4 kernel: [    0.511280] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 28 03:29:51 node-4 kernel: [    0.511309] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 28 03:29:51 node-4 kernel: [    0.511310] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 03:29:51 node-4 kernel: [    0.511325] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 03:29:51 node-4 kernel: [    0.511354] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 28 03:29:51 node-4 kernel: [    0.511355] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 03:29:51 node-4 kernel: [    0.511370] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 03:29:51 node-4 kernel: [    0.511399] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 28 03:29:51 node-4 kernel: [    0.511400] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 03:29:51 node-4 kernel: [    0.511403] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 03:29:51 node-4 kernel: [    0.511407] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 28 03:29:51 node-4 kernel: [    0.511409] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 28 03:29:51 node-4 kernel: [    0.511411] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 03:29:51 node-4 kernel: [    0.511415] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 28 03:29:51 node-4 kernel: [    0.511420] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 28 03:29:51 node-4 kernel: [    0.511428] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 28 03:29:51 node-4 kernel: [    0.511431] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 28 03:29:51 node-4 kernel: [    0.511438] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 28 03:29:51 node-4 kernel: [    0.511438] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 28 03:29:51 node-4 kernel: [    0.511439] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 28 03:29:51 node-4 kernel: [    0.511440] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 28 03:29:51 node-4 kernel: [    0.511441] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 28 03:29:51 node-4 kernel: [    0.511442] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 28 03:29:51 node-4 kernel: [    0.511443] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 28 03:29:51 node-4 kernel: [    0.511444] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 28 03:29:51 node-4 kernel: [    0.511445] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 28 03:29:51 node-4 kernel: [    0.511446] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 28 03:29:51 node-4 kernel: [    0.511447] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 28 03:29:51 node-4 kernel: [    0.511447] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 28 03:29:51 node-4 kernel: [    0.511448] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 28 03:29:51 node-4 kernel: [    0.511449] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 28 03:29:51 node-4 kernel: [    0.511450] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 28 03:29:51 node-4 kernel: [    0.511451] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 28 03:29:51 node-4 kernel: [    0.511452] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 28 03:29:51 node-4 kernel: [    0.511453] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 28 03:29:51 node-4 kernel: [    0.511454] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 28 03:29:51 node-4 kernel: [    0.511455] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 28 03:29:51 node-4 kernel: [    0.511456] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 28 03:29:51 node-4 kernel: [    0.511457] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 28 03:29:51 node-4 kernel: [    0.511459] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 28 03:29:51 node-4 kernel: [    0.511460] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 28 03:29:51 node-4 kernel: [    0.511495] NET: Registered protocol family 2
Jul 28 03:29:51 node-4 kernel: [    0.511756] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 28 03:29:51 node-4 kernel: [    0.512097] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 28 03:29:51 node-4 kernel: [    0.512245] TCP: Hash tables configured (established 262144 bind 65536)
Jul 28 03:29:51 node-4 kernel: [    0.512282] TCP: reno registered
Jul 28 03:29:51 node-4 kernel: [    0.512313] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 28 03:29:51 node-4 kernel: [    0.512410] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 28 03:29:51 node-4 kernel: [    0.512559] NET: Registered protocol family 1
Jul 28 03:29:51 node-4 kernel: [    0.552063] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 28 03:29:51 node-4 kernel: [    0.552077] PCI: CLS 64 bytes, default 64
Jul 28 03:29:51 node-4 kernel: [    0.552154] Trying to unpack rootfs image as initramfs...
Jul 28 03:29:51 node-4 kernel: [    0.771474] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 28 03:29:51 node-4 kernel: [    0.771522] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 28 03:29:51 node-4 kernel: [    0.771525] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 28 03:29:51 node-4 kernel: [    0.771949] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 03:29:51 node-4 kernel: [    0.771955] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 03:29:51 node-4 kernel: [    0.771960] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 03:29:51 node-4 kernel: [    0.771966] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 03:29:51 node-4 kernel: [    0.771975] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 03:29:51 node-4 kernel: [    0.771987] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 03:29:51 node-4 kernel: [    0.771996] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 03:29:51 node-4 kernel: [    0.772004] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 03:29:51 node-4 kernel: [    0.772012] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 03:29:51 node-4 kernel: [    0.772021] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 03:29:51 node-4 kernel: [    0.772027] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 03:29:51 node-4 kernel: [    0.772034] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 03:29:51 node-4 kernel: [    0.772041] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 03:29:51 node-4 kernel: [    0.772048] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 03:29:51 node-4 kernel: [    0.772055] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 03:29:51 node-4 kernel: [    0.772062] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 03:29:51 node-4 kernel: [    0.772167] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 28 03:29:51 node-4 kernel: [    0.772170] Scanning for low memory corruption every 60 seconds
Jul 28 03:29:51 node-4 kernel: [    0.772562] Initialise system trusted keyring
Jul 28 03:29:51 node-4 kernel: [    0.772614] audit: initializing netlink socket (disabled)
Jul 28 03:29:51 node-4 kernel: [    0.772631] type=2000 audit(1469676555.728:1): initialized
Jul 28 03:29:51 node-4 kernel: [    0.790499] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 28 03:29:51 node-4 kernel: [    0.792046] zbud: loaded
Jul 28 03:29:51 node-4 kernel: [    0.792165] VFS: Disk quotas dquot_6.5.2
Jul 28 03:29:51 node-4 kernel: [    0.792200] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 28 03:29:51 node-4 kernel: [    0.792577] fuse init (API version 7.22)
Jul 28 03:29:51 node-4 kernel: [    0.792632] msgmni has been set to 32768
Jul 28 03:29:51 node-4 kernel: [    0.792685] Key type big_key registered
Jul 28 03:29:51 node-4 kernel: [    0.793213] Key type asymmetric registered
Jul 28 03:29:51 node-4 kernel: [    0.793214] Asymmetric key parser 'x509' registered
Jul 28 03:29:51 node-4 kernel: [    0.793236] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 28 03:29:51 node-4 kernel: [    0.793304] io scheduler noop registered
Jul 28 03:29:51 node-4 kernel: [    0.793306] io scheduler deadline registered (default)
Jul 28 03:29:51 node-4 kernel: [    0.793323] io scheduler cfq registered
Jul 28 03:29:51 node-4 kernel: [    0.793747] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    0.793887] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    0.794000] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    0.794149] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    0.794260] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    0.794363] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    0.794748] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 28 03:29:51 node-4 kernel: [    0.794773] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 28 03:29:51 node-4 kernel: [    0.794789] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 28 03:29:51 node-4 kernel: [    0.794802] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794804] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794807] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 28 03:29:51 node-4 kernel: [    0.794812] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794813] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794815] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794816] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794818] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794820] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794821] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794822] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794824] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794825] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794826] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794828] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794830] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 28 03:29:51 node-4 kernel: [    0.794835] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794838] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 28 03:29:51 node-4 kernel: [    0.794849] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794852] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 28 03:29:51 node-4 kernel: [    0.794863] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794864] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 28 03:29:51 node-4 kernel: [    0.794868] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 28 03:29:51 node-4 kernel: [    0.794913] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 28 03:29:51 node-4 kernel: [    0.794918] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 28 03:29:51 node-4 kernel: [    0.794922] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 28 03:29:51 node-4 kernel: [    0.794940] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 28 03:29:51 node-4 kernel: [    0.794979] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 28 03:29:51 node-4 kernel: [    0.794981] vesafb: scrolling: redraw
Jul 28 03:29:51 node-4 kernel: [    0.794982] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 28 03:29:51 node-4 kernel: [    0.815584] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 28 03:29:51 node-4 kernel: [    0.824246] Console: switching to colour frame buffer device 80x30
Jul 28 03:29:51 node-4 kernel: [    0.833069] fb0: VESA VGA frame buffer device
Jul 28 03:29:51 node-4 kernel: [    0.833266] intel_idle: MWAIT substates: 0x2120
Jul 28 03:29:51 node-4 kernel: [    0.833267] intel_idle: v0.4 model 0x3F
Jul 28 03:29:51 node-4 kernel: [    0.833267] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 28 03:29:51 node-4 kernel: [    0.833496] ipmi message handler version 39.2
Jul 28 03:29:51 node-4 kernel: [    0.833770] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 28 03:29:51 node-4 kernel: [    0.834207] ACPI: AC Adapter [P111] (on-line)
Jul 28 03:29:51 node-4 kernel: [    0.839481] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 28 03:29:51 node-4 kernel: [    0.850513] ACPI: Power Button [PWRB]
Jul 28 03:29:51 node-4 kernel: [    0.856269] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 28 03:29:51 node-4 kernel: [    0.867896] ACPI: Power Button [PWRF]
Jul 28 03:29:51 node-4 kernel: [    0.885479] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 28 03:29:51 node-4 kernel: [    0.897138] pstore: Registered erst as persistent store backend
Jul 28 03:29:51 node-4 kernel: [    0.903343] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 28 03:29:51 node-4 kernel: [    0.915286] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 28 03:29:51 node-4 kernel: [    0.942030] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 28 03:29:51 node-4 kernel: [    0.975329] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 28 03:29:51 node-4 kernel: [    0.989404] Linux agpgart interface v0.103
Jul 28 03:29:51 node-4 kernel: [    0.997053] brd: module loaded
Jul 28 03:29:51 node-4 kernel: [    1.004080] loop: module loaded
Jul 28 03:29:51 node-4 kernel: [    1.010814] libphy: Fixed MDIO Bus: probed
Jul 28 03:29:51 node-4 kernel: [    1.017298] tun: Universal TUN/TAP device driver, 1.6
Jul 28 03:29:51 node-4 kernel: [    1.023777] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 28 03:29:51 node-4 kernel: [    1.030311] PPP generic driver version 2.4.2
Jul 28 03:29:51 node-4 kernel: [    1.036698] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 28 03:29:51 node-4 kernel: [    1.043158] ehci-pci: EHCI PCI platform driver
Jul 28 03:29:51 node-4 kernel: [    1.049683] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 28 03:29:51 node-4 kernel: [    1.056101] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 28 03:29:51 node-4 kernel: [    1.068639] ehci-pci 0000:00:1a.0: debug port 2
Jul 28 03:29:51 node-4 kernel: [    1.078840] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 28 03:29:51 node-4 kernel: [    1.078857] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 28 03:29:51 node-4 kernel: [    1.095468] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 28 03:29:51 node-4 kernel: [    1.101552] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 28 03:29:51 node-4 kernel: [    1.107732] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 28 03:29:51 node-4 kernel: [    1.119642] usb usb1: Product: EHCI Host Controller
Jul 28 03:29:51 node-4 kernel: [    1.125663] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 28 03:29:51 node-4 kernel: [    1.131715] usb usb1: SerialNumber: 0000:00:1a.0
Jul 28 03:29:51 node-4 kernel: [    1.137668] hub 1-0:1.0: USB hub found
Jul 28 03:29:51 node-4 kernel: [    1.143459] hub 1-0:1.0: 2 ports detected
Jul 28 03:29:51 node-4 kernel: [    1.149242] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 28 03:29:51 node-4 kernel: [    1.154832] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 28 03:29:51 node-4 kernel: [    1.165724] ehci-pci 0000:00:1d.0: debug port 2
Jul 28 03:29:51 node-4 kernel: [    1.175039] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 28 03:29:51 node-4 kernel: [    1.175042] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 28 03:29:51 node-4 kernel: [    1.191386] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 28 03:29:51 node-4 kernel: [    1.196591] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 28 03:29:51 node-4 kernel: [    1.201878] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 28 03:29:51 node-4 kernel: [    1.212621] usb usb2: Product: EHCI Host Controller
Jul 28 03:29:51 node-4 kernel: [    1.218167] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 28 03:29:51 node-4 kernel: [    1.223813] usb usb2: SerialNumber: 0000:00:1d.0
Jul 28 03:29:51 node-4 kernel: [    1.229409] hub 2-0:1.0: USB hub found
Jul 28 03:29:51 node-4 kernel: [    1.234830] hub 2-0:1.0: 2 ports detected
Jul 28 03:29:51 node-4 kernel: [    1.240187] ehci-platform: EHCI generic platform driver
Jul 28 03:29:51 node-4 kernel: [    1.245483] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 28 03:29:51 node-4 kernel: [    1.250860] ohci-pci: OHCI PCI platform driver
Jul 28 03:29:51 node-4 kernel: [    1.256228] ohci-platform: OHCI generic platform driver
Jul 28 03:29:51 node-4 kernel: [    1.261514] uhci_hcd: USB Universal Host Controller Interface driver
Jul 28 03:29:51 node-4 kernel: [    1.266932] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 28 03:29:51 node-4 kernel: [    1.459166] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 28 03:29:51 node-4 kernel: [    1.631382] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 28 03:29:51 node-4 kernel: [    1.636899] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 28 03:29:51 node-4 kernel: [    1.642647] hub 1-1:1.0: USB hub found
Jul 28 03:29:51 node-4 kernel: [    1.648116] hub 1-1:1.0: 6 ports detected
Jul 28 03:29:51 node-4 kernel: [    1.762899] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 28 03:29:51 node-4 kernel: [    1.767451] tsc: Refined TSC clocksource calibration: 3491.845 MHz
Jul 28 03:29:51 node-4 kernel: [    2.031042] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 28 03:29:51 node-4 kernel: [    2.036595] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 28 03:29:51 node-4 kernel: [    2.042435] hub 2-1:1.0: USB hub found
Jul 28 03:29:51 node-4 kernel: [    2.048154] hub 2-1:1.0: 8 ports detected
Jul 28 03:29:51 node-4 kernel: [    2.308670] i8042: No controller found
Jul 28 03:29:51 node-4 kernel: [    2.314091] mousedev: PS/2 mouse device common for all mice
Jul 28 03:29:51 node-4 kernel: [    2.319634] rtc_cmos 00:02: RTC can wake from S4
Jul 28 03:29:51 node-4 kernel: [    2.325224] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 28 03:29:51 node-4 kernel: [    2.326492] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 28 03:29:51 node-4 kernel: [    2.336375] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 28 03:29:51 node-4 kernel: [    2.347461] device-mapper: uevent: version 1.0.3
Jul 28 03:29:51 node-4 kernel: [    2.353099] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 28 03:29:51 node-4 kernel: [    2.364337] ledtrig-cpu: registered to indicate activity on CPUs
Jul 28 03:29:51 node-4 kernel: [    2.370271] TCP: cubic registered
Jul 28 03:29:51 node-4 kernel: [    2.376173] NET: Registered protocol family 10
Jul 28 03:29:51 node-4 kernel: [    2.382160] NET: Registered protocol family 17
Jul 28 03:29:51 node-4 kernel: [    2.387843] Key type dns_resolver registered
Jul 28 03:29:51 node-4 kernel: [    2.393887] Loading compiled-in X.509 certificates
Jul 28 03:29:51 node-4 kernel: [    2.400056] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 28 03:29:51 node-4 kernel: [    2.411437] registered taskstats version 1
Jul 28 03:29:51 node-4 kernel: [    2.419430] Key type trusted registered
Jul 28 03:29:51 node-4 kernel: [    2.427100] Key type encrypted registered
Jul 28 03:29:51 node-4 kernel: [    2.432547] AppArmor: AppArmor sha1 policy hashing enabled
Jul 28 03:29:51 node-4 kernel: [    2.438022] IMA: No TPM chip found, activating TPM-bypass!
Jul 28 03:29:51 node-4 kernel: [    2.444162] regulator-dummy: disabling
Jul 28 03:29:51 node-4 kernel: [    2.449719]   Magic number: 8:352:463
Jul 28 03:29:51 node-4 kernel: [    2.455372] rtc_cmos 00:02: setting system clock to 2016-07-28 03:29:17 UTC (1469676557)
Jul 28 03:29:51 node-4 kernel: [    2.466679] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 28 03:29:51 node-4 kernel: [    2.472384] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 28 03:29:51 node-4 kernel: [    2.483766] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 28 03:29:51 node-4 kernel: [    2.483768] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 28 03:29:51 node-4 kernel: [    2.483768] EDD information not available.
Jul 28 03:29:51 node-4 kernel: [    2.483795] PM: Hibernation image not present or could not be loaded.
Jul 28 03:29:51 node-4 kernel: [    2.501383] usb 2-1.4: Manufacturer: Avocent
Jul 28 03:29:51 node-4 kernel: [    2.501384] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 28 03:29:51 node-4 kernel: [    2.513765] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 28 03:29:51 node-4 kernel: [    2.525087] Write protecting the kernel read-only data: 12288k
Jul 28 03:29:51 node-4 kernel: [    2.531373] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 28 03:29:51 node-4 kernel: [    2.543878] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 28 03:29:51 node-4 kernel: [    2.575962] device-mapper: multipath: version 1.6.0 loaded
Jul 28 03:29:51 node-4 kernel: [    2.583967] systemd-udevd[217]: starting version 204
Jul 28 03:29:51 node-4 kernel: [    2.604933] md: linear personality registered for level -1
Jul 28 03:29:51 node-4 kernel: [    2.618824] md: multipath personality registered for level -4
Jul 28 03:29:51 node-4 kernel: [    2.626792] md: raid0 personality registered for level 0
Jul 28 03:29:51 node-4 kernel: [    2.634882] md: raid1 personality registered for level 1
Jul 28 03:29:51 node-4 kernel: [    2.646629] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 28 03:29:51 node-4 kernel: [    2.652985] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 28 03:29:51 node-4 kernel: [    2.659373] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 28 03:29:51 node-4 kernel: [    2.659382] hidraw: raw HID events driver (C) Jiri Kosina
Jul 28 03:29:51 node-4 kernel: [    2.660150] megasas: FW now in Ready state
Jul 28 03:29:51 node-4 kernel: [    2.660539] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.660700] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.660820] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.660888] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.660995] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.661075] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.661234] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.661344] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.661459] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.661616] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.661747] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.661890] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.661944] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.662094] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.662452] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.662586] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.663207] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 28 03:29:51 node-4 kernel: [    2.694557] usbcore: registered new interface driver usbhid
Jul 28 03:29:51 node-4 kernel: [    2.700893] usbhid: USB HID core driver
Jul 28 03:29:51 node-4 kernel: [    2.701567] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 28 03:29:51 node-4 kernel: [    2.701609] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 28 03:29:51 node-4 kernel: [    2.701614] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 03:29:51 node-4 kernel: [    2.702482] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.702574] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.702763] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.702959] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.703224] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.710255] raid6: sse2x1    1196 MB/s
Jul 28 03:29:51 node-4 kernel: [    2.723319] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 28 03:29:51 node-4 kernel: [    2.723333] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 28 03:29:51 node-4 kernel: [    2.723334] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 03:29:51 node-4 kernel: [    2.724148] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.724288] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.724479] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.724611] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.724898] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.740217] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 28 03:29:51 node-4 kernel: [    2.740218] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 28 03:29:51 node-4 kernel: [    2.740227] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 03:29:51 node-4 kernel: [    2.740436] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.740547] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.740662] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.740789] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.741011] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.753708] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 28 03:29:51 node-4 kernel: [    2.753716] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 28 03:29:51 node-4 kernel: [    2.753717] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 03:29:51 node-4 kernel: [    2.753935] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.754190] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.754324] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.754432] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.754678] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 03:29:51 node-4 kernel: [    2.778355] raid6: sse2x2     750 MB/s
Jul 28 03:29:51 node-4 kernel: [    2.846146] raid6: sse2x4    1351 MB/s
Jul 28 03:29:51 node-4 kernel: [    2.913924] raid6: avx2x1    1490 MB/s
Jul 28 03:29:51 node-4 kernel: [    2.985877] raid6: avx2x2   18854 MB/s
Jul 28 03:29:51 node-4 kernel: [    3.057815] raid6: avx2x4   21310 MB/s
Jul 28 03:29:51 node-4 kernel: [    3.063733] raid6: using algorithm avx2x4 (21310 MB/s)
Jul 28 03:29:51 node-4 kernel: [    3.069816] raid6: using avx2x2 recovery algorithm
Jul 28 03:29:51 node-4 kernel: [    3.075721] Switched to clocksource tsc
Jul 28 03:29:51 node-4 kernel: [    3.077113] megasas:IOC Init cmd success
Jul 28 03:29:51 node-4 kernel: [    3.088151] xor: automatically using best checksumming function:
Jul 28 03:29:51 node-4 kernel: [    3.096228] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Jul 28 03:29:51 node-4 kernel: [    3.098950] megasas: INIT adapter done
Jul 28 03:29:51 node-4 kernel: [    3.113658] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Jul 28 03:29:51 node-4 kernel: [    3.125610] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Jul 28 03:29:51 node-4 kernel: [    3.133780]    avx       : 35618.000 MB/sec
Jul 28 03:29:51 node-4 kernel: [    3.143377] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Jul 28 03:29:51 node-4 kernel: [    3.155189] async_tx: api initialized (async)
Jul 28 03:29:51 node-4 kernel: [    3.155195] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Jul 28 03:29:51 node-4 kernel: [    3.156013] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Jul 28 03:29:51 node-4 kernel: [    3.169894] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 28 03:29:51 node-4 kernel: [    3.171953] scsi0 : LSI SAS based MegaRAID driver
Jul 28 03:29:51 node-4 kernel: [    3.180489] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 28 03:29:51 node-4 kernel: [    3.213543] md: raid6 personality registered for level 6
Jul 28 03:29:51 node-4 kernel: [    3.213759] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 28 03:29:51 node-4 kernel: [    3.232509] md: raid5 personality registered for level 5
Jul 28 03:29:51 node-4 kernel: [    3.239190] md: raid4 personality registered for level 4
Jul 28 03:29:51 node-4 kernel: [    3.246534] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 28 03:29:51 node-4 kernel: [    3.253231] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 28 03:29:51 node-4 kernel: [    3.266924] md: raid10 personality registered for level 10
Jul 28 03:29:51 node-4 kernel: [    3.267145] sd 0:2:0:0: [sda] Write Protect is off
Jul 28 03:29:51 node-4 kernel: [    3.267166] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 28 03:29:51 node-4 kernel: [    3.267584] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 28 03:29:51 node-4 kernel: [    3.301253]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 28 03:29:51 node-4 kernel: [    3.308058] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 28 03:29:51 node-4 kernel: [    3.355559] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Jul 28 03:29:51 node-4 kernel: [    3.451612] random: lvm urandom read with 28 bits of entropy available
Jul 28 03:29:51 node-4 kernel: [    3.570711] bio: create slab <bio-1> at 1
Jul 28 03:29:51 node-4 kernel: [    4.262710] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 03:29:51 node-4 kernel: [    5.011295] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 28 03:29:51 node-4 kernel: [    5.052982] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 28 03:29:51 node-4 kernel: [    5.218908] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 28 03:29:51 node-4 kernel: [    5.278746] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 28 03:29:51 node-4 kernel: [    5.348912] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 03:29:51 node-4 kernel: [    5.404835] random: nonblocking pool is initialized
Jul 28 03:29:51 node-4 kernel: [    5.528234] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 28 03:29:51 node-4 kernel: [    5.559842] XFS (dm-0): Mounting Filesystem
Jul 28 03:29:51 node-4 kernel: [    5.734618] XFS (dm-0): Ending clean mount
Jul 28 03:29:51 node-4 kernel: [    5.783851] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 03:29:51 node-4 kernel: [    5.808162] XFS (dm-1): Mounting Filesystem
Jul 28 03:29:51 node-4 kernel: [    5.919624] XFS (dm-1): Ending clean mount
Jul 28 03:29:51 node-4 kernel: [    7.830921] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 28 03:29:51 node-4 kernel: [    7.858570] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 28 03:29:51 node-4 kernel: [    8.008403] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 28 03:29:51 node-4 kernel: [    8.008414] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 28 03:29:51 node-4 kernel: [    8.008423] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 28 03:29:51 node-4 kernel: [    8.008431] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 28 03:29:51 node-4 kernel: [    8.037009] systemd-udevd[774]: starting version 204
Jul 28 03:29:51 node-4 kernel: [    8.269115] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 28 03:29:51 node-4 kernel: [    8.269121] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 03:29:51 node-4 kernel: [    8.269124] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 28 03:29:51 node-4 kernel: [    8.269126] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 03:29:51 node-4 kernel: [    8.269187] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 28 03:29:51 node-4 kernel: [    8.275140] wmi: Mapper loaded
Jul 28 03:29:51 node-4 kernel: [    8.280303] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 28 03:29:51 node-4 kernel: [    8.281843] IPMI System Interface driver.
Jul 28 03:29:51 node-4 kernel: [    8.281868] ipmi_si: probing via ACPI
Jul 28 03:29:51 node-4 kernel: [    8.281880] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 28 03:29:51 node-4 kernel: [    8.281881] ipmi_si: Adding ACPI-specified kcs state machine
Jul 28 03:29:51 node-4 kernel: [    8.281906] ipmi_si: probing via SMBIOS
Jul 28 03:29:51 node-4 kernel: [    8.281907] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 28 03:29:51 node-4 kernel: [    8.281908] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 28 03:29:51 node-4 kernel: [    8.281910] ipmi_si: probing via SPMI
Jul 28 03:29:51 node-4 kernel: [    8.281911] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 28 03:29:51 node-4 kernel: [    8.281912] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 28 03:29:51 node-4 kernel: [    8.281914] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 28 03:29:51 node-4 kernel: [    8.297077] power_meter ACPI000D:00: Found ACPI power meter.
Jul 28 03:29:51 node-4 kernel: [    8.297106] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 28 03:29:51 node-4 kernel: [    8.349661] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 28 03:29:51 node-4 kernel: [    8.349667] ipmi_si 00:09: IPMI kcs interface initialized
Jul 28 03:29:51 node-4 kernel: [    8.393676] systemd-udevd[800]: renamed network interface eth2 to enp8s0
Jul 28 03:29:51 node-4 kernel: [    8.417542] systemd-udevd[798]: renamed network interface eth0 to enp6s0
Jul 28 03:29:51 node-4 kernel: [    8.441538] systemd-udevd[819]: renamed network interface eth3 to enp9s0
Jul 28 03:29:51 node-4 kernel: [    8.465472] systemd-udevd[815]: renamed network interface eth1 to enp7s0
Jul 28 03:29:51 node-4 kernel: [    8.789067] type=1400 audit(1469676563.836:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1048 comm="apparmor_parser"
Jul 28 03:29:51 node-4 kernel: [    8.789318] type=1400 audit(1469676563.836:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1048 comm="apparmor_parser"
Jul 28 03:29:51 node-4 kernel: [    8.789535] type=1400 audit(1469676563.836:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1048 comm="apparmor_parser"
Jul 28 03:29:51 node-4 kernel: [    8.794807] type=1400 audit(1469676563.840:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1044 comm="apparmor_parser"
Jul 28 03:29:51 node-4 kernel: [    8.794949] type=1400 audit(1469676563.840:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1044 comm="apparmor_parser"
Jul 28 03:29:51 node-4 kernel: [    8.795070] type=1400 audit(1469676563.840:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1044 comm="apparmor_parser"
Jul 28 03:29:51 node-4 kernel: [    8.796926] type=1400 audit(1469676563.844:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1045 comm="apparmor_parser"
Jul 28 03:29:51 node-4 kernel: [    8.797069] type=1400 audit(1469676563.844:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1045 comm="apparmor_parser"
Jul 28 03:29:51 node-4 kernel: [    8.797192] type=1400 audit(1469676563.844:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1045 comm="apparmor_parser"
Jul 28 03:29:51 node-4 kernel: [    8.804361] type=1400 audit(1469676563.848:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1046 comm="apparmor_parser"
Jul 28 03:29:51 node-4 kernel: [    9.321169] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 28 03:29:51 node-4 kernel: [    9.336325] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 28 03:29:51 node-4 kernel: [    9.509762] enic 0000:06:00.0 enp6s0: Link UP
Jul 28 03:29:51 node-4 kernel: [    9.510787] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 28 03:29:51 node-4 kernel: [    9.510792] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 28 03:29:51 node-4 kernel: [   18.841604] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 28 03:29:52 node-4 failsafe: Failsafe of 120 seconds reached.
Jul 28 03:29:52 node-4 kernel: [   37.450684] init: failsafe main process (8393) killed by TERM signal
Jul 28 03:29:52 node-4 dbus[8425]: [system] AppArmor D-Bus mediation is enabled
Jul 28 03:29:53 node-4 kernel: [   37.714011] audit_printk_skb: 30 callbacks suppressed
Jul 28 03:29:53 node-4 kernel: [   37.714012] type=1400 audit(1469676593.075:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8522 comm="apparmor_parser"
Jul 28 03:29:53 node-4 kernel: [   37.717855] type=1400 audit(1469676593.079:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8521 comm="apparmor_parser"
Jul 28 03:29:53 node-4 kernel: [   37.717859] type=1400 audit(1469676593.079:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8521 comm="apparmor_parser"
Jul 28 03:29:53 node-4 kernel: [   37.717862] type=1400 audit(1469676593.079:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8521 comm="apparmor_parser"
Jul 28 03:29:53 node-4 kernel: [   37.718083] type=1400 audit(1469676593.079:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8521 comm="apparmor_parser"
Jul 28 03:29:53 node-4 kernel: [   37.718085] type=1400 audit(1469676593.079:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8521 comm="apparmor_parser"
Jul 28 03:29:53 node-4 kernel: [   37.718197] type=1400 audit(1469676593.079:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8521 comm="apparmor_parser"
Jul 28 03:29:53 node-4 kernel: [   37.818514] type=1400 audit(1469676593.179:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8524 comm="apparmor_parser"
Jul 28 03:29:53 node-4 anacron[8588]: Anacron 2.3 started on 2016-07-28
Jul 28 03:29:53 node-4 cron[8553]: (CRON) INFO (pidfile fd = 3)
Jul 28 03:29:53 node-4 anacron[8588]: Will run job `cron.daily' in 5 min.
Jul 28 03:29:53 node-4 anacron[8588]: Will run job `cron.weekly' in 10 min.
Jul 28 03:29:53 node-4 anacron[8588]: Will run job `cron.monthly' in 15 min.
Jul 28 03:29:53 node-4 anacron[8588]: Jobs will be executed sequentially
Jul 28 03:29:53 node-4 cron[8591]: (CRON) STARTUP (fork ok)
Jul 28 03:29:53 node-4 cron[8591]: (CRON) INFO (Running @reboot jobs)
Jul 28 03:29:53 node-4 multipathd: path checkers start up
Jul 28 03:29:53 node-4 postfix/master[8732]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 28 03:29:56 node-4 puppet-agent[8916]: Reopening log files
Jul 28 03:29:58 node-4 puppet-agent[8916]: Could not request certificate: Connection refused - connect(2)
Jul 28 03:30:01 node-4 CRON[8947]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 28 03:30:07 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 03:30:07 node-4 nailgun-agent: D, [2016-07-28T03:30:01.569553 #8950] DEBUG -- : Sleep for 6 seconds before sending request
Jul 28 03:30:07 node-4 nailgun-agent: I, [2016-07-28T03:30:07.593084 #8950]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 28 03:30:08 node-4 nailgun-agent: D, [2016-07-28T03:30:08.343176 #8950] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 28 03:30:10 node-4 puppet-user[9135]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 28 03:30:10 node-4 puppet-user[9135]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 28 03:30:11 node-4 puppet-user[9135]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 28 03:30:11 node-4 puppet-user[9135]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 28 03:30:11 node-4 puppet-user[9135]: Finished catalog run in 0.38 seconds
Jul 28 03:30:12 node-4 multipathd: uevent trigger error
Jul 28 03:30:12 node-4 puppet-user[9560]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 28 03:30:12 node-4 puppet-user[9560]: Compiled catalog for node-4.domain.tld in environment production in 0.08 seconds
Jul 28 03:30:12 node-4 puppet-user[9560]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 28 03:30:12 node-4 puppet-user[9560]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 28 03:30:12 node-4 puppet-user[9560]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Jul 28 03:30:12 node-4 puppet-user[9560]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 28 03:30:12 node-4 puppet-user[9560]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 28 03:30:12 node-4 puppet-user[9560]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 28 03:30:12 node-4 puppet-user[9560]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 28 03:30:12 node-4 puppet-user[9560]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 28 03:30:12 node-4 puppet-user[9560]: Finished catalog run in 0.05 seconds
Jul 28 03:30:14 node-4 puppet-user[10022]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 28 03:30:14 node-4 puppet-user[10022]: Compiled catalog for node-4.domain.tld in environment production in 0.09 seconds
Jul 28 03:30:14 node-4 puppet-user[10022]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 28 03:30:14 node-4 puppet-user[10022]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 28 03:30:14 node-4 puppet-user[10022]: Finished catalog run in 0.02 seconds
Jul 28 03:30:16 node-4 puppet-user[10614]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 28 03:30:16 node-4 puppet-user[10614]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Jul 28 03:30:16 node-4 puppet-user[10614]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 28 03:30:16 node-4 puppet-user[10614]: Finished catalog run in 0.03 seconds
Jul 28 03:30:17 node-4 puppet-user[11075]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 28 03:30:17 node-4 puppet-user[11075]: Compiled catalog for node-4.domain.tld in environment production in 0.19 seconds
Jul 28 03:30:18 node-4 puppet-user[11075]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 28 03:30:18 node-4 puppet-user[11075]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Jul 28 03:30:18 node-4 puppet-user[11075]: Finished catalog run in 0.47 seconds
Jul 28 03:30:19 node-4 puppet-user[11559]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 28 03:30:19 node-4 puppet-user[11559]: Compiled catalog for node-4.domain.tld in environment production in 0.23 seconds
Jul 28 03:30:20 node-4 puppet-user[11559]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 28 03:30:20 node-4 puppet-user[11559]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 28 03:30:20 node-4 puppet-user[11559]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.340880 #8950] DEBUG -- : Trying to find block devices
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.340947 #8950] DEBUG -- : Found block device: sda
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.340995 #8950] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.341020 #8950] DEBUG -- : Trying to get list of physical devices
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.341231 #8950] DEBUG -- : Getting udev properties for device: sda
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.342986 #8950] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc7880
Jul 28 03:30:20 node-4 nailgun-agent: a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63324", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.343015 #8950] DEBUG -- : Trying to find out if device sda is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.343058 #8950] DEBUG -- : Device sda removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.343094 #8950] DEBUG -- : Device sda seems to be appropriate
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.343530 #8950] DEBUG -- : Getting udev properties for device: dm-0
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.345107 #8950] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-RFM9CdYOL8VpbI7gP0nDSQrR57jp2yUdVIzM67ed8581vlLkxOtopgXMeUYS8XRI /dev/disk/by-uuid/23c10d3d-48a0-4a5c-bf2e-9921e0bd7629 /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-RFM9CdYOL8VpbI7gP0nDSQrR57jp2yUdVIzM67ed8581vlLkxOtopgXMeUYS8XRI", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"23c10d3d-48a0-4a5c-bf2e-9921e0bd7629", "ID_FS_UUID_ENC"=>"23c10d3d-48a0-4a5c-bf2e-9921e0bd7629", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"29354", "nomdmonddf"=>"1", "nomd
Jul 28 03:30:20 node-4 nailgun-agent: monisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.345147 #8950] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.345178 #8950] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.345191 #8950] DEBUG -- : Device dm-0 seems to be appropriate
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.345205 #8950] DEBUG -- : Getting udev properties for device: dm-1
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.346739 #8950] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-rTnI01LVjQ0PSrUYHzG1zA4oGXeXpY6VI5XmqSgL0pDjAjIfvOAatMxE1R8cIZw8 /dev/disk/by-uuid/84511159-ea2c-4fc9-8076-91aa6cf58a0e /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-rTnI01LVjQ0PSrUYHzG1zA4oGXeXpY6VI5XmqSgL0pDjAjIfvOAatMxE1R8cIZw8", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"84511159-ea2c-4fc9-8076-91aa6cf58a0e", "ID_FS_UUID_ENC"=>"84511159-ea2c-4fc9-8076-91aa6cf58a0e", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"74
Jul 28 03:30:20 node-4 nailgun-agent: 776", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.346768 #8950] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.346802 #8950] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.346827 #8950] DEBUG -- : Device dm-1 seems to be appropriate
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.346871 #8950] DEBUG -- : Getting udev properties for device: dm-2
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.348418 #8950] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-GrUMzLqLdloCWqUPkhbrRDx5bc4PJUu5uVZdXcD4bfGNuv0lFsqYln3GgPzXa9e3 /dev/disk/by-uuid/34176794-b1c6-4c18-a0be-e505e51bf3b6 /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-GrUMzLqLdloCWqUPkhbrRDx5bc4PJUu5uVZdXcD4bfGNuv0lFsqYln3GgPzXa9e3", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"34176794-b1c6-4c18-a0be-e505e51bf3b6", "ID_FS_UUID_ENC"=>"34176794-b1c6-4c18-a0be-e505e51bf3b6", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82817", "nomdmond
Jul 28 03:30:20 node-4 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.348447 #8950] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.348509 #8950] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.348524 #8950] DEBUG -- : Device dm-2 seems to be appropriate
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.348538 #8950] DEBUG -- : Getting udev properties for device: dm-3
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.350084 #8950] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-RQZNJOJv7Y1Oe9RIKvhJwfGtCkSiOxoAJANGDE2xKImOndAK1ShxElu6uWGcupSn /dev/disk/by-uuid/bf2796be-b1c5-4308-be82-da9444461f8a /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-RQZNJOJv7Y1Oe9RIKvhJwfGtCkSiOxoAJANGDE2xKImOndAK1ShxElu6uWGcupSn", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"bf2796be-b1c5-4308-be82-da9444461f8a", "ID_FS_UUID_ENC"=>"bf2796be-b1c5-4308-be82-da9444461f8a", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86693", "nomdmonddf"=>"1", 
Jul 28 03:30:20 node-4 nailgun-agent: "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.350112 #8950] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.350143 #8950] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.350157 #8950] DEBUG -- : Device dm-3 seems to be appropriate
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.350174 #8950] DEBUG -- : Getting udev properties for device: dm-4
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.351799 #8950] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-YtSJSuy75D2rBnRuB1rNmrE8ib29FvYVwqYMTmBxjnRR90eos4ASMxEzndHL3a0J /dev/disk/by-uuid/e3c97571-97d9-4932-92e3-59f8bed02a1a /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-YtSJSuy75D2rBnRuB1rNmrE8ib29FvYVwqYMTmBxjnRR90eos4ASMxEzndHL3a0J", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"e3c97571-97d9-4932-92e3-59f8bed02a1a", "ID_FS_UUID_ENC"=>"e3c97571-97d9-4932-92e3-59f8bed02a1a", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97904", "nomdmonddf"=>"1", "nomd
Jul 28 03:30:20 node-4 nailgun-agent: monisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.351836 #8950] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.351867 #8950] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.351881 #8950] DEBUG -- : Device dm-4 seems to be appropriate
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.351910 #8950] DEBUG -- : Getting udev properties for device: dm-5
Jul 28 03:30:20 node-4 puppet-user[11559]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.353522 #8950] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-YtSJSuy75D2rBnRuB1rNmrE8ib29FvYVEZ1c5TMDit2YW1pdVl40Ke0ne8LbSRgq /dev/disk/by-uuid/dd33c636-b21a-4921-a7bb-5cbe3bfd1103 /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-YtSJSuy75D2rBnRuB1rNmrE8ib29FvYVEZ1c5TMDit2YW1pdVl40Ke0ne8LbSRgq", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"dd33c636-b21a-4921-a7bb-5cbe3bfd1103", "ID_FS_UUID_ENC"=>"dd33c636-b21a-4921-a7bb-5cbe3bfd1103", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98241", "nomdmonddf"=>"1", "nomdmonisw"
Jul 28 03:30:20 node-4 nailgun-agent: =>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.353561 #8950] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.353606 #8950] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.353621 #8950] DEBUG -- : Device dm-5 seems to be appropriate
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.353636 #8950] DEBUG -- : Getting udev properties for device: ram0
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.355105 #8950] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47365", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.355131 #8950] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.355174 #8950] DEBUG -- : Device ram0 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.355194 #8950] DEBUG -- : Getting udev properties for device: ram1
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.356638 #8950] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47373", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.356673 #8950] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.356711 #8950] DEBUG -- : Device ram1 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.356732 #8950] DEBUG -- : Getting udev properties for device: ram2
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.358148 #8950] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47438", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.358176 #8950] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.358212 #8950] DEBUG -- : Device ram2 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.358232 #8950] DEBUG -- : Getting udev properties for device: ram3
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.359619 #8950] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47447", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.359654 #8950] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.359693 #8950] DEBUG -- : Device ram3 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.359712 #8950] DEBUG -- : Getting udev properties for device: ram4
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.361105 #8950] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47456", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.361127 #8950] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.361159 #8950] DEBUG -- : Device ram4 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.361177 #8950] DEBUG -- : Getting udev properties for device: ram5
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.362565 #8950] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47465", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.362586 #8950] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.362618 #8950] DEBUG -- : Device ram5 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.362638 #8950] DEBUG -- : Getting udev properties for device: ram6
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.364023 #8950] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47474", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.364045 #8950] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.364091 #8950] DEBUG -- : Device ram6 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.364110 #8950] DEBUG -- : Getting udev properties for device: ram7
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.365486 #8950] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47483", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.365515 #8950] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.365562 #8950] DEBUG -- : Device ram7 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.365579 #8950] DEBUG -- : Getting udev properties for device: ram8
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.366964 #8950] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47492", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.366984 #8950] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.367017 #8950] DEBUG -- : Device ram8 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.367036 #8950] DEBUG -- : Getting udev properties for device: ram9
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.368408 #8950] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47502", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.368445 #8950] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.368481 #8950] DEBUG -- : Device ram9 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.368512 #8950] DEBUG -- : Getting udev properties for device: loop0
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.369900 #8950] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47296", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.369930 #8950] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.369966 #8950] DEBUG -- : Device loop0 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.369984 #8950] DEBUG -- : Getting udev properties for device: loop1
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.371336 #8950] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47306", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.371357 #8950] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.371387 #8950] DEBUG -- : Device loop1 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.371414 #8950] DEBUG -- : Getting udev properties for device: loop2
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.372835 #8950] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47313", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.372889 #8950] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.372920 #8950] DEBUG -- : Device loop2 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.372939 #8950] DEBUG -- : Getting udev properties for device: loop3
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.374365 #8950] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47322", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.374397 #8950] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.374427 #8950] DEBUG -- : Device loop3 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.374472 #8950] DEBUG -- : Getting udev properties for device: loop4
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.375900 #8950] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47331", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.375921 #8950] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.375958 #8950] DEBUG -- : Device loop4 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.375994 #8950] DEBUG -- : Getting udev properties for device: loop5
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.377364 #8950] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47338", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.377401 #8950] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.377430 #8950] DEBUG -- : Device loop5 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.377460 #8950] DEBUG -- : Getting udev properties for device: loop6
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.378826 #8950] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47348", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.378847 #8950] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.378878 #8950] DEBUG -- : Device loop6 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.378897 #8950] DEBUG -- : Getting udev properties for device: loop7
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.380303 #8950] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47357", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.380325 #8950] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.380356 #8950] DEBUG -- : Device loop7 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.380386 #8950] DEBUG -- : Getting udev properties for device: ram10
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.387536 #8950] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47381", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.387565 #8950] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.387602 #8950] DEBUG -- : Device ram10 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.387621 #8950] DEBUG -- : Getting udev properties for device: ram11
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.389163 #8950] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47391", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.389185 #8950] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.389218 #8950] DEBUG -- : Device ram11 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.389235 #8950] DEBUG -- : Getting udev properties for device: ram12
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.390592 #8950] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47400", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.390612 #8950] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.390648 #8950] DEBUG -- : Device ram12 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.390666 #8950] DEBUG -- : Getting udev properties for device: ram13
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.392030 #8950] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47409", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.392051 #8950] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.392089 #8950] DEBUG -- : Device ram13 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.392106 #8950] DEBUG -- : Getting udev properties for device: ram14
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.393438 #8950] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47420", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.393487 #8950] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.393524 #8950] DEBUG -- : Device ram14 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.393541 #8950] DEBUG -- : Getting udev properties for device: ram15
Jul 28 03:30:20 node-4 puppet-user[11559]: Finished catalog run in 0.26 seconds
Jul 28 03:30:20 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.394893 #8950] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47429", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.394913 #8950] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.394940 #8950] DEBUG -- : Device ram15 removable parameter: "0"
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395003 #8950] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395017 #8950] DEBUG -- : Block device seems to be physical data storage: sda
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395052 #8950] DEBUG -- : Found block device: dm-0
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395066 #8950] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395080 #8950] DEBUG -- : Found block device: dm-1
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395103 #8950] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395113 #8950] DEBUG -- : Found block device: dm-2
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395122 #8950] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395131 #8950] DEBUG -- : Found block device: dm-3
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395142 #8950] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395174 #8950] DEBUG -- : Found block device: dm-4
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395183 #8950] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395193 #8950] DEBUG -- : Found block device: dm-5
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395203 #8950] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395211 #8950] DEBUG -- : Found block device: ram0
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395221 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395230 #8950] DEBUG -- : Found block device: ram1
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395240 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395248 #8950] DEBUG -- : Found block device: ram2
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395258 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395294 #8950] DEBUG -- : Found block device: ram3
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395306 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395314 #8950] DEBUG -- : Found block device: ram4
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395324 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395333 #8950] DEBUG -- : Found block device: ram5
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395344 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395352 #8950] DEBUG -- : Found block device: ram6
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395363 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395372 #8950] DEBUG -- : Found block device: ram7
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395382 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395416 #8950] DEBUG -- : Found block device: ram8
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395426 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395435 #8950] DEBUG -- : Found block device: ram9
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395445 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395453 #8950] DEBUG -- : Found block device: loop0
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395463 #8950] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395471 #8950] DEBUG -- : Found block device: loop1
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395482 #8950] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395490 #8950] DEBUG -- : Found block device: loop2
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395500 #8950] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395542 #8950] DEBUG -- : Found block device: loop3
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395554 #8950] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395563 #8950] DEBUG -- : Found block device: loop4
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395576 #8950] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395584 #8950] DEBUG -- : Found block device: loop5
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395594 #8950] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395603 #8950] DEBUG -- : Found block device: loop6
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395612 #8950] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395621 #8950] DEBUG -- : Found block device: loop7
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395631 #8950] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395672 #8950] DEBUG -- : Found block device: ram10
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395681 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395690 #8950] DEBUG -- : Found block device: ram11
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395699 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395708 #8950] DEBUG -- : Found block device: ram12
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395718 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395727 #8950] DEBUG -- : Found block device: ram13
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395737 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395746 #8950] DEBUG -- : Found block device: ram14
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395789 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395799 #8950] DEBUG -- : Found block device: ram15
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395809 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.395837 #8950] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.467425 #8950] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 28 03:30:20 node-4 nailgun-agent: D, [2016-07-28T03:30:20.467492 #8950] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 28 03:30:21 node-4 puppet-user[12227]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 28 03:30:22 node-4 puppet-user[12227]: Compiled catalog for node-4.domain.tld in environment production in 0.17 seconds
Jul 28 03:30:22 node-4 puppet-user[12227]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 28 03:30:22 node-4 kernel: [   66.911239] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 28 03:30:22 node-4 kernel: [   66.911295] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Jul 28 03:30:22 node-4 puppet-user[12227]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Jul 28 03:30:22 node-4 puppet-user[12227]: Finished catalog run in 0.06 seconds
Jul 28 03:30:23 node-4 puppet-user[12688]: (Scope(Class[main])) MODULAR: sync_time
Jul 28 03:30:23 node-4 puppet-user[12688]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Jul 28 03:30:24 node-4 ntpdate[13109]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 28 03:30:30 node-4 ntpdate[13109]: adjust time server 10.20.0.2 offset 0.000161 sec
Jul 28 03:30:30 node-4 puppet-user[12688]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 28 03:30:30 node-4 puppet-user[12688]: Finished catalog run in 6.18 seconds
Jul 28 03:30:32 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.374912 #8950] DEBUG -- : Trying to find block devices
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375003 #8950] DEBUG -- : Found block device: sda
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375052 #8950] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375072 #8950] DEBUG -- : Block device seems to be physical data storage: sda
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375094 #8950] DEBUG -- : Found block device: dm-0
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375107 #8950] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375119 #8950] DEBUG -- : Found block device: dm-1
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375131 #8950] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375141 #8950] DEBUG -- : Found block device: dm-2
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375152 #8950] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375176 #8950] DEBUG -- : Found block device: dm-3
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375188 #8950] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375208 #8950] DEBUG -- : Found block device: dm-4
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375218 #8950] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375228 #8950] DEBUG -- : Found block device: dm-5
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375238 #8950] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375247 #8950] DEBUG -- : Found block device: ram0
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375268 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375278 #8950] DEBUG -- : Found block device: ram1
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375288 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375297 #8950] DEBUG -- : Found block device: ram2
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375319 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375328 #8950] DEBUG -- : Found block device: ram3
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375338 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375347 #8950] DEBUG -- : Found block device: ram4
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375369 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375378 #8950] DEBUG -- : Found block device: ram5
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375388 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375397 #8950] DEBUG -- : Found block device: ram6
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375416 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375426 #8950] DEBUG -- : Found block device: ram7
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375436 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375444 #8950] DEBUG -- : Found block device: ram8
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375463 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375472 #8950] DEBUG -- : Found block device: ram9
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375482 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375490 #8950] DEBUG -- : Found block device: loop0
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375510 #8950] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375519 #8950] DEBUG -- : Found block device: loop1
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375528 #8950] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375553 #8950] DEBUG -- : Found block device: loop2
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375563 #8950] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375572 #8950] DEBUG -- : Found block device: loop3
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375581 #8950] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375591 #8950] DEBUG -- : Found block device: loop4
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375600 #8950] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375608 #8950] DEBUG -- : Found block device: loop5
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375640 #8950] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375650 #8950] DEBUG -- : Found block device: loop6
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375660 #8950] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375668 #8950] DEBUG -- : Found block device: loop7
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375677 #8950] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375686 #8950] DEBUG -- : Found block device: ram10
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375695 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375704 #8950] DEBUG -- : Found block device: ram11
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375713 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375722 #8950] DEBUG -- : Found block device: ram12
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375754 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375763 #8950] DEBUG -- : Found block device: ram13
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375772 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375780 #8950] DEBUG -- : Found block device: ram14
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375789 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375797 #8950] DEBUG -- : Found block device: ram15
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375806 #8950] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.375835 #8950] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Jul 28 03:30:32 node-4 nailgun-agent: D, [2016-07-28T03:30:32.499146 #8950] DEBUG -- : Response: status: 200 body: {"id": 4}
Jul 28 03:30:32 node-4 nailgun-agent: I, [2016-07-28T03:30:32.499306 #8950]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 28 03:30:35 node-4 puppet-user[13597]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 28 03:30:35 node-4 puppet-user[13597]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Jul 28 03:30:35 node-4 puppet-user[13597]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 28 03:30:35 node-4 puppet-user[13597]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Jul 28 03:30:35 node-4 puppet-user[13597]: Finished catalog run in 0.06 seconds
Jul 28 03:30:36 node-4 puppet-user[14055]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 28 03:30:37 node-4 puppet-user[14055]: Compiled catalog for node-4.domain.tld in environment production in 1.21 seconds
Jul 28 03:30:38 node-4 puppet-user[14055]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Jul 28 03:30:38 node-4 puppet-user[14055]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Jul 28 03:30:38 node-4 puppet-user[14055]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Jul 28 03:30:38 node-4 puppet-user[14055]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 28 03:30:38 node-4 puppet-user[14055]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Jul 28 03:30:38 node-4 puppet-user[14055]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 28 03:30:38 node-4 puppet-user[14055]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 28 03:30:38 node-4 kernel: [   82.868834] init: plymouth-upstart-bridge main process ended, respawning
Jul 28 03:30:38 node-4 puppet-user[14055]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 28 03:30:38 node-4 puppet-user[14055]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 28 03:30:38 node-4 puppet-user[14055]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 28 03:30:38 node-4 puppet-user[14055]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 28 03:30:38 node-4 puppet-user[14055]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 28 03:30:38 node-4 puppet-user[14055]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 28 03:30:38 node-4 puppet-user[14055]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Jul 28 03:30:38 node-4 puppet-user[14055]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 28 03:30:38 node-4 puppet-user[14055]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 28 03:30:38 node-4 puppet-agent[8916]: Could not run: SIGTERM
Jul 28 03:30:38 node-4 kernel: [   83.134826] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 28 03:30:38 node-4 ec2: 
Jul 28 03:30:38 node-4 ec2: #############################################################
Jul 28 03:30:38 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 28 03:30:38 node-4 ec2: 1024 48:c1:a7:56:22:e8:ed:45:9f:9e:84:ac:1d:53:43:08  root@node-4.domain.tld (DSA)
Jul 28 03:30:38 node-4 ec2: 256 31:1e:a5:4f:a5:18:79:de:ad:84:79:8f:94:89:17:85  root@node-4.domain.tld (ECDSA)
Jul 28 03:30:38 node-4 ec2: 256 88:4d:59:6a:cf:2f:8a:c1:07:04:8e:6e:31:6a:d3:0b  root@node-4.domain.tld (ED25519)
Jul 28 03:30:38 node-4 ec2: 2048 1b:a4:8e:d4:45:9b:e9:ef:0e:e8:df:6b:65:c8:ab:fb  root@node-4.domain.tld (RSA)
Jul 28 03:30:38 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 28 03:30:38 node-4 ec2: #############################################################
Jul 28 03:30:51 node-4 puppet-user[14055]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 28 03:30:52 node-4 puppet-user[14055]: Finished catalog run in 13.93 seconds
Jul 28 03:30:53 node-4 puppet-user[15257]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 28 03:30:53 node-4 puppet-user[15257]: Compiled catalog for node-4.domain.tld in environment production in 0.13 seconds
Jul 28 03:30:58 node-4 puppet-user[15257]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 28 03:31:01 node-4 CRON[16280]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 28 03:31:29 node-4 puppet-user[15257]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 28 03:31:29 node-4 puppet-user[15257]: Finished catalog run in 35.63 seconds
Jul 28 03:31:29 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 03:31:29 node-4 nailgun-agent: I, [2016-07-28T03:31:29.672879 #16283]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 28 03:31:31 node-4 puppet-user[17868]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 28 03:31:31 node-4 puppet-user[17868]: Compiled catalog for node-4.domain.tld in environment production in 0.56 seconds
Jul 28 03:31:32 node-4 puppet-user[17868]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 28 03:31:32 node-4 puppet-user[17868]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 28 03:31:32 node-4 puppet-user[17868]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 28 03:31:32 node-4 puppet-user[17868]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 28 03:31:32 node-4 puppet-user[17868]: Finished catalog run in 0.08 seconds
Jul 28 03:31:33 node-4 puppet-user[18355]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 28 03:31:34 node-4 puppet-user[18355]: Compiled catalog for node-4.domain.tld in environment production in 1.02 seconds
Jul 28 03:31:35 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 28 03:31:35 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 28 03:31:35 node-4 crontab[18791]: (root) LIST (root)
Jul 28 03:31:35 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 28 03:31:35 node-4 crontab[18794]: (root) REPLACE (root)
Jul 28 03:31:37 node-4 puppet-user[18355]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 28 03:31:38 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 28 03:31:39 node-4 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 28 03:31:39 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8367" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 03:31:39 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 28 03:31:41 node-4 multipathd: uevent trigger error
<27>Jul 28 03:31:41 node-4 multipathd: uevent trigger error
<27>Jul 28 03:31:41 node-4 multipathd: uevent trigger error
<27>Jul 28 03:31:41 node-4 multipathd: uevent trigger error
<27>Jul 28 03:31:41 node-4 multipathd: uevent trigger error
<27>Jul 28 03:31:59 node-4 multipathd: uevent trigger error
<27>Jul 28 03:31:59 node-4 multipathd: uevent trigger error
<27>Jul 28 03:31:59 node-4 multipathd: uevent trigger error
<27>Jul 28 03:31:59 node-4 multipathd: uevent trigger error
<27>Jul 28 03:32:02 node-4 multipathd: uevent trigger error
<27>Jul 28 03:32:02 node-4 multipathd: uevent trigger error
<27>Jul 28 03:32:02 node-4 multipathd: uevent trigger error
<27>Jul 28 03:32:02 node-4 multipathd: uevent trigger error
<27>Jul 28 03:32:02 node-4 multipathd: uevent trigger error
<27>Jul 28 03:32:05 node-4 multipathd: uevent trigger error
<27>Jul 28 03:32:05 node-4 multipathd: uevent trigger error
<27>Jul 28 03:32:05 node-4 multipathd: uevent trigger error
<27>Jul 28 03:32:05 node-4 multipathd: uevent trigger error
<27>Jul 28 03:32:05 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:05 node-4 ntpdate[30334]: no servers can be used, exiting
<27>Jul 28 03:33:36 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:36 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:36 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:36 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:36 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:36 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:41 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:41 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:41 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:41 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:41 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:52 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:52 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:52 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:52 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:52 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:55 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:55 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:55 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:55 node-4 multipathd: uevent trigger error
<27>Jul 28 03:33:55 node-4 multipathd: uevent trigger error
<27>Jul 28 03:34:27 node-4 multipathd: uevent trigger error
<27>Jul 28 03:34:27 node-4 multipathd: uevent trigger error
<27>Jul 28 03:34:27 node-4 multipathd: uevent trigger error
<27>Jul 28 03:34:27 node-4 multipathd: uevent trigger error
<27>Jul 28 03:34:27 node-4 multipathd: uevent trigger error
<27>Jul 28 03:34:27 node-4 multipathd: uevent trigger error
<27>Jul 28 03:34:27 node-4 multipathd: uevent trigger error
<27>Jul 28 03:34:34 node-4 multipathd: uevent trigger error
<27>Jul 28 03:34:34 node-4 multipathd: uevent trigger error
<27>Jul 28 03:34:34 node-4 multipathd: uevent trigger error
<27>Jul 28 03:34:34 node-4 multipathd: uevent trigger error
<27>Jul 28 03:34:34 node-4 multipathd: uevent trigger error
<27>Jul 28 03:34:34 node-4 multipathd: uevent trigger error
<43>Jul 28 03:34:49 node-4 apache2_error [Thu Jul 28 03:34:47.213433 2016] [mpm_event:notice] [pid 13481:tid 140547796174720] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 28 03:34:49 node-4 apache2_error [Thu Jul 28 03:34:47.213497 2016] [core:notice] [pid 13481:tid 140547796174720] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 28 03:34:49 node-4 apache2_error [Thu Jul 28 03:34:49.307342 2016] [mpm_event:notice] [pid 13481:tid 140547796174720] AH00491: caught SIGTERM, shutting down
<27>Jul 28 03:34:54 node-4 multipathd: uevent trigger error
<27>Jul 28 03:34:54 node-4 multipathd: uevent trigger error
<27>Jul 28 03:34:54 node-4 multipathd: uevent trigger error
<27>Jul 28 03:34:54 node-4 multipathd: uevent trigger error
<43>Jul 28 03:34:59 node-4 apache2_error [Thu Jul 28 03:34:50.383040 2016] [mpm_worker:notice] [pid 13861:tid 140717251680128] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 28 03:34:59 node-4 apache2_error [Thu Jul 28 03:34:50.383095 2016] [core:notice] [pid 13861:tid 140717251680128] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 28 03:35:29 node-4 apache2_error [Thu Jul 28 03:35:28.138896 2016] [mpm_worker:notice] [pid 13861:tid 140717251680128] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 03:35:29 node-4 apache2_error [Thu Jul 28 03:35:28.146406 2016] [mpm_worker:warn] [pid 13861:tid 140717251680128] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 03:35:29 node-4 apache2_error [Thu Jul 28 03:35:28.147167 2016] [mpm_worker:notice] [pid 13861:tid 140717251680128] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 28 03:35:29 node-4 apache2_error [Thu Jul 28 03:35:28.147179 2016] [core:notice] [pid 13861:tid 140717251680128] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 03:35:31 node-4 multipathd: uevent trigger error
<27>Jul 28 03:35:31 node-4 multipathd: uevent trigger error
<27>Jul 28 03:35:31 node-4 multipathd: uevent trigger error
<27>Jul 28 03:35:31 node-4 multipathd: uevent trigger error
<27>Jul 28 03:35:31 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:04 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 28 03:36:08 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:08 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:08 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:08 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:08 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:08 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:12 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:12 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:12 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:12 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:18 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:19 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:19 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:19 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:19 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:26 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:26 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:26 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:26 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:26 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:31 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:31 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:31 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:31 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:31 node-4 multipathd: uevent trigger error
<129>Jul 28 03:36:34 node-4 haproxy[28451]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 03:36:37 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:37 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:37 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:37 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:40 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:40 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:40 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:40 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:40 node-4 multipathd: uevent trigger error
<129>Jul 28 03:36:43 node-4 haproxy[30725]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:36:44 node-4 haproxy[30729]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 03:36:45 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:45 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:45 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:45 node-4 multipathd: uevent trigger error
<129>Jul 28 03:36:48 node-4 haproxy[31919]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:36:49 node-4 haproxy[31923]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:36:49 node-4 haproxy[31923]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 03:36:51 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:51 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:51 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:51 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:51 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:51 node-4 multipathd: uevent trigger error
<129>Jul 28 03:36:53 node-4 haproxy[733]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:36:54 node-4 haproxy[737]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:36:54 node-4 haproxy[737]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:36:54 node-4 haproxy[737]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:36:55 node-4 haproxy[737]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 03:36:56 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:56 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:56 node-4 multipathd: uevent trigger error
<27>Jul 28 03:36:56 node-4 multipathd: uevent trigger error
<129>Jul 28 03:36:59 node-4 haproxy[1974]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:36:59 node-4 haproxy[1974]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:36:59 node-4 haproxy[1974]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:00 node-4 haproxy[1974]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:00 node-4 haproxy[1974]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:00 node-4 haproxy[1974]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 03:37:01 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:01 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:01 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:01 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:01 node-4 multipathd: uevent trigger error
<129>Jul 28 03:37:02 node-4 haproxy[1974]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:02 node-4 haproxy[1974]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:02 node-4 haproxy[1974]: proxy aodh has no server available!
<129>Jul 28 03:37:04 node-4 haproxy[3171]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:04 node-4 haproxy[3171]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:04 node-4 haproxy[3171]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:05 node-4 haproxy[3180]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:05 node-4 haproxy[3180]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:05 node-4 haproxy[3180]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:06 node-4 haproxy[3180]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 03:37:07 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:07 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:07 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:07 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:07 node-4 multipathd: uevent trigger error
<129>Jul 28 03:37:07 node-4 haproxy[3180]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:07 node-4 haproxy[3180]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:07 node-4 haproxy[3180]: proxy aodh has no server available!
<129>Jul 28 03:37:07 node-4 haproxy[3180]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:07 node-4 haproxy[3180]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:07 node-4 haproxy[3180]: proxy ceilometer has no server available!
<129>Jul 28 03:37:09 node-4 haproxy[4370]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:10 node-4 haproxy[4374]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:10 node-4 haproxy[4374]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:10 node-4 haproxy[4374]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:10 node-4 haproxy[4374]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:11 node-4 haproxy[4374]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:11 node-4 haproxy[4374]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 03:37:12 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:12 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:12 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:12 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:12 node-4 multipathd: uevent trigger error
<129>Jul 28 03:37:12 node-4 haproxy[4374]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:13 node-4 haproxy[4374]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:13 node-4 haproxy[4374]: proxy aodh has no server available!
<129>Jul 28 03:37:13 node-4 haproxy[4374]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:13 node-4 haproxy[4374]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:13 node-4 haproxy[4374]: proxy ceilometer has no server available!
<129>Jul 28 03:37:15 node-4 haproxy[5600]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:15 node-4 haproxy[5600]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:15 node-4 haproxy[5600]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:16 node-4 haproxy[5604]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:16 node-4 haproxy[5604]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:16 node-4 haproxy[5604]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:16 node-4 haproxy[5604]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:17 node-4 haproxy[5604]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:17 node-4 haproxy[5604]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 03:37:17 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:17 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:17 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:17 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:18 node-4 multipathd: uevent trigger error
<129>Jul 28 03:37:18 node-4 haproxy[5604]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:18 node-4 haproxy[5604]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:18 node-4 haproxy[5604]: proxy aodh has no server available!
<129>Jul 28 03:37:18 node-4 haproxy[5604]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:18 node-4 haproxy[5604]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:18 node-4 haproxy[5604]: proxy ceilometer has no server available!
<129>Jul 28 03:37:21 node-4 haproxy[6870]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:21 node-4 haproxy[6870]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:21 node-4 haproxy[6870]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:21 node-4 haproxy[6870]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 03:37:21 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Jul 28 03:37:21 node-4 haproxy[6870]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:21 node-4 haproxy[6870]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:22 node-4 haproxy[6870]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:22 node-4 haproxy[6870]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:22 node-4 haproxy[6870]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:22 node-4 haproxy[6870]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:22 node-4 haproxy[6870]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:22 node-4 haproxy[6870]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:23 node-4 haproxy[6870]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:23 node-4 haproxy[6870]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:23 node-4 haproxy[6870]: proxy glance-registry has no server available!
<27>Jul 28 03:37:23 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:23 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:23 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:23 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:23 node-4 multipathd: uevent trigger error
<129>Jul 28 03:37:24 node-4 haproxy[6870]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:24 node-4 haproxy[6870]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:24 node-4 haproxy[6870]: proxy aodh has no server available!
<129>Jul 28 03:37:24 node-4 haproxy[6870]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:24 node-4 haproxy[6870]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:24 node-4 haproxy[6870]: proxy ceilometer has no server available!
<129>Jul 28 03:37:26 node-4 haproxy[8152]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:27 node-4 haproxy[8156]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:27 node-4 haproxy[8156]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:27 node-4 haproxy[8156]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:27 node-4 haproxy[8156]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:27 node-4 haproxy[8156]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:27 node-4 haproxy[8156]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:27 node-4 haproxy[8156]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:28 node-4 haproxy[8156]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:28 node-4 haproxy[8156]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:28 node-4 haproxy[8156]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:28 node-4 haproxy[8156]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:28 node-4 haproxy[8156]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:28 node-4 haproxy[8156]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:28 node-4 haproxy[8156]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:29 node-4 haproxy[8156]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:29 node-4 haproxy[8156]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:29 node-4 haproxy[8156]: proxy glance-registry has no server available!
<27>Jul 28 03:37:29 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:29 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:29 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:29 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:30 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:30 node-4 multipathd: uevent trigger error
<129>Jul 28 03:37:30 node-4 haproxy[8156]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:30 node-4 haproxy[8156]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:30 node-4 haproxy[8156]: proxy aodh has no server available!
<129>Jul 28 03:37:30 node-4 haproxy[8156]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:30 node-4 haproxy[8156]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:30 node-4 haproxy[8156]: proxy ceilometer has no server available!
<129>Jul 28 03:37:30 node-4 haproxy[8156]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:30 node-4 haproxy[8156]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:30 node-4 haproxy[8156]: proxy nova-novncproxy has no server available!
<129>Jul 28 03:37:32 node-4 haproxy[9603]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:32 node-4 haproxy[9603]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:32 node-4 haproxy[9603]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:32 node-4 haproxy[9603]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:32 node-4 haproxy[9603]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:33 node-4 haproxy[9613]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:33 node-4 haproxy[9613]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:33 node-4 haproxy[9613]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:33 node-4 haproxy[9613]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:33 node-4 haproxy[9613]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:33 node-4 haproxy[9613]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:33 node-4 haproxy[9613]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:33 node-4 haproxy[9613]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:34 node-4 haproxy[9613]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:34 node-4 haproxy[9613]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:34 node-4 haproxy[9613]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 03:37:35 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:35 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:35 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:35 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:35 node-4 multipathd: uevent trigger error
<129>Jul 28 03:37:35 node-4 haproxy[9613]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:35 node-4 haproxy[9613]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:35 node-4 haproxy[9613]: proxy glance-registry has no server available!
<129>Jul 28 03:37:35 node-4 haproxy[9613]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:35 node-4 haproxy[9613]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:35 node-4 haproxy[9613]: proxy aodh has no server available!
<129>Jul 28 03:37:35 node-4 haproxy[9613]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:35 node-4 haproxy[9613]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:35 node-4 haproxy[9613]: proxy ceilometer has no server available!
<129>Jul 28 03:37:36 node-4 haproxy[9613]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:36 node-4 haproxy[9613]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:36 node-4 haproxy[9613]: proxy nova-novncproxy has no server available!
<129>Jul 28 03:37:38 node-4 haproxy[10899]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:38 node-4 haproxy[10899]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:38 node-4 haproxy[10899]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:38 node-4 haproxy[10899]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:38 node-4 haproxy[10899]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:38 node-4 haproxy[10899]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:38 node-4 haproxy[10899]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:38 node-4 haproxy[10899]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:38 node-4 haproxy[10899]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:39 node-4 haproxy[10899]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:39 node-4 haproxy[10899]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:39 node-4 haproxy[10899]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:39 node-4 haproxy[10899]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:39 node-4 haproxy[10899]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:39 node-4 haproxy[10899]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:39 node-4 haproxy[10899]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:39 node-4 haproxy[10899]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:39 node-4 haproxy[10899]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:39 node-4 haproxy[10899]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:40 node-4 haproxy[10899]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:40 node-4 haproxy[10899]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:40 node-4 haproxy[10899]: proxy glance-registry has no server available!
<27>Jul 28 03:37:40 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:40 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:41 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:41 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:41 node-4 multipathd: uevent trigger error
<129>Jul 28 03:37:41 node-4 haproxy[10899]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:41 node-4 haproxy[10899]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:41 node-4 haproxy[10899]: proxy aodh has no server available!
<129>Jul 28 03:37:41 node-4 haproxy[10899]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:41 node-4 haproxy[10899]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:41 node-4 haproxy[10899]: proxy ceilometer has no server available!
<129>Jul 28 03:37:41 node-4 haproxy[10899]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:41 node-4 haproxy[10899]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:41 node-4 haproxy[10899]: proxy nova-novncproxy has no server available!
<27>Jul 28 03:37:44 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:44 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:44 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:44 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:44 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:47 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:47 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:47 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:47 node-4 multipathd: uevent trigger error
<129>Jul 28 03:37:48 node-4 haproxy[10899]: Server keystone-1/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:48 node-4 haproxy[10899]: Server keystone-1/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:48 node-4 haproxy[10899]: proxy keystone-1 has no server available!
<129>Jul 28 03:37:48 node-4 haproxy[10899]: Server keystone-2/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:48 node-4 haproxy[10899]: Server keystone-2/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:48 node-4 haproxy[10899]: proxy keystone-2 has no server available!
<129>Jul 28 03:37:48 node-4 haproxy[10899]: Server nova-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:48 node-4 haproxy[10899]: Server nova-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:48 node-4 haproxy[10899]: proxy nova-api has no server available!
<129>Jul 28 03:37:48 node-4 haproxy[10899]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:48 node-4 haproxy[10899]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:48 node-4 haproxy[10899]: proxy nova-metadata-api has no server available!
<129>Jul 28 03:37:48 node-4 haproxy[10899]: Server cinder-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:48 node-4 haproxy[10899]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:48 node-4 haproxy[10899]: proxy cinder-api has no server available!
<129>Jul 28 03:37:48 node-4 haproxy[10899]: Server glance-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:48 node-4 haproxy[10899]: Server glance-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:48 node-4 haproxy[10899]: proxy glance-api has no server available!
<129>Jul 28 03:37:48 node-4 haproxy[10899]: Server glance-glare/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:48 node-4 haproxy[10899]: Server glance-glare/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:48 node-4 haproxy[10899]: proxy glance-glare has no server available!
<129>Jul 28 03:37:48 node-4 haproxy[10899]: Server neutron/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:48 node-4 haproxy[10899]: Server neutron/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:48 node-4 haproxy[10899]: proxy neutron has no server available!
<129>Jul 28 03:37:49 node-4 haproxy[10899]: Server mysqld/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:49 node-4 haproxy[10899]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:49 node-4 haproxy[10899]: proxy mysqld has no server available!
<129>Jul 28 03:37:49 node-4 haproxy[10899]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:49 node-4 haproxy[10899]: Server object-storage/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:49 node-4 haproxy[10899]: proxy object-storage has no server available!
<129>Jul 28 03:37:49 node-4 haproxy[10899]: Server heat-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:49 node-4 haproxy[10899]: Server heat-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:49 node-4 haproxy[10899]: proxy heat-api has no server available!
<129>Jul 28 03:37:49 node-4 haproxy[10899]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:49 node-4 haproxy[10899]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:49 node-4 haproxy[10899]: proxy heat-api-cfn has no server available!
<129>Jul 28 03:37:49 node-4 haproxy[10899]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 03:37:49 node-4 haproxy[10899]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 03:37:49 node-4 haproxy[10899]: proxy heat-api-cloudwatch has no server available!
<27>Jul 28 03:37:51 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:51 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:51 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:51 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:51 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:51 node-4 multipathd: uevent trigger error
<27>Jul 28 03:37:51 node-4 multipathd: uevent trigger error
<27>Jul 28 03:38:09 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 28 03:38:10 node-4 multipathd: uevent trigger error
<27>Jul 28 03:38:16 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 28 03:38:24 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 03:38:24 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 28 03:38:25 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 28 03:38:35 node-4 multipathd: uevent trigger error
<27>Jul 28 03:38:35 node-4 multipathd: uevent trigger error
<27>Jul 28 03:38:35 node-4 multipathd: uevent trigger error
<27>Jul 28 03:38:35 node-4 multipathd: uevent trigger error
<27>Jul 28 03:38:35 node-4 multipathd: uevent trigger error
<27>Jul 28 03:38:40 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 28 03:39:10 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 28 03:39:12 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 28 03:40:27 node-4 multipathd: uevent trigger error
<27>Jul 28 03:40:27 node-4 multipathd: uevent trigger error
<27>Jul 28 03:40:27 node-4 multipathd: uevent trigger error
<27>Jul 28 03:40:27 node-4 multipathd: uevent trigger error
<27>Jul 28 03:40:27 node-4 multipathd: uevent trigger error
<27>Jul 28 03:41:44 node-4 multipathd: uevent trigger error
<27>Jul 28 03:41:44 node-4 multipathd: uevent trigger error
<27>Jul 28 03:41:44 node-4 multipathd: uevent trigger error
<27>Jul 28 03:41:44 node-4 multipathd: uevent trigger error
<27>Jul 28 03:41:44 node-4 multipathd: uevent trigger error
<27>Jul 28 03:45:02 node-4 multipathd: uevent trigger error
<27>Jul 28 03:45:03 node-4 multipathd: uevent trigger error
<27>Jul 28 03:45:03 node-4 multipathd: uevent trigger error
<27>Jul 28 03:45:03 node-4 multipathd: uevent trigger error
<27>Jul 28 03:45:03 node-4 multipathd: uevent trigger error
<43>Jul 28 03:46:20 node-4 apache2_error [Thu Jul 28 03:46:10.693735 2016] [mpm_worker:notice] [pid 13861:tid 140717251680128] AH00295: caught SIGTERM, shutting down
<43>Jul 28 03:46:20 node-4 apache2_error [Thu Jul 28 03:46:11.439415 2016] [mpm_worker:notice] [pid 29260:tid 140424014317440] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 03:46:20 node-4 apache2_error [Thu Jul 28 03:46:11.439452 2016] [core:notice] [pid 29260:tid 140424014317440] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 03:46:49 node-4 multipathd: uevent trigger error
<27>Jul 28 03:46:49 node-4 multipathd: uevent trigger error
<27>Jul 28 03:46:49 node-4 multipathd: uevent trigger error
<27>Jul 28 03:46:49 node-4 multipathd: uevent trigger error
<27>Jul 28 03:46:49 node-4 multipathd: uevent trigger error
<43>Jul 28 03:46:50 node-4 apache2_error [Thu Jul 28 03:46:43.625467 2016] [mpm_worker:notice] [pid 29260:tid 140424014317440] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 03:46:50 node-4 apache2_error [Thu Jul 28 03:46:43.632304 2016] [mpm_worker:warn] [pid 29260:tid 140424014317440] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 03:46:50 node-4 apache2_error [Thu Jul 28 03:46:43.637305 2016] [mpm_worker:notice] [pid 29260:tid 140424014317440] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 03:46:50 node-4 apache2_error [Thu Jul 28 03:46:43.637327 2016] [core:notice] [pid 29260:tid 140424014317440] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 03:47:47 node-4 multipathd: uevent trigger error
<27>Jul 28 03:47:47 node-4 multipathd: uevent trigger error
<27>Jul 28 03:47:47 node-4 multipathd: uevent trigger error
<27>Jul 28 03:47:47 node-4 multipathd: uevent trigger error
<27>Jul 28 03:47:47 node-4 multipathd: uevent trigger error
<27>Jul 28 03:48:58 node-4 multipathd: uevent trigger error
<27>Jul 28 03:48:58 node-4 multipathd: uevent trigger error
<27>Jul 28 03:48:58 node-4 multipathd: uevent trigger error
<27>Jul 28 03:48:58 node-4 multipathd: uevent trigger error
<27>Jul 28 03:48:58 node-4 multipathd: uevent trigger error
<27>Jul 28 03:53:09 node-4 multipathd: uevent trigger error
<27>Jul 28 03:53:09 node-4 multipathd: uevent trigger error
<27>Jul 28 03:53:09 node-4 multipathd: uevent trigger error
<27>Jul 28 03:53:09 node-4 multipathd: uevent trigger error
<27>Jul 28 03:53:09 node-4 multipathd: uevent trigger error
<27>Jul 28 03:55:15 node-4 multipathd: uevent trigger error
<27>Jul 28 03:55:15 node-4 multipathd: uevent trigger error
<27>Jul 28 03:55:15 node-4 multipathd: uevent trigger error
<27>Jul 28 03:55:15 node-4 multipathd: uevent trigger error
<27>Jul 28 03:55:15 node-4 multipathd: uevent trigger error
<27>Jul 28 03:55:15 node-4 multipathd: uevent trigger error
<27>Jul 28 03:56:25 node-4 multipathd: uevent trigger error
<27>Jul 28 03:56:25 node-4 multipathd: uevent trigger error
<27>Jul 28 03:56:25 node-4 multipathd: uevent trigger error
<27>Jul 28 03:56:25 node-4 multipathd: uevent trigger error
<27>Jul 28 03:56:25 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:02 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:02 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:02 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:02 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:12 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:12 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:12 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:12 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:12 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:17 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:17 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:17 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:17 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:23 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:23 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:23 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:23 node-4 multipathd: uevent trigger error
<27>Jul 28 03:57:23 node-4 multipathd: uevent trigger error
<43>Jul 28 03:58:11 node-4 apache2_error [Thu Jul 28 03:58:09.435792 2016] [mpm_worker:notice] [pid 29260:tid 140424014317440] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 03:58:11 node-4 apache2_error [Thu Jul 28 03:58:09.821381 2016] [mpm_worker:warn] [pid 29260:tid 140424014317440] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 03:58:11 node-4 apache2_error [Thu Jul 28 03:58:09.826602 2016] [mpm_worker:notice] [pid 29260:tid 140424014317440] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 03:58:11 node-4 apache2_error [Thu Jul 28 03:58:09.826633 2016] [core:notice] [pid 29260:tid 140424014317440] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 28 03:58:51 node-4 apache2_error [Thu Jul 28 03:58:46.434010 2016] [mpm_worker:notice] [pid 29260:tid 140424014317440] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 03:58:51 node-4 apache2_error [Thu Jul 28 03:58:47.947906 2016] [mpm_worker:warn] [pid 29260:tid 140424014317440] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 03:58:51 node-4 apache2_error [Thu Jul 28 03:58:47.962376 2016] [mpm_worker:notice] [pid 29260:tid 140424014317440] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 03:58:51 node-4 apache2_error [Thu Jul 28 03:58:47.962413 2016] [core:notice] [pid 29260:tid 140424014317440] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 03:58:54 node-4 multipathd: uevent trigger error
<27>Jul 28 03:58:54 node-4 multipathd: uevent trigger error
<27>Jul 28 03:58:54 node-4 multipathd: uevent trigger error
<27>Jul 28 03:58:54 node-4 multipathd: uevent trigger error
<27>Jul 28 03:58:54 node-4 multipathd: uevent trigger error
<27>Jul 28 03:59:39 node-4 multipathd: uevent trigger error
<27>Jul 28 03:59:39 node-4 multipathd: uevent trigger error
<27>Jul 28 03:59:39 node-4 multipathd: uevent trigger error
<27>Jul 28 03:59:39 node-4 multipathd: uevent trigger error
<27>Jul 28 03:59:51 node-4 multipathd: uevent trigger error
<27>Jul 28 03:59:51 node-4 multipathd: uevent trigger error
<27>Jul 28 03:59:51 node-4 multipathd: uevent trigger error
<27>Jul 28 03:59:51 node-4 multipathd: uevent trigger error
<27>Jul 28 04:01:29 node-4 multipathd: uevent trigger error
<27>Jul 28 04:01:29 node-4 multipathd: uevent trigger error
<27>Jul 28 04:01:29 node-4 multipathd: uevent trigger error
<27>Jul 28 04:01:29 node-4 multipathd: uevent trigger error
<27>Jul 28 04:01:29 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:19 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:19 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:19 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:19 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:19 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:29 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:29 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:29 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:29 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:29 node-4 multipathd: uevent trigger error
<11>Jul 28 04:02:39 node-4 liberasurecode[22932]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:39 node-4 liberasurecode[22932]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:39 node-4 liberasurecode[22932]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:39 node-4 liberasurecode[22932]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:39 node-4 liberasurecode[22956]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:39 node-4 liberasurecode[22956]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:39 node-4 liberasurecode[22956]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:39 node-4 liberasurecode[22956]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:42 node-4 liberasurecode[23357]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:42 node-4 liberasurecode[23357]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:42 node-4 liberasurecode[23357]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:42 node-4 liberasurecode[23357]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:47 node-4 liberasurecode[25220]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:47 node-4 liberasurecode[25220]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:47 node-4 liberasurecode[25220]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:47 node-4 liberasurecode[25220]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:47 node-4 liberasurecode[25301]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:47 node-4 liberasurecode[25301]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:47 node-4 liberasurecode[25301]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:47 node-4 liberasurecode[25301]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:47 node-4 liberasurecode[25381]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:47 node-4 liberasurecode[25381]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:47 node-4 liberasurecode[25381]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:47 node-4 liberasurecode[25381]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:48 node-4 liberasurecode[25579]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:48 node-4 liberasurecode[25579]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:48 node-4 liberasurecode[25579]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:48 node-4 liberasurecode[25579]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:48 node-4 liberasurecode[25594]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:48 node-4 liberasurecode[25594]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:48 node-4 liberasurecode[25594]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:48 node-4 liberasurecode[25594]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:48 node-4 liberasurecode[25606]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:48 node-4 liberasurecode[25606]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:48 node-4 liberasurecode[25606]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:48 node-4 liberasurecode[25606]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:48 node-4 liberasurecode[25618]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:48 node-4 liberasurecode[25618]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:48 node-4 liberasurecode[25618]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:02:48 node-4 liberasurecode[25618]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 28 04:02:54 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:54 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:54 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:54 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:54 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:59 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:59 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:59 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:59 node-4 multipathd: uevent trigger error
<27>Jul 28 04:02:59 node-4 multipathd: uevent trigger error
<11>Jul 28 04:05:01 node-4 liberasurecode[13349]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:05:01 node-4 liberasurecode[13349]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:05:01 node-4 liberasurecode[13349]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 04:05:01 node-4 liberasurecode[13349]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 28 04:05:21 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:21 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:21 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:21 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:22 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:27 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:27 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:27 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:27 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:27 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:40 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:40 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:40 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:40 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:53 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:53 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:53 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:53 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:57 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:57 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:57 node-4 multipathd: uevent trigger error
<27>Jul 28 04:05:57 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:10 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:10 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:10 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:10 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:10 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:15 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:15 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:15 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:15 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:15 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:19 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:19 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:19 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:19 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:19 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:23 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:23 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:23 node-4 multipathd: uevent trigger error
<27>Jul 28 04:06:24 node-4 multipathd: uevent trigger error
