Guest User!

You are not Sophos Staff.

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

Sophos stucks on Downloading

Hi All,

since yesterday my Sophos AV is not updating anymore. From /var/tslog/up2date_av.log the last events I see are:

2016-05-07 03:46:47 PM: savapi inc update...still looping
2016-05-07 03:46:49 PM: savapi inc update...still looping
2016-05-07 03:46:51 PM: savapi inc update...still looping
2016-05-07 03:46:53 PM: savapi inc update...still looping
2016-05-07 03:46:55 PM: savapi inc update...still looping
2016-05-07 03:46:57 PM: savapi inc update...still looping
2016-05-07 03:46:59 PM: savapi inc update...still looping
2016-05-07 03:47:02 PM: savapi inc update...still looping
2016-05-07 03:47:04 PM: savapi inc update...still looping
2016-05-07 03:47:06 PM: New savapi inc udate successfully done

Clicking on "update pattern now" does not change the up2date_av.log file at all.

Anyone is experiencing this issue?

Thanks.



This thread was automatically locked due to age.
  • Sachin, I wil check. I am out of the office and I will be back on thursday.

    Thanks.

  • I have the same issue (stuck on downloading Sophos AV since May 6th) I tried to fix it by rebooting the firewall, but then the download status changed to 'Failed'.

    As suggested:

    I've changed the web content filter from 'dual antivirus' to 'single antivirus' and I've changed the malware protection to 'Avira'

    After this, I've manually updated the patterns.

    The status of Sophos AV remains 'Failed'. So this workaround didn't do the trick. Any options to flush the update manually?

    When is the patch to be released?

  • I have found a post on here https://community.sophos.com/products/xg-firewall/f/46/t/73626#pi394=3

    posted by dempie, this has fixed my issues, it may sort yours out too.

    this uses the console.

    "In Main Menu choose:
    5. Device Management
    Then
    3. Advanced Shell.
    On command prompt type this command:
    mv /content/u2d/pattern /content/u2d/pattern.org
    This will rename the pattern file to pattern.org.
    Now update the pattern files with the GUI using System > Administration > Updates.
    Give the firewall some time to succeed the update process.

    Hope this helps.

    Best Regards."

  • Thank you Tony. Before creating the thread, I already tried the solution and moved even other folder. The fix did not help.

    Thanks.

  • Thank you Tony, tried this, and after a while the Sophos AV definition was updated correctly to .9126.

    The Avira definition (.14391) however is two days old, is this correct? Update status is: "success"

  • Hi Luk,

    Please post u2d.log and fresh up2date_av.log.

    Thanks

  • Hi,

    this loop is so annoying :O)

    /log/u2d.log

    ARNING May 12 10:52:10 [8036]: A new update is available for savi but we are ignoring it as download for a previous update is in progress.
    Thu May 12 10:52:30 2016 Download completed for file savi_1.00_1.0.9116_fdiff20.tar.gz.gpg
    Thu May 12 10:52:30 2016 Validate file savi_1.00_1.0.9116_fdiff20.tar.gz.gpg failed, md5sum = b2d8c477b7672a5f0f2acd81af1a0815, expecting md5sum = 9bcd1647d5a6e7a5cf759508c6c50cee
    Thu May 12 10:52:30 2016 Deleting file /sdisk/u2d/downloads/savi_1.00_1.0.9116_fdiff20.tar.gz.gpg
    Thu May 12 10:52:30 2016 Download for file savi_1.00_1.0.9116_fdiff20.tar.gz.gpg was interrupted/did not complete.
    Thu May 12 10:52:30 2016 Retrying/Resuming download for file savi_1.00_1.0.9116_fdiff20.tar.gz.gpg. Try = 1.
    Thu May 12 10:53:30 2016 Download completed for file savi_1.00_1.0.9116_fdiff20.tar.gz.gpg
    Thu May 12 10:53:30 2016 Validate file savi_1.00_1.0.9116_fdiff20.tar.gz.gpg failed, md5sum = b2d8c477b7672a5f0f2acd81af1a0815, expecting md5sum = 9bcd1647d5a6e7a5cf759508c6c50cee
    Thu May 12 10:53:30 2016 Deleting file /sdisk/u2d/downloads/savi_1.00_1.0.9116_fdiff20.tar.gz.gpg
    Thu May 12 10:53:30 2016 Download for file savi_1.00_1.0.9116_fdiff20.tar.gz.gpg was interrupted/did not complete.
    Thu May 12 10:53:30 2016 Retrying/Resuming download for file savi_1.00_1.0.9116_fdiff20.tar.gz.gpg. Try = 1.
    Thu May 12 10:54:29 2016 Download completed for file savi_1.00_1.0.9116_fdiff20.tar.gz.gpg
    Thu May 12 10:54:29 2016 Validate file savi_1.00_1.0.9116_fdiff20.tar.gz.gpg failed, md5sum = b2d8c477b7672a5f0f2acd81af1a0815, expecting md5sum = 9bcd1647d5a6e7a5cf759508c6c50cee
    Thu May 12 10:54:29 2016 Deleting file /sdisk/u2d/downloads/savi_1.00_1.0.9116_fdiff20.tar.gz.gpg
    Thu May 12 10:54:29 2016 Download for file savi_1.00_1.0.9116_fdiff20.tar.gz.gpg was interrupted/did not complete.
    Thu May 12 10:54:29 2016 Retrying/Resuming download for file savi_1.00_1.0.9116_fdiff20.tar.gz.gpg. Try = 1.

    <Up2Date>

    <Package u2dtype="pattern">
    <File name="savi_1.00_1.0.9135_full.tar.gz.gpg">
    <location>d30ncyzaneb4q0.cloudfront.net/.../location>
    <version>1.0.9135</version>
    <size>143312047</size>
    <md5sum>54aeb288018db51804c72e918261ab98</md5sum>
    <module>savi</module>
    <cv>1.00</cv>
    <type>full</type>
    </File>
    </Package>
    </Up2Date>

    is this downloading the wrong file and that is why getting the wrong checksum ? or it is the the expected checksum wrong ? cant we just donwload the correct file and push it to update with it ?

    .....https://d30ncyzaneb4q0.cloudfront.net/savi_1.00_1.0.9135_full.tar.gz.gpg ?

    54aeb288018db51804c72e918261ab98 savi_1.00_1.0.9135_full.tar.gz.gpg

    b2d8c477b7672a5f0f2acd81af1a0815 savi_1.00_1.0.9116_fdiff20.tar.gz.gpg

    expecting md5sum = 9bcd1647d5a6e7a5cf759508c6c50cee

    EDIT: sry i didnt see there was page 1 for this...

    resetting the patter solved this, now it is downloading  54aeb288018db51804c72e918261ab98 savi_1.00_1.0.9135_full.tar.gz.gpg and now in cat  /content/u2d/pattern

    seems  to be expecting the correct md5

  • I still have the same issue today even renaming patterns.

    It is very sad that there is no way to fix it.

  • Hi Luk,

    I investigated this, the issue is related with incorrect md5 checksum value passed , we are working to rectify this. This will be resolved with the next release. 

    Thanks