SCCM Patching - OD services do not start

Legacy Execution
1

Hello team,
I have an issue with OD every time we patch with SCCM. Services will not come back online (OD Server services are always down coming out of the patching reboot). Tentacles are looking much better, but still about 20-30% services will be down following the patching day.

I’ve seen on this forum that this is common theme with OD and I’ve read some posts where people implement watchdog services or create scheduled tasks with custom scripts to check the service health.
My challenge is that I’m in highly secure environment with up to 20k servers - scheduled tasks would be administrative nightmare.

I’ve tried delayed starts, different restart actions etc but nothing helps.

Is there anything I can do to help the OD team troubleshoot further? It’s mind bogging that this is happening. I’m running v 3.13.7.

Windows System log records:
The OctopusDeploy service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

2

Hi Lukas, thanks for reaching out.

The issue with services not starting after a Windows Update has affected a number of customers, and the recommended workaround is documented at https://octopus.com/docs/administration/service-watchdog. However this solution does use scheduled tasks.

At this point the exact cause is not yet known, and the issue is being tracked at https://github.com/OctopusDeploy/Issues/issues/2375. Any additional information you could provide on that ticket would be welcome.

Regards
Matt C

3

Thank you.