Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 57 replies
  • Answers 2 answers
  • Subscribers 39 subscribers
  • Views 205774 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Avira up2date error: Is there any solution?

dempie

Hi,

since yesterday my XG-Firewall cannot download the pattern files for the AVIRA virus scanner any more. This is what I read from 'Log Viewer' under 'View Log for Admin':

2015-12-29 11:17:30 Up2Date FAILED - Failed to download file avira_1.00_1.0.12965_full.tar.gz.gpg 18030
2015-12-29 11:16:31 Up2Date FAILED - Failed to download file savi_1.00_1.0.8492_full.tar.gz.gpg 18030

This process repeats every 30 seconds and is wasting all of my Internet bandwidth, as the download starts, but cannot be finished successfully.

I disbled 'Auto Update' from System>Administration>Updates'. Nevertheless, the XG Firewall doesn't stop downloading these files.

Is there any solution?

Thanks for your help.

Best Regards



This thread was automatically locked due to age.
  • 0 in reply to BrunoZavettieri

    BrunoZavettieri said:

    Now i have update pattern file and revert file hosts. Pattern file now is empty but in updates status antivirus is now ok.

    /content/u2/pattern is something like a queue file. Entries in there have to be handled by the up2date process. After all is done the file is empty. So it is ok.

    BrunoZavettieri said:

    There is another strange thing. Log file:

    Thu Jan 07 10:41:54 2016 Download completed for file savi_1.00_1.0.8528_full.tar.gz.gpg

    but in downloads:

    /var/u2d/downloads/savi_1.00_1.0.8492_full.tar.gz.gpg



    So what I saw from the up2date process it is like this:

    /var/u2d/downloads is the directory where the curl process stores its pattern file downloads. When the up2date process has updated the virus engine files - I believe this is in /var/savapi for Avira AV and in /var/sav for Sophos AV - it normally cleans the files from directory /var/u2d/downloads.

    In your case the old pattern files were downloaded, but they could not be handled because of wrong file sizes and md5 hashes. By renaming the pattern file in /content/ud2d you cleaned the queue file and the firewall was able to process new pattern file informations it got from Sophos up2date servers. So that is how the latest pattern files got in your firewall.

    As you missed the older version 1.0.8492 of Sophos pattern files the file still is there.

    The directory /var/u2d/downloads on my firewall is empty at the moment. The up2date scripts finished even the old pattern files as I corrected the file sizes and checksums in the pattern file at that time.

    Hope I could answer all of your questions.

    Best Regards.

  • 0 in reply to dempie
    Renaming the pattern file worked for me to fix the savi update. Support didnt help with this.
  • 0 in reply to dempie

    Hi Dempie,

    I have renamed the pattern file as suggested and now the updates are downloading. But after a successful download, the installation fails because of the following error:

    "Either FILE or MSID received in U2DVERSION is blank".

    When I check the U2DVERSION file, there is no value for MSID (MSID =       ). What should the value be?

    Kind Regards,

    Werner

  • 0 in reply to WernerSteenkamp

    Same here.... MSID with new value..... any help??

  • 0 in reply to dempie

    Re-installing Sophos XG Virtual Appliance solved my issue. Made sure all updates was completed before installing latest firmware.

    Regards,

    Willem

  • 0 in reply to WernerSteenkamp

    I was able to get this working by booting the previous firmware, turn on both AV in the Web Content Filter setup, then validated that both AV had the latest definitions in the update screen.  Once I saw both AV had definitions with todays date, I then booted the latest firmware.   Problem solved.

    Note:  Take a backup of your config before reverting firmware (you dont want to take chances)

    Note2:  When I reverted to the OLD firmware, I had to use the 172.16.16.16 address, once i booted to the new firmware my config was back to normal.

    Crazy bug!

  • 0

    I have the same issue.

    After got the new V17 appliance, and install the V16.05.8 MR-8 firmware, the issue happened...

    I have tried to modify the "/content/u2d/pattern" & "/var/savapi" and update XG pattern.

    But both of them didn't work.

    The firewall is online and  for service already, so I can restore to the V17 firmware...

     

    I open a case, and support team help me to resolve the issue.

    But support team can not share steps to resolve this issue,

    reason is there is a patch available for this issue and only development team have all details about it.

    It so sad...

     

    Shunze