How to Fix BOINCCMD Poll Status Error -1

For users who are leveraging BOINC (Berkeley Open Infrastructure for Network Computing) to contribute computing power or manage distributed computing tasks, encountering an error can be particularly frustrating. One such issue that regularly comes up is the BOINCCMD poll status error -1. This article dives into what this error means, why it occurs, and how to effectively resolve it.

TLDR: The poll status error -1 in boinccmd usually indicates a communication failure between the command-line tool and the local or remote BOINC client. The cause can range from BOINC not running, connection permissions, port issues, or incorrect command syntax. The solution typically involves verifying the status of the BOINC Manager and client software, ensuring correct port binding and authentication, and checking your command syntax. This guide walks through diagnostics and step-by-step solutions to eliminate the error.

Understanding the Error

The error message “poll status error -1” from boinccmd is generally associated with a failure in socket communication between the BOINC command-line tool and the BOINC client daemon.

This often looks something like:

poll status: -1
can't connect to localhost

Essentially, this suggests that the boinccmd utility can’t find or talk to a running BOINC client process either on the host machine or across the network. This issue is most common on systems where BOINC was installed but not properly configured, or after an accidental client crash.

Common Causes of Poll Status Error -1

• BOINC Client Not Running: The most common cause. If the BOINC client isn’t active, boinccmd has nothing to talk to.
• Firewall Issues: Firewalls or antivirus software may block internal or external connections.
• Wrong Port or Host: The command may be trying to reach the client on the wrong host or port.
• Authentication Failures: Missing or incorrect hashed passwords in the gui_rpc_auth.cfg file.
• BOINC Running as a Different User or Service: If BOINC is running under a service account and not under your user context.

Step-by-Step Instructions to Fix It

Let’s dive into each solution methodically.

1. Check if BOINC is Running

Before anything else, confirm that the BOINC client is running. Without this, boinccmd cannot communicate successfully.

On Linux/macOS:

ps aux | grep boinc

On Windows: Open Task Manager and look for “boinc.exe” or “boincmgr.exe”.

If it’s not running, you can start it manually:

• Linux: boinc --daemon
• macOS: Launch BOINC from Applications
• Windows: Double-click on the BOINC icon from Start Menu or launch the service

2. Verify Command Syntax

Often, the issue is simply using wrong or incomplete command syntax. The proper way to use boinccmd requires at minimum:

boinccmd --host localhost --passwd YOUR_PASSWORD --get_state

If you’re running it locally, omitting the host is fine, but you must still provide the password if authentication is required.

3. Check Authentication File

BOINC uses a file named gui_rpc_auth.cfg for authentication. This file contains a hashed password (or plain text depending on the system) that must be passed using the --passwd option with boinccmd.

Steps to locate this file:

• Linux: /var/lib/boinc/gui_rpc_auth.cfg
• Windows: C:\ProgramData\BOINC\gui_rpc_auth.cfg
• macOS: /Library/Application Support/BOINC Data/gui_rpc_auth.cfg

Copy the content and use it as the password parameter when invoking boinccmd.

4. Port and Firewall Configuration

BOINC listens on port 31416 by default. If this port is blocked by a firewall, you’ll get a poll status -1 error.

Check your firewall:

• Allow port 31416 through your software firewall (like Windows Defender or UFW on Linux)
• Check router port-forwarding if accessing remotely

5. Connect to Remote Host (if applicable)

If you are trying to connect to a remote BOINC client, make sure of the following:

• BOINC is running in server mode and accepts remote commands
• Your machine’s IP is in the remote_hosts.cfg file on the server
• You’re using the correct password from gui_rpc_auth.cfg

6. Run BOINC Manager in Admin Mode (Windows)

Sometimes, boinccmd cannot access the running BOINC client due to privileges. Try running the BOINC Manager and command-line as administrator.

Steps:

1. Right-click BOINC Manager and select “Run as administrator”
2. Repeat the same for the command prompt terminal used to launch boinccmd

7. Review Logs for More Information

BOINC logs can provide detailed insight into communication issues. Review the log file typically located at:

• Linux: /var/lib/boinc/stdoutdae.txt
• Windows: C:\ProgramData\BOINC\stdoutdae.txt

Quick Troubleshooting Checklist

• ✔ Is the BOINC client running?
• ✔ Are you using the correct syntax for boinccmd?
• ✔ Did you provide the correct password or check for gui_rpc_auth.cfg?
• ✔ Is port 31416 open on your system’s firewall?
• ✔ Are you running it with the right user permissions?

Advanced Tip: Use a Scripted Wrapper

If you’re automating boinccmd tasks, consider wrapping it in a script that checks for client availability first, and logs any failed attempts. This avoids mid-operation interruptions caused by poll status -1 errors.

Conclusion

The poll status -1 error, while initially intimidating, often boils down to simple misconfigurations or environmental issues. By methodically working through the error’s potential causes—from BOINC not running to authentication mismatches—users can both resolve their problem and gain a deeper understanding of the BOINC system. Understanding how boinccmd interfaces with the client is essential for efficient command-line or scripted management of BOINC workflows.

FAQ: BOINCCMD Poll Status Error -1

Q: What does “poll status -1” mean in BOINC?

A: It indicates that the command-line client couldn’t communicate with the BOINC client software, likely due to it not running, a blocked port, or incorrect settings.

Q: How do I check if BOINC is running?

A: On Linux or macOS, use ps aux | grep boinc. On Windows, check the Task Manager for boinc.exe or boincmgr.exe.

Q: What port does BOINC use by default?

A: BOINC typically uses TCP port 31416 for RPC communication.</dd