Skip navigation
McAfee Secure sites help keep you safe from identity theft, credit card fraud, spyware, spam, viruses and online scams
1008 Views 1 Reply Latest reply: Mar 21, 2012 2:15 AM by daloy RSS
brentil Apprentice 380 posts since
Oct 31, 2007
Currently Being Moderated

Mar 1, 2012 12:58 PM

NSM constantly erroring on sig download

With the release of the new sig set this morning our NSM has been erroring every minute until we turned off the automated sig download process.  So we're having 2 issues here.


One the setting is set to try every hour but in reality the system is retrying every minute and it sends a error & then error cleared email every minute because of this.


Secondly the manager seems to be failing to get to the resources to download the content.  The following error is what shows in the logs.



Scheduled signature set download failed
Condition Type:ScheduledUpdateFailure
Alarm Type:Management
Last Occurrence Time:2012-Mar-01 09:33:56 EST
Additional Text:The Manager is unable to perform the scheduled signature set download from the Update Server. Error Message: Access status for the url '' is, the http response code is, 404, the response status is ,Not Found.


Trying to go to the URL listed puts up a username/password prompt to gain access.  The website is the one listed in the SNS alerts as well as a location to go acquire the download so I would assume it's supposed to still be active.  I then went to the McAfee download grant portal to get the sig set manually but the file is not there either.  So it seems the SNS alert went out and the NSM list was updated to say these files exist but in reality they don't.

Leith Tussing - University of Central Florida

  • daloy McAfee Employee 56 posts since
    Sep 17, 2010
    Currently Being Moderated
    1. Mar 21, 2012 2:15 AM (in response to brentil)
    Re: NSM constantly erroring on sig download

    This should be now resolved as we had a problem with that specific sigset.


    Regarding your other question, the NSM scheduler will run evry hour after the last pull (or check) is completed. In this case the response code it was receiving was a 404, therefore it kept re-trying.




More Like This

  • Retrieving data ...

Bookmarked By (0)


  • Correct Answers - 5 points
  • Helpful Answers - 3 points