From: Gary V (no email)
Date: Thu Jul 03 2008 - 23:12:41 EDT
> #> amavisd-new debug
> Jul 3 06:58:50 blix.rfi.net /usr/sbin/amavisd-new[15341]: starting. /usr/sbin/amavisd-new at blix.rfi.net amavisd-new-2.4.2 (20060627), Unicode aware
> Jul 3 06:58:50 blix.rfi.net /usr/sbin/amavisd-new[15341]: user=, EUID: 0 (0); group=, EGID: 0 0 (0 0); log_level=
> Jul 3 06:58:50 blix.rfi.net /usr/sbin/amavisd-new[15341]: Perl version 5.008008
>
> Jul 3 06:58:58 blix.rfi.net /usr/sbin/amavisd-new[15341]: SpamControl: init_pre_fork done
> Jul 3 06:58:58 blix.rfi.net /usr/sbin/amavisd-new[15341]: Net::Server: Beginning prefork (2 processes)
> Jul 3 06:58:58 blix.rfi.net /usr/sbin/amavisd-new[15341]: Net::Server: Starting "2" children
> Jul 3 06:58:58 blix.rfi.net /usr/sbin/amavisd-new[15341]: Net::Server: 2008/07/03-06:58:58 Bad fork [Cannot allocate memory]\n at line 159 in file /usr/share/perl5/Net/Server/PreForkSimple.pm
> Jul 3 06:58:58 blix.rfi.net /usr/sbin/amavisd-new[15341]: Net::Server: 2008/07/03-06:58:58 Server closing!
>
> And I'm including this here as a final footnote, so that other people may benefit from our pooled experience.
>
> The problem is not postfix, but postfix (thankfully) gave us the original error message and a place to start looking for the actual problem.
>
> The problem is not amavisd-new, but amavis identified the real problem in the end (see above).
>
> Richard Foley
> Ciao - shorter than aufwiedersehen
>
> http://www.rfi.net/
The reason for the lack of memory may be elusive, but you are not the first this has happened to:
http://marc.info/?l=amavis-user&m=118907218708830
Looks like you are using Debian (or maybe Ubuntu).
To prevent spamd from starting up, in /etc/default/spamassassin set ENABLED=0 and then stop spamd
/etc/init.d/spamassassin stop
if you have not already done so.
Try running the 'top' command and use> to sort by descending memory size. What items are at the top of the list and what size are they? This may give some clue.
If you have added custom rules or non default plugins in spamassassin, try disabling them. If you are using a rule set (spamassassin .cf file) with the text 'blacklist' in the name, I recommend removing it.
Debian etch uses ClamAV 0.90.1 which does not work well with current virus definition sets. If you are using etch and if you are running ClamAV 0.90.x, add the Debian etch volatile source in /etc/apt/sources.list and reinstall ClamAV:
http://marc.info/?l=postfix-users&m=119852130019268
You might consider rebooting and then observe if amavisd-new starts up. Continue to monitor with 'top' and possibly amavisd-nanny.
Gary V
_________________________________________________________________
Don't get caught with egg on your face. Play chicktionary!
http://club.live.com/chicktionary.aspx?icid=chick_wlhmtextlink1_feb
|
|
|