Hi Markus,
Am 24.03.2018 um 05:22 schrieb Markus Gschwendt:
> Sorry for the late Answer. I had lots of work last week.
No worries :)
> I tried again but got stuck on restarting 'mailman-web'.
> There is a '/var/run/mailman3/web/ directory which is empty and the
> log reports a different
Sorry for the late Answer. I had lots of work last week.
I tried again but got stuck on restarting 'mailman-web'.
There is a '/var/run/mailman3/web/ directory which is empty and the log
reports a different directory for the pid file:
writing pidfile to /run/mailman3-web/mailman3-web.pid
Hi Markus,
I did quite some testing of the mailman3 packages in the last days,
using all possible database backends. So far, I failed to reproduce the
bug you discovered.
After testing different settings, I'm pretty confident that indeed the
database settings from
cat /etc/mailman3/mailman3-suite.py
# This file is imported by the Mailman Suite. It is used to override
# the default settings from /usr/share/mailman3-suite/settings.py.
# SECURITY WARNING: keep the secret key used in production secret!
SECRET_KEY =
Control: reassign -1 mailman3-suite
Control: notfound -1 3.1.1
Control: found -1 0+20170523-10
Control: tag -1 +moreinfo
Hi Markus,
thanks for the bugreport.
Am 02.03.2018 um 20:23 schrieb Markus Gschwendt:
> Fresh install with sqlite as DB.
> Hyperkitty tries to connect postgres on system
Same/similar issue with the cron daily script:
...
OperationalError: could not connect to server: No such file or
directory
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.5432"?
ERROR OCCURED IN DAILY JOB: daily_cleanup
Package: mailman3
Version: 3.1.1
System: debian stretch-backports
Fresh install with sqlite as DB.
Hyperkitty tries to connect postgres on system using sqlite.
Postgres is not installed on this system.
Mail from (hourly) cronjob:
Traceback (most recent call last):
File
7 matches
Mail list logo
