A few issues
[root@localhost BUILD]# dsctl localhost db2bak usage: dsctl instance db2bak [-h] archive dsctl instance db2bak: error: the following arguments are required: archive
The old db2bak would create a backup using the date as the name, and would store it in the server's backup directory if the user did NOT supply a specific backup location. We should add this functionality back.
Then if the command fails, it report success anyway
# dsctl localhost db2bak mark OK group dirsrv exists OK user dirsrv exists db2bak: Can not operate while directory server is running db2bak successful Command successful. # echo $? 0
Also we should also remove the extra output:
OK group dirsrv exists OK user dirsrv exists [12/Jun/2018:10:42:08.493182296 -0400] - INFO - ldbm_instance_config_cachememsize_set - force a minimal value 512000 [12/Jun/2018:10:42:08.511524768 -0400] - INFO - ldbm_instance_config_cachememsize_set - force a minimal value 512000 [12/Jun/2018:10:42:08.525847260 -0400] - INFO - dblayer_copy_directory - Backing up file 1 (/var/log/dirsrv/slapd-localhost/mark/userroot/nscpEntryDN.db) [12/Jun/2018:10:42:08.528364169 -0400] - INFO - dblayer_copyfile - Copying /var/lib/dirsrv/slapd-localhost/db/userroot/nscpEntryDN.db to /var/log/dirsrv/slapd-localhost/mark/userroot/nscpEntryDN.db ... ...
These scripts should be as "quiet" as possible. Only in a verbose mode should we print this extra info. Also it seems a bit odd that it's storing the backup in the logs directory. Not sure if this was by design or not, but it should go into the server's backup directory
Making good progress here.
I've also decided it is best to leave the output as is. It's actually coming from the db2bak shell script. So until we get rid of the shell scripts (and replace them with python scripts?) we'll not change this behavior.
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
Closing this as a duplicate of https://pagure.io/389-ds-base/issue/49712
Metadata Update from @mreynolds: - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2834
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: duplicate)
Login to comment on this ticket.