We'd love to hear about it! Click here to go to the product suggestion community
I noticed that the service "ssod" gets stopped after the Sophos XG 17.5 MR1 is running for a while.
I didn't notice that before updating to 17.5 MR1 and it didn't happen with 17.5 GA.
Anyone also experiencing this?
This Sophos XG is managed by Sophos Central.
In reply to Bjoern Ebner:
Are you experiencing the issue with Sophos Central? Restarting of the service is expected.
In reply to Aditya Patel:
Central Management EAP is used.
The ssod Service is not restarted but stopped permanently.
Is this a expected behaviour with Sophos Home License with Sophos Central Management?
I didn't see this before 17.5.1 and don't see it now on a customers hardware install.
The service is stopped on the machine, when you request for a connection from Sophos Central the service ssod is started and when the connection is terminated the ssod would be stopped or terminated.
Now when the connection is ended from your end, the connection will have have a wait cycle and if the channel between the user and Central is not found it will reset the connection and stop ssod service.
The service will only active during the connection event with Sophos Central.
Wouldn't it be good to exclude this stopped service from reporting as warning in the dashboard if the stop of the service is intended?
Now I see the concern, I will persue this issue as clearly it would need to be ignored.
+3 from me also, glad to get it fixed! ;)
In reply to twister5800:
We have created the KBA for this issue.
I have XG450 (SFOS 17.5.5 MR-5) in production and I have enabled their XG Firewall to be managed by SCFM, what is the solution of this.
In reply to Alejandro Pico Burgos:
What is your exact issue ?
SSOD should not be there anymore (at least i did not see this issue right now).
In reply to LuCar Toni:
The service is sttoped.
This issue is recently.
As far as i know, this is fixed with MR6.