Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 41 subscribers
  • Views 2972 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

Firewall Home - Anti Spam is Dead?

Sophos Me

Hey Guys,

I installed the Home Version of the Firewall yesterday on my ProxMox Server and it seems to run fine for now. What i noticed today, the Antispam Service is dead:

When trying to start it from the Services menu i get the message "Couldn’t start service", and from the console 503 Service Failed:


Can anyone kick me in the right direction?

Greetings

Mike



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to LuCar Toni

    Hi LuCar, i tried the same as John Groller and changed the CPU in the VM to IvyBridge (CPU: Intel(R) Core(TM) i7-8809G), a little success i think, it's not dead anymore.


    But sadly i got the same errors like before when I try to start the Service.

  • 0 in reply to Sophos Me

    Do you use Email in the product? 

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    Yes I do and for some days it also worked fine.

  • 0 in reply to Sophos Me

    Hi  Sophos Me 

    Seems the issue is related to your hardware compatibility where Sophos XG is installed or some advanced setting is not enabled on the same hardware to run v19.0.

    Please share the output you have checked for the below command here from SSH option 5>3 :     
    # grep SSSE3 /var/log/sasi.log
    # grep flags -m1 /proc/cpuinfo
    Regards

    "Sophos Partner: Networkkings Pvt Ltd".

    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to Bharat J

    Hi Bharat

    The output from this commands:

    SFVH_SO01_SFOS 19.0.1 MR-1-Build365# grep SSSE3 /var/log/sasi.log
    grep: /var/log/sasi.log: No such file or directory
    SFVH_SO01_SFOS 19.0.1 MR-1-Build365# grep flags -m1 /proc/cpuinfo
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm cpuid_fault pti fsgsbase smep erms xsaveopt arat

    After i changed the CPU I restartet die VM in ProxMox, today I restarted the hole Server and now it works:

  • 0 in reply to Sophos Me

    Great!

    "Sophos Partner: Networkkings Pvt Ltd".

    If a post solves your question please use the 'Verify Answer' button.

Unfiltered HTML