On 11/3/25 08:06, dap1--- via Mailman-users wrote:
I seems to be having a problem with some cronjobs not running; I'm getting the
following email errors/warnings:
Subject: Cron <www-data@dap002> [ -f /usr/bin/django-admin ] && flock -n
/var/run/mailman3-web/cron.minutely /usr/share/mailman3-web/manage.py runjobs minutely
Body: flock: cannot open lock file /var/run/mailman3-web/cron.minutely: No such
file or directory
Obviously there is a path specified wrong but I can't find where that is.
Something is configured incorrectly. Is this left over from a prior
install of an Ubuntu mailman-web package?
https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-mailman-web
says these should run /opt/mailman/venv/bin/mailman-web runjobs, not
/usr/share/mailman3-web/manage.py runjobs.
Subject: Cron <mailman@dap002> /opt/mailman/venv/bin/mailman-web runjobs
minutely
Body: System check identified some issues:
WARNINGS:
?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use:
settings.ACCOUNT_LOGIN_METHODS = {'username', 'email'}
?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use:
settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*',
'password2*']
This is https://gitlab.com/mailman/mailman-web/-/issues/37, fixed for
the next release by
https://gitlab.com/mailman/mailman-web/-/merge_requests/58. See the
changelog at https://gitlab.com/mailman/mailman-web
In the mean time, these aren't fatal.
--
Mark Sapiro <[email protected]> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
_______________________________________________
Mailman-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at:
https://lists.mailman3.org/archives/list/[email protected]/message/4MUMS2AZJLZ6NDPCTZ7OEY2HKE66HO4M/
This message sent to [email protected]
