Adds a new function to check the system dmesg logs for any critical errors or warnings. This
helps identify potential hardware or kernel issues that may impact the system stability.
The function will print out the last 10 errors found in the dmesg logs, and indicate if
there are more errors. It also warns the user if they don't have the required permissions
to read the dmesg logs.
This change is important to provide a more comprehensive health check for CasaOS systems,
as dmesg logs can often contain valuable information about underlying system issues.
Adds two new functions, `check_root_privileges()` and `check_sudo_privileges()`, to handle
the cases where the script is run with insufficient privileges. The script now
provides clearer instructions and prompts the user to either continue with the
limited functionality or exit and run the script with the required privileges.
This commit refactors all the shell scripts to use `#!/usr/bin/env bash` instead of `#!/bin/bash`. This change ensures that the scripts will run with the system's default Bash interpreter, even if it is not located at the standard `/bin/bash` path.
Replaces the hardcoded shebang `#!/bin/bash` with `#!/usr/bin/env bash` to
ensure the script can be executed on systems where the Bash binary is not
located at the default path `/bin/bash`.
This commit introduces the following changes:
- Checks if the script is running with sudo privileges. If not, it prompts the
user to continue without sudo or exit the script.
- Updates the version display of the BigBearCasaOS Healthcheck to V3.2.
The sudo check is added to ensure that the script can perform all necessary
checks and provide complete information, as some checks may require elevated
privileges. The version update reflects the latest release of the healthcheck
tool.
This commit introduces several improvements to the server update script:
- Added branding message and decorative lines for better presentation
- Implemented an unattended mode to allow for automated updates without user prompts
- Added functions to check disk space and handle known problematic packages
- Divided the update process into multiple steps (update package list, upgrade packages, full upgrade, remove unnecessary packages, clean cache) with user confirmation prompts
- Improved logging to a log file for better troubleshooting
- Added instructions on how to support the project
The goal of these changes is to provide a more user-friendly and reliable server update script for Ubuntu and Debian systems.
This commit introduces a set of functions and variables to provide colorful and formatted console output for the `run.sh` script. It includes the following changes:
- Added color variables for ANSI escape codes (BLUE, GREEN, YELLOW, RED, BOLD, NC).
- Added Unicode characters for various symbols (CHECK_MARK, CROSS_MARK, RIGHT_ARROW, INFO_MARK).
- Created print functions for success, warning, and error messages.
- Displayed a welcome message with community links and support information.
- Formatted the memory output to display in MB or GB as appropriate.
- Improved the formatting and readability of the script's output.
The primary goal of these changes is to enhance the user experience and make the script's output more visually appealing and informative.
This commit introduces the following changes:
1. Adds a new function `check_docker_ports` to the `casaos-healthcheck/run.sh` script. This
function checks if Docker is installed and running, and if UFW (Uncomplicated Firewall)
is installed and active. It then retrieves all running Docker containers and checks if
the ports exposed by these containers are allowed by the UFW rules. If a port is not
allowed, a warning is displayed.
2. Updates the version display in the `print_header` function from "BigBearCasaOS Healthcheck
V3.0" to "BigBearCasaOS Healthcheck V3.1".
The Docker port check is an important addition to the healthcheck script, as it helps
identify potential issues with firewall rules that may be blocking Docker container ports.
This can be especially useful in troubleshooting network-related problems.
The version update reflects the changes introduced in this commit.
* ✨🔑 feat(reset-password): Add fallback for missing user.db
This change adds a fallback mechanism to handle cases where the
`/var/lib/casaos/db/user.db` file is not found. If the file is
missing, the script attempts to check if the file exists in an
alternative location. If found, it backs up the file and restarts
the CasaOS user service to ensure the password reset functionality
works correctly.
* 🔐 feat(reset-password-for-casaos): Remove user.db existence
check and provide alternative method
The changes remove the check for the existence of the `user.db` file
and provide an alternative method to handle the case where the file is
not found. This change is intended to make the password reset process
more robust and accommodate systems where the `user.db` file may not be
present.
This commit introduces several improvements to the CasaOS password reset script:
- Adds functions to print headers, check service status, and backup the user database.
- Checks if the script is run with sudo privileges.
- Displays a welcome message with links and information about supporting the project.
- Checks if the CasaOS service is active before proceeding.
- Prompts the user for confirmation before resetting the password.
- Backs up the user database before removing the original file.
- Restarts the CasaOS user service to reflect the changes.
- Provides clear success and error messages to the user.
These changes aim to make the password reset process more robust, user-friendly, and informative.
* 🎨 feat(healthcheck): add new health checks for Docker and storage
This commit introduces two new health checks to the BigBearCasaOS
Healthcheck script:
1. `check_docker_status()`: This function checks if Docker is installed and
running on the system. It provides clear feedback based on the Docker
status.
2. `check_storage_health()`: This function checks the health of all storage
devices (disks) connected to the system using the `smartctl` tool. It
reports the health status of each disk, indicating if it has passed the
SMART health check or if there may be potential issues.
These new health checks provide a more comprehensive overview of the system's
overall health and help identify any potential issues related to Docker or
storage-related problems.
* ✨📄 feat(casaos-healthcheck): Enhance DNS resolution and add system health checks
This change enhances the DNS resolution checks in the casaos-healthcheck script and adds new system health checks for disk space, CPU load, memory usage, and system temperature.
The key changes include:
- Improve DNS resolution by trying multiple DNS servers and retrying on failure
- Add a check for basic network connectivity before attempting DNS lookups
- Implement a check for disk space usage, with a configurable threshold
- Implement a check for CPU load, with a configurable threshold based on the number of cores
- Implement a check for memory usage, with a configurable threshold based on total memory
- Implement a check for system temperature, using the `sensors` command or `/sys/class/thermal` when available
- Add a check for available system updates using `apt-get`
These new checks provide a more comprehensive health monitoring solution for the CasaOS system.
* ✨ feat: Bump healthcheck version to 3.0
Bumped the version of the BigBearCasaOS Healthcheck tool from 2.3 to 3.0.
This change reflects the latest updates and improvements made to the
healthcheck script.
This commit introduces several improvements to the Docker cleanup script:
- Adds a verbose mode to print detailed messages during the cleanup process.
- Implements a dry run mode to simulate the cleanup without actually removing any resources.
- Improves the container, image, volume, and network cleanup functions to better handle the cleanup process and provide more informative output.
- Adds a summary of the cleanup results at the end of the script.
- Includes a help message to explain the available options.
- Refactors the script to improve readability and maintainability.
The main goal of these changes is to provide a more user-friendly and robust Docker cleanup solution.
This change ensures that the new Portainer container is created with the same ports as the
current configuration. It first checks the existing Portainer container to get the
current port mappings, and then uses those values when starting the new container.
This way, clients do not need to update any of their configurations when the Portainer
version is updated.
