diff options
Diffstat (limited to 'health/guides/boinc')
| -rw-r--r-- | health/guides/boinc/boinc_active_tasks.md | 44 | ||||
| -rw-r--r-- | health/guides/boinc/boinc_compute_errors.md | 33 | ||||
| -rw-r--r-- | health/guides/boinc/boinc_total_tasks.md | 32 | ||||
| -rw-r--r-- | health/guides/boinc/boinc_upload_errors.md | 30 |
4 files changed, 0 insertions, 139 deletions
diff --git a/health/guides/boinc/boinc_active_tasks.md b/health/guides/boinc/boinc_active_tasks.md deleted file mode 100644 index efdb7b9e2..000000000 --- a/health/guides/boinc/boinc_active_tasks.md +++ /dev/null @@ -1,44 +0,0 @@ -### Understand the alert - -This alert monitors the BOINC (Berkeley Open Infrastructure for Network Computing) client's average number of active tasks over the last 10 minutes. If you receive this alert, it means that there might be an issue with your BOINC tasks or client. - -### Troubleshoot the alert - -- Check the BOINC client logs - -1. Locate the BOINC client log file, usually in `/var/lib/boinc-client/`. -2. Inspect the log file for any issues or error messages related to task execution, connection, or client behavior. - -- Check the status of the BOINC client - -1. To check the status, run the following command: - - ``` - sudo /etc/init.d/boinc-client status - ``` - -2. If the client is not running, start it using: - - ``` - sudo /etc/init.d/boinc-client start - ``` - -- Restart the BOINC client - -1. Restart the BOINC client, in most of the Linux distros: - - ``` - sudo /etc/init.d/boinc-client restart - ``` - -- Ensure your system has adequate resources - -Monitoring and managing your computer resources (CPU, memory, disk space) can help ensure smooth operation of the BOINC client and its tasks. If your system is low on resources, consider freeing up space or upgrading your hardware. - -- Update the BOINC client - -Make sure your BOINC client is up-to-date by checking the official BOINC website (https://boinc.berkeley.edu/download.php) for the latest version. - -### Useful resources - -1. [BOINC User Manual](https://boinc.berkeley.edu/wiki/User_manual) diff --git a/health/guides/boinc/boinc_compute_errors.md b/health/guides/boinc/boinc_compute_errors.md deleted file mode 100644 index 8390686c3..000000000 --- a/health/guides/boinc/boinc_compute_errors.md +++ /dev/null @@ -1,33 +0,0 @@ -### Understand the alert - -The `boinc_compute_errors` alert indicates that your system has experienced an increase in the average number of compute errors over the last 10 minutes when running BOINC tasks. It is important to identify the cause of these errors and take appropriate action to minimize the impact on your system. - -### Troubleshoot the alert - -1. Check the BOINC client logs - BOINC client logs can provide useful information about compute errors. The logs can usually be found in the `/var/lib/boinc-client/` directory. Look for any error messages or information that could indicate the cause of the issues. - -2. Verify the system requirements - Ensure that your system meets the minimum requirements to run the BOINC tasks. This includes checking the CPU, RAM, disk space, and any other device-specific requirements. If your system does not meet the requirements, you may need to upgrade your hardware or reduce the number of tasks you are running simultaneously. - -3. Check for software and hardware compatibility - Some BOINC tasks may have specific hardware or software requirements, such as GPU support or compatibility with certain operating systems. Check the BOINC project documentation for any specific requirements you may be missing. - -4. Update the BOINC client software - Make sure your BOINC client software is up-to-date, as outdated versions can cause errors or unexpected behavior. You can check for updates and download the latest version from the [official BOINC website](https://boinc.berkeley.edu/download.php). - -5. Restart the BOINC client - If the issue persists, try restarting the BOINC client following the steps provided in the alert: - - - Abort the running task - - Restart the BOINC client: - ``` - root@netdata # /etc/init.d/boinc-client restart - ``` - -6. Seek assistance from the BOINC community - If you continue to experience issues after following these troubleshooting steps, consider seeking assistance from the BOINC community through forums or mailing lists. - -### Useful resources - -1. [BOINC hardware and software requirements](https://boinc.berkeley.edu/wiki/System_requirements) diff --git a/health/guides/boinc/boinc_total_tasks.md b/health/guides/boinc/boinc_total_tasks.md deleted file mode 100644 index c14e15f85..000000000 --- a/health/guides/boinc/boinc_total_tasks.md +++ /dev/null @@ -1,32 +0,0 @@ -### Understand the alert - -This alert monitors the average number of total tasks for the BOINC system over the last 10 minutes. If you receive this alert, it means that there is a deviation in the number of total tasks for your BOINC system, which may indicate an issue with the projects, the client, or even the tasks themselves. - -### Troubleshoot the alert - -#### Verify the project status - -1. Verify that the projects you contribute to are not suspended. You can check if the project has queued tasks to be done on the [BOINC projects page](https://boinc.berkeley.edu/projects.php). - -2. Access your BOINC Manager, go to the _Projects_ tab, and check if the projects you contribute to are in the correct state (Active or Running). If a project is suspended, you can select it and click _Resume_ to reactivate it. - -#### Investigate task issues - -1. Access your BOINC Manager and go to the _Tasks_ tab to check the status of the current tasks. Look for any _Failed_, _Error_, or _Postponed_ tasks. - -2. If there are failed tasks, try to reset them by selecting the task, right-clicking on it, and choosing _Update_ or _Reset_. Be aware that resetting a task will discard any progress made on it. - -#### Restart the BOINC client - -1. For most Linux distributions: - - ``` - sudo /etc/init.d/boinc-client restart - ``` - -2. For other operating systems or custom installations, refer to the BOINC's documentation for restarting the client: https://boinc.berkeley.edu/wiki/Stop_or_restart_BOINC - -#### Check system resources - -BOINC tasks may fail or slow down if there is not enough system resources (CPU, RAM, or Disk Space) available. Monitor your system performance using tools like `top`, `free`, and `df`, and make adjustments if necessary to ensure that BOINC has enough resources to complete tasks. - diff --git a/health/guides/boinc/boinc_upload_errors.md b/health/guides/boinc/boinc_upload_errors.md deleted file mode 100644 index 80c0ad364..000000000 --- a/health/guides/boinc/boinc_upload_errors.md +++ /dev/null @@ -1,30 +0,0 @@ -### Understand the alert - -This alert indicates that your BOINC node is experiencing an increase in the average number of failed uploads over the last 10 minutes. Failed uploads can affect the overall efficiency of your BOINC setup and may result in lost work and wasted computational resources. - -### Troubleshoot the alert - -1. Check for a new BOINC client's version - - Verify if there's a new version of the BOINC client available for your system on the [BOINC client downloads page](https://boinc.berkeley.edu/download_all.php). If there's a new version available, download and install the _recommended_ version. - -2. Verify BOINC project configuration - - Ensure that your BOINC client is properly configured to work on the projects you're participating in. Double-check your account login credentials, project URLs, and other settings in the BOINC client. Refer to the [BOINC User Manual](https://boinc.berkeley.edu/wiki/User_manual) for more information on configuring your BOINC client. - -3. Check network connectivity - - Verify that your system has a stable network connection and there are no firewall or proxy issues that might be blocking your BOINC client from uploading files. If necessary, adjust your firewall settings or connect to a different network. - -4. Inspect BOINC client logs - - Consult the BOINC client logs to gain insight into the upload errors. The logs can be found in the client's data directory. Refer to the [BOINC log file documentation](https://boinc.berkeley.edu/wiki/Log_Files) for more information on how to read and analyze the logs. - -5. Contact project support - - If you're still experiencing upload issues after following the steps above, consider reaching out to the support forums or mailing lists of the relevant BOINC project. The project's support team might be able to offer assistance or guidance in resolving your issue. - -### Useful resources - -1. [BOINC User Manual](https://boinc.berkeley.edu/wiki/User_manual) -2. [BOINC Downloads](https://boinc.berkeley.edu/download_all.php) |