SM <[email protected]> writes: > At 09:02 28-08-2009, Micah Anderson wrote: >>Everything seems fine on my dkim signing service. However, every >>hour, almost exactly at the same time, I get this error >>in my logs: >> >>Aug 26 14:02:45 mx2 postfix/cleanup[12057]: warning: connect to >>Milter service unix:/var/run/dkim-filter/dkim-filter.sock: No such file or >>directory > > The milter is not running.
However, it actually is... as you can see from the process list below, the milter has not been stopped, and it has been running for days, the socket itself has the same date/timestamp as when the process was started. Perhaps internally the milter is not responding, or postfix has closed its internal connection to the milter? >>It goes away, only to come back at :02 after the hour again next hour. >> >>I have no cronjobs running on this machine at all, and nothing else >>happening at a regular hourly interval. > > Do your logs show that the milter is started around that time? Your > description points to a process starting the milter or the > autorestart feature of the milter kicking in. No, the only log entry I am seeing is the one above. >>I don't want to ignore this error, because when dkim-milter *does* >>crash, I get quite a few of these messages, and that notifies me that >>the daemon needs to be restarted. However, seeing this message once an >>hour is a bit annoying. > > dkim-milter should not crash. No it should not... and it has not for a long time, I think the newer versions have been very stable. However, if for some reason it *does* crash (e.g. an OOM condition is met, or a sloppy sysadmin, etc.), then these errors are generated, and we will know about it, as long as we aren't ignoring this message. >>The dkim-milter process runs like this: >> >>108 11255 0.0 0.0 19892 1704 ? Ssl Aug21 0:10 >>/usr/sbin/dkim-filter -x /etc/dkim-filter.conf -u dkim-filter -P >>/var/run/dkim-filter/dkim-filter.pid -p >>local:/var/run/dkim-filter/dkim-filter.sock -l -i /etc/dkim-sign -c >>relaxed/simple -S rsa-sha1 -d mydomain.net -D -s myselector > > [snip] > >>As you can see from the process list above, the dkim-filter process has >>been running for 7 days, so it is not being restarted every hour. > > Verify whether the sock file exists. It does, in fact it is still running, with the same date/timestamps as the process entry I originally wrote this email about: srwxrwxr-x 1 dkim-filter dkim-filter 0 2009-08-21 22:45 /var/run/dkim-filter/dkim-filter.sock > BTW, how are the alert messages being generated? They are put in our logfiles, and we use logcheck to be alerted of uncommon messages. Thanks, Micah ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
