Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Netscreen 5GT antivirus errors in event log

Status
Not open for further replies.

Moffet

Technical User
Nov 5, 2002
50
GB

I'm getting the following error in the event log very frequently (every couple of minutes):

2005-07-20 15:51:26 error SCAN-MGR: Check Pattern File failed: code from VSAPI: -98.

Can anyone tell me what is wrong?

Thanks
 
VSAPI -98 has to do with not being able to allocate the memory. Make sure no debugs are running. If a debug was run recently make sure you 'clear db'. Also try reducing the size of the debug buffer with the 'set dbuf size <number>' command. Try not to do AV pattern update when unit is busy. These are good places to start.
 
Thanks for the suggestions. Memory usage looks like it is running a bit high on the home page (sometimes going into the red), but I'm not sure why. I don't have that many services running, I've switched off pretty much all the logging, and AV now only scans incoming email and I don't even have Deep Inspection turned on at the moment. The memory usage doesn't seem to come down any no matter what I do!

I'm not sure how to check the debugging is off because I'm not very familiar with the command line interface, but have cleared the buffer. I'm also not sure what the dbuf size currently is so I don't know what to change it to in order to reduce it!

After doing all this, the error message has changed to:
2005-07-21 10:14:27 error SCAN-MGR: Check Pattern File failed: code from VSAPI: -3.

The updates are automatic every 60 minutes, so it could be busy receiving or sending an email when the updates take place but there isn't much I can do about that.

Any more suggestions? Your help is appreciated!

Thanks.
 
Ok, used the "undebug all" command to make sure debugging is off. Set the dbuf size to the default of 512 and cleared the dbuf and db again.

Doesn't seem to have made much difference in the memory usage.

There is an article about this new error on the Juniper support site. It basically says there is a mismatch and just to wait a day to see if the update eventually works and to contact technical support if it doesn't update after a couple of days.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top