A QoreStor server upgraded to 7.5.x (often following an OS upgrade such as CentOS 8.x to AlmaLinux 8.x) experiences frequent crashes or service restarts. The issue is typically triggered when a backup job is initiated. While storage services like ocafsd may not show immediate critical errors, the system becomes unstable, and the UI may fail to load or report fatal errors.
An incompatibility with the system's sar (System Activity Reporter) utility output. In certain OS environments, the sar command produces a special character that resembles a space but is a non-standard character. The QoreStor UI/monitoring logic interprets this as an unexpected additional column in the command output, leading to a fatal parsing error and a subsequent service restart loop.
To resolve this issue, the sar binary used must be replaced with a version that correctly handles the output:
Note: Before proceeding with the steps below, please contact Quest Support to obtain the corrected sar binary file required for this resolution.
1. Check if the QoreStor sar binary is a symbolic link to the system's sar:
ls -l /opt/qorestor/bin/sar
Expected output example: lrwxrwxrwx. 1 root root 12 Apr 29 02:28 /opt/qorestor/bin/sar -> /usr/bin/sar
2. Remove the symbolic link:
unlink /opt/qorestor/bin/sar
3. Replace with the corrected binary:
Copy the obtained binary received from Quest Support to /opt/qorestor/bin/sar
4. Set executable permissions:
chmod +x /opt/qorestor/bin/sar
5. Restart QoreStor services to apply the changes:
systemctl stop ocards
systemctl stop ocards
