Dear Tony I am running Linux 2.4.29 and built dspam-3.8.0 from source. I used dspam-3.6.8 before and have had dspam running for about 9 months. This problem occurred with dspam-3.6.8 and is VERY intermittent usually occuring at boot up but not every time and the server is rebooted rarely usually after a power outage.
The other type of message logged is Jun 24 14:23:21 brooks sendmail-fast[31116]: l5O4rDj0031110: to=<[EMAIL PROTECTED]>, delay=00:00:06, xdelay=00:00:00, mailer=dspam, pri=122299, relay=localhost, dsn=4.3.5, stat=Deferred: No such file or directory I did another test last in killing the current dspam process and noticed the initial process starts and forks another dspam process that is used to fork other dspam processes to handle subsequent emails (see below). I now wonder if this is normal. Tonight I will do another test without using the supervise process to manage dspam. I now wonder if it is my startup script that I got from the Sendmail+DSPAM+Cyrus HOWTO. It is /usr/local/bin/dspam --daemon 2>&1 | /usr/bin/logger -t dspam -p daemon.notice Thanks Stephen Carr Processing two emails |-supervise,30831 /service | `-run,27445 ./run | |-dspam,27446 --daemon | | `-dspam,27586 --daemon | | |-dspam,24886 --daemon | | `-dspam,24889 --daemon | `-logger,27447 -t dspam -p daemon.notice Waiting to process email |-supervise,30831 /service | `-run,27445 ./run | |-dspam,27446 --daemon | | `-dspam,27586 --daemon | `-logger,27447 -t dspam -p daemon.notice Tony Earnshaw wrote: > Stephen Carr skrev, on 25-06-2007 01:23: > >> I have reported this very intermittent problem before where sendmail >> reports errors of the type >> >> Jun 24 13:10:57 brooks sendmail[28340]: l5O3TvJl027795: to=<[EMAIL >> PROTECTED]>, >> delay=00:10:55, xdelay=00:00:00, mailer=dspam, pri=211603, >> relay=localhost, dsn=4.0.0, stat=Deferred: Connection reset by localhost >> >> The emails build in the queue awaiting delivery. >> >> I suspected it was the problem was in DSPAM connecting to the MySQL >> database. >> >> My fix was to disable DSPAM processing and enable it 4 or 6 hours later. >> >> Since this happened on the weekend I had a closer look and what I >> noticed >> was that there was only one dspam process running. Normally there are >> two >> or more dspam processes running with the minimum being two. Since I use >> freedt to monitor the dspam daemon I killed the dspam process - after >> repeating this several times it started to work. >> >> Below is a clip from pstree showing dspam processes 6127, 6158 and 32765 >> - >> this snapshot was taken as emails were being processed. In the error >> state >> there is only the primary process running eg 6127. When not >> delivering/processing emails only 6127 and 6158 are running. >> >> Any idea as to the fix to make the second process activate/spawn and >> accept connections. >> >> Using dspam-3.8.0, sendmail-8.14.1 and Cyrus-imap-2.3.8 > >> |-supervise,30831 /service >> | `-run,6126 ./run >> | |-dspam,6127 --daemon >> | | `-dspam,6158 --daemon >> | | `-dspam,32765 --daemon >> | `-logger,6128 -t dspam -p daemon.notice > > Strange, someone correct me if I'm wrong, but I don't believe dspam is > designed to fork. I haven't look at the code, but on mu RHAS4/FC6 rigs > it has never forked, always been a single process. > > Your using freedt would point to you using (Open)BSD, are you installing > from ports, or do you build your own dspam? > > --Tonni > > -- > Tony Earnshaw > Email: tonni at hetnet dot nl > > -- Stephen Carr Computing Officer School of Civil and Environmental Engineering The University of Adelaide Tel +618-8303-4313 Fax +618-8303-4359 Email [EMAIL PROTECTED] CRICOS Provider Number 00123M ----------------------------------------------------------- This email message is intended only for the addressee(s)and contains information that may be confidential and/or copyright. If you are not the intended recipient please notify the sender by reply email and immediately delete this email. Use, disclosure or reproduction of this email by anyone other than the intended recipient(s) is strictly prohibited. No representation is made that this email or any attachments are free of viruses. Virus scanning is recommended and is the responsibility of the recipient.
