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 fails to update on old Linux systems

Hey all,

It would seem that the new version of Sophos for Linux that was released this week is failing to install on some of our older Linux systems. Specifially, I have a few (very) old systems running Petium 3 CPUs with 512MB of RAM, and on each one of these systems the update failed, and has continued to fail, since May 8th. These systems all update from a central Enterprise Conolse server.

The error these systems get are all the same:

savd: update.failed: /opt/sophos-av/update/cache/Primary/install.sh: line 282: 25886 Illegal instruction     "$PYTHON" -c "import Installer.SavForLinux,sys;sys.exit(Installer.SavForLinux.SavForLinux.main(sys.argv))" "$DISTDIR" "$@" "$coreopt" "$talpaopt"

At that, the update fails and tries again at the next scheduled interval. These systems have been failing every couple hours now for the past couple days. The only similarity I can see between these systems is the fact that they are all running the same old CPU. Did something change with the release this week that would cause Sophos to be unable to install on these systems?

We have Enterprise Console set to keep the Linux version up to date on version 9. These systems are running CentOS 5.

Systems that have updated successfully show a product version of 4.89.0, an engine version of 3.43.0 and a virus data version of 4.89, with a release date of May 8th. Systems that have failed to update show a product version of 4.87, an engine version of 3.41, and virus data version of 4.87, with a release date of March 13. The last IDE file loaded on those systems is also May 8, which means they are not loading new definitions since the new version came out either. Needless to say, we need to figure out why so the systems can update again.

Any thoughts on what's happening here?

:39987


This thread was automatically locked due to age.
Parents
  • Yeah, I would assume it's all compiled on 64-bit systems at this point, just as I'd assume the -m32 option would need to be used in order for all the 32-bit systems to be able to run it. I'm certainly no expert on gcc, but I'm not familiar with the -march=x86-64 option. I'd always thought it needed a specific CPU type specified, such as -march=pentium3 or something. Either way, if the march architecture is set to anything newer than pentium3, then it would be trying to use SSE2 or newer, which would not be supported.

    Unfortunately, none of this was mentioned anywhere in the system requirements. We now have to rebuild multiple systems with different hardware in order to keep Sophos working. What are the chances of having the installer updated so the -march option specifies something like simply i386?

    :40083
Reply
  • Yeah, I would assume it's all compiled on 64-bit systems at this point, just as I'd assume the -m32 option would need to be used in order for all the 32-bit systems to be able to run it. I'm certainly no expert on gcc, but I'm not familiar with the -march=x86-64 option. I'd always thought it needed a specific CPU type specified, such as -march=pentium3 or something. Either way, if the march architecture is set to anything newer than pentium3, then it would be trying to use SSE2 or newer, which would not be supported.

    Unfortunately, none of this was mentioned anywhere in the system requirements. We now have to rebuild multiple systems with different hardware in order to keep Sophos working. What are the chances of having the installer updated so the -march option specifies something like simply i386?

    :40083
Children
No Data