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
