Troubleshooting BOINC Monitor: Fixes for Common Sync and Reporting IssuesBOINC Monitor is a useful tool for volunteers who participate in distributed computing projects through BOINC (Berkeley Open Infrastructure for Network Computing). It helps track workunits, report statistics, and synchronize project data. However, like any client or monitoring tool, users can run into sync and reporting issues that prevent accurate tracking or proper contribution credit. This article walks through the most common problems, explains likely causes, and gives step-by-step fixes and preventative tips.
Quick checklist before troubleshooting
- Make sure BOINC Manager itself is working — if the manager isn’t connecting to projects, BOINC Monitor can’t sync.
- Confirm internet connectivity — intermittent or restricted network access can break sync.
- Update software — use the latest versions of BOINC Manager and BOINC Monitor (or any third-party monitor) where possible.
- Restart both BOINC Manager and BOINC Monitor after changing settings or applying fixes.
Common problem 1 — BOINC Monitor cannot connect to BOINC Manager
Symptoms
- Monitor shows “Not connected” or similar status.
- No workunit or host data appear in the monitor.
Causes
- BOINC Manager isn’t running, or it’s running under a different user account.
- Local RPC password or port mismatch.
- Firewall or antivirus blocking local connections (localhost).
- Permission issues on OS (especially Windows UAC or macOS permissions).
Fixes
- Ensure BOINC Manager is running on the same machine and under the same user account as BOINC Monitor.
- Check BOINC Manager’s RPC settings:
- Open BOINC Manager → Advanced → Set Controller Password. If a password is set, supply the same in BOINC Monitor.
- Verify the RPC port (default 31416) — custom ports must match in both apps.
- Test local connection:
- In a browser on the same machine, try http://localhost:31416/ (or your configured port). If it prompts for the password or shows BOINC pages, the manager is reachable.
- Adjust firewall/antivirus:
- Allow BOINC Manager and BOINC Monitor to accept local network connections.
- On Windows, add inbound/outbound rules for the apps or allow the port.
- Run both apps with the same privileges:
- On Windows, avoid running BOINC Manager as Administrator while Monitor runs under a normal user (or vice versa).
- If using a remote manager, ensure remote RPC is enabled on the target BOINC instance and the remote host’s IP is allowed.
Prevention
- Keep RPC password and port documented when changing them.
- Use matching user accounts for background services and GUIs where possible.
Common problem 2 — Stale or incorrect statistics (credits, host runs, RAC)
Symptoms
- Reported credits or RAC (recent average credit) differ from project web pages.
- Stats in BOINC Monitor don’t update after tasks complete.
Causes
- Monitor uses cached data or poll interval is too long.
- BOINC Manager hasn’t uploaded finished results yet (upload queue stalled).
- Timezone or clock skew causing misinterpretation of timestamps.
- Different credit policies or server-side adjustments not reflected locally.
Fixes
- Force a refresh:
- In BOINC Monitor and BOINC Manager, use the refresh/reconnect option to pull the latest stats.
- Check BOINC upload queue:
- Open BOINC Manager → Tasks → check if finished tasks are queued for upload. If uploads are stalled, check network or project server status.
- Verify system clock and timezone:
- Ensure system time is accurate (consider using NTP/time sync).
- Compare with project server:
- Some projects adjust credit after validation; allow up to several hours for server-side changes to propagate.
- Clear Monitor cache:
- Locate BOINC Monitor’s cache or data directory and clear or reset it if corruption is suspected (backup first).
- Increase polling frequency (if configurable) to reduce lag between updates.
Prevention
- Schedule regular uploads and avoid overly restrictive firewall rules that block outbound HTTP(S).
- Keep monitor polling intervals reasonable (not too frequent to avoid server throttling, not too infrequent to avoid stale reads).
Common problem 3 — Workunits show as “in progress” but aren’t running
Symptoms
- BOINC Monitor and/or BOINC Manager list WUs as running but CPU/GPU usage is zero.
- Tasks remain in “running” state for a long time without completion.
Causes
- Task is waiting for a required resource (GPU drivers, disk access, or dependent application).
- Application crashed silently or is blocked by OS policy.
- Project sent an invalid or incompatible workunit for the host.
- Scheduler/server-side issue flagged workunit as running while client never executed it.
Fixes
- Inspect application logs:
- BOINC Manager → Event Log/Log files. Look for error messages about application start failures.
- Check dependencies:
- For GPU tasks, verify GPU drivers are up to date and CUDA/OpenCL runtimes are installed.
- Ensure the required application (binary) is present in the project’s app directory.
- Restart the task:
- Abort the workunit and re-request work (right-click → Abort task or Cancel and Fetch).
- Update BOINC client and project apps:
- Older clients may be incompatible with new app versions.
- If persistent, detach and reattach the project:
- Detach clears project state (backup any unreported results you want to keep).
- Contact project forums/support if many hosts show identical failures — may be server-side.
Prevention
- Keep drivers and BOINC client updated; monitor project announcements about app changes.
Common problem 4 — Results not uploading or validations pending
Symptoms
- Completed tasks remain in “upload pending” for an extended time.
- Validations take a very long time or never complete.
Causes
- Network issues (firewall, proxy, intermittent connectivity).
- Project server availability or queue backlogs.
- BOINC’s transfer throttling or limited bandwidth settings.
- Disk or filesystem issues preventing creation of upload files.
Fixes
- Check network connectivity:
- Ensure no proxy or corporate firewall is blocking BOINC’s outgoing connections (HTTP/HTTPS).
- Temporarily disable network-limiting features or test on a different network.
- Review BOINC transfer settings:
- In BOINC Manager → Options → Transfers, confirm bandwidth limits aren’t too restrictive.
- Inspect event log for upload errors:
- Look for specific HTTP error codes or timeout messages and act accordingly (e.g., 403 may indicate blocked by server; 503 indicates server overload).
- Free disk space and check filesystem health:
- Completed results are stored before upload; insufficient space or permission errors can block uploads.
- Retry uploads manually:
- Restart BOINC Manager or use the “Update”/“Synchronize” options to prompt uploads.
- If many uploads fail with server-side errors, check project status pages or forums.
Prevention
- Keep a buffer of free disk space, set reasonable transfer windows, and schedule uploads during non-peak hours if needed.
Common problem 5 — Discrepancies between BOINC Monitor and project web stats
Symptoms
- Monitor shows different totals for completed tasks, errors, or credit than the project web site.
- Host names or IDs differ between the monitor and project pages.
Causes
- Project servers apply credit adjustments, reclaimed work, or validation rejections not reflected immediately.
- Monitor may be reading local client state while web pages reflect aggregated server state.
- Multiple clients/hosts using the same account can make tracking confusing.
Fixes
- Allow time for server reconciliation — some changes take hours to appear on the website.
- Confirm account and host IDs:
- Ensure the same account is being used and that hostnames match.
- Refresh account data on the BOINC Manager:
- Use “Update” or “Synchronize” to force a server-side refresh.
- Cross-check logs:
- Look for messages about result rejection, credit adjustments, or duplicate host detections.
- Use project web tools:
- Many projects have diagnostics and host lists that explain rejections or changes.
Prevention
- Use distinct host names for each machine and avoid multiple clients sharing identical IDs.
Advanced diagnostics and tools
- Use the BOINC client’s command-line tools (boinccmd) for precise status and control:
- boinccmd –get_tasks
- boinccmd –simple_gui_info
- boinccmd –update
- Inspect BOINC event and stderr/stdout logs (usually in the BOINC data directory) for application-specific errors.
- For remote monitoring setups, ensure secure RPC and correct IP allowlists.
- Consider using project-specific diagnostic utilities or community tools that parse logs for common error patterns.
When to ask for help: what to include in support requests
If you contact project forums or support, include:
- BOINC Manager and BOINC Monitor versions.
- OS and version (Windows/macOS/Linux; service vs. GUI).
- Exact error messages from the Event Log.
- Recent relevant entries from stdout/stderr and client_event logs (pastebin or forum code blocks).
- Steps you’ve already tried (restart, detach/reattach, clear cache).
- Whether multiple hosts exhibit the same issue.
Summary of best practices
- Keep BOINC Manager, BOINC Monitor, and system drivers updated.
- Ensure consistent RPC/password/port settings and run apps under the same user context.
- Monitor upload queues, keep sufficient disk space, and verify network connectivity.
- Use logs and boinccmd for deeper diagnostics and share concise log excerpts when seeking help.
If you want, I can:
- Walk through your specific BOINC Monitor and Manager logs (paste relevant log snippets).
- Provide platform-specific steps (Windows/macOS/Linux) for checking RPC, firewall, and permissions.
Leave a Reply