now after a dist-upgrade to Buster, my machine sometimes becomes unresponsive.
I cannot say, what is showing on the screen, as my machine runs headless.
this morning, again, the only communication was with Ping.
no SSH, no RDP, no web-gui of Deluged nor Sabnzbdplus.
where do I begin to look at ??
which logfiles are most relevant ??
sudo dmesg doesn't look any different than before.
edit:
I looked at /var/log/syslog and found this:
Code: Select all
Jul 17 00:00:05 Debian systemd[1]: logrotate.service: Succeeded.
Jul 17 00:00:05 Debian systemd[1]: Started Rotate log files.
Jul 17 00:00:05 Debian systemd[1]: man-db.service: Succeeded.
Jul 17 00:00:05 Debian systemd[1]: Started Daily man-db regeneration.
Jul 17 00:14:48 Debian systemd[1]: Started Deluge Bittorrent Client Daemon.
Jul 17 00:17:01 Debian CRON[23275]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 17 01:17:01 Debian CRON[23315]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 17 02:17:01 Debian CRON[23348]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 17 09:56:27 Debian systemd[1]: Starting Flush Journal to Persistent Storage...
Jul 17 09:56:27 Debian kernel: [ 0.000000] Linux version 4.19.0-5-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-7)) #1 SMP Debian 4.19.37-5 (2019-06-19)
Jul 17 09:56:27 Debian systemd[1]: Started udev Kernel Device Manager.
Jul 17 09:56:27 Debian kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-amd64 root=UUID=c13aae11-e70b-4c32-95d4-887063631a09 ro quiet
Jul 17 09:56:27 Debian systemd[1]: Started Flush Journal to Persistent Storage.