Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 26 replies
  • Subscribers 34 subscribers
  • Views 21648 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

Service SSOD stopped in Sophos XG17.5.1

Björn Ebner

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.



This thread was automatically locked due to age.
  • 0 in reply to Björn Ebner

    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.

     

     

     

  • 0 in reply to Luca Armellini

    +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 *****************************                               
  • 0 in reply to ChrisKnight

    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.

  • 0 in reply to AndersK

    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. 

  • 0 in reply to Aditya Patel

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

  • 0 in reply to Björn Ebner

    Hello Bjoern,

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

  • 0 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.

  • 0 in reply to Björn Ebner

    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.

  • 0 in reply to Aditya Patel

    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?

  • 0 in reply to Björn Ebner

    Hello Bjoern,

    Now I see the concern, I will persue this issue as clearly it would need to be ignored.