Job is unresponsive - no heartbeat received

Troubleshooting
12

We are still not sure about the cause of the issues described under this topic; there might be two separate issues.
Do you still experience the problems in either the first post or in Job is unresponsive - no heartbeat received - #8 by emgreen ?

  1. may point to an intermittent networking issue (failed transmission of heartbeat to the CryoSPARC master) or some (temporary?) disruption of the CryoSPARC master server itself.
    What are the outputs of these commands on the CryoSPARC master:

    uname -a
free -h
sudo journalctl | grep -i oom
ps -eo pid,ppid,start,command | grep cryosparc_
cat /sys/kernel/mm/transparent_hugepage/enabled

    How many concurrently active users, how many concurrently interactive jobs (exposure or particle curation, manual picking, etc.) does the CryoSPARC master need to handle?

  2. The job described in Job is unresponsive - no heartbeat received - #10 by emgreen may have suffered from a problem similar to the one discussed in Cryosparc v4.6.0 2D job never finish, for which you may consider the suggestions in Cryosparc v4.6.0 2D job never finish - #36 by wtempel. As you seem to be working on AWS, the special note regarding cloud-based VMs and vCPU configuration may apply.