Description of problem: `db-control backup` should log when it creates a backup and that log should be present in spacewalk-debug tarball Version-Release number of selected component (if applicable): Satellite 5.7.0+ How reproducible: always Steps to Reproduce: 1. # db-control backup 2. # db-control online-backup Actual results: It is not logged anywhere Expected results: Successful run should be recorded somewhere
db-control already logs into /var/log/rhn/rhn_database.log which is packed with spacewalk-debug, I've just extended it by a bit to see whether the action completed successfully or not spacewalk.git(master): 372963d390ce0ffa0b1cfb9591d4a12ddf0b703c
FailedQA with spacewalk-web-2.5.2-14. db-control is indeed logged in /var/log/rhn/rhn_database.log. However, regardless of whether it completed successfully or unsuccessfully, it always says "Completed: db-control [...]" so there is no way to determine whether the backup was actually done or it failed. Please, just make the output say something about failure in case $?!=0.
Verified with spacewalk-web-2.5.2-14. 1) # db-control backup 2) # spacewalk-debug 3) untar + unbzip the resulting archive 4) # grep backup rhn_logs/rhn/rhn_database.log 5) ^ check time, it should be a few seconds ago when you ran the backup 6) repeat for db-control online-backup In case of successful run, the log says "Invocation:" and then "Completed:" while in case of unsuccessfull run, it only says "Invocation:".
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0274