NextPVR Forums

I'm using a post processing script to move files after the recording is done, and it was working well for some time (at least a few years), but I just noticed that the NextPVR database no longer seems to be updated with the new loaction. The last line of the script is:



It's supposed to tell the NextPVR database that the file moved from the input filename (in $1) to my new location (in $plex_file)

For a very long time it was working fine, but now it doesn't seem to update the database. I did upgrade recently; has this command changed, or should this still work as-is?

I personally don't suppport NScriptHelper because I don't use it and sub doesn't test it enough. I think I found that you had to change to the folder the and run it like this the last time I checked

cd /opt/nextpvr/system/
/opt/dotnet/dotnet NScriptHelper.dll ....

Sub probably needs to update the json files.

Martin

OK, thanks, I'll give that a try, and I'll add some extra tracing to the script while I'm there to see if I can track it down. 

It's not a major issue since I never play or manipulate the recordings from NextPVR (as you may have spotted from the script, I use Plex for that), so if they "disappear" from the database, it's kind of OK; but it is nice to at least get the status from NextPVR as a sanity check (e.g recorded fine, or failed because error 404, or something else).

That change didn't seem to help; the debugging tells me everything else is correct in the script, so the only conclusion I can come to is that NScriptHelper isn't working properly.

One thing that did occur to me was that the action is non-atomic, and there may be some kind of timing window. I move the file first and then tell NextPVR it was moved; if NextPVR notices that the file is no longer there, it may remove it from the database before I get a chance to tell it that the file moved. There is only one line of script between moving it and running NScriptHelper, so the change is petty much instant, but it is a possibility. If I run NScriptHelper first, then I probably still have the same issue since the file will not be at the target location yet. I could copy the file instead, and then delete at the old location after running NScriptHelper, but these files can be petty big, a move to the same drive is instant (simple inode change), but a copy could be much longer running.

Maybe I'll play with it if I get time, but right now, this functionality seems to be broken, unless there are some requirements I don't know about.

NScripthelper is often broken. The only way I test it is with this in my PostStartup.sh comand and restart the service


Perhaps that will help you. There would also be scripthelper logs if it running correctly.

Martin

Thanks for the hint on the logs. looks like it does run the rename, but my timing window theory might be correct, error is:



Yeah...that makes sense, I just moved that file to some other location.

The strange thing is that I'm sure this worked at some time in the past; I guess something changed in the newer releases somewhere.

Full logs attached for this one record cycle in case you can spot anything else of use.

Logs didn't upload. I'm getting:



One more try.

Deleted old attachments. Last try

OK, in text form: