Search results

Fortunately I was able to reboot the server with systemctl --force --force reboot and now everything seems to be back to normal. Login is as fast as before, and systemctl works too. Since this is a production system, I will use memtester to test the RAM. A short test with 1GB didn't reveal any...

Does RAM really go bad after many years of service, without any kind of problems except for systemd? This doesn't really make sense to me...

Yes, it's a Hetzner device, it's unfortunate that they ditched Plesk. Since they don't offer paid support, they should at least offer an easy way to maintain the server. When switching from CentOS to Almalinux, I didn't restore from the Plesk backup (although I have one off site). I just...

Thanks for the instructions! Step 1) Both memory (RAM) and disk space are plenty, no OOM kills. Only 4GB of RAM out of 64GB are used, 47GB cache (large forum database). Disk is only half full. dmesg returns error "Failed to send WATCHDOG=1 notification message: systemd-journald[<redacted>]...

The command ps aux | wc -l returns 208, which doesn't seem higher than usual. The server is a dedicated Core i7-6700 with 64GB RAM and two SSDs (RAID 1) running a forum and download server. Uptime is 414 days, so maybe I should really try a reboot. For testing, I have taken the forum offline...

Thanks for your reply! Unfortunately I get "-- No entries --" running this command as root, even when I just use journalctl -u systemd I also tried journalctl -r to see all the last entries immediately after a failed systemctl call, but there was nothing in there except for the usual failed...

Our server has been running Plesk for many years without problems. Currently we are on Almalinux 9.6, which was a fresh Almalinux 9 install (no upgrade from CentOS). We are currently on Plesk Obsidian 18.0.71 with automatic updates and system updates, safe updates enabled. Suddenly a few days...