I've recently set up a small mail server in a FreeBSD jail including OpenSMTPD.
One of the anomalies I am seeing is that /etc/periodic/daily/440.status-mailq ends up using 100% of one CPU core indefinitely.
Manually running this script also sits at 100% CPU with no apparent output or logging, so I think the most likely cause is an incompatibility with the periodic script settings and OpenSMTPD that just either hangs or sits in a loop.
For a small mail servers, would it make sense to just disable this task?
/etc/periodic.conf
daily_status_mailq_enable="NO"
One of the anomalies I am seeing is that /etc/periodic/daily/440.status-mailq ends up using 100% of one CPU core indefinitely.
Manually running this script also sits at 100% CPU with no apparent output or logging, so I think the most likely cause is an incompatibility with the periodic script settings and OpenSMTPD that just either hangs or sits in a loop.
Code:
root@mail:/etc/periodic/daily # /etc/periodic/daily/440.status-mailq
Mail in local queue:For a small mail servers, would it make sense to just disable this task?
/etc/periodic.conf
daily_status_mailq_enable="NO"