* Patrick Ben Koetter <[email protected]>: > * Mark Martinec <[email protected]>: > > > Mar 8 19:37:34 de amavis[3285]: (03285-18) > > > (!!)file(1) utility (/usr/bin/file) FAILED: > > > run_command: can't fork: > > > Cannot allocate memory at /usr/sbin/amavisd-new line 3077. > > > Mar 8 19:37:34 de amavis[3287]: (03287-18) > > > (!!)file(1) utility (/usr/bin/file) FAILED: > > > run_command: can't fork: > > > Cannot allocate memory at /usr/sbin/amavisd-new line 3077. > > > Mar 8 19:37:34 de amavis[3270]: (03270-19) > > > (!!)file(1) utility (/usr/bin/file) FAILED: > > > run_command: can't fork: > > > Cannot allocate memory at /usr/sbin/amavisd-new line 3077. > > > Mar 8 19:37:35 de amavis[18622]: > > > (!)Net::Server: 2011/03/08-19:37:35 > > > Bad fork [Cannot allocate memory]\n > > > at line 166 in file /usr/share/perl5/Net/Server/PreForkSimple.pm > > > > > > after that amavis died. Is there any workaround for this > > > or should I use "runit" to restart it? > > > > You shouldn't ever allow this to happen. Disk space is cheap, > > increase the swap space! After running out of virtual memory > > all sorts of funny things can be happening on the host, > > just restarting amavisd is not a solution. > > > > Is this the reason we were unsubscribed from the list today > > (and then apparently resubscribed)? > > Yes, it was. The VM had no swap space. This has been fixed.
And it has more RAM now as well -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 [email protected] | http://www.charite.de
