How to Set Up BOINC Monitor for Efficient Project Management

Troubleshooting BOINC Monitor: Common Issues and Quick Fixes

BOINC Monitor is a helpful tool for tracking distributed computing projects, but like any software it can encounter issues. This guide lists common problems and concise fixes so you can get back to crunching quickly.

1. BOINC Monitor won’t start

• Cause: Corrupted configuration or missing runtime files.
• Fix:
  1. Close BOINC Monitor and BOINC client.
  2. Move the Monitor config file (typically in your user folder under .boinc or the app’s settings directory) to a backup location.
  3. Restart BOINC Monitor to recreate default settings.
  4. If that fails, reinstall the Monitor application.

2. Monitor shows no projects or tasks

• Cause: Monitor not connected to the BOINC client or wrong client host/port.
• Fix:
  1. Ensure the BOINC client is running.
  2. In Monitor settings, confirm host is set to localhost (or client IP) and port matches the client’s RPC port (default 31416).
  3. Verify the client’s remote access settings allow local connections (check GUI or config files).
  4. Restart both applications.

3. Incorrect or stale stats displayed

• Cause: Caching, delayed polling, or API mismatch.
• Fix:
  1. Force a refresh in the Monitor (use the refresh button or keyboard shortcut).
  2. Increase polling frequency in settings if updates are too slow.
  3. If values remain stale, restart the BOINC client and Monitor.
  4. Make sure both programs are compatible versions.

4. Authentication or permission errors

• Cause: RPC password missing/incorrect or file permission issues.
• Fix:
  1. Check the BOINC client’s gui_rpc_auth.cfg (or equivalent) for the correct password/token.
  2. Enter this password in Monitor’s connection settings.
  3. Ensure Monitor has permission to read BOINC files (run as the same user or grant access).
  4. On Linux, check file ownership and set appropriate permissions (e.g., chown/chmod).

5. Connection times out or is refused

• Cause: Firewall, SELinux, or network blocking.
• Fix:
  1. Temporarily disable firewall to test connectivity.
  2. If that fixes it, add an exception for the BOINC client port (default 31416) for local/remote connections.
  3. On Linux, check SELinux/AppArmor logs and allow the Monitor if blocked.
  4. For remote monitoring, ensure port forwarding or VPN is configured properly.

6. CPU/GPU usage shown incorrectly

• Cause: Compatibility with GPU drivers or incorrect device mapping.
• Fix:
  1. Update GPU drivers and BOINC client to the latest stable versions.
  2. Confirm Monitor supports your GPU type and driver version.
  3. Re-scan devices in Monitor settings or restart the client to detect hardware changes.
  4. For heterogeneous systems, ensure task affinity settings aren’t masking device usage.

7. Notifications or alerts not appearing

• Cause: Notification system disabled or muted.
• Fix:
  1. Check Monitor notification settings and enable desired alerts.
  2. Confirm system notification permissions allow the app to post alerts.
  3. Test notifications with a sample alert if available.

8. Crashes or freezes

• Cause: Memory leaks, conflicts, or corrupted UI cache.
• Fix:
  1. Update Monitor and BOINC to latest versions.
  2. Clear any UI cache or temp files used by the Monitor.
  3. Run the Monitor in safe or debug mode (if available) to capture logs.
  4. Submit logs to the Monitor’s issue tracker if the crash persists.

9. Wrong time remaining or deadline data

• Cause: Project server reporting changes or local clock skew.
• Fix:
  1. Sync system clock with an NTP server.
  2. Force update from project servers in the client and Monitor.
  3. Verify individual task deadlines on the project web pages if discrepancies continue.

10. Web interface not accessible

• Cause: Web server disabled or binding to wrong interface.
• Fix:
  1. Ensure the BOINC client’s web server is enabled in settings.
  2. Check which IP/interface the web server is bound to (localhost vs all interfaces).
  3. Verify port and firewall rules allow access.
  4. Use the correct URL (including port) and include any necessary RPC password if required.

Diagnostic checklist (quick)

1. Confirm BOINC client is running.
2. Verify host, port, and RPC password.
3. Restart both client and Monitor.
4. Check firewall/SELinux and permissions.
5. Update software and drivers.
6. Inspect logs for errors and report if needed.

When to seek help

• If logs show repeated errors after updates and restarts, or if crashes persist, collect Monitor and BOINC logs and open an issue on the Monitor’s support forum or GitHub with those logs and environment details (OS, BOINC and Monitor versions, GPU drivers).