On Wed, 18 Nov 2009, Aniruddha Barua wrote:
When mimedefang is working fine after this manual stop, 5 sec wait and start, what happens when you restart it again? Does it still show the error messages or other problematic signs?
The restart fails again. I get a lot of this: sm-mta[36460]: nAKBJxPa036460: Milter (mimedefang): local socket name /var/spool/MIMEDefang/mimedefang.sock unsafe sm-mta[36460]: nAKBJxPa036460: Milter (mimedefang): to error state sm-mta[36460]: nAKBJxPa036460: Milter: initialization failed, temp failing commands sm-mta[36464]: nAKBK19G036464: Milter (mimedefang): local socket name /var/spool/MIMEDefang/mimedefang.sock unsafe sm-mta[36464]: nAKBK19G036464: Milter (mimedefang): to error state sm-mta[36464]: nAKBK19G036464: Milter: initialization failed, temp failing commands etc... A stop with a short delay, then another start seems to do the trick.
What are the other related services like clamav or other anti virus running in your host? Any other memory intensive application running?
Nothing serious is running. Not even clam as a daemon.
When you compiled mimedefang, did it show any error/warning message(s)?
Not much to see, although, from the config, this could be interesting: checking if it is safe to destroy and recreate a Perl interpreter... Bus error (core dumped) no During compile time, I found this: ./embperl.c: In function 'make_embedded_interpreter': ./embperl.c:72: warning: passing argument 2 of 'Perl_sys_init3' from incompatible pointer type Jeffrey Moskot System Administrator [email protected] _______________________________________________ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list [email protected] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
