-
Notifications
You must be signed in to change notification settings - Fork 439
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manager gets stuck on "Communicating with boinc client" #5518
Comments
There is no easy way to do a simple timeout from this situation, as the lost RPC can potentially cause significant problems for the BOINC Manager. But if you click on the Cancel button, the Manager will reset its communications and try to recover. What happens if you click on the Cancel button? |
I experience these same symptoms on and off. Pressing the cancel button opens a prompt with a '"boincmgr" is not responding.' message. If I choose the wait options, the prompt reappears moments later, so "Force Quit" is the only way forward. Opening the application again brings me back to the start. The machine in question is a Dell OptiPlex 755 running Ubuntu 22.04.4 LTS The issue is not reliably solved with a computer restart. It just occasionally starts acting responsive again days or weeks later. |
@wyzwon That is a Windows PC. I only work with Macs. But I can tell you that the communicating with client message is only a symptom indicating that the client is stuck and not responding to RPCs from the manager. I am not the right person to diagnose that actual problem. |
The Manager makes periodic RPCs to the client (once/minute, more in some cases). This behavior isn't as user-friendly as it could be, |
Describe the bug
Boinc manager got stuck on "Communicating with boinc client" if system lags during communication because of memory exhaustion.
Boinctasks can connect just fine.
Steps To Reproduce
1.
2.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System Information
Additional context
It seems as if response to a request gets lost, and boinc manager remains content to wait for a response infinitely, without timing out.
The text was updated successfully, but these errors were encountered: