AntiSpam Service died-v19

Question

Hi 
 After Upgrade Sophos SW-19MR-1, the AntiSpam Service died and I Can't Start Service. 
 ApplianceCertificate was also regenerated, but it didn't work. 
 Please, guide me 
 Tanks

JanosRapcsak · Accepted Answer

After identifying the root cause of this issue we're working on a fix for it. 
 Here are the steps to start the antispam service when there are "... database length < sizeof( ..." entries in the SASI log:

stop the SASI sevice:

service antispam:stop -ds nosync

delete the anti-spam DB files:

rm /sdisk/sasi/*

start SASI from the CLI:

/bin/sasi -c /cfs/sasi/sasidaemon.conf 
 
 wait until you see this in the console output: 
 
 "... Signatures don't exist, fetching new signatures.." 
 "... Lased started on port : 25315"

stop the SASI process by pressing CTRL+C 
 start the SASI service: 
 
 service antispam:start -ds nosync 
 
 check the SASI log to see if SASI started, again look for this entry: "... Lased started on port : 25315": 
 
 tail /log/sasi.log 
 
 you shouldn't see "... database length < sizeof( ..."log entries anymore.

John Groller · Answer

I change the CPU type in the VM to IvyBridge, and things seem to be working so far. "Host" also works. Thanks for the tip and for looking into it. kvm64 may not provide these flags. 
 https://qemu-project.gitlab.io/qemu/system/qemu-cpu-models.html 
 https://forum.proxmox.com/threads/enable-kvm-cpu-ssse3-support.106032/

LuCar Toni · Answer

So DEV took a look into your installation. It seems like you are affected by this: https://support.sophos.com/support/s/article/KB-000042345?language=en_US 
 Essentially your hardware is "to old to support the standards we are using". Is this true based on your used hardware?

rfcat_vk · Answer

Hi, 
 try forcing a firmware update, then try restarting the service and if all else fails try restarting the device. If that is not successful, please create a support case. 
 ian

LuCar Toni · Answer

Do you use Email in the first place? Because AntiSpam is not running, if you dont use Email.

Paul van Driel · Answer

I ended up by adding a line to the config file of the Proxmox VM in /etc/pve/qemu-server/. Just add next line and reboot Sophos XG 
 args: -cpu qemu64,+ssse3

Service name	Status
Antispam	DEAD

Service name	Status
Antispam	DEAD

Services	Status
Anti-spam	Running

AntiSpam Service died-v19

Top Replies