[sniffer] LogRotate no longer working?
Hi, After 10/28 the log files have not been rotation. I even logged into the server and executed the send-rotate - but the current log files just continues to grow: 10/24/2004 11:00p 1,324,321 x.log.20041025040052 10/25/2004 05:44a 1,303,683 x.log.20041025104510 10/25/2004 01:37p 1,711,062 x.log.20041025183751 10/25/2004 08:25p 1,403,988 x.log.20041026012528 10/26/2004 03:19a 1,100,582 x.log.20041026082022 10/26/2004 11:17a 2,158,910 x.log.20041026161756 10/26/2004 07:11p 1,999,926 x.log.20041027001129 10/27/2004 01:53a 1,619,614 x.log.20041027065310 10/27/2004 09:52a 1,689,744 x.log.20041027145244 10/27/2004 04:41p 1,591,043 x.log.20041027214159 10/28/2004 01:11a 1,598,140 x.log.20041028061150 10/28/2004 07:22a 1,137,471 x.log.20041028122216 10/28/2004 02:27p 1,518,661 x.log.20041028192727 10/31/2004 09:09p 16,790,875 x.log Best Regards Andy Schmidt Phone: +1 201 934-3414 x20 (Business) Fax:+1 201 934-9206 This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
RE: [sniffer] LogRotate no longer working?
For what it's worth, another two lessons I learned: If you start a persistent instance, then delete or rename your rulebase, when you issue a reload, you get this in your log: snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 I also learned that if you don't notice it for a day, you can slow your mail server down by letting sniffer append new log lines to an ever-growing 800+ MB text file! Andrew ;) -Original Message- From: Colbeck, Andrew Sent: Sunday, October 31, 2004 6:27 PM To: '[EMAIL PROTECTED]' Subject: RE: [sniffer] LogRotate no longer working? Oh, yeah. I had two problems. The other was that I was running tail on the log file, and it wouldn't rotate, ending with an errorlevel = 63. Andrew 8) -Original Message- From: Andy Schmidt [mailto:[EMAIL PROTECTED] Sent: Sunday, October 31, 2004 6:19 PM To: [EMAIL PROTECTED] Subject: [sniffer] LogRotate no longer working? Hi, After 10/28 the log files have not been rotation. I even logged into the server and executed the send-rotate - but the current log files just continues to grow: 10/24/2004 11:00p 1,324,321 x.log.20041025040052 10/25/2004 05:44a 1,303,683 x.log.20041025104510 10/25/2004 01:37p 1,711,062 x.log.20041025183751 10/25/2004 08:25p 1,403,988 x.log.20041026012528 10/26/2004 03:19a 1,100,582 x.log.20041026082022 10/26/2004 11:17a 2,158,910 x.log.20041026161756 10/26/2004 07:11p 1,999,926 x.log.20041027001129 10/27/2004 01:53a 1,619,614 x.log.20041027065310 10/27/2004 09:52a 1,689,744 x.log.20041027145244 10/27/2004 04:41p 1,591,043 x.log.20041027214159 10/28/2004 01:11a 1,598,140 x.log.20041028061150 10/28/2004 07:22a 1,137,471 x.log.20041028122216 10/28/2004 02:27p 1,518,661 x.log.20041028192727 10/31/2004 09:09p 16,790,875 x.log Best Regards Andy Schmidt Phone: +1 201 934-3414 x20 (Business) Fax:+1 201 934-9206 This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
Re: [sniffer] LogRotate no longer working?
On Sunday, October 31, 2004, 9:18:48 PM, Andy wrote: AS Hi, AS After 10/28 the log files have not been rotation. I even logged into the AS server and executed the send-rotate - but the current log files just AS continues to grow: AS 10/24/2004 11:00p 1,324,321 x.log.20041025040052 AS 10/25/2004 05:44a 1,303,683 x.log.20041025104510 AS 10/25/2004 01:37p 1,711,062 x.log.20041025183751 AS 10/25/2004 08:25p 1,403,988 x.log.20041026012528 AS 10/26/2004 03:19a 1,100,582 x.log.20041026082022 AS 10/26/2004 11:17a 2,158,910 x.log.20041026161756 AS 10/26/2004 07:11p 1,999,926 x.log.20041027001129 AS 10/27/2004 01:53a 1,619,614 x.log.20041027065310 AS 10/27/2004 09:52a 1,689,744 x.log.20041027145244 AS 10/27/2004 04:41p 1,591,043 x.log.20041027214159 AS 10/28/2004 01:11a 1,598,140 x.log.20041028061150 AS 10/28/2004 07:22a 1,137,471 x.log.20041028122216 AS 10/28/2004 02:27p 1,518,661 x.log.20041028192727 AS 10/31/2004 09:09p 16,790,875 x.log Did you make an changes on 10/29 ? In any case you might restart the persistent server to see if it clears the condition. Please keep us posted. Thanks, _M This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
Re[2]: [sniffer] LogRotate no longer working?
On Sunday, October 31, 2004, 9:45:19 PM, Andrew wrote: CA For what it's worth, another two lessons I learned: CA If you start a persistent instance, then delete or rename your rulebase, CA when you issue a reload, you get this in your log: CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA I also learned that if you don't notice it for a day, you can slow your mail CA server down by letting sniffer append new log lines to an ever-growing 800+ CA MB text file! Is this condition cleared after a proper rulebase file is in place again? Please clarify so that I can look into this. Thanks, _M This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
Re[2]: [sniffer] LogRotate no longer working?
On Sunday, October 31, 2004, 11:33:49 PM, Andy wrote: AS 1. on 10:28 5:46PM I downloaded and installed the new Sniffer version. AS 2. I just ran: AS D:\IMAIL\Sniffer\Win32mylicense.exe myauthcode rotate -- this had no effect AS D:\IMAIL\Sniffer\Win32mylicense.exe myauthcode stop AS D:\IMAIL\Sniffer\Win32mylicense.exe myauthcode persistent -- this created a new log file, but, this command NEVER returns - the AS command window is STILL running! AS Now what? The command window will continue to run since you launched a persistent instance within it. That is designed never to return. There were no changes in the latest version that should effect the log rotate command so this will take some hunting. Normally when you run a persistent instance you would run it from a utility that allows the program to run as a service. I suggest you open a new dos window and re-issue the stop command. You shouldn't need that authentication code - in testing we never use it and had no trouble. Both windows should return to the command prompt. Once you are sure your persistent instance has been stopped, you can go to your service control panel and stop, then start the persistent instance service that you set up. (If this doesn't make sense then please explain how you have your persistent instance running under normal conditions.) If the program accepts and processes the stop command then it should also answer the rotate command - they are processed by the same patch of code - only the final details are different. I've not tested log rotation when there might be interference - such as a duplicate file name or having the log file open when it must be renamed. If you find that your persistent instance is answering to the stop command but not answering to the rotate command then check for anything that might be holding on to the log file or otherwise causing a problem that might prevent it from being renamed. I have not yet been able to duplicate the conditions you are describing. Hope this helps, _M This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
RE: Re[2]: [sniffer] LogRotate no longer working?
Pete, Another test: - stopped IMAIL SMTP and QUEUE service - stopped SNIFFER service - there were no more sniffer tasks in the task manager list - I ran mylicense.exe stop (it returned) - I ran mylicense.exe rotate (it returned) - I started the SNIFFER service - I restarted the IMAIL QUEUE then the SMTP service - I checked my Sniffer win32 folder - the OLD .log file continues to grow and be updated with new dates. NO new log file was created, no old one was renamed. Where do I look for any error messages/indicators/return codes? Best Regards Andy Schmidt Phone: +1 201 934-3414 x20 (Business) Fax:+1 201 934-9206 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pete McNeil Sent: Sunday, October 31, 2004 11:48 PM To: Andy Schmidt Subject: Re[2]: [sniffer] LogRotate no longer working? On Sunday, October 31, 2004, 11:33:49 PM, Andy wrote: AS 1. on 10:28 5:46PM I downloaded and installed the new Sniffer AS version. AS 2. I just ran: AS D:\IMAIL\Sniffer\Win32mylicense.exe myauthcode rotate -- this had no effect AS D:\IMAIL\Sniffer\Win32mylicense.exe myauthcode stop AS D:\IMAIL\Sniffer\Win32mylicense.exe myauthcode persistent -- this created a new log file, but, this command NEVER returns - the AS command window is STILL running! AS Now what? The command window will continue to run since you launched a persistent instance within it. That is designed never to return. There were no changes in the latest version that should effect the log rotate command so this will take some hunting. Normally when you run a persistent instance you would run it from a utility that allows the program to run as a service. I suggest you open a new dos window and re-issue the stop command. You shouldn't need that authentication code - in testing we never use it and had no trouble. Both windows should return to the command prompt. Once you are sure your persistent instance has been stopped, you can go to your service control panel and stop, then start the persistent instance service that you set up. (If this doesn't make sense then please explain how you have your persistent instance running under normal conditions.) If the program accepts and processes the stop command then it should also answer the rotate command - they are processed by the same patch of code - only the final details are different. I've not tested log rotation when there might be interference - such as a duplicate file name or having the log file open when it must be renamed. If you find that your persistent instance is answering to the stop command but not answering to the rotate command then check for anything that might be holding on to the log file or otherwise causing a problem that might prevent it from being renamed. I have not yet been able to duplicate the conditions you are describing. Hope this helps, _M This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
Re[4]: [sniffer] LogRotate no longer working?
On Monday, November 1, 2004, 12:02:30 AM, Andy wrote: AS Pete, AS - okay, I ran the STOP command - it never ended AS - the persistent command window never ended AS - I finally stopped the SERVICE and the stop command ended AS - I finally CLOSED the command window to flush the persistent task AS Then I saw a whole bunch of sniffer tasks launch in the task window - so I AS assume it was no longer running in persistent mode. After watching this for AS 2 minutes, I restarted the server. Ok. AS Now I tried against AS mylicense.exe rotate AS from the command line. AS - It DOES return, I see no error message. AS - It creates an EMPTY mylicense.ROTATE file !? That is a signal to the Persistent instance. Under normal conditions the persistent server will see this file, delete it, and process the command it represents. When the issuing instance sees the file dissapear - or times out - then it returns. AS - It does NOT rename the active log and continues to use it. This means that the Persistent instance did not recognize or process the command. When you issued the command it returned after 30 seconds or so simply because it had finished waiting - there is a time-out. What version operating system are you using? What does your licenseid.persistent.stat file contain? If you run your sniffer exe from the command line with no parameters what is the build information? Thanks, _M This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
RE: Re[4]: [sniffer] LogRotate no longer working?
Hi, A) for what it's worth, I ran: rename mylicense.log mylicense.log.20041101051900 and the command prompt was able to rename the file WITHOUT problems (I didn't even stop the IMAIL or Sniffer services. So it appears that nothing locks the .log file. B) Under normal conditions the persistent server will see this file, delete it, and process the command it represents. Well - in my case it's 30 MINUTES later and the .rotate file still exists! What version operating system are you using? Windows 2000 Server, Service Pack 4 on a dual-processor Dell machine Hotfixchecker lists no missing security fixes What does your licenseid.persistent.stat file contain? Hm - interesting - that file does NOT exists. However, I DID see it exist while I had executed mylicenseid.exe persistent from the command line what is the build information? build - v2-3.1 Oct 26 2004 22:03:06 Best Regards Andy Schmidt Phone: +1 201 934-3414 x20 (Business) Fax:+1 201 934-9206 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pete McNeil Sent: Monday, November 01, 2004 12:14 AM To: Andy Schmidt Subject: Re[4]: [sniffer] LogRotate no longer working? On Monday, November 1, 2004, 12:02:30 AM, Andy wrote: AS Pete, AS - okay, I ran the STOP command - it never ended AS - the persistent command window never ended AS - I finally stopped the SERVICE and the stop command ended AS - I finally CLOSED the command window to flush the persistent task AS Then I saw a whole bunch of sniffer tasks launch in the task window AS - so I assume it was no longer running in persistent mode. After AS watching this for 2 minutes, I restarted the server. Ok. AS Now I tried against AS mylicense.exe rotate AS from the command line. AS - It DOES return, I see no error message. AS - It creates an EMPTY mylicense.ROTATE file !? That is a signal to the Persistent instance. Under normal conditions the persistent server will see this file, delete it, and process the command it represents. When the issuing instance sees the file dissapear - or times out - then it returns. AS - It does NOT rename the active log and continues to use it. This means that the Persistent instance did not recognize or process the command. When you issued the command it returned after 30 seconds or so simply because it had finished waiting - there is a time-out. What version operating system are you using? What does your licenseid.persistent.stat file contain? If you run your sniffer exe from the command line with no parameters what is the build information? Thanks, _M This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
RE: Re[2]: [sniffer] LogRotate no longer working?
Sure thing. I was able to repeat my mistake on a test box. If the current version (build - v2-3.1 Oct 26 2004 22:03:06) is started in persistent mode without a valid rulebase .snf file present, the log file will quickly grow containing the error message. If a .stop semaphore file is correctly dropped, it will be ignored and the log will continue to grow. Likewise, if that file is renamed or deleted after an instance is persistent, and either the 10 minute reload interval elapses or a .reload semaphore is correctly dropped, the error message is logged and will continue to grow. And I mean GROW, as in grow 10,000 lines per minute. If a new message scan order comes in while the error condition is present, it will get processed (slowly, as the server is busy creating the log) and as per the documentation, it fails open and returns a code of 0, thus not penalizing any good mail with an erroneous result. If a valid rulebase is then created in the correct folder, sniffer loads it and the error stops being logged. I think that this is a condition that users might run into with a bad download script (ahem, me) or if they are upgrading from 2.2 to 2.3 and they only extract the executable from the download archive. I think that covers it. Happy to help! Andrew 8) -Original Message- From: Pete McNeil [mailto:[EMAIL PROTECTED] Sent: Sunday, October 31, 2004 8:24 PM To: Colbeck, Andrew Subject: Re[2]: [sniffer] LogRotate no longer working? On Sunday, October 31, 2004, 9:45:19 PM, Andrew wrote: CA For what it's worth, another two lessons I learned: CA If you start a persistent instance, then delete or rename your CA rulebase, when you issue a reload, you get this in your log: CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA I also learned that if you don't notice it for a day, you can slow CA your mail server down by letting sniffer append new log lines to an CA ever-growing 800+ MB text file! Is this condition cleared after a proper rulebase file is in place again? Please clarify so that I can look into this. Thanks, _M This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
[sniffer] logrotate
Hi, In the default logrotate.cmd script is a move in stead of a ren command. Is there any special reason for that? As Ren is an internal command and move an external command I would have expected Ren to be used. p.s. Did my comment about an updated AutoSNF.cmd file make it to you Pete? I sent it to the list friday april 9th but it never made it back overhere? Groetjes, Bonno Bloksma
Re: [sniffer] logrotate
At 10:01 AM 4/14/2004, you wrote: Hi, In the default logrotate.cmd script is a move in stead of a ren command. Is there any special reason for that? As Ren is an internal command and move an external command I would have expected Ren to be used. That's a good point - I guess I used move because I was in my *nix head using mv. Ren would be a better choice I think. With version 2-3 log rotation scripts may have to be rethought since 2-3 accepts a 'rotate' command which cleanly rotates the current log file. A new log rotation script would do something like (pseudo-script): [snflicid].exe rotate copy [snflicid].log.2* /sniffer/log-archives ftp-upload [snflicid].log.2* p.s. Did my comment about an updated AutoSNF.cmd file make it to you Pete? I sent it to the list friday april 9th but it never made it back overhere? I don't seem to have it. _M
