After an upgrade this morning, the Channels DVR server failed to start so Channels DVR could not be accessed at all. I was in office all day so I couldn't do anything about it. The good news is that it was still doing its thing (recording as scheduled), it's just that we couldn't connect to it (no web access even on the computer itself at 127.0.0.1:8089, and no client access).
2024/10/02 06:02:31.426643 [SYS] Created database snapshot: backup-20241002.100231
2024/10/02 06:02:31.426643 [SYS] Removing old backup backup-20240911.135656
2024/10/02 06:02:31.493049 [SYS] Shutting down for upgrade from v2024.09.26.2019 to v2024.10.01.1128
2024/10/02 06:02:32.032635 [SYS] Bonjour service stopped.
2024/10/02 06:02:32.132278 [DVR] Recording engine stopped.
2024/10/02 06:02:33.638434 [SYS] Goodbye.
2024/10/02 06:02:33.655916 [SYS] Starting Channels DVR v2024.10.01.1128 (windows-x86_64 pid:22672) in C:\ProgramData\ChannelsDVR\data
2024/10/02 06:02:33.787498 [ERR] Could not start server: listen tcp :8089: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.
Logs have been submitted as 4a9100de-ddc8-4513-93f6-3b757142934a .
As soon as I got back from the office, I fixed it by restarting the whole computer. Killing Channels DVR alone and trying to restart it didn't work.
This already happened not too long ago and I didn't think much of it at the time. I figured it was just a random hiccup with Windows.
But now that's twice so maybe there's something going on?