AntiSpam Service died-v19

Can we get the access-ID of your installation in V19.0 MR1 with the Dead service? Naderi // John Groller ? 

Can we get the access-ID of your installation in V19.0 MR1 with the Dead service? Naderi // John Groller ? 

By following this?  https://docs.sophos.com/nsg/sophos-firewall/18.5/Help/en-us/webhelp/onlinehelp/AdministratorHelp/Diagnostics/ConnectionList/SupportAccess/index.html

Let me look into that and think on it.  I'm a little leery of "Sophos Support uses this access ID to sign in to your Sophos Firewall device."

Are there logs or something I can provide instead?

DEV wants to look into your system and debug it to check the reason. Therefore a Access would be the best approach as they do not know, what is the current root cause. 

The access is granted via EULA and Legal: https://www.sophos.com/en-us/trust

I PM'd you the ID.  It's good for 48 hours.  Is there a way I'll know when you're done so I can turn this back off?

Thanks!

So only Sophos has access to this device now and Sophos is not changing any configuration etc. We will report back, if there is any kind of Feedback. 

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? 

Seems unlikely. 

24 x Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz

I'm using the kvm64 processort on the virtual machine.  Perhaps I'll try a different virtual CPU.

Also the previous version of XG worked fine.  Prior to that, I used UTM on this hardware for about 4 years.

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/

Hi John, I had a similar experience and resolved by adding a line to the config of the VM and no need to change cpu type. See below.