Why is NextPVR logging http://localhost:nnnnn/status ?

[PapaJay]

Hi

NextPVR Service is logging [DEBUG][XX] http://localhost:nnnnn/status every 5 seconds - the value of nnnnn over the last several days has been 53803, 58567 and many others.   The XX in DEBUG also varies a lot (see logs).

localhost:nnnnn is usually used when debugging/testing and application that is not yet ready to access remote resources.  It can also be used to see if an app that is listening on a given port is still there.

Running this every 5 seconds would appear to be excessive even if it is testing to see if an app is listening on a port on the local machine.  If this is expected is there any way to control the interval?

I discovered this when my HTPC was not sleeping as it should have been.  HTPC is a Windows 10 box, running NextPVR   .  You will also see in the logs that there is a Kodi 19 client running on a Shield.  I killed off Kodi on the Shield around 9:26 AM local time on March 21, 2021 - you will see in the logs that the client was constantly pinging the NextPVR server for /service (recording.lastupdated) and sometimes getting updates prior to this time - I will open a separate thread for the excessive /service (recording.lastupdated) prior to 9:26 AM as this will most likely be an issue to be understood from the client perspective as it is the client making the request of the server.

Can anyone shed some light on what is going on.  Is there a way to control this?

Thanks.

[sub]

NextPVR Service is logging [DEBUG][XX] http://localhost:nnnnn/status every 5 seconds - the value of nnnnn over the last several days has been 53803, 58567 and many others. 

This log message is removed in the next build.

[PapaJay]

Sub

I have discovered that if I take direct action to sleep HTPC - don't wait for it to sleep because the system is idle - these messages don't start again when the system is started by me.  If the system is awake when we get up in the morning, I will check to see if the localhost messages are being logged, and if they are I will put it to sleep, then wake it up and see if the logging has stopped.

Two questions:

1. Would restarting the NextPVR Service via a scheduled task stop the logging?  I have a scheduled task that will do this that is currently disabled.
   
2. Do you have a target for the next build?
   

Thanks

[sub]

Would restarting the NextPVR Service via a scheduled task stop the logging?  I have a scheduled task that will do this that is currently disabled.

That specific log message is from the NextPVR Recording Service to DeviceHostWindows.exe. Putting the machine to sleep will be causing DeviceHostWindows.exe to terminate (until the next time it needs to use a tuner). Unticking 'keep digital tuners primed' should cause DeviceHostWindows.exe to terminate after each use, and it'll stop logging those messages.

Do you have a target for the next build?

Hopefully some time in the next few days.

[PapaJay]

Sub

First, I apologize for not updating this thread sooner.  So far, only when I sleep the machine do the http://localhost:nnnnn/status messages stop.  As was stated the restart as soon as a scheduled recording takes place.

I checked my config.xml file, which I assume is still used in V5 and the setting of PrimeDigitalTuners = false - I assume that this is the configuration value you meant when you said 'Unticking 'keep digital tuners primed' should cause DeviceHostWindows.exe to terminate after each use'  Here is the line from the config.xml file.

<PrimeDigitalTuners>false</PrimeDigitalTuners>

I am assume false means it is unticked.  If not then I would I need to set this to true to 'untick it'?

I am fairly sure that the writing of this message to the log every 5 seconds is what is keeping my HTPC from sleeping - even if there is little CPU involved, there will be some amount of I/O from the writing of the message and this will keep Windows from sleeping.

I am going to activate my scheduled task to stop and start the NextPVR Service once a day at 00:30 to see if this causes the messages to end and the HTPC will sleep once MCEBuddy has finished its work which starts at 11:30 PM every night and finishes sometime in the morning depending on how many shows it has to process.  I will report back in a few days with results.

Jay

Suggestion:  When zipping logs for upload include configuration data (config.xml).  May help with debugging problems.

Background

• NextPVR 5.1.0.201216 on Windows Pro, Kodi 19 on Shield
  
• Sleep timers - attended and unattended - set to 20 minutes per other threads.  Network adapter will only wake HTPC when Wake on LAN magic packet received
  
• Kodi on Shield terminated (stopped) after use to prevent calling server for updates continuously when not watching TV
  

[Graham]

<PrimeDigitalTuners>false</PrimeDigitalTuners>

I am assume false means it is unticked.  If not then I would I need to set this to true to 'untick it'?

You can untick it in NextPVR Settings ... https://github.com/sub3/NextPVR/wiki/Add...e-settings ... though iit appears that the tick box is not described in the wiki webpage.

[sub]

Suggestion:  When zipping logs for upload include configuration data (config.xml).  May help with debugging problems.

It includes username/password, and connection details, and potentially IPTV account details, so I wouldn't want config.xml included with the log files anyone can view.

[sub]

First, I apologize for not updating this thread sooner.  So far, only when I sleep the machine do the http://localhost:nnnnn/status messages stop.  As was stated the restart as soon as a scheduled recording takes place.

I checked my config.xml file, which I assume is still used in V5 and the setting of PrimeDigitalTuners = false - I assume that this is the configuration value you meant when you said 'Unticking 'keep digital tuners primed' should cause DeviceHostWindows.exe to terminate after each use'  Here is the line from the config.xml file.

<PrimeDigitalTuners>false</PrimeDigitalTuners>

I am assume false means it is unticked.  If not then I would I need to set this to true to 'untick it'?

You'd still get them while a tuner is in use. ie recording and live tv.

The message is gone entirely in the next release.

Having it ticked (in the Settings->Devices page) causes the tuner to stay alive after first use, making subsequent uses quicker to start.