Error: Reprocessing metadata for TV

Channels DVR Server
#1

I keep seeing this in my logs:

——————

2022/09/25 10:52:23.547221 [SCN] Reprocessing metadata for TV episode #21479 Sister Wives/Season 17/Sister Wives - S17E01 - It's Over WEBRip-1080p.mkv: 2528493884 != 0

2022/09/25 10:52:23.548280 [ERR] Could not probe file 21479: exit status 1

————-

In fact i realized it was actually killing my streaming connection when i looked at my logs and matched up the times.

I don’t even have this episode. We haven’t watched the series lately, so When i first noticed it i went and deleted all the episodes, cancelled the season pass, and even deleted the few episodes i had in my local media server. So i have nothing sister wives on anything now.

The errors is always the exact same episode and same message.

I even restarted the server and pressed the “prune deleted” button under maintenance.

Nothing works.

Based on time stamps it is happening every five minutes.

image
image1170×1644 213 KB

On daily beta version of DVR.

#2

One little update - i completely removed the connection to my local media and that seems to have stopped the error. From consistently every five minutes to It now being 12 minutes since the last time it errored (which would have been two errors).

Going to leave local media disconnected for now as we usually watch that in Plex anyways….was still odd though…

#3

As you found, Channels DVR does a background scan every 5 minutes looking for new imports.
You can remove them from the Channels database numerous ways.
Trash them from within Channels and empty trash which also deletes the files on disk.
Remove a user defined import source from within Channels which only removes them from the Channels database and doesn't delete the files on disk.
Delete or move the files from outside Channels, then do a Purge deleted from Channels to remove them from its database.

If you have a lot of imports, any adding or removing can take a while.

#4

Yes. The issue was it was hung on this one file even though it did not exist, was emptied from trash, and the database was purged. It was not a new file. The only way to clear the error was to completely remove the connection.

#5

My guess is you had a lot of imports (thousands?)

#6

A few hundred, they were done months ago. Nothing bulk anytime recent.

#7

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