On Sun, Jun 22, 2003 at 09:59:13AM +0100, Pete Henshall wrote: > Hi qmail-scanner-list, > > > Here's a bug report/problem...If you ever Email the mailing-list with an > error report, PLEASE ensure you tell us what OS you are running, the Q-S > version > > number and include the part of qmail-queue.log that shows where the error > occurs. Without that information, no-one can help.
Pete - you still haven't said what OS/version you are running! Anway, first thing first. You have all sorts of add-ons to Qmail there that are confusing the hell out of me. Make a new SMTP service on - say - port 26 - and just have qmail-smtpd running on there with Q-S and none of that autoturn stuff. Also ensure your logging is actually working - i.e. connecting to port 26 causes a log entry by tcpserver, sending a message on port 26 causes a log entry, etc. Then enable Q-S and do the same thing - and check that qmail-queue.log contains data. Then you can fiddle to your hearts content without affecting the "live" port 25 SMTP server. > > > Here is the qmail-queue.log and my process watch for the orphaned processes > as it is doing it. I can't see anything. :\ Neither can I. I see a success and a drop due to there being no sender and recip. Both are normal - both don't cause hangs... Is what you are saying that after a restart (of the server, or just qmail-smtpd?), it all works fine for a time - but then turns to custard? Can it be that it's overloaded? What kind of messages/sec are we talking about here? Right back in the beginning you said you had a disk problem - how do we know this isn't still the case? A bad disk could certainly cause hangs as I/O operations block. The fact that it works for a while and then starts hanging implies it's not a Q-S problem. As Q-S is forked per SMTP connection, there's no long-term process/threads lying around that could be buggy enough to hang on you. Also, you need to spend more time diagnosing those logs. I don't think the ones you including here have anything to do with the problem. I'm afraid you will have to look through the logs, and tie together all the records that are part of the same transaction. The related qmail-queue.log records share the same timestamp - so what you're looking for is a new transaction beginning and never ending - those will be the hung ones. Then you need to see if they hang at the same point - if so, you'll now know where the problem is occurring. I don't think it's a bug. -- 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: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
