Hi Michael!
I uninstalled Dfix and replaced it with Dfix2. Ran all night with no
error messages! You are a genius!
A new dovecot sounds GREAT! My head is currently hurting from reading
the configs. The only change I made that has stayed is dovecot.conf
where I added the public IP of the router where most of the users
connect to login_trusted_networks. It seemed to delay the restarts a
bit. If this is a valid setting it might be useful to add the entries
from Server manager, Login Manager, Whitelist to this configuration
value, or not...
THANK YOU!
Michael Stauber wrote:
Hi Lewis,
Have replaced server with a much stouter machine but the number of
processes for dovecot remains the same.
I'm currently working on upgrading Dovecot to 2.2.30.1-1 on 5207R, 5208R
and 5209R as I hope that the latest version might address some of these
issues. However: As the update isn't trivial and needs a hell of a lot
of testing before I publish it, this will take some time. I hope to have
it ready sometime next week.
Cron <root@xxxx> /usr/local/sbin/dfix.sh
From (Cron Daemon)
To r...@xxxx.yyyy.zzz
Date Today 07:31
Contact photo
Message Body
Warning: Dovecot process count = 53 processes
Stopping dovecot (via systemctl): [ OK ]
dovecot: no process found
dovecot-auth: no process found
Starting dbrecover (via systemctl): Job for dbrecover.service failed
because the control process exited with error code. See "systemctl
status dbrecover.service" and "journalctl -xe" for details.
[FAILED]
In my experience the maximum number of allowed dovecot processes as
specified by the free Dfix package is a bit too arbitrarily picked. I've
seen highly active boxes that easily and without problems supported much
more than what Dfix allowed.
My suggestion: Uninstall Dfix and replace it with Dfix2 from the shop.
_______________________________________________
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx
