bacula awk script for sqlite catalog backup broken
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bacula |
Invalid
|
Undecided
|
Unassigned | ||
bacula (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: bacula-
When I try to run a catalog backup it appears to be endlessly looping and recreating the sqlite dump. It is not quite endless though, just a bug in the awk script.
The script /etc/bacula/
system("echo '.dump' | /usr/bin/sqlite3 /var/lib/
This gets run as part of:
/usr/bin/awk -f /etc/bacula/
which essentially does the sqlite dump for every line in bacula-dir.conf.
The simplest way to solve this and maintain compatibility with other versions of this script for other databases is to use:
BEGIN {system("echo '.dump' | /usr/bin/sqlite3 /var/lib/
This may have gone unnoticed since the sqlite3 back-end is not the default for bacula installs.
Related branches
Changed in bacula (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Low |
Confirmed that the script is doing "the wrong thing", and the proposed fix is the right way to go.
Marking Importance Low because, while it does waste a lot of time and system resources, it still "works", just not very well.