HI Matt, We started having that problem coincidentally right after we upgraded to 3.x. For us the .tmp file creation in the spool was indicative of sniffer processing delays. We do have Sniffer modifying headers.
Darin. From: Matt Sent: Thursday, June 27, 2013 5:32 PM To: Message Sniffer Community Subject: [sniffer] Re: Slow processing times, errors Darin, I'm not seeing that sort of thing. With 3.x, there doesn't appear to be any extraneous file creation in the Sniffer program directory, and never any TMP files in my spool. I do not have Sniffer modifying headers, so that may be different on our systems. Matt On 6/27/2013 5:25 PM, Darin Cox wrote: When we had sluggish performance similar that yours, resulting in numerous sniffer .tmp files in the spool, the cause was eventually traced to a proliferation of files in the sniffer directory. Clearing them out brought performance back up to normal. Darin. From: e...@protologic.com Sent: Thursday, June 27, 2013 5:17 PM To: Message Sniffer Community Subject: [sniffer] Re: Slow processing times, errors We were experiencing this several days ago and couldn't find a fix that worked or worked for long. We uninstalled SNF and reinstalled and have not detected a problem since. I will check the logs and report back if I see anything intermittent. Sent using SmarterSync Over-The-Air sync for iPad, iPhone, BlackBerry and other SmartPhones. May use speech to text. If something seems odd please don't hesitate to ask for clarification. E.&O.E. On 2013-06-27, at 2:06 PM, Matt wrote: > Pete, > > I've had many recent incidences where, as it turns out, SNFclient.exe takes 30 to 90 seconds to respond to every message with a result code (normally less than a second), and as a result backs up processing. Restarting the Sniffer service seems to do the trick, but I only tested that for the first time today after figuring this out. > > I believe the events are triggered by updates, but I'm not sure as of yet. Updates subsequent to the slow down do not appear to fix the situation, so it seems to be resident in the service. When this happens, my SNFclient.exe.err log fill up with lines like this: > > 20130627155608, arg1=F:\\proc\work\D6063018a00002550.smd : Could Not Connect! > > At the same time, my Sniffer logs start showing frequent "ERROR_MSG_FILE" results on about 1/8th of the messages. > > I'm currently using the service version 3.0.2-E3.0.17. It's not entirely clear to me what the most current one is. > > Any suggestions as to the cause or solution? > > Thanks, > > Matt > > > ############################################################# > This message is sent to you because you are subscribed to > the mailing list . > This list is for discussing Message Sniffer, > Anti-spam, Anti-Malware, and related email topics. > For More information see http://www.armresearch.com > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > To switch to the INDEX mode, E-mail to > Send administrative queries to >
