Benedict White wrote: > Hello! > > I have had a bit of trouble with the following message: > > (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=07140-17, > parts_decode_ext FAILED: > file(1) utility (/usr/bin/file) error: run_command (open pipe): Can't fork at > /usr/lib/perl5/core_perl/IO/File.pm line 188, <GEN182> line 59. at > /usr/sbin/amavisd line 2873, > <GEN182> line 59. (in reply to end of DATA command)) > > Which seems to come about as memory runs out. I am not sure if this is a leak. > > I am using Amavisd-new 2.6.1, Spamassassin and clamav with postfix. > > The machine it runs in has 512MB of RAM and I did have it running 10 servers > max.
At min of 50-60MB/server, you'd have amavis consume all of your RAM! > > I have now dropped that to 5 and am monitoring. That is still 250-300MB. Perhaps 2 is about your max. Get more RAM if you have this much traffic that you need more a few clients. > > Is there a rough and ready recomendation for how much memory each child needs? Certain SpamAssassin add-on rule sets, they can increase memory requirements significantly. Choose wisely. Disable them, look at the RSS (resident set size) of an amavis process without the rules, and the enable, restart amavis and check again. This will give you a good approximation of how much RAM they consume. > > What tools do people use for hunting memory leaks? First get your house in order! > > Kind regards > > Benedict White Mike ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
