It seem you may have a Berkley DB problem on your system. From https://web.stanford.edu/class/cs276a/projects/docs/berkeleydb/api_c/log_archive.html <https://web.stanford.edu/class/cs276a/projects/docs/berkeleydb/api_c/log_archive.html>: Errors
The DB_ENV->log_archive method may fail and return a non-zero error for the following conditions: EINVAL An invalid flag value or parameter was specified. The log was corrupted. The DB_ENV->log_archive method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->log_archive method may fail and return DB_RUNRECOVERY <https://web.stanford.edu/class/cs276a/projects/docs/berkeleydb/ref/program/errorret.html#DB_RUNRECOVERY>, in which case all subsequent Berkeley DB calls will fail in the same way. I’d recommend checking that your DB is not corrupt and consider re-building it to see if you have better luck. You might also want to see if re-building/installing the SKS software on the system helps. I’m using the bionic package from: https://launchpad.net/~canonical-sysadmins/+archive/ubuntu/sks-public/+packages <https://launchpad.net/~canonical-sysadmins/+archive/ubuntu/sks-public/+packages> so no build was required and I have not had any issues with the same cron job. -T > On Sep 5, 2020, at 16:39, Dan via SKS development and deployment list > <sks-devel@nongnu.org> wrote: > > Not on my end. Watch: > > root@jupiter:/var/lib/sks# db_archive -d -h PTree > db_archive: BDB1566 DB_ENV->log_archive interface requires an environment > configured for the logging subsystem > db_archive: DB_ENV->log_archive: Invalid argument > > On 9/5/2020 5:35 PM, Skip Carter wrote: >> What args are you using ? >> >> For me: db_archive -d -h PTree >> just silently runs with no errors >> >
signature.asc
Description: Message signed with OpenPGP
