On Mon, Jun 09, 2003 at 11:02:45PM +0100, Pete Henshall wrote: > Hi qmail-scanner-general,
Hi Pete - first off - thanks for the FULL details you provided - really helps :-) > spamd is running from service as > #!/bin/sh > exec spamd -m 15 -L Bang softlimits in front of that for a start - if spamd swallowed all your memory - that'd explain your symptoms. Mine looks like: exec /usr/local/bin/softlimit -a 30000000 /usr/bin/spamd ..... > QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue.pl" export QMAILQUEUE > exec /usr/local/bin/softlimit -m 12000000 \ > /usr/local/bin/tcpserver -v -c 50 -o -x /etc/tcp.smtp.cdb -H -R -u 1001 -g OK - 12Meg limit of qmail-smtpd - which means a 12Meg limit on how much memory Qmail-Scanner can use too. "-c 50" means that you can have up to 50 incoming SMTP sessions at a time - looks fine for a 2Gig system. I must say - I always use "softlimit -a" instead of "-m" - don't really know if it helps :-) > sophie is running from service from /var/qmail/scripts/start-qmail-sophie > #!/bin/sh > exec softlimit -m 13000000 /usr/local/sbin/sophie OK - sophie runs within a 13Meg RAM limit. I have to run mine at 20Meg BTW - but if you have it running successfully under that - fine. > The problem is that the server spirals out of control and dies after a few > days or so (dies = won't let me ssh in), I am not local so do not know if I > can login locally. Once rebooted all works fine for 2 or 3 dsays then dies. > All the services answer when it is "dying" but dont actually work. It seems > to die when the RAM file cache memory "fills up" and tries to swap out to > disk, but I can't see anything for defs. I have setup remote syslogging to > see if that helps more next time it happens, but if I can stop there being > an next time then all the better!! Irrespective of your access, the reason for the failure should still have been recorded in the syslogs - what do you find? I have a particular IDS box that is failing (nothing to do with Q-S) - "out of file descriptors". I am trying to hunt down the process swallowing all the FDs - but syslog still reported this error before failing. You should have something logged... Check your syslog and qmail-queue.log files after a crash (do you have the logs from the last crash? Check those). If those logfiles appears to be working, and yet tell you nothing - then I'd guess you're looking at a HARDWARE problem. You comments on disk issues may reflect that... -- Cheers Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +64 3 9635 377 Fax: +64 3 9635 417 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
