On 21-02-22 10:56, Brent Clark via Exim-users wrote:
Good day Guys Where I work, we keep getting the following message "retry time not reached for any host". To resolve, we run the following: cd /var/spool/exim/db rm -f retry retry.lockfile rm -f wait-remote_smtp wait-remote_smtp.lockfile service exim restart Can anyone please share any preventative tips and / tricks. Or better a means of auto healing. I dont want to have to write a bash / cron to manage this. It would be ideal to get exim to (re)solve the issue. Googling isn't proving to be helpful in this instance. Your help / feedback would be appreciated. Regards Brent Clark
hi Brent, You can finetune your intervals in the "retry configuration" of your exim, versus the queue run interval (-q option). Its documented here: https://www.exim.org/exim-html-current/doc/html/spec_html/ch-retry_configuration.html To make simple, if you configure your retry time << queue run interval, you will not see these messages in the logs. There is no need to remove the lockfiles by hand if your exim is configured properly. A. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
