nova crashed the CPU

asked 2019-01-28 22:22:05 -0600

anonymous user

Anonymous

Hi,

I have been working on a clean installation of RHEL 7.6 and OSP 14 on my VM, I had the following problem:

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.**

it crashed the server, and this was the components of Nova that did it, before I had a problem with OVS component, I upgraded the RAM to 16GB recently, and reduced the cores to 4 instead of 8 on the VM, and upgraded the VMware workstation from 12 to 14, there is v15 now, now I have installed a Machine on 12GB RAM, and it was a clean on the 1st trial installation, configured the OS /etc/hosts file and it contains only one line myIP amer amer.example.com, the result was that I have a relatively faster Machine, but still no luck with creating the Instance in Compute, No hosts found in the Error message, I didn't configure anything in this Machine except hosts and hostname before installation, and OVS br-ex after installation, still the same issue I faced before is still present.

issued the command

[root@amer ~(keystone_admin)]# openstack compute service list
+----+------------------+------------------+----------+---------+-------+----------------------------+
| ID | Binary           | Host             | Zone     | Status  | State | Updated At                 |
+----+------------------+------------------+----------+---------+-------+----------------------------+
|  5 | nova-conductor   | amer             | internal | enabled | down  | 2019-01-28T00:43:20.000000 |
|  7 | nova-scheduler   | amer             | internal | enabled | down  | 2019-01-28T00:43:20.000000 |
| 10 | nova-consoleauth | amer             | internal | enabled | down  | 2019-01-28T00:43:22.000000 |
| 11 | nova-consoleauth | amer.example.com | internal | enabled | up    | 2019-01-28T02:38:55.000000 |
| 12 | nova-scheduler   | amer.example.com | internal | enabled | up    | 2019-01-28T02:38:53.000000 |
| 16 | nova-conductor   | amer.example ...
(more)
edit retag flag offensive close merge delete

Comments

Install named servers (DNS) on your node, or add records of nodes to your DNS server because the /ect/hosts file doesn't work for nova if you have installed https services install the nova.cert

amer.hwitat gravatar imageamer.hwitat ( 2019-01-30 19:23:23 -0600 )edit