NextPVR is being shut down/shutting itself down

[mvallevand]

I thought you said that a launchagent script like this https://forums.nextpvr.com/showthread.ph...#pid578589 wasn't a good thing?

My hackintosh is probably similar to your mac mini i5 7th gen I will see if I can get is started once I see what Kodi is doing.

Martin

[Allan]

All the launchagent in the linked message is not optimal. All it does is call a bash script at login, and all the bash script does is launch nextpvr in a terminal window and hide the terminal window. Terminal is still open and running (and quitting it inadvertently will also quit nextpvr). As well, a key utility of launchd is the keepalive key to keep nextpvr running in case of a crash, etc.. That script does not use the keepalive key, and I am not sure it would work if it is calling a bash script.

The launchagent (preferably launchdaemon) I am working on runs nextpvr in the background. It does not open terminal or use a terminal window. If NextPVR dies, it respawns.

[mvallevand]

If possible on your firestick could you try sideloading uidroid https://forums.nextpvr.com/showthread.ph...#pid562489 you don't need to use it but once it starts if you go to the Exit it will do a session.logout and we will see if there is an API issue on macOS.

Martin

[Allan]

I'll give it a try tomorrow

[Allan]

It did not shut itself down last night (although the launchagent would respawn it, the respawn would be logged - there was no respawn).

On the off-chance there is anything useful in the Kodi log, here it is anyway.

I will install uidroid.

[mvallevand]

Those are still info logs not debug logs, maybe use an advancedsettings.xml so you don't have to set it.

Code:

<advancedsettings>
    <loglevel hide="false">1</loglevel>
</advancedsettings>

Martin

[mvallevand]

I can't believe how default it is to install this on macOS, clearly not many people try or at least no one that isn't a real PRO. It definitely needs brew

When you install uidroid you will need to unblock some files not sure which of these. You probably had to unblock libe_sqlite3.dylib so you know how to do that .

Code:

NPVR/libHarfBuzzSharp.dylib
NPVR/libSkiaSharp.dylib

NPVR/runtimes/osx/native/libHarfBuzzSharp.dylib
NPVR/runtimes/osx/native/libSkiaSharp.dylib

I don't know if you noticed by you will also need to brew install libmediainfo

Anyway once I had this, it could be because a table was empty.

Code:

[3] Got request [172.16.3.3]: /service (session.logout)
[3] parameters:
[3]    method: session.logout
[3]    sid: 1a95a23edb3d41f3b2e77db1fc1620ef
[3]    client: 1d4c6080d81
[3]    format: json
[3]    client_ip: 172.16.3.3
[3]    client_local: true
[3]    user_agent: yauiclient-2.0
[3]    host_callback: ...
[3] Logging out sid: 1a95a23edb3d41f3b2e77db1fc1620ef
[3] {"stat":"ok"}

[3] Disposing UI Client session 1a95a23edb3d41f3b2e77db1fc1620ef
[3] System.NullReferenceException: Object reference not set to an instance of an object.
   at NextPVRServer.Controllers.WebClientHelper.TerminateSession(Dictionary`2 parameters)
   at NPVR.Controllers.ServicesController.HandleServiceRequest(String body, String contentType)

but it didn't kill the server. I expect it is related though and need to test with Kodi but so far Kodi has exited ok.

Martin

[mvallevand]

For completeness my logs show a few lines where the signal is showing on your server. I will try again after recording the CTV News at 11. No other problems since the first one.

Code:

[21] Got request [172.16.3.3]: /service (session.logout)
[21] parameters:
[21]    method: session.logout
[21]    sid: 9c0048b2541c45c1891c3716eec451ce
[21]    client_ip: 172.16.3.3
[21]    client_local: true
[21]    user_agent: Kodi/21.1 (Windows NT 10.0.26100.2605; Win64; x64) App_Bitness/64 Version/21.1-(21.1.0)-Git:20240817-183eb85f10
[21]    host_callback: ...
[21] Logging out sid: 9c0048b2541c45c1891c3716eec451ce
[21] <?xml version="1.0" encoding="utf-8" ?>
<rsp stat="ok">
</rsp>

[11] PowerManagement AllowSleep (needs implementation)
[11] No longer active

Martin

[Allan]

A couple of things:

1. No kill last night either. It may be a coincidence, but there has been no kill since I set up the launchagent, although it previously happened most nights when running in a terminal window.
   
2. I have 100% turned on debug logging. In fact, I located additional log settings under "component specific logging" and turned on verbose looking of per component. Nonetheless, the lowest tag in the log is still info. Attached for your info. I won't have time to figure out how to edit the xml files on the fire tv stick until the weekend.
   
3. Personally, I found it pretty easy to install NPVR - copy NPVR folder to applications and launch dotnet app. The only complications were dealing with gatekeeper blocking numerous items, which has become more complicated under sequoia. It's deliberately unintuitive, I think. I will expand in a separate note.
   
4. Speaking of gatekeeper - I unblocked a bunch of items during first run of NPVR, but I did not keep track, and the command that used to give a comprehensible list of "allowed" unsigned items now just produces a list of non-human readable info like: "541[GKE] P0 allow install [(gke)] cdhash H"53138ef29e79bd853f20ca1d3faf26110d29ef3e". I have unblocked everything where I got a gatekeeper prompt and I'm not sure I can unblock anything else without being prompted by the OS.
   
5. Trying to use the android UI was unsuccessful. I initially got a gray screen (and almost gave up) which went to a setup page after several minutes. In this regard, it looks like those minutes were spent trying to connect to a nonexistent preconfigured IP address. I suggest that, on initial startup, one should get a screen with three fields: 1. to set up the server IP address, 2. the port number (defaulting to 8866) 3. the pin  (defaulting to 0000). That would have saved me a lot of time, as I had several false starts. Even after I entered the string exactly as required, I could not get anything to work until I deleted the cache and user data, and started again with a clean slate.
   
6. (really 5.1) When I finally got an interface (BTW, not intuitive that you have to hit the back button to get there from the settings page - a done or save button would be good) I navigated to a program and pressed play, but no cigar.
   

[mvallevand]

I've been testing Kodi and UI clients randomly all day with no issue. I am just running in foreground terminal window.

I would try my advancedsettings.xml since clearly whateve you have done isn't maintaining the debug logging.

My problem wasn't unzipping NPVR.zip it was trying to install ASPNet core and dotnet runtimes. Perhaps things were more complicated because I did test v5 on it so it did have dotnet 3. There is not installer and I just kept download tar files with no instructions on how to get them installed or in the path. By default brew didn't install v8 and it took a bunch of reading before I found out that I needed a special cask. Then there was the original gatekeeper on the sqlite dylb just to run (and then remembering I had to go to setting to unblock and start NextPVR again) Just allowing it wasn't enough I still had to wait until prompted to accept it and enter my password.

My experience is also hampered with my Windows keyboard on my hackintosh because my normal keys to edit the command line like Home don't take me to the beginning of the line and Ctrl-C isn't Ctrl-c so I get frustrated with the CLI.

Normally UI clients would find NextPVR via UDP discovery maybe your LAN is segmented. Also if you are running NextPVR anywhere on Docker you would need to configure the UDP discovery, since there is no pre-configured IP.

Pretty much all the NextPVR UI client GUI depends on the back key as a new user I understand that might take getting used to. I don't plan on changing the settings screen. You should have been able to play Canadian OTA though, I was mainly interested in you hitting the Exit from the maim menu since that forces the session logout.

Martin