Print Page | Close Window

Logsat in Stand-alone Mode and 100% Utilization

Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Spam Filter ISP Support
Forum Description: General support for Spam Filter ISP
URL: https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=4260
Printed Date: 18 April 2025 at 9:30pm


Topic: Logsat in Stand-alone Mode and 100% Utilization
Posted By: Guests
Subject: Logsat in Stand-alone Mode and 100% Utilization
Date Posted: 13 September 2004 at 4:01pm

This is a "Re-Post" with a different Subject line. I am hoping to catch more attention. Please forgive the re-post.

I have been seeing some strangeness where a sender causes my SPAMFORISP server to hang. It appears that when "some" emails are being sent, the server will hold a connection with the status of RCPT TO: indefinately. When this condition occurs the only way to get control of the server again is to "Kill the Process". This can not be done by selecting "Kill" from the connections window, (I assume this is within the normal operation of the program), and the application can not be shut down normally, the process has to be killed from the task manager. When the process is killed, I get a memory error and Dr Watson. The application will run normally on a restart.

I have had issues in the past with SPAMFORISP running as a service, and I am wondering if this may be related. I have been running V2.1.1.367 as a stand alone app without issue for a while, then this popped up.

The error code is DR Watson Fatal error

could not attach to the application

Windows NT error code = 87

Sometimes there is a memory error as well. When there is a RCPT TO: hang, CPU utilization climbs up to 99% and stays there until that connection is broken, then returns to a normal state until the condition is encountered again.

I have used Telnet, and attached to the server on port 25, began a transaction, and just stopped after the DATA command was issued, and my connection times out, as expected, at the same time I can watch processor use climb until the connection actually drops. I have seen connections from the Internet grab hold and not release for 45minutes to "Hours", choking the life out of my server.

This ia a Dual Processor (1.6GHZ) machine with 1 GB Ram.

 


Replies:
Posted By: LogSat
Date Posted: 14 September 2004 at 7:00am
David,

I'm sorry for missing the previous post. For some reason I was sure we had responded to that by email, but that was not the case. These hurricanes caused us to slack a bit.

There should never be the need to manually kill a connection, as 60 seconds after there is no input received, SpamFilter will automatically disconnect it. The processor and memory climbing by simply using telnet to enter commands and stopping at the DATA command is also very odd, we have never seen that. In that case too SpamFilter should terminate the connection after 60 seconds. Is it possible for us to remote in the server so we can see what is happening? You can email us at support@logsat.com if you wish with the info.

Please note that it is "normal" however to receive errors when using the "kill" or "end task" commands to terminate the main SpamFilter ISP process, as that caused Windows to abruptly terminate whatever the main SpamFilter thread may be doing at the moment, possibly causing the other threads to cause errors as the main thread is gone.

Roberto F. LogSat Software


Print Page | Close Window