This is similar to another closed thread here:
Im also seeing this in the logs:
2024/12/19 10:06:26.798537 [TRS] DBG: Version info: &{2024.12.10.0055 https://cdn.channelsdvr.net/dvr false}
2024/12/19 10:06:26.798615 [TRS] DVR Status: OK: DVR is enabled
2024/12/19 10:06:26.798682 [TRS] macOS Rosetta: OK
2024/12/19 10:06:26.798778 [TRS] System Firewall: OK
2024/12/19 10:06:26.798813 [TRS] DBG: Could not query com.apple.alf state: open /Library/Preferences/com.apple.alf.plist: no such file or directory
2024/12/19 10:06:27.088694 [TRS] Third Party Firewall: OK
2024/12/19 10:06:27.205600 [TRS] Little Snitch: OK
2024/12/19 10:06:27.205671 [TRS] Power Management: OK
2024/12/19 10:06:34 bolt.Open(): flock error: timeout
2024/12/19 10:06:34 couldn't open settings.db: timeout
2024/12/19 10:06:42.593603 New diagnostic log submitted under 6da3ae3b-ab82-4e50-aca0-7e5fcaa2efab
2024/12/19 10:06:44 bolt.Open(): flock error: timeout
2024/12/19 10:06:44 couldn't open settings.db: timeout
2024/12/19 10:06:54 bolt.Open(): flock error: timeout
2024/12/19 10:06:54 couldn't open settings.db: timeout
2024/12/19 10:07:04 bolt.Open(): flock error: timeout
2024/12/19 10:07:04 couldn't open settings.db: timeout
2024/12/19 10:07:14 bolt.Open(): flock error: timeout
2024/12/19 10:07:14 couldn't open settings.db: timeout
2024/12/19 10:07:24 bolt.Open(): flock error: timeout
2024/12/19 10:07:24 couldn't open settings.db: timeout
2024/12/19 10:07:34 bolt.Open(): flock error: timeout
2024/12/19 10:07
I just migrated this machine from 2010 mini to M4 Mac mini this morning.
During the install process I first installed channels as a system service. I then realized that my new machine has hardware transcoding and decided that I don't want to use it that way, so I uninstalled and reinstalled and have channels now set to start at power up. It will be an always on machine - no sleep. Migration actually went very SMOOTH - except Im now getting tons of those messages in the logs.
I submitted diagnostic logs after troubleshooting self check:
6da3ae3b-ab82-4e50-aca0-7e5fcaa2efab
I think this may be because of my first using it as a system service and then changing my mind - and I hosed something. Am I correct?
If so, what terminal commands can I use to fix it?
The only other thing I can think of is that my database is now running on the original machine which is going to be used as a NAS. The old channels server is disabled. I just changed the path to the network drive and everything seems to be OK - even after reboots and power failure.