Re: opendkim died or not responding?

From: Seba <free4cd_at_googlemail.com>
Date: Wed, 7 Oct 2009 21:51:44 +0200

Murray,

>> -----Original Message-----
>> From: opendkim-users-bounce_at_lists.opendkim.org [mailto:opendkim-users-
>> bounce_at_lists.opendkim.org] On Behalf Of Seba
>> Sent: Tuesday, October 06, 2009 6:06 AM
>> To: opendkim-users_at_lists.opendkim.org
>> Subject: opendkim died or not responding?
>>
>> Hi,
>>
>> I've found these errors in my logfile and I've no idea what happened.
>>
>> Oct  5 21:39:57 tux postfix/smtpd[30692]: connect from
>> unknown[173.58.114.189]
>> Oct  5 21:40:17 tux postfix/smtpd[30692]: fatal: host/service
>> localhost/8891 not found: Name or service not known
>> Oct  5 21:40:18 tux postfix/master[28810]: warning: process
>> /usr/libexec/postfix/smtpd pid 30692 exit status 1
>> Oct  5 21:40:18 tux postfix/master[28810]: warning:
>> /usr/libexec/postfix/smtpd: bad command startup -- throttling
>> Oct  5 21:41:38 tux postfix/smtpd[30696]: connect from
>> unknown[173.58.114.189]
>> Oct  5 21:41:58 tux postfix/smtpd[30696]: fatal: host/service
>> localhost/8891 not found: Name or service not known
>> Oct  5 21:41:59 tux postfix/master[28810]: warning: process
>> /usr/libexec/postfix/smtpd pid 30696 exit status 1
>> Oct  5 21:41:59 tux postfix/master[28810]: warning:
>> /usr/libexec/postfix/smtpd: bad command startup -- throttling
>>
>> I've nothing found in other logs that opendkim died or else. The PID
>> of opendkim was created on 09-20-2009 so it seems that opendkim was OK
>> and was not restarted.
>>
>> opendkim versrion is 1.1.0 and postfix is 2.6.5.
>>
>> Any idea what could be the case for that error or to prevent such
>> failures?
>
> I don't know a lot about postfix so I'm guessing here, but it looks to me like postfix is having problems understanding what "localhost/8891" means.  Perhaps your DNS is down and it can't translate "localhost"?
>
> If you see opendkim in your "ps guaxww" output, or the pid listed in the pid file is still running, or you can use telnet to talk to port 8891 on 127.0.0.1, the filter is still running but postfix is unable to connect to it for some reason.
>
> I'm afraid I can't say much else given the information you've provided so far.
>
> -MSK

thank you for your hint. It may be possible that it was really a
problem with the name resolution...

I use a "minimal" linux installation from my webhoster as a base
installation. Normally I do not use a local dns or the local
/etc/hosts so I thought that it would be a good idea to verify if the
entries in /etc/hosts contains "localhost" and so on but this file
does not exist... I noticed this only now so this could be the reason.

Now I've changed "localhost" to "127.0.0.1" and created a local
/etc/hosts file which contains basic entries like "localhost" and the
"real" hostname which the correct IP addresses.

The problem should hopefully be solved with these measures.

Thanks,
Seba
Received on Wed Oct 07 2009 - 19:51:59 PST