Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 2 subscribers
  • Views 4535 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

Linux

DavidL

We installed 9.12.2 successfully on 20+ machines running

Red Hat 6.8 and 5.11 and CentOS 6.8

But, two machines, one running CentOS 6.2 and one running 5.11 won't update.

They show as connected but.... 

Download of savupdate failed. [0x0000006B]

CRITICAL savupdate.util.Logger: CANT_FIND_INDEX



This thread was automatically locked due to age.
Parents
  • +1

    Hello DavidL,

    is the CRITICAL line from the savupdate-debug.log in /opt/sophos-av/log/? Your update location is a UNC path and you don't have a secondary defined? As far as I can see you get this rather terse information when e.g. the server name can't be resolved (RMS communication - they show as connected - could nevertheless work as mrinit.conf usually also contains the server's IP address).

    Christian

Reply
  • +1

    Hello DavidL,

    is the CRITICAL line from the savupdate-debug.log in /opt/sophos-av/log/? Your update location is a UNC path and you don't have a secondary defined? As far as I can see you get this rather terse information when e.g. the server name can't be resolved (RMS communication - they show as connected - could nevertheless work as mrinit.conf usually also contains the server's IP address).

    Christian

Children
Unfiltered HTML