Curtis Vaughan via Postfix-users:
I realize there have been a lot of posts about this issue, but in my
attempts so far, nothing has resolved this issue for me.
The postfix server in question is running on Ubuntu LTS 24.04 and has
been in operation for over a decade. But today while looking in the logs
about a different issue I was constantly seeing:
warning: connect to milter service inet:127.0.0.1:8891: connection refused
That usuallyu means that the daemon isn't running, or some 'security'
is preventing connections to it.
The culprit seems to be opendkim. All the config files have info
relating to this server, so it must have been set up to run previously.
When I checked the service it wouldn't start and was masked. After
unmasking it, I was able to start it.
> service opendkim start
Regardless, checking to see what is listening on port 8891 produced no
results.
postfix is part of the opendkim group, btw.
Kind of at my wits end here. Any ideas?
Find out why opendkim does not start. Maybe strace can reveal
something. But I don't know if systemd allows you to do that.
In that case one may have to use old-school tooling
mv opendkim opendkim-real
cat >opendkim
#!/bin/sh
mkdir -p /tmp/opendkim
strace -f -o /tmp/opendkim/$$ /path/to/opendkim-real "$@"
^D
chmod 755 opendkim
Start opendkin with systctl, then look for errors in files under
/tmp/opendkim.
Wietse
_______________________________________________
But doesn't this mean it is running?
systemctl status opendkim
● opendkim.service - LSB: Start the OpenDKIM service
Loaded: loaded (/etc/init.d/opendkim; generated)
Active: active (exited) since Wed 2025-01-22 13:06:32 PST; 11min ago
Docs: man:systemd-sysv-generator(8)
Process: 2177789 ExecStart=/etc/init.d/opendkim start (code=exited,
status=0/SUCCESS)
CPU: 6ms
Jan 22 13:06:32 Nautilus systemd[1]: Starting opendkim.service - LSB:
Start the OpenDKIM service...
Jan 22 13:06:32 Nautilus systemd[1]: Started opendkim.service - LSB:
Start the OpenDKIM service.
Furthermore, I can't start and stop it with systemctl, I have to use the
service command, so maybe the old-school tooling might work.
However, another thing I've noticed is that there is no opendkim.sock
nor opendkim.pid file being created.
It looks like there should be a /run/opendkim directory, but it doesn't
exist.
Final note, looking at mail.err logs, well, there are logs there for
opendkim from Sept. So obviously it was working up through Sept.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
