Hi!
I'm very grateful for your help :)
Okay, sorry about that. I will try to give more information now. We use https://gitlab.com/mailman/mailman-suite to set up mailman with postorius and hyperkitty. Additional we use NGINX web server and postgresql database.
Settings.py configuration are basically same with this - https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_project... The only differences are: *In database section we use postgresql configuration *Social accounts configuration is disabled *Haystack connections we use xapian_backend.XapianEngine engine
Here is also our mailman.cfg: [database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgres://mailman:xxxxxx@localhost/mailman
[paths.custom] bin_dir: /usr/local/bin var_dir: /var/lib/mailman queue_dir: /var/spool/mailman log_dir: /var/log/mailman lock_dir: /var/lock/mailman etc_dir: /etc ext_dir: /etc/mailman.d pid_file: /var/run/mailman/master.pid
[mailman] layout: custom site_owner: xxxx anonymous_list_keep_headers:
[mta]
[loggin.archiver] path: archiver.log level: debug
[archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /etc/hyperkitty.cfg clobber_date: maybe clobber_skew: 1d
Here is our uwsgi.ini: # /etc/uwsgi.ini [uwsgi] uid = uwsgi gid = uwsgi pidfile = /run/uwsgi/uwsgi.pid emperor = /etc/uwsgi.d stats = /run/uwsgi/stats.sock chmod-socket = 660 emperor-tyrant = true cap = setgid,setuid buffer-size = 32000
# process limits limit-as = 512
# Mailman settings plugins = python36,logfile master = true process = 2 threads = 2 chdir = /opt/mailman-suite/mailman-suite_project/ wsgi-file = wsgi.py uwsgi-socket = 0.0.0.0:8000 attach-daemon = ./manage.py qcluster
# Logging req-logger = file:/var/log/uwsgi/uwsgi.log logger = cron file:/var/log/uwsgi/uwsgi-cron.log log-route = cron uwsgi-cron logger = qcluster file:/var/log/uwsgi/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons logger = file:/var/log/uwsgi/uwsgi-error.log
It seems that we have some perfomance issues on webUI, if we try to check archived messages. Some lists, that contains low number of archives is not a problem but lists, that contains several thousand messages and grows faster are issue. Sometimes it loads so long, that i get "504 Gateway Time-Out" I was also monitoring server perfomance and i didnt see any issues on that side. It seems that there might be some issues to read archived messages from database. But this is just my one opinion.
I also debugged log files and found some error messages:
- mailmansuite.log -> django.db.utils.DatabaseError: out of memory for query result
it happens when i try to open a lists in webui, to check archived messages.
nginx-error.log -> upstream timed out (110: Connection timed out) while reading response header from upstream # also happens when i try to open list in hyperkitty and it takes long time to open
If any information is more needed then let me know. My one thought was also, that maybe i need to try rebuild_indexes.