Hiya,
We’ve had Deadline 10.3 running for over a year, and the Web Service running for about 9 months. No issues.
I checked the Deadline logs folder recently and noticed a huge number of deadlinewebservice logs, 1KB every 5 minutes.
The content of each one is pretty much identical - attempts to start webservice, but socket is already in use.
2026-03-12 09:47:21: BEGIN - <domain>\<service account>
2026-03-12 09:47:21: Operating System: Windows Server 2019 Datacenter
2026-03-12 09:47:21: CPU Architecture: x64
2026-03-12 09:47:21: CPUs: 4
2026-03-12 09:47:21: Video Card: Microsoft Hyper-V Video
2026-03-12 09:47:21: Deadline Web Service 10.3 [v10.3.2.1 Release (1a66fe40f)]
2026-03-12 09:47:21: Connected to "localhost:8080"
2026-03-12 09:47:21: Turning off Kestrel logging
2026-03-12 09:47:22: Could not connect to Deadline Repository: Only one usage of each socket address (protocol/network address/port) is normally permitted.
2026-03-12 09:47:22: Web Service Shutting Down...
I’ve double checked, and the web service is running just fine. I can identify the log file belonging to the running process occupying the socket since that updates every minute.
I’m assuming this behaviour is because we have KeepWebServiceRunning=True set in deadline.ini and for some reason Deadline thinks that the webservice is down so attempts to start it back up?
Is this a known behaviour? Might it be because we’ve got authentication enabled and that’s blocking whatever check Deadline is running? Can I stop it without setting KeepWebServiceRunning=False?