NextPVR is being shut down/shutting itself down

[Allan]

At least once a day NextPVR shuts down spontaneously. It does not appear to be a crash, because the last item in the terminal window is "Killed: 9", which I assume means the unix kill command with signal 9 was received. An example is reproduced below, and the log coinciding with this terminal output is attached.

You will note that the last entry in the log is at 23:48. This also happens to be the exact time that I exited Kodi, after watching a program. I have seen this same coinciding kill an a few occasions. 

Code:

[198] > 64412 frames decoded in 77.65 seconds (829.52 fps)
[198] Got request [10.0.100.151]: /service (session.logout)
[198] parameters:
[198]    method: session.logout
[198]    sid: 80b1000977584d7c9a5995efa549c0f8
[198]    client_ip: 10.0.100.151
[198]    client_local: true
[198]    user_agent: Kodi/21.1 (Linux; Android 9.0; AFTKA Build/PS7685.4486N) Android TV/9.0.0 Sys_CPU/armv7l App_Bitness/32 Version/21.1-(21.1.0)-Git:20240817-183eb85f10
[198]    host_callback: ...
[198] Logging out sid: 80b1000977584d7c9a5995efa549c0f8
[198] <?xml version="1.0" encoding="utf-8" ?>
<rsp stat="ok">
</rsp>

Killed: 9

[mvallevand]

Do you have the Kodi debug logs? I am curious if Kodi core has finished updating itself when pvr.nextpvr is closed.

I also don't think comskip has finished so do you have any indication in the macOS system journal when it finishes.

Martin

[Allan]

The Comskip log file was last modified at the same time as the NextPVR log closed: 11:48. log attached. Also, there is no comskip file with the recording, although every other recording I looked at now has both a txt and edl file (including a program that finished recording 45 minutes ago).

Kodi is running on a Fire TV stick. I don't know if there is a way to get at the logs. Let me know if is still useful (given the above) and I will figure it out.

[mvallevand]

Yes comskip is probably crashing too I wanted to confirm. I am wondering if the signal 9 is one that could come when the OS runs out of memory. I see that from time to time on Linux when I need to increase the swap.

Yes you can get the logs from Android in multiple ways. The log uploader addon is probably easiest but you can use the Kodi file manager to copy them to a share or you could use adb directly or this helper http://www.jocala.com/

Martin

[Allan]

So... Kodi starts a new log each time it is launched and only keeps one archive, so the only one I have to attach is last nights. I am also attaching the contemporaneous comskip and nextpvr logs.

Notably: comskip did not crash. It created its comskip files at 12:04 am.
12:04 Comskip log timestamp
12:14 NextPVR kill signal 9
12:15:04  Kodi exits. NB: time is from the fire TV stick. From the tail end of the terminal session, below, you can see that the logout from kodi was the last thing that happened before the kill, so it looks like the kill is either simultaneous to or shortly after kodi exits.

I do not believe there is a memory issue. The computer running NextPVR has 32 GB

Code:

[23] Got request [10.0.100.151]: /service (session.logout)
[23] parameters:
[23]    method: session.logout
[23]    sid: ae3c5b0893b744f7be67e0d75286b9d5
[23]    client_ip: 10.0.100.151
[23]    client_local: true
[23]    user_agent: Kodi/21.1 (Linux; Android 9.0; AFTKA Build/PS7685.4486N) Android TV/9.0.0 Sys_CPU/armv7l App_Bitness/32 Version/21.1-(21.1.0)-Git:20240817-183eb85f10
[23]    host_callback: ...
[23] Logging out sid: ae3c5b0893b744f7be67e0d75286b9d5
[23] <?xml version="1.0" encoding="utf-8" ?>
<rsp stat="ok">
</rsp>

Killed: 9

[Allan]

For your information:
next night, same result (kill at the same time as I quit kodi)
night after that, I did not use kodi, and Nextpvr was still running in the morning.

[mvallevand]

I personally am still waiting for the requested Kodi debug logs, the default logs are useless.

Martin

[Allan]

I was unaware that the logs I sent were not what you were looking for. I have now identified a kodi setting to turn on debug logging and will furnish that log tomorrow.

For your information, I have now set up a launchagent that will respawn the dotnet app when it is killed, crashes, etc.

Since this works around the problem, if you are uninterested in pursuing it further, please advise.

[mvallevand]

Sorry yes I am getting tired of having to ask users for logs so basically I ask once (it is also on the wiki).

My hackintosh to test macOS is currently in pieces I am mainly interested to see what is going on in Kodi to see if I can fake it. Sub the author is probably more interested than I am on what might be causing this. I close down Kodi often and do many session.logouts a day on Windows and Linux so it feels like something specific to macOS or potentially Apple Silicon which I can't test.

Martin

[Allan]

Not apple silicon on the mac that's running nextpvr here. 2018 intel mac mini.

BTW, the launchagent is significant from a usability perspective on the mac. No terminal window. respawns in case of failure. I would rather have it run as a launchdaemon (no user login necessary) but I have not been able to get that working. Probably an apple security measure I have not figured out how to address. I will post details in the forum when I am comfortable that it is 100%. It would likely make a desirable addition to the mac installation instructions.