bolt.Open(): flock error: timeout

Channels DVR Server Troubleshooting
#1

Anything to worry about?
I just migrated my server from a Synology Package install to a new docker container.
Seems to be working.

2023/01/17 14:48:33.700839 [SYS] Starting Channels DVR v2023.01.16.2221 (linux-x86_64 pid:7) in /channels-dvr/data
2023/01/17 14:48:33.738848 [SYS] Started HTTP Server on 8089
2023/01/17 14:48:44.959443 [ERR] Failed to refresh auth: Post "https://community.getchannels.com/dvr/api": dial tcp: lookup community.getchannels.com on 127.0.0.11:53: read udp 127.0.0.1:51285->127.0.0.11:53: i/o timeout
2023/01/17 14:48:45.149982 [DVR] Recording engine started in /shares/dvr
2023/01/17 14:48:45.160630 [CACHE] Deleted cache for already deleted file 1469
2023/01/17 14:48:45.165558 [CACHE] Deleted cache for already deleted file 1482
2023/01/17 14:48:45.233467 [SYS] Created database snapshot: backup-20230117.224845
2023/01/17 14:48:45.233869 [SYS] Removing old backup backup-20230106.023112
2023/01/17 14:48:55.114868 [IDX] Pruned 1 expired airings from X-TVE in 51.879421ms.
2023/01/17 14:50:27.173106 [DVR] Recording engine stopped.
2023/01/17 14:50:28.439080 [M3U] Refreshed lineup for frndlyTV with 36 channels
2023/01/17 14:50:29.010678 [M3U] Refreshed lineup for frndlyTVNoEpg with 4 channels
2023/01/17 14:50:29.420301 [DVR] Restored backup backup-20230117.223913 from /shares/dvr/Database
2023/01/17 14:50:49.041216 bolt.Open(): flock error: timeout
2023/01/17 14:50:49.041300 timeout
2023/01/17 14:50:51.057108 [SYS] Starting Channels DVR v2023.01.16.2221 (linux-x86_64 pid:6) in /channels-dvr/data
2023/01/17 14:50:51.092404 [SYS] Started HTTP Server on 8089
2023/01/17 14:50:53.238526 [M3U] Refreshed lineup for frndlyTVNoEpg with 4 channels
2023/01/17 14:50:53.797456 [M3U] Refreshed lineup for frndlyTV with 36 channels
2023/01/17 14:50:54.388662 [DVR] Waiting 21h9m5.611351846s until next job 1674072000-ch6085 Canary SUNDANCE Recording
2023/01/17 14:50:54.739493 [DVR] Recording engine started in /shares/dvr

And it allowed me to get my local Fox, FS1 and FS2 back using chrome v109.

#2

If it's printed only once it's fine. If it keeps repeating then reboot

1 Like
#3

I'm getting this error repeatedly when trying to get guide data for a custom channel list.

2023/01/29 17:51:29.765236 [ERR] No stations available in lineup USA-OTA85001 during guide data download
2023/01/29 17:51:32.758540 bolt.Open(): flock error: timeout
2023/01/29 17:51:32.758645 timeout
2023/01/29 17:52:29.874020 [SYS] Starting Channels DVR v2023.01.28.0211 (linux-x86_64 pid:29682) in /volume1/@appstore/ChannelsDVR/channels-dvr/data
2023/01/29 17:52:29.885335 [SYS] Started HTTP Server on 8089
2023/01/29 17:52:37.170497 [HDR] Found 1 devices
2023/01/29 17:52:37.788929 [M3U] Refreshed lineup for Pluto with 351 channels
2023/01/29 17:52:38.439283 [DVR] Recording engine started in /volume2/ChannelsDVR

I go into the Synology Package Manager and see Channels is no longer running, so I have to restart it each time. Any ideas?

#4

Reboot?

#5

Tried that several times. No luck.

#6

Still getting this issue.

