Service SSOD stopped in Sophos XG17.5.1

I'm facing the same problem on 17.5.0 GA in HA active-passive mode

Sophos XG 17.5 MR-3 which should fix this is scheduled for 10th Febuary 2019.

On Topic:

ssod Service is stopped about 10 minutes after it's started. It reports:

Feb 04 16:24:26.647 err [0000004146730752] Wait for channel failed. Channel not found
Feb 04 16:24:26.647 err [0000004146730752] Failed to accept connection from listener: Connection reset by peer
Feb 04 16:24:33.293 *****************************
Feb 04 16:24:33.293 ssod stopped
Feb 04 16:24:33.293 *****************************

I also have the problem with the firmware 17.5.3 on my XG105 and the software version.

Now I test the stability without syncing with the Central platform.

+1

ssod still stopping on 17.5 MR3. ssod.log records the following:

Feb 19 13:48:57.742 *****************************                               
Feb 19 13:48:57.742 Starting ssod                                               
Feb 19 13:48:57.742 *****************************                               
Feb 19 13:59:01.897 err [0000004147025664] Wait for channel failed. Channel not found                                                                           
Feb 19 13:59:01.897 err [0000004147025664] Failed to accept connection from listener: Connection reset by peer                                                  
Feb 19 14:09:15.901 err [0000004147025664] Wait for channel failed. Channel not found                                                                           
Feb 19 14:09:15.901 err [0000004147025664] Failed to accept connection from listener: Connection reset by peer                                                  
Feb 19 14:09:28.388 *****************************                               
Feb 19 14:09:28.388 ssod stopped                                                
Feb 19 14:09:28.388 *****************************                               

I've also noticed this on 17.5 MR3 and the service seems to always stop when I sign out from Sophos Central firewall management.

Hello , 

We have checked and found that the service is meant to stop after a failed connection with Sophos Central console. If the connection did not establish then the service would  restart and would attempt to connect again. 

Strange thing is, that it's connected to Sophos Central but the service is stopped.

Strange thing is, that it's connected to Sophos Central but the service is stopped.

Hello Bjoern,

Are you experiencing the issue with Sophos Central? Restarting of the service is expected.

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.

Hello Bjoern,

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?

Hello Bjoern,

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! ;)

Hello Everyone,

We have created the KBA for this issue.

https://community.sophos.com/kb/en-us/133780 

Good Moring,

Dear Aditya,

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. 

What is your exact issue ?

SSOD should not be there anymore (at least i did not see this issue right now). 

Good Afternoon,

The service is sttoped.

This issue is recently.