Detectads - Plugin Failure

C

Cancunia

Member
Apologies if this has been covered, or if I've pressed too many buttons to try & fix it, but I'm having problems with Detectads:
Custom FW 3.13 installed.
Detectads is set on auto in the root 'My Video' folder and has been running without issue for a long time.

Last night, I noticed that some programmes that had been recorded the night before did not have bookmarks for ads, so had apparently not been processed by Detectads.
Today, I noticed a few more that I thought would normally have been processed by now so I started to look a bit deeper into things:

If I look at the system queue I can see that detectads is running from what looks to be the oldest recordings on the disk, these had already been processed months ago. The log comments show 'plugin failure' & it seems to be looping trying to run detectads on the same 2 old recordings, then reporting 'plugin failure'.

Some info that may be relevant & may not but I noticed in the WiKi that detectads uses jim so thought it may be. I had a problem a few days ago with the webif showing '500 Internal Server Error' after auto updating a couple of packages, the webif error log showed

Code: 
/mod/bin/jimsh: can't load library 'libutil.so.0'

The webif problem has now been resolved by a force reinstall and the webif error log is now clear. But the detectads problem comes from about the same time.
 
A quick update, detectads is still working on single programmes at least.
I removed the flag from the video root & also changed the settings from 'Auto' to 'Folder flag', then ran detectads against a single programme via 'Run Now' rather than 'Background'. I'll try some more & report back.
 
Are there any error messages in detectads.log, auto.log or chaseget.log around the time of the most recent detectads processing of the failed programmes?
Webif-error.log is only used for errors related to generating web pages,
Can you delete the queue entries for the old recording that it is trying to process - perhaps move the recordings to another folder with noDetectads flag set so it doesn't try to process them again.
 
I'll check the logs, do the actions you've suggested & report back. Understood re the Webif-error.log, I mentioned it just in case there might have been some relationship to the current problem.
 
detectads.log & auto.log were empty but below is a snippet from chaseget.log.

I cleared the queue as suggested & then queued some sub folders for ad detection that had already been processed at an earlier date & they ran correctly. I've now queued a mix of detected & undetect ed programmes and will see what happens.


Code: 
144    16/11/2022 17:00:12 -    Plugin failure
143    16/11/2022 17:00:12 -     -1 -  -
142    16/11/2022 17:00:12 - De-queuing 10762 - detectads - /mnt/hd2/My Video/Venus and Serena_20140622_2219.ts
141    16/11/2022 17:00:12 -    Plugin failure
140    16/11/2022 17:00:12 -     -1 -  -
139    16/11/2022 17:00:12 - De-queuing 10763 - detectads - /mnt/hd2/My Video/Laurel Canyon_20220425_2122.ts
138    16/11/2022 17:00:12 -    Plugin failure
137    16/11/2022 17:00:12 -     -1 -  -
136    16/11/2022 17:00:12 - De-queuing 10764 - detectads - /mnt/hd2/My Video/The Martian_20180519_2201.ts
135    16/11/2022 17:00:12 -    Plugin failure
134    16/11/2022 17:00:12 -     -1 -  -
133    16/11/2022 17:00:12 - De-queuing 10765 - detectads - /mnt/hd2/My Video/Britain's Favourite 90's Hits_20220107_2303.ts
132    16/11/2022 17:00:12 -    Plugin failure
131    16/11/2022 17:00:12 -     -1 -  -
130    16/11/2022 17:00:11 - De-queuing 10766 - detectads - /mnt/hd2/My Video/New_ Paul Simon_ Under African____20220806_2000.ts
129    16/11/2022 17:00:11 -    Plugin failure
128    16/11/2022 17:00:11 -     -1 -  -
127    16/11/2022 17:00:11 - De-queuing 10767 - detectads - /mnt/hd2/My Video/Man on Wire_20160601_2315.ts
126    16/11/2022 17:00:11 -    Plugin failure
125    16/11/2022 17:00:11 -     -1 -  -
 
if you get any repeats of the problem add -d 2 on the Other options field of the Detectads settings section of the Settings page
And Auto-processing log level = Degbugging information in the Auto Processing options section and then see if there are more helpful messages
 
MymsMan said:
if you get any repeats of the problem add -d 2 on the Other options field of the Detectads settings section of the Settings page
And Auto-processing log level = Degbugging information in the Auto Processing options section and then see if there are more helpful messages
Click to expand...
Thanks for your help, I recorded another programme this morning and all has gone well with detectads. It's a strange coincidence but I had no problems at all until the other day when the WebIf stopped working after an auto upgrade of some packages.
 
I think the problem was caused by corrupt / incorrect sidecar files, so far I've rebuilt sidecars for 2 recordings after moving the .ts files to another directory and then re-run dectectads, all looks good. I'll do the rest but as it will take a while, I'll only report back if there are further problems.
 
You must log in or register to reply here.
Back
Top