Cron error from exim4-base: "run-parts: /etc/cron.daily/exim4-base exited with return code 123"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
exim4 (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
The script /etc/cron.
run-parts: /etc/cron.
This error appears to originate from line 99, which reads:
su - --shell /bin/bash \
--command "xargs -0r -n 1 /usr/sbin/
When trying to run this command by hand, the following error is received:
Usage: exim_tidydb [-t <time>] <spool-directory> <database-name>
<database-name> = retry | misc | wait-<transport
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: exim4-base 4.74-1ubuntu1.2
ProcVersionSign
Uname: Linux 2.6.38-11-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Tue Aug 23 09:39:51 2011
InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426)
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
LANGUAGE=en_US:
SourcePackage: exim4
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in exim4 (Ubuntu): | |
importance: | Undecided → Medium |
I'm not able to reproduce this using the current codebase.
Note that exim_tidydb needs run like this:
$ /usr/sbin/ exim_tidydb /tmp misc
Tidying Exim hints database /tmp/db/misc
The exim4-base script itself has changed over the years, and I suspect it's fixed whatever the original problem is. For reference, the corresponding code now looks like this:
# if we reach this, invoking exim_tidydb from start-stop-daemon has
--command= "xargs -0r -n 1 /usr/sbin/ exim_tidydb $SPOOLDIR > /dev/null" \
Debian- exim
# failed, most probably because of libpam-tmpdir being in use
# (see #373786 and #376165)
find $SPOOLDIR/db -maxdepth 1 -name '*.lockfile' -or -name 'log.*' \
-or -type f -printf '%f\0' | \
runuser --shell=/bin/bash \
Is the original issue still reproducible with Ubuntu 18.04 or 20.04?