From: Murray S. K. <ms...@se...> - 2008-02-01 17:50:41
|
On Thu, 31 Jan 2008, Chris 'Chipper' Chiapusio wrote: > I started experiencing dkim-filter (signing) crashes after upgrading > past 2.4.0. > > 2.4.1-4 crash with the following error: > Jan 31 15:00:17 chipsworld postfix/cleanup[15448]: 400D31C80C2: > message-id=<200...@ch...> > Jan 31 15:00:17 chipsworld postfix/cleanup[15448]: warning: milter > inet:localhost:10027: can't read SMFIC_EOH reply packet header: S > uccess > Jan 31 15:00:17 chipsworld dkim-filter[11676]: terminated with signal 6, > restarting > Jan 31 15:00:17 chipsworld postfix/cleanup[15448]: 400D31C80C2: > milter-reject: END-OF-MESSAGE from localhost[127.0.0.1]: 4.7.1 Servi > ce unavailable - try again later; from=<na...@ll...> > to=<ch...@ll...> > > I've tried setting milter_protocol equal to 2 or 3 with the same > results, 2.4.0 is reliable and anything after will evenatully crash. > If there is any other information I can provide to help diagnose this, > just say the word. My dkim-filter for verifying does not tank. Signal 6 is SIGABRT which is almost always tripped by an assertion failure in the code. Did it leave a coredump? If not, you were either running having changed userids (the "-u" command line option or "UserID" configuration file option), or the current directory wasn't writeable by the process. Either an e-mail that causes the problem or a stack trace would be ideal for figuring out the problem. |