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

Linux client not able to update - Please help

Hello,

We have a single linux machine that we are running into issues with. We do the install by mounting a cifs share on the linux machine and running a script. The install seems to be successful and we can see the machine check-in initially. I assume it received its initial policies as it is configured to run its scheduled scans. The linux client seems to communicate on a regular basis with the management console based on time stamps. In the Enterprise console, "Up to Date" column shows not since [date of initial installation]. The computer details gives me the error code 0000006b "Download of savupdate failed from server sdds: SOPHOS and also code 0000006a "Installation caught error savupdate".

On the client machine, i ran /opt/sophos-av/bin/savupdate -v5 --debug and received the output below:

Update to include '*' priority 10
Update to exclude 'sav-*' priority 20
Update to exclude 'sdf.xml' priority 20
Update to include 'sav-linux/licence*' priority 30
Update to include 'sav-linux/manifest.dat' priority 30
Update to include 'sav-linux/manifest.spec' priority 30
Update to include 'sav-linux/cidsync.upd' priority 30
Update to include 'sav-linux/common/*' priority 30
Update to include 'sav-linux/x86/*' priority 30
Update to include 'uncdownload/*' priority 20
Update to exclude 'talpa/*' priority 20
Update to include 'talpa/talpa-srcpack.tar.gz' priority 30
Update to include 'talpa/manifest.dat' priority 30
Update to include 'talpa/cidsync.upd' priority 30
Update to include 'talpa/copying' priority 30
Update to include 'talpa/talpa-redhat/combined.tgz' priority 30
Update to include 'talpa/talpa-redhat/talpa-binpack-redhat-x86_64-2.6.32-431.17.1.el6.x86_64-1smpfriapr11172700edt2014.tar.gz' priority 30
Update to include 'talpa/talpa-redhat/talpa-binpack-redhat-x86_64-2.6.32-431.17.1.el6.x86_64.tar.gz' priority 30
Update to exclude 'sav-linux/x86/32/*' priority 40
Update to exclude 'uncdownload/32/*' priority 40
Updating from \\[server_name]\SophosUpdate\CIDs\S000\savlinux
Reading \\[server_name]\SophosUpdate\CIDs\S000\savlinux/savlinux/cidsync.upd
Reading \\[server_name]\SophosUpdate\CIDs\S000\savlinux/cidsync.upd
Reading \\[server_name]\SophosUpdate\CIDs\S000\savlinux/master.upd
Can't locate index of \\[server_name]\SophosUpdate\CIDs\S000\savlinux
Failed to replicate from \\[server_name]\SophosUpdate\CIDs\S000\savlinux
Exception recorded in /opt/sophos-av/tmp/savupdateException.log
DownloadConfigurationException for Invalid update source
SOPHOS source is either SOPHOS, or the warehouse update source address.
read_remote_metadata failed: result=4
error_details: Out of sources
log_entry: [E26245] Cannot locate server for http://dci.sophosupd.com/update/e/0a/e0abe8f45bbec20b556a063ff81ef388.dat
log_entry: [I20317] No proxy was used.
log_entry: [E26245] Cannot locate server for http://dci.sophosupd.net/update/e/0a/e0abe8f45bbec20b556a063ff81ef388.dat
log_entry: [I20317] No proxy was used.
log_entry: [E75373] Ran out of sophos aliases for this update source
log_entry: [E35369] Out of update sources
Failed to replicate from sdds:SOPHOS
Exception recorded in /opt/sophos-av/tmp/savupdateException.log
SDDSException for read_remote_metadata failed
Failed to replicate from all update sources

Any ideas on the issue? I have confirmed that the share is accessible by that machine. The share is the same share we use to perform the initial install.

:51334


This thread was automatically locked due to age.
Parents
  • So your Primary update is failing as it isn't able to access the server, in particular I'd expect the path:

    \\[server_name]\SophosUpdate\CIDs\S000\savlinux/cidsync.upd

    to work, so maybe you could try that with smbclient, and if that works with uncdownload (part of SAV) directly. (You'll need to switch \ for / for smbclient)

    Your secondary updating fails as it can't access the Sophos update site. This might be due to not having proxy configured correctly?

    :51350
Reply
  • So your Primary update is failing as it isn't able to access the server, in particular I'd expect the path:

    \\[server_name]\SophosUpdate\CIDs\S000\savlinux/cidsync.upd

    to work, so maybe you could try that with smbclient, and if that works with uncdownload (part of SAV) directly. (You'll need to switch \ for / for smbclient)

    Your secondary updating fails as it can't access the Sophos update site. This might be due to not having proxy configured correctly?

    :51350
Children
No Data