No more incorrect error messages for scheduled backups on non-master nodes
Details
| Detail name | Value |
|---|---|
| Changelog Number | 21824 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 8.0.0 |
| Fix Versions | Exasol 8.32.0, Exasol 8.29.6 |
| Resolution Date | 2024-11-08 |
Description
Previously backups scheduled via confd_client db_backup_add_schedule would incorrectly log error messages such as Could not start backup 'X' for database Y (system not started?!) on all but one node (even if everything actually worked). This could cause false positive alerts in monitoring systems.
Workaround
Ignore the error message unless it is logged on every node.
Fix
Running a scheduled backup now no longer prints the incorrect error message. Therefore any custom rules that have been set up in monitoring tools for ignoring the incorrect error message can and should now be revoked, because this error message is now only printed when something actually went wrong.
