Getting Pluto extra to work

[mvallevand]

I have no idea what log that is but my gut says you shouldn't be running this twice so something is off (maybe a manual update I don't know.

05/28/24 18:04:43.00 [ PostLoadEPG.bat] EPG has been LOADED
05/28/24 18:05:14.98 [ PostLoadEPG.bat] EPG has been LOADED

Otherwise logs would be required, maybe on resume your network is down and it fails.


Martin

[bouilliabai]

The log is BatchProcessing.log, as generated from the templates provided in the Custom Scripts section of the guide. Those templates were edited by adding the lines pasted above. The templates provide a nice means to send status messages to a separate file, so one doesn't have to search through nrecord.log to find them.

You're right, that is very strange. That shouldn't have run twice unless I did so by accident. The main logs were useless because errors were filling them up and causing them to roll every couple of hours. Lines like this led me to believe the web client hadn't been logged out of cleanly.

Code:

2024-05-30 17:42:12.952    [DEBUG][57]    {"stat":"Failed","code":8,"msg":"Invalid Session."}

Perhaps something did happen at the network level during a short power outage. We got real lucky there, many folks are still without juice nearly 3 days after the fact. The rapidly filling log issue seems to have fixed itself by simply re-logging into NextPVR via the web interface. Also, Kodi has been running with the client, so perhaps it was pinging the server for an updated EPG and not getting one, then sending an error in return.

That said, the same update.lock file PID is still there and the Pluto EPG didn't update all day, so something got messed up.

Any further investigation from this end is going to have to wait a few days.

[bouilliabai]

Road trip delayed by a couple of hours. Here's a little more info.

The LAN has been up and running since power was restored Tuesday morning. No errors that I can tell.

On boot this morning, the machine running NextPVR did process PostStartup.bat, including the line:

START /b "" python C:\Users\Public\NPVR-data\scripts\plutotv\pluto.py xmltv-update 180

Since no update had occurred in the 3 previous hours and it was after 7 am when the computer was started, one would think that should have triggered a Pluto EPG update. Curiously, it did rewrite the update.lock file with a new PID. There are no instances of "Locked" or "Killing waiting task" in the logs.

Also, there was a 2:44 am scheduled general EPG update missed, and this line in the log seems to indicate that its timer was moved a day forward.

2024-05-31 11:31:22.942 [DEBUG][11] Requesting wake up for 'EPG-UPDATE' [EPG Update] at 6/1/24 2:44 AM

I won't be waiting around for 3 hours to see what happens, but the expectation is that no Pluto EPG updates will occur unless manually initiated, or the machine is left awake until at least 2:44 am. I'm happy to check various scenarios and submit logs and other results next week, but for now perhaps this is enough info to provide some clues as to why the undesired results are occurring.

[mvallevand]

It is calculating the wrong update time when it not called, I will need to fix that.

Martin

[bouilliabai]

After letting this run for a couple of months, I've noticed that the Pluto EPG is correctly updated at regular 3 hour intervals (t=180) during the 'active' hours, but between 11 pm and 7 am updates are regular, yet far more frequent, even as close as 10 minutes apart. The regular EPG update is set for 2:44 am per default, and there have been a few manual EPG updates performed as well during this period.

Certainly not a show-stopper, but it is consuming bandwidth and filling up the logs.

[mvallevand]

Sounds like you set something up wrong the update should be disabled overnight

[bouilliabai]

Everything was done per your instructions. Notably, the following lines appear in the respective scripts.

PostLoadEPG.bat

Code:

START /b "" python C:\Users\Public\NPVR-data\scripts\plutotv\pluto.py xmltv-update 180

PostStartup.bat

Code:

START /b "" python C:\Users\Public\NPVR-data\scripts\plutotv\pluto.py xmltv-update 180

UpdateEPG.bat

Code:

START /b "" python C:\Users\Public\NPVR-data\scripts\plutotv\pluto.py xmltv

[mvallevand]

Logs give a better picture. What I posted was a guide to get you going and not a full solution

[bouilliabai]

I was under the impression from a message on 5/31 that you'd discovered the nature of the problem and had a solution in mind.

This is an excerpt from BatchProcessing.log. A storm last night forced the shutdown and isolation of most electronics, including putting the laptop running NextPVR into sleep mode. The larger log has rolled over since then and has no information from this time frame, but I could send nrecord.log.1 if it helps.

Code:

07/22/24  2:44:49.39 [         UpdateEPG.bat] New Log created.
07/22/24  2:44:49.40 [         UpdateEPG.bat] EPG Update TRIGGERED
07/22/24  2:48:44.88 [       PostLoadEPG.bat] EPG has been LOADED
07/22/24  3:11:19.51 [       PostLoadEPG.bat] EPG has been LOADED
07/22/24  3:40:44.98 [       PostLoadEPG.bat] EPG has been LOADED
07/22/24  4:09:40.00 [       PostLoadEPG.bat] EPG has been LOADED
07/22/24  4:38:10.56 [       PostLoadEPG.bat] EPG has been LOADED
07/22/24  5:06:15.02 [       PostLoadEPG.bat] EPG has been LOADED
07/22/24  5:33:48.50 [       PostLoadEPG.bat] EPG has been LOADED
07/22/24  6:00:57.60 [       PostLoadEPG.bat] EPG has been LOADED
07/22/24  6:27:34.14 [       PostLoadEPG.bat] EPG has been LOADED
07/22/24  6:53:43.76 [       PostLoadEPG.bat] EPG has been LOADED
07/22/24  7:19:27.12 [       PostLoadEPG.bat] EPG has been LOADED
07/22/24  7:44:48.62 [       PostLoadEPG.bat] EPG has been LOADED
07/22/24  8:09:46.18 [       PostLoadEPG.bat] EPG has been LOADED
07/22/24 11:10:35.57 [       PostLoadEPG.bat] EPG has been LOADED
07/22/24 14:11:20.12 [       PostLoadEPG.bat] EPG has been LOADED
07/22/24 17:12:03.98 [       PostLoadEPG.bat] EPG has been LOADED

[mvallevand]

I have an improvement in mind but I haven't posted anything since I  don't consider it high priority given the low reliability of the streams

Snippets like that show me nothing not worth the effort just post zipped full logs