2023/08/01 15:54:47.301245 [SNR] Rewriter statistics for 192.168.152.150 (Living Room) for ch6764 NEWSMAX: discontinuity_detected=0 transport_errors=0 saw_pcr=true saw_pmt=true highest_pts=1099.331567
2023/08/01 15:54:47.301402 [SNR] Buffer statistics for 192.168.152.150 (Living Room) for ch6764 NEWSMAX: buf=0% drop=0%
2023/08/01 15:54:47.301527 [SNR] Streaming statistics for 192.168.152.150 (Living Room) for ch6764 NEWSMAX: timeouts=0
2023/08/01 15:54:47.307214 [TNR] Closed connection to TVE-Spectrum for ch6764 NEWSMAX
2023/08/01 16:12:56.340711 bolt.Open(): flock error: timeout
2023/08/01 16:12:56.340883 timeout
2023/08/01 16:15:15.606309 [SYS] Starting Channels DVR v2023.07.31.2351 (linux-x86_64 pid:31080) in /volume1/@appstore/ChannelsDVR/channels-dvr/data
2023/08/01 16:15:15.659623 [SYS] Started HTTP Server on 8089
2023/08/01 16:15:22.542400 [HDR] Found 1 devices
2023/08/01 16:15:22.651823 [M3U] Refreshed lineup for Pluto with 366 channels

2023/08/01 17:04:09.102031 [DVR] Fetching guide data for 5 stations in X-M3U @ 2023-08-16 5:00PM
2023/08/01 17:04:09.520730 [DVR]   indexed 48 airings (5 channels) [0s fetch, 0s index]
2023/08/01 17:04:09.522783 [DVR] Fetching guide data for 5 stations in X-M3U @ 2023-08-16 11:00PM
2023/08/01 17:04:09.933599 [DVR]   indexed 44 airings (5 channels) [0s fetch, 0s index]
2023/08/01 17:04:09.935326 [DVR] Fetching guide data for 5 stations in X-M3U @ 2023-08-17 5:00AM
2023/08/01 17:04:10.236206 [DVR]   indexed 25 airings (5 channels) [0s fetch, 0s index]
2023/08/01 17:04:10.238140 [DVR] Fetching guide data for 5 stations in X-M3U @ 2023-08-17 11:00AM
2023/08/01 17:04:10.579087 [DVR]   indexed 38 airings (5 channels) [0s fetch, 0s index]
2023/08/01 17:04:11.270975 [IDX] Pruned 0 expired groups from X-M3U in 220.328µs.
2023/08/01 17:04:14.274391 bolt.Open(): flock error: timeout
2023/08/01 17:04:14.274519 timeout
2023/08/01 17:04:41.021793 [SYS] Starting Channels DVR v2023.07.31.2351 (linux-x86_64 pid:8486) in /volume1/@appstore/ChannelsDVR/channels-dvr/data
2023/08/01 17:04:41.285311 [SYS] Started HTTP Server on 8089
2023/08/01 17:04:48.160403 [HDR] Found 1 devices
2023/08/01 17:04:48.269781 [M3U] Refreshed lineup for Pluto with 366 channels
2023/08/01 17:04:49.760467 [DVR] Recording engine started in /volume2/ChannelsDVR
2023/08/01 17:04:49.761008 [SYS] Bonjour service running for dvr-nas.local. [192.168.152.35 192.168.152.37]
2023/08/01 17:04:49.887049 [SYS] Created database snapshot: backup-20230802.000449
2023/08/01 17:04:49.887185 [SYS] Removing old backup backup-20230709.000516
2023/08/01 17:04:50.428706 [HC] Removed 30 entries for 2.5M from /volume2/ChannelsDVR/Images/tmsimg to keep under cache limit of 1G (oldest deleted: 2022-01-17T18:35:40-07:00, newest deleted: 2022-01-19T19:46:35-07:00)

Each time, Channels crashes, and has to be restarted in the Synology Package Manager. Version 2023.07.31.2351

#7

You may want to wait on Aman to comment, but it looks like either a problem with your hard dive, or your memory. Bolt is the database that Channels uses, so the inability to access it would imply there is a problem. I generally think it is loaded into memory first, so the error to me implies your RAM is failing.

#8

Did you try rebooting the NAS

#9

It's been going on for over 6 months. It's been rebooted no less than 5 or 6 times since, including once after the error last night.

#10

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.