[SOLVED] Report trigger for Ubuntu Report restarts and ends with crash

ethereal1m · 03-23-2021, 10:54 PM

Hi all,
I have a machine that runs a cryptomining software gpu overnight and nonstop. Sometimes it triggers ubuntu report multiple times until it crashes. It starts by creating user slice of root then stars report triggering:

Code:

Mar 24 01:27:35 r9 systemd[1]: Created slice User Slice of root.
Mar 24 01:27:35 r9 systemd[1]: Starting User Manager for UID 0...
Mar 24 01:27:36 r9 systemd[13968]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Mar 24 01:27:36 r9 systemd[13968]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 24 01:27:36 r9 systemd[13968]: Starting D-Bus User Message Bus Socket.
Mar 24 01:27:36 r9 systemd[13968]: Listening on GnuPG network certificate management daemon.
Mar 24 01:27:36 r9 systemd[13968]: Started Pending report trigger for Ubuntu Report.
Mar 24 01:27:36 r9 systemd[13968]: Reached target Paths.
Mar 24 01:27:36 r9 systemd[13968]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Mar 24 01:27:36 r9 systemd[13968]: Listening on REST API socket for snapd user session agent.
Mar 24 01:27:36 r9 systemd[13968]: Listening on GnuPG cryptographic agent and passphrase cache.
Mar 24 01:27:36 r9 systemd[13968]: Reached target Timers.
Mar 24 01:27:36 r9 systemd[13968]: Listening on D-Bus User Message Bus Socket.
Mar 24 01:27:36 r9 systemd[13968]: Reached target Sockets.
Mar 24 01:27:36 r9 systemd[13968]: Reached target Basic System.
Mar 24 01:27:36 r9 systemd[1]: Started User Manager for UID 0.
Mar 24 01:27:36 r9 systemd[13968]: Reached target Default.
Mar 24 01:27:36 r9 systemd[13968]: Startup finished in 35ms.

then it closes it:

Code:

Mar 24 01:27:36 r9 systemd[1]: Stopping User Manager for UID 0...
Mar 24 01:27:36 r9 systemd[13968]: Stopped target Default.
Mar 24 01:27:36 r9 systemd[13968]: Stopped target Basic System.
Mar 24 01:27:36 r9 systemd[13968]: Stopped target Timers.
Mar 24 01:27:36 r9 systemd[13968]: Stopped target Paths.
Mar 24 01:27:36 r9 systemd[13968]: Stopped Pending report trigger for Ubuntu Report.
Mar 24 01:27:36 r9 systemd[13968]: Stopped target Sockets.
Mar 24 01:27:36 r9 systemd[13968]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Mar 24 01:27:36 r9 systemd[13968]: Closed D-Bus User Message Bus Socket.
Mar 24 01:27:36 r9 systemd[13968]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 24 01:27:36 r9 systemd[13968]: Closed GnuPG network certificate management daemon.
Mar 24 01:27:36 r9 systemd[13968]: Closed GnuPG cryptographic agent and passphrase cache.
Mar 24 01:27:36 r9 systemd[13968]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Mar 24 01:27:36 r9 systemd[13968]: Closed REST API socket for snapd user session agent.
Mar 24 01:27:36 r9 systemd[13968]: Reached target Shutdown.
Mar 24 01:27:36 r9 systemd[13968]: Starting Exit the Session...
Mar 24 01:27:36 r9 systemd[13968]: Received SIGRTMIN+24 from PID 13986 (kill).
Mar 24 01:27:36 r9 systemd[1]: Stopped User Manager for UID 0.
Mar 24 01:27:36 r9 systemd[1]: Removed slice User Slice of root.

it repeats continuously until the system crashes because of memory problem:

Code:

Mar 24 04:48:36 r9 kernel: [22475.696935] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message

I'm using ubuntu 18 and kernel 5.4.0-54-generic.

What could be the cause of the continuous report trigger? How can I disable that? Please advise.

regards

Gad · 03-24-2021, 03:53 AM

What are the specs of your computer?

Is your machine not maybe running out of resources? I could be wrong but I believe mining would take up much of your systems resources.

Quote:

What could be the cause of the continuous report trigger? How can I disable that? Please advise.

I don't think disabling it would be a good option as the problem will still occur in the background. It would be like silencing a fire alarm and ignoring the fire

ethereal1m · 03-24-2021, 09:44 AM

Most of the resources are taken care by gpu. The system has plenty of memory, supposedly. Could you tell me what "report trigger for ubuntu report" is? Why does it start and stop repeatedly?

ethereal1m · 03-26-2021, 12:09 AM

The crash causes by flushing data to disk takes too long and causing "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" error. The ubuntu reporting is nothing to do with it