Bunch of tmdb timeout errors

Channels DVR Server
#1

I am getting a bunch of the following errors in my log....

Thanks

2026/07/22 04:49:04.332504 [ERR] Failed to get movie info for tmdb/41446: GET: https://contentdb.fancybits.co/api/movies/tmdb/41446: 429 Too Many Requests
2026/07/22 05:01:09.989399 [ERR] Failed to get movie info for tmdb/4233: GET: https://contentdb.fancybits.co/api/movies/tmdb/4233: 429 Too Many Requests
2026/07/22 05:04:33.766571 [ERR] Failed to get movie info for tmdb/646385: GET: https://contentdb.fancybits.co/api/movies/tmdb/646385: 429 Too Many Requests
2026/07/22 05:08:37.583617 [ERR] Failed to get movie info for tmdb/4232: GET: https://contentdb.fancybits.co/api/movies/tmdb/4232: 429 Too Many Requests
2026/07/22 05:13:40.365102 [ERR] Failed to get movie info for tmdb/629176: GET: https://contentdb.fancybits.co/api/movies/tmdb/629176: 429 Too Many Requests
2026/07/22 05:18:12.351168 [ERR] Failed to get movie info for tmdb/7364: GET: https://contentdb.fancybits.co/api/movies/tmdb/7364: 429 Too Many Requests
2026/07/22 05:22:24.015385 [ERR] Failed to get movie info for tmdb/5174: GET: https://contentdb.fancybits.co/api/movies/tmdb/5174: 429 Too Many Requests
2026/07/22 05:28:26.758858 [ERR] Failed to get movie info for tmdb/5175: GET: https://contentdb.fancybits.co/api/movies/tmdb/5175: 429 Too Many Requests
2026/07/22 05:34:30.506623 [ERR] Failed to get movie info for tmdb/2109: GET: https://contentdb.fancybits.co/api/movies/tmdb/2109: 429 Too Many Requests

#2

This indicates the server is busy. If it's a one time thing you can ignore it.

#3

Same, been going on since late last night. I've even tried to kill it with full system reboots to give it some cool off time, but it can't stop, won't stop!

This has happened once before, IIRC, it it took a day or two for the Devs to get their server cleared up and working.

EDIT:

Also starting to see errors like this one:

2026/07/22 12:55:15.957093 [ERR] Failed to get movie info for tmdb/12096: database is locked
#4

We're looking into it.

2 Likes
#5

The outage has been resolved and we have understood the underlying issue and will be deploying a long-term fix for that shortly.

#6

Thanks!

#7

Don't know if it's related but I found this tonight in the logs when I was looking for something else and was wondering about it:

2026/07/26 20:41:55.492724 [ERR] Failed to get movie info for tms/28473622: sql: no rows in result set
2026/07/26 20:41:56.726446 [ERR] Failed to get movie info for tmdb/1325917: fetching by title: sql: no rows in result set
2026/07/26 20:41:57.112919 [ERR] Failed to get movie info for tmdb/1325912: fetching by title: sql: no rows in result set
2026/07/26 20:41:57.550840 [ERR] Failed to get movie info for tmdb/1361215: fetching by title: sql: no rows in result set
2026/07/26 20:41:57.796687 [ERR] Failed to get movie info for tmdb/1319443: fetching by title: sql: no rows in result set
2026/07/26 20:42:07.464647 [ERR] Failed to get movie info for tmdb/1360780: fetching by title: sql: no rows in result set
2026/07/26 20:42:07.883122 [ERR] Failed to get movie info for tmdb/1360779: fetching by title: sql: no rows in result set
2026/07/26 20:42:08.349344 [ERR] Failed to get movie info for tmdb/1360774: fetching by title: sql: no rows in result set
2026/07/26 20:42:18.115588 [ERR] Failed to get movie info for tmdb/1310508: fetching by title: sql: no rows in result set
#8

Thank for reporting this. The errors should be resolved and it will not report it again on the next rescan.

2 Likes
#9