BitBOINC

Hello!
Seems like we run out of Sphinx wus?

Hans Sveen
Oslo, Norway

---

The server automatically stops production because there is a large backlog of jobs. It resumes once the jobs are completed and the queue drops to a certain level.

---

Thank You for the information, keep up with the exelent work done 👍😊

Hans S.

Hi Alperen,
I think I found a suspend/resume issue with the Sphinx CPU app.
BOINC reports 4 Sphinx CPU tasks as SUSPENDED, but the corresponding Linux processes continue to run and consume almost a full CPU thread each.
Example:
sphinx_eccp131_1790904303_1739 → PID 3265 → ~90% CPU
sphinx_eccp131_1790901903_17115 → PID 3266 → ~90% CPU
sphinx_eccp131_1790901903_28910 → PID 3267 → ~85% CPU
sphinx_eccp131_1790904903_30398 → PID 68988 → ~0.4% CPU
BOINC shows all four as active_task_state: SUSPENDED.
In ps, the first three processes have state S/R, not T, so they are not actually stopped by the OS and keep computing in the background.
I confirmed the PID-to-WU mapping via the BOINC slot directories under /var/lib/boinc/slots/.
Manually sending SIGSTOP to the affected PIDs stops them correctly.
This may also explain why the system becomes overloaded even though BOINC appears to be running fewer CPU tasks than are actually consuming CPU time.
Let me know if you want the full command output.