Recording service crashed, resulting log files are huge

[HarryH3]

The recording service crashed on my server during recording on 9/24. Best I can tell, from looking at NRecord.Log.3, the mayhem started at 2018-09-24 19:58:00.280 From there, there's an overwhelming amount of info in the file. I don't know just what I'm looking for, so I'm hoping that someone can make sense of all of this and help me understand what happened and if it was a random fluke, or something I need to change on the system. It seems like NPVR was trying hundreds of combinations of tuners to find a way to record the scheduled shows?

On the Recordings screen, it shows that the shows "Bull: The Ground Beneath Their Feet (S03E01)" and "The Good Doctor: Hello (S02E01)" started to record and then failed, and then restarted, at 21:04. Another recording in the same time slot, "Manifest: Pilot (S01E01)" didn't start, and is just marked "Failed", but with an error that I've never seen before. Instead of the red "Recording service restarted during recording" message, it shows info about the HDHR Prime in red: "http://192.168.104.27:5004/tuner2/v612".

The fall TV season is starting, so to keep WAF at its highest, I need to get this sorted. Are there any clues buried in the blizzard of log data?

Logs attached.

Thanks!

[HarryH3]

Is there nothing in the logs that indicate what triggered the crash?

[sub]

The recording service crashed on my server during recording on 9/24. Best I can tell, from looking at NRecord.Log.3, the mayhem started at 2018-09-24 19:58:00.280 From there, there's an overwhelming amount of info in the file. I don't know just what I'm looking for, so I'm hoping that someone can make sense of all of this and help me understand what happened and if it was a random fluke, or something I need to change on the system. It seems like NPVR was trying hundreds of combinations of tuners to find a way to record the scheduled shows?

You can safely ignore those messages - they're normal. It's just saying it wants to start a recording during it's pre-padding, but no tuner was available yet. It does that same check over and over until the tuner eventually freeze up at about 20:00:00 when a previous recording finishes.

The actual error seemed to happen right at the end of the log, when it asked (the now available) HDHR Prime for a channel, but it was unable to connect to the prime. It's not clear why it couldn't connect to the Prime though.

2018-09-24 21:00:01.141 [DEBUG][11] Requesting: http://192.168.104.27:5004/tuner2/v612
2018-09-24 21:00:01.141 [DEBUG][11] SetStreamingURL@2
2018-09-24 21:00:01.141 [DEBUG][11] Graph stopping...
2018-09-24 21:00:01.160 [DEBUG][22] got season info
2018-09-24 21:00:01.242 [DEBUG][11] Graph stopped
2018-09-24 21:00:01.243 [DEBUG][11] GetErrorMessage
2018-09-24 21:00:01.243 [DEBUG][11] Unable to open requested stream

[HarryH3]

Thanks sub. I had been watching Live TV at some point that evening, when NPVR locked up hard during a channel change. I ended the task and started NPVR again. Perhaps that left the HDHR Prime in an unknown state. I'll reboot the HDHR, just in case.