Print Page | Close Window

Logsat stops working

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=6158
Printed Date: 12 March 2025 at 7:47am


Topic: Logsat stops working
Posted By: bmahesh
Subject: Logsat stops working
Date Posted: 25 July 2007 at 6:41am
 Hello,
         Logsat(3.1.3 605) suddenly stops working and not able to accept mail.
We need to restart to logsat.Below logs  shows that it stop working.
also change in time interval

07/23/07 20:47:26:859 -- (30960) TBayesianThread - LoadFromFile for Corpus.db - loaded files in memory - Ind85DA.tmp
07/23/07 20:46:49:765 -- Reloading local black / white lists: SpamFilter.ini
07/23/07 20:46:49:843 -- (31136) Running TTerminateIdleThreads - SFTC=0 - SFFC=0
07/23/07 20:46:49:843 -- (22316) Blacklist cache - starting cleanup
07/23/07 20:47:49:765 -- Reloading local black / white lists: SpamFilter.ini


07/23/07 20:47:26:328 -- (31084) Blacklist cache - 151.21.245.4 removed from limbo, will add to cache
07/23/07 20:47:26:328 -- (31084) Blacklist cache - Added 151.21.245.4 to cache
07/23/07 20:47:26:453 -- Bayesian Thread is not running - starting...
07/23/07 20:47:26:500 -- (30960) BayesianThread starting
07/23/07 20:47:26:500 -- (30960) TBayesianThread - Begin LoadFromFile for corpus.db (db.dat)
07/23/07 20:47:26:562 -- (30960) TBayesianThread - LoadFromFile for Corpus.db - copied db.dat -> Ind85D9.tmp
07/23/07 20:47:26:640 -- (30960) TBayesianThread - LoadFromFile for Corpus.db - copied db.dat.prb -> Ind85DA.tmp
07/23/07 20:47:26:640 -- (30960) TBayesianThread - LoadFromFile for Corpus.db - setting Buffer size to 14350737
07/23/07 20:47:26:640 -- (30960) TBayesianThread - LoadFromFile for Corpus.db - Reading Buffer in mem
07/23/07 20:47:26:687 -- (30960) TBayesianThread - LoadFromFile for Corpus.db - loaded files in memory - Ind85D9.tmp
07/23/07 20:47:26:859 -- (30960) TBayesianThread - LoadFromFile for Corpus.db - loaded files in memory - Ind85DA.tmp
07/23/07 20:46:49:765 -- Reloading local black / white lists: SpamFilter.ini
07/23/07 20:46:49:843 -- (31136) Running TTerminateIdleThreads - SFTC=0 - SFFC=0
07/23/07 20:46:49:843 -- (22316) Blacklist cache - starting cleanup
07/23/07 20:47:49:765 -- Reloading local black / white lists: SpamFilter.ini
07/23/07 20:47:49:828 -- (31596) Running TTerminateIdleThreads - SFTC=0 - SFFC=0
07/23/07 20:47:49:843 -- (24960) Blacklist cache - starting cleanup
07/23/07 20:48:49:765 -- (31696) Running TTerminateIdleThreads - SFTC=0 - SFFC=0
07/23/07 20:48:49:765 -- (17408) Blacklist cache - starting cleanup
07/23/07 20:49:49:703 -- Starting to process queue directory...
07/23/07 20:49:49:765 -- (24588) Running TTerminateIdleThreads - SFTC=0 - SFFC=0
07/23/07 20:49:49:765 -- (27092) Blacklist cache - starting cleanup
07/23/07 20:50:49:765 -- (28840) Running TTerminateIdleThreads - SFTC=0 - SFFC=0
07/23/07 20:50:49:765 -- (17408) Blacklist cache - starting cleanup
07/23/07 20:51:49:765 -- (24780) Running TTerminateIdleThreads - SFTC=0 - SFF


Replies:
Posted By: sgeorge
Date Posted: 25 July 2007 at 12:15pm
I'm a bit confused by your log sample(s)... the chronology of events is neither ascending nor descending, but a bit mixed.  Can you try re-including a range from your log, which includes a little time before the shutdown through a little time after the restart?

