OpenDKIM Filter: Unable to create listening socket

Question

hi i keep getting this error in maillog.any ideas

Jul 22 10:16:52 veepiz opendkim[5145]: OpenDKIM Filter: Unable to bind to port inet:20209@localhost: Address already in use
Jul 22 10:16:52 veepiz opendkim[5145]: OpenDKIM Filter: Unable to create listening socket on conn inet:20209@localhost
Jul 22 10:16:52 veepiz opendkim[5145]: smfi_opensocket() failed

#ps aux | grep opendkim
opendkim  1361  0.0  0.1  40424   780 ?        Ss   10:11   0:00 /usr/local/sbin/opendkim -x /etc/opendkim.conf
opendkim  1362  0.0  0.2  56948  1508 ?        Sl   10:11   0:00 /usr/local/sbin/opendkim -x /etc/opendkim.conf
opendkim  2256 19.6  0.1  40424   928 ?        Ss   10:16   1:18 /usr/local/sbin/opendkim -x /etc/opendkim.conf
root     20733  0.0  0.1  61224   740 pts/0    S+   10:23   0:00 grep opendkim


#netstat -nlp | grep 20209
tcp        0      0 127.0.0.1:20209             0.0.0.0:*                   LISTEN      1362/opendkim

Answer 1

Looks like you've already got at least one OpenDKIM process running, which is preventing it from starting a new one. Kill all the processes you found with ps aux | grep opendkim and then restart OpenDKIM.

Answer 2

There is an "AutoRestart" option in dkim-filter.conf, which means that if the service is shutdown using "service dkim-milter stop", it will automatically restart itself. However, if you then try to start the service manually using "service dkim-milter start", it seems to create a second process and the server logs start filling up with the error message as the port is in use.

I have a script to manually check my mail server processes and restart them that was using the stop/start method, and experienced this problem.

Using "service dkim-milter restart" seems to work better, but occasionally I get the problem kicking in.

Answer 3

syntax, just rename Socket to SOCKET on DKIM-MILTER.CONF