Recording fails (help needed to analyse logs)

[vnormand 3]

Hello! 

Some of my recordings are currently not working and I am not sure why.

I see there is an error in the attached file at 19:30. But unsure what it means. 

A little help would be appreciated! 

Thank you!embyserver.txt

[emveepee 132]

I'd say this 

2025-11-05 19:30:56.694 Error SharedHttpPipelineSource: Failed to shut down GraphRunner!

and the NextPVR logs to determine why it is returning error 500 ( I expect too many calls fro the same channel)

[vnormand 3]

@emveepeeThank you for your help !

So, the problem seems to be with NextPVR then... I will try and update it and see if it helps.

[emveepee 132]

I don't necessarily say it is a NextPVR "problem" if Emby is trying to use more tuners than are available.  Make sure the channel you were trying to record works in NextPVR first.  Post the NextPVR logs here too before they roll.

Martin

Edited November 6, 2025 by emveepee

[vnormand 3]

I have 2 tuners and both were available at that moment.

Looking at NextPVR logs, I see there is a Null reference pointer exception when starting the recording.

Will try updating it as I was pretty late on updates, and we'll see.

Thanks

[emveepee 132]

I would need to see the NextPVR logs, Emby doesn't start a NextPVR recording.

[vnormand 3]

Here it is. Thanks

nrecord.log

[emveepee 132]

Unfortunately that is not all the logs, the DeviceHostWindows logs would have the information but I see CIVQ failing at least 3 times.

[vnormand 3]

Sorry, did not know there was other logs relevant. Here are all the logs.

logs-20251106-0733.zip

[emveepee 132]

I didn't see any testing in NextPVR  you need to confirm all the channels work there before bothering to debug Emby.  Check your antenna and remove splitters and any booster amplifiers they can cause as many problems as they fix

Also for sure turn off the OTA EPG updates they are a waste of time with Emby and make a tuner unavailable when Emby might use  plus I assume you are using Emby guide data anyway.  You are right though the 2 year old version is old, but wait a few weeks for 7.0.4

Martin

[vnormand 3]

It seems the channel that was not working had changed frequency or something. I realized it was not even able to tune. So, I redid the whole setup of channel scan + mapping in Emby, and now it seems ok. We'll see.

Thanks for your help @emveepee

[emveepee 132]

Great, they don't change frequency often but the the internal mpegts ID do change which is why you need to check the backend first.