2021-03-21, 04:29 PM
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.
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.