Stephen

Posted By: LogSat
Date Posted: 25 July 2007 at 9:33pm
bmahesh,

From the logs you emailed us, we see the following entries when you start SpamFilter:
 
07/23/07 13:19:49:421 -- SpamFilter ISP v3.1.3.605 Listening on 202.71.nnn.nnn:25,
07/23/07 13:19:49:421 -- Exception occurred during UpdateSMTPSettings: Could not bind socket. Address and port are already in use.

The error:
"Could not bind socket. Address and port are already in use"

indicates that the SMTP port was already in use when SpamFilter was started. Can you please ensure there are no other applications using the SMTP port when SpamFilter starts? This is because Windows will not allow 2 separate applications to use the same port (port 25 in this case).

Also, can you make sure you are not starting the "standalone" version of SpamFilter if you have the SpamFilter service already running (or viceversa). If SpamFilter is already running as a service, starting the standalone version of SpamFilter will try to open a second instance of the application, which will cause conflicts. I'm including a section of our manual at the end of this email which talks about how to display SpamFilter's GUI window when using Terminal Services to access a server.
 
=================================
SpamFilter can run in two different ways.

· As a Windows service (the most common - SpamFilterSvc.exe).
· As a standalone application using SpamFilter.exe. This is mostly used for troubleshooting and testing purposes.

If SpamFilter is already running as a service, subsequently running the standalone application (SpamFilter.exe) will open a new instance of SpamFilter, it will not be the GUI for the service. This will most likely create a conflict, as two applications cannot bind to the same port on a server.

Please note that the SpamFilter service does show display a GUI (launched from an icon in the tray bar), but if you are accessing a Windows 2000 server remotely using Terminal Services will not be able to display the GUI. This is because Terminal Services in Windows 2000 is not able to display the server's physical console.

Looking at the physical server's screen, or using a product like PCAnywhere, DameWare, VNC etc that displays the actual screen will reveal the console.

Microsoft fixed this limitation in Windows 2003. In this version of the operating system, Terminal Services allows RDP clients to connect to the server's console.

Some Terminal Services clients have a checkbox in their settings that forces them to connect to the console. In the Remote Desktop client that ships with Windows XP, Microsoft (in)conveniently decided to not make this checkbox available. In this case, to view the server's physical console, you'll need to invoke Remote Desktop from the command line as follows:

mstsc -console
=================================



-------------
Roberto Franceschetti

http://www.logsat.com" rel="nofollow - LogSat Software

http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP

Posted By: bmahesh
Date Posted: 26 July 2007 at 1:28am
Please consider the following logs, there are continuous logs
 Please look into the highlighted time interval.
 
  07/23/07 20:47:26:859 -- (30960) TBayesianThread - LoadFromFile for Corpus.db - loaded files in memory - Ind85DA.tmp
07/23/07 20:46:49:765 -- Reloading local black / white lists: SpamFilter.ini
07/23/07 20:46:49:843 -- (31136) Running TTerminateIdleThreads - SFTC=0 - SFFC=0
07/23/07 20:46:49:843 -- (22316) Blacklist cache - starting cleanup
07/23/07 20:47:49:765 -- Reloading local black / white lists: SpamFilter.ini

Posted By: LogSat
Date Posted: 26 July 2007 at 8:05am
To improve performance, we recently modified the logging performed by SpamFilter so that it is now multi-threaded. This means that while before log entries were added sequentially (thus possibly causing log queues to build up), now the log entries are created by independent threads, and can occur simultaneously. For this reason, sometimes when there are concurrent entries to be added, Windows will change the priority of the threads, so that newer threads (containing newer timestamps) can sometimes receive a higher priority than older threads (containing older timestamps), so that the order in the logfile itself may not be time-sequential. This is absolutely normal, as we log the exact time of the event, which is what is to be used in troubleshooting.


-------------
Roberto Franceschetti

http://www.logsat.com" rel="nofollow - LogSat Software

http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP


Print Page | Close Window