tickets #65792
closedolaf: mb unknown command "vacuum"
100%
Description
There is a cronjob on olaf that continues to fail:
mirrorbrain@olaf withlock -q $WITHLOCK_DIR/LOCK-vacuum /usr/bin/mb -b $MB_INSTANCE vacuum
Output:
mb: unknown command: 'vacuum'
Try 'mb help' for info.
Updated by darix about 4 years ago
mb db --help
db: perform database maintenance, or start a shell
This command needs to be called with one of the following actions:
vacuum
Clean up unreferenced
files from the mirror database.
This should be done once a week for a busy file tree. Otherwise it
should be rarely needed, but can possibly improve performance if it
is able to shrink the database.
When called with the -n option, only the number of files to be
cleaned up is printed. This is purely for information.
sizes
Print the size of each database relation. This can provide insight
for the most appropriate database tuning.
shell
Conveniently open a database shell.
usage:
mb db vacuum [-q] [-n]
mb db sizes
mb db shell
Options:
-h, --help show this help message and exit
-q, --quiet Produce less output. Can be given multiple times.
-n, --dry-run don't delete, but only show statistics.
and it seems it has been like this for a while.
Updated by pjessen about 4 years ago
Please also see https://progress.opensuse.org/issues/65867 - function ip4r_size(iprange) does not exist.
Last time I added a mirror was in early March, https://progress.opensuse.org/issues/64135
Wrt to the 'vacuum' issue, it looks like the syntax was changed ? "mb db vacuum" instead of "mb vacuum" ?
Updated by pjessen about 4 years ago
pjessen wrote:
Please also see https://progress.opensuse.org/issues/65867 - function ip4r_size(iprange) does not exist.
Darix, if you are working on mirrorbrain - in January, I fixed the above, but only temporarily:
https://progress.opensuse.org/issues/62678#note-4
Updated by lrupp over 2 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Hi there - and a Happy and Healthy 2022!
I'm currently closing old tickets which did not see much change.
If the main concern still exists and should be handled, please re-open by just replying to this Email.
Thanks in advance,
Lars