apt full-upgrade causes system lock-up

[Keith]

On 6/2/22 10:27 AM, Bo Berglund wrote:
[snip]

> And syslog seems not to contain any line concerning manual start of apt, such as
> the command line "apt full-upgrade" or similar so I cannot pinpoint the timing
> of the command leading up to the crash.
> Syslog itself is too massive to browse through manually using only command line
> tools...
> 
> 

Well, syslog.log and the kern.log are going to be the logs you really 
want to examine for hardware or filesystem failures. What I do when I 
need to troubleshoot a problem is to start with clean logs. So you could 
issue "$ sudo logrotate -v -f /etc/logrotate.conf" and that'll rotate 
the logs and create an empty syslog.log and kern.log among the others in 
/var/log. After that command go ahead and run apt full-ugrade and see if 
you can trigger the problem. If it happens, reboot and immediately 
rotate the logs when the system is back up. Syslog.1 and kernel.log.1 
and dmesg.0 will be the logs you want to examine.

Also, you may want to change the amount of information being logged. By 
default systemd-journald logs pretty much everything at the debug level 
and higher, which tends to create huge log files which are difficult to 
parse, especially if you not sure what you're looking for exactly. You 
can edit /etc/systemd/journald.conf and tell journald to log only 
messages that are a certain level or higher. I have mine to "warning" 
level and higher. This cuts debug,info,notice level messages from being 
saved to syslog by systemd-journald, though you can still read them 
using journalctl.

-- 
Keith