View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001796aMuleMulti Platformpublic2019-01-31 06:322019-02-10 21:59
Reporteramer.hwitat 
Assigned To 
PrioritynormalSeverityminorReproducibilitysometimes
StatusnewResolutionopen 
PlatformOSP 14OSRHEL 7.6 MaipoOS VersionRHEL 7.6 Maipo
Product Version2.3.2 
Target VersionFixed in Version 
Summary0001796: Some Bugs that crashes the Kernel of RHEL 7.6
Description
[root@localhost log]#
Message from syslogd@localhost at Jan 23 02:23:31 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [ovsdb-server:10088]

[root@amer network-scripts]#
Message from syslogd@amer at Jan 27 12:46:38 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [nova-api:102738]

Message from syslogd@amer at Jan 27 19:26:19 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 26s! [swapper/5:0]

Message from syslogd@amer at Jan 27 19:26:19 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#1 stuck for 27s! [dmeventd:71548]

Message from syslogd@amer at Jan 27 19:27:30 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [6_scheduler:64928]

Message from syslogd@amer at Jan 27 19:31:25 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [ksoftirqd/5:34]

Message from syslogd@amer at Jan 27 19:32:42 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#3 stuck for 33s! [swift-object-up:11358]

Message from syslogd@amer at Jan 27 19:33:55 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#3 stuck for 24s! [dmeventd:71548]

Message from syslogd@amer at Jan 27 19:34:25 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#2 stuck for 65s! [kworker/2:0:59993]

Message from syslogd@amer at Jan 27 19:37:50 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#2 stuck for 24s! [kworker/u256:3:8447]

Message from syslogd@amer at Jan 27 19:37:50 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [ksoftirqd/5:34]

Message from syslogd@amer at Jan 27 19:37:51 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [systemd:11968]

The CPU has been disabled by the guest operating system. Power off or reset the virtual machine.


[root@amer network-scripts]#
Message from syslogd@amer at Jan 27 12:46:38 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [nova-api:102738]

these Bugs of OSP 14 Nova were recorded because the system depends heavily on NSlookup to process it's function call, and I reported it to RH, launchpad.net,Bgzilla, and RDO.

I have configured /etc/hosts several times and setup a named service (DNS), the service Nova overlooks the hosts and issues NSlookups to DNS, rabbitMQ fails and Nova because it depends on RabbitMQ in it's infrastructure code in python.
Steps To Reproduceinstall OSP 14 and drop connectivity, it will produce some Bugs
Additional Informationit's on RHEL 7.6 platform and I don't really know if it is valid for Ubuntu, or any Debian variant, it shows that Kernel and Firmware is not compatible, so if you want to install OSP 14 , choose an updated version of firmware, and new equipment.
TagsNo tags attached.
Fixed in Revision
Operating SystemAny
Attached Filespng file icon Red Hat Enterprise Linux 7 64-bit (2)-2019-01-28-03-57-27.png [^] (26,978 bytes) 2019-01-31 06:32

- Relationships

-  Notes
(0003719)
ValdikSS (reporter)
2019-02-10 21:59

This is not an amule bug, this is because of high I/O load. You should tune permitted load with cgroups, maybe tune sysctl vm.dirty_bytes/vm.dirty_background_bytes.
Search "linux bug 12309" for more information.

- Issue History
Date Modified Username Field Change
2019-01-31 06:32 amer.hwitat New Issue
2019-01-31 06:32 amer.hwitat File Added: Red Hat Enterprise Linux 7 64-bit (2)-2019-01-28-03-57-27.png
2019-02-10 21:59 ValdikSS Note Added: 0003719


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker