snf2check.exe makes the assumption that if the entire file is there and the head and tail of it can be verified that it must have survived the transfer. Clearly something is happening where that is not the case - something new.

One possibility that has been suggested is that we could gzip these files. That would be a somewhat radical change - but so would any change to the file format so this may be the best option.

On the other hand the system has worked as is for quite some time. I would like to discover what has changed as that clearly represents a problem that must be corrected.

_M

At 06:35 PM 3/25/2004, you wrote:
If that were the case then there is something wrong with either
snf2check.exe and/or autosnf.cmd. The autosnf.cmd calls snf2check.exe to
validate the downloaded file. If snf2check.exe found the downloaded file
invalid, an error is suppose to be returned to keep it from going into
production.  So if I assume the file does get corrupted during the download,
snf2check.exe must not be returning the correct value to indicate the file
is bad, snf2check.exe hasn't changed in a long time.

So while I can't argue that the file is bad before or after download. I will
try to watch the logs more closely and manually test the snf files that
begin to generate bad_matrix errors to see if their bad at that time.

-----Original Message-----
From: Pete McNeil <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Thu, 25 Mar 2004 18:05:39 -0500
Subject: Re: [sniffer] Spam storm?

> This helps narrow things down. Specifically we know that the rulebase
> files
> are not corrupted on the server but during the download. That explains
> why
> I haven't been able to recreate a problem in the lab.
>
> I have a suspicion that wget may be failing intermittently.
> Another customer recently had unexplainable, intermittent issues with
> wget.
> They replaced wget with code of their own and have had no further
> problems.
>
> Can we narrow this down to wget under heavy traffic conditions perhaps?
>
> _M
>
>
> At 10:08 PM 3/24/2004, you wrote:
> >I've noticed that if I do a manual download of the rule base file, it
> works
> >well, but if it is downloaded automatically via the Windows Task CMD,
> then
> >sniffer fails and the log fills up with the BAD_MATRIX errors.
> >
> >Anyone else seeing this?
> >
> >
> >Mike
> >
> >
> >----- Original Message -----
> >From: "Landry William" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >Sent: Wednesday, March 24, 2004 8:43 PM
> >Subject: RE: [sniffer] Spam storm?
> >
> >
> > >
> > > I see over a 1000 of these ERROR_BAD_MATRIX entries in my Sniffer
> log file
> > > today, as well.  Is this due to the ruleset issue from earlier
> today?
> > >
> > > Bill
> > >
> > > -----Original Message-----
> > > From: Sheldon Koehler [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, March 24, 2004 3:19 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: [sniffer] Spam storm?
> > >
> > >
> > > Well it may not be a spam storm. Log file shows:
> > >
> > > nsx4b3eh 20040324200108 De90392330028271a.SMD 421 0
> ERROR_BAD_MATRIX 71 0
> >0
> > > 2 5
> > > nsx4b3eh 20040324200117 De90c923a00284b5b.SMD 422 0
> ERROR_BAD_MATRIX 71 0
> >0
> > >
> > > What is a Bad Matrix?
> > >
> > >
> > > Sheldon
> > >
> > >
> > > Sheldon Koehler, Owner/Partner        http://www.tenforward.com
> > > Ten Forward Communications           360-457-9023
> > > Nationwide access, neighborhood support!
> > >
> > > "Whenever you find yourself on the side of the majority, it's time
> > > to pause and reflect." Mark Twain
> > >
> > >
> > >
> > > 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 message and any included attachments are from Siemens Medical
> >Solutions
> > > USA, Inc. and are intended only for the addressee(s).
> > > The information contained herein may include trade secrets or
> privileged
> >or
> > > otherwise confidential information.  Unauthorized review,
> forwarding,
> >printing,
> > > copying, distributing, or using such information is strictly
> prohibited
> >and may
> > > be unlawful.  If you received this message in error, or have reason
> to
> >believe
> > > you are not authorized to receive it, please promptly delete this
> message
> >and
> > > notify the sender by e-mail with a copy to
> >[EMAIL PROTECTED]
> > >
> > > Thank you
> > >
> > > 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



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

Reply via email to