Pluto TV - Incremental EPG updates

[mvallevand]

Great. And yes you really should only have one copy, there will be other updates. I wouldn't rename just unzip overtop, I can't guarantee there weren't other changes.

Martin

[Bstephens]

OK. Then the new plutotv files are supposed to replace the old install ones? I didn't understand that. Thank you.

Bob

[mvallevand]

OK. Then the new plutotv files are supposed to replace the old install ones? I didn't understand that. Thank you.

Yes it is a version bump, but the other thread is locked and I was too lazy to ask sub to open it for me.

Martin

[Bstephens]

Well . . . This is not working for me yet.

I have tracked this for a while and here's what I have observed.

The 8am update does not take place. The pluto-xmltv.xml is time stamped 02:45. There is no update.lock file in the plutotv directory.

When I executed PostLoadEPG.sh in a terminal window, update.lock was created and three hours later pluto-xmltv.xml was updated. So all that works as advertised.

BUT somehow, PostLoadEPG.sh is not being run after the update because there is no update.lock file.

Updating the EPG information from NextPVR settings reports that it is running PostLoadEPG.sh but there is no evidence, that is, there is no update.lock file created.

Where do I go next to troubleshoot this?

Bob



I then ran

[mvallevand]

You go to the button to post a new topic and add zipped logs.

Martin

[mvallevand]

I've updated post #1 with an update, to handle an error condition on overlapping runs of xmltv-update.

Martin

[Bstephens]

Martin:

You mention in the instructions that the Pluto updates do not survive a reboot. You are correct. But after rebooting the server because of some updates, I have not figured out the key to getting the plutotv extra working again. The xmltv updates at the 3am point, but fails to repeat every three hours. My simple reading of the log indicates that PostLoadEPG.sh is being run and I can't find any error messages, though I am certainly not expert enough to know all of the places to look. 

I can run nohup python3 /var/opt/nextpvr/scripts/plutotv/pluto.py xmltv-update and I get an EPG update, but obviously something is wrong.

How are we supposed to restart this extra after a reboot?

Bob

[mvallevand]

I only gave the examples as a guide to help users create their own scripts to update the EPG. If you want to reboot things change. It is not intended to be robust.

I do see this which would indicate the the process should not have loaded a second instance of the addon because it assumes python is running.

2021-05-05 03:17:52.784 [DEBUG][114] About to run /var/opt/nextpvr/scripts/PostLoadEPG.sh
2021-05-05 03:17:52.784 [DEBUG][114] Starting: bash -c "'/var/opt/nextpvr/scripts/PostLoadEPG.sh' "
2021-05-05 03:17:52.862 [DEBUG][121] > Locked

My suggestion is to download the version now maintained on the wiki just in case it is different from yours. You can create this script to get back on track after you reboot, if you'd like

Code:

sudo rm /var/opt/nextpvr/scripts/plutotv/update.lock
sudo python3  /var/opt/nextpvr/scripts/plutotv/pluto.py xmltv-update

Martin

[Bstephens]

Martin:

When I ran the xmltv-update, I got this in the terminal window after "Running PostLoadEPG.sh"
Traceback (most recent call last):
File "/var/opt/nextpvr/scripts/plutotv/pluto.py", line 321, in <module>
if os.path.isfile(updateLockFile) == True:
NameError: name 'updateLocfFile' is not defined

I'm not sure yet whether PostLoadEPG.sh was successful. Time will tell.

Bob

[mvallevand]

You might have copied the screen wrong , but it does look like the version on the wiki isn't quite the same as I run here, but you should be able to ignore that error.

However if you are getting that error I fell that your PostLoadEPG.sh file might be wrong since it would be missing the second parameter to defer the update and it could cause loops

Martin