Server acting up

QuickBox Support
,
#1

Hello,

I’ve been enjoying running QuickBox on a Hetzner server for nearly a month now, but my server has been unresponsive multiple times within the last 24 hours. Most services no longer respond (sFTP, rTorrent, even SSH). The box was installed using Ubuntu 16.04.

Can anyone help me troubleshoot this problem? I found some odd looking errors in the syslog, not sure if it’s related:

Dec 26 23:54:12 Oslo kernel: [38619.111808] NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [kswapd0:83]
Dec 26 23:54:20 Oslo kernel: [38647.113691] NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [kswapd0:83]
Dec 26 23:54:49 Oslo kernel: [38675.115574] NMI watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [kswapd0:83]

This is the output from df -h:

Filesystem            Size  Used Avail Use% Mounted on
udev                  7.8G     0  7.8G   0% /dev
tmpfs                 1.6G   13M  1.6G   1% /run
/dev/mapper/vg0-root  5.4T  1.9T  3.3T  38% /
tmpfs                 7.8G     0  7.8G   0% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
tmpfs                 7.8G     0  7.8G   0% /sys/fs/cgroup
/dev/md0              488M  115M  348M  25% /boot
/dev/mapper/vg0-tmp    20G   33M   20G   1% /tmp
tmpfs                 1.6G     0  1.6G   0% /run/user/1000

A hard reboot operated from the console fixes the problem, until it starts acting up again.

#2

Hard to say as I am thinking this would be something you’d possibly need to report to Hetzner support. However, when was the last time you ran apt update and apt upgrade on your system?

#3

Hello JMSolo,

Thanks for your quick response.

I haven’t yet run this from the console, I usually only run updates from the Quickbox console. I’ll run these if you think it might solve the problem.

As you can imagine, I’m a bit hesitant to put in a support ticket with Hetzner due to the material that’s on my server.

#4

They typically honor your privacy in most cases, they will not browse the contents of a server unless they have good reason to. Although, this could be a kernel issue… hard to say. Running the update/upgrade may resolve the issue if any fixes have been published upstream.

#5

OK thank you, I’ve run the update/upgrade.

Fingers crossed! :slight_smile:

#6

Also (for cleanliness sake) run the following commands, apt -y autoclean and apt -y autoremove. This will remove unused dependencies etc that would otherwise fill up your /boot records.

1 Like
#7

All done, thanks!