Hi Ivan, the best way to engage Canonical Support to get assistance with
this issue will be to file a support case on support.canonical.com and
attach an sosreport of the affected system that is collected when the
issue happens. See my previous comment #5 for the details of sosreport.
Please check with Stephen Zarkos if you need access to the Canonical
Support Portal.
One other idea that may help in case your system is not responsive is to
have a serial console output logged in a gnu screen or tmux session.
Inside this console session, you can enable the maximum log level ("echo
9 > /proc/sysrq-trigger", you might have to run "sysctl -w
kernel.sysrq=1" before to enable sysrq) and run "dmesg -w", which will
dump dmesg and continuously append new entries to the kernel log. This
way, you won't depend on saving logs to the disk to see what's going on,
since the disk access could freeze in the moment of the failure.
You can also enable kdump and all the "panic_on_X" sysctl settings
(section Enabling various types of panics in CrashdumpRecipe
article[1]). If the system is locking up so hard that it freezes, it may
then capture a dump so that we can see what's going on. Refer to the
CrashdumpRecipe article[1] for more information.
[1] https://wiki.ubuntu.com/Kernel/CrashdumpRecipe
Thank you,
David
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788643
Title:
zombies pile up, system becomes unresponsive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1788643/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
