web client on Mac streaming failed transcoder exited

[rjbeep]

Hi folks,

Got a fresh Catalina install on a MacBook Pro and I've installed ffmpeg via homebrew. Using fresh install of Chrome for browser. Can't get the npvr web client to work. streaming failed / transcoder exited.

server is running on a different Mac in the other room.

hdhomerun client directly to the tuners works fine... just the web client to npvr server that I can't figure out.

here's what npvr had to say about it (attached). any direction?

thanks very much for the continued help...
Richard

[mvallevand]

Send all the logs that you get zipped up from the main settings page.

Martin

[rjbeep]

Send all the logs that you get zipped up from the main settings page.

Martin

logs uploaded
thanks Martin

[sub]

It looks like it's unable to connect to your HDHomeRun. Have you tried power cycling the HDHomeRun?

2019-12-11 09:59:42.913 [DEBUG][107] Requesting: http://192.168.11.188:5004/tuner1/v9.1
2019-12-11 09:59:42.917 [DEBUG][118] HTTP input source starting
…
2019-12-11 09:59:42.961 [DEBUG][118] Unexpected error in HTTP input source: System.Net.WebException: Connection refused Connection refused ---> System.Net.Http.HttpRequestException: Connection refused ---> System.Net.Sockets.SocketException: Connection refused
at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)
at System.Threading.Tasks.ValueTask`1.get_Result()
at System.Net.Http.HttpConnectionPool.CreateConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)
at System.Threading.Tasks.ValueTask`1.get_Result()
at System.Net.Http.HttpConnectionPool.WaitForCreatedConnectionAsync(ValueTask`1 creationTask)
at System.Threading.Tasks.ValueTask`1.get_Result()
at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
at System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)
at System.Net.HttpWebRequest.SendRequest()
at System.Net.HttpWebRequest.GetResponse()
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at NShared.Shim.InputSourceHTTP.WorkerThread()

[rjbeep]

subIt looks like it's unable to connect to your HDHomeRun. Have you tried power cycling the HDHomeRun?


Hi sub,

I seem to have all kinds of strangeness happening all of a sudden.

the HDHRs are in another room so since the HDHR app was connecting to them fine, I tried some other stuff before power cycling the tuners (yep... I'm that lazy).

I shut down the NPVR server
renamed the NPVR and .NPVR-data folders to *.old
did a fresh download of the NPVR zip from this site
unpacked it into a new NPVR folder
chmod +x the server binary
ran the server
rediscovered the tuners
rescanned the channels

now...
I can connect and watch live tv from both the local mac running NPVR and a client mac (so Chrome/ffmpeg are working, right?)
I can schedule a recording and it records a .ts file
I can manually go to the recording directory and play the recorded file with any tool I want (so the recording is good).

*BUT*, I cannot play the recording from the NPVR web interface
I get a "permission denied error" on the browser web interface (either on the local mac or on a client mac)
fmpeg goes nuts on the server
the CPU on the server goes into some kind of race condition, the fans start spooling up, etc.
I have to either click something else in the interface to get the server to stop trying to play the file or I have to close the server down in order to get the CPU/fans to come back down to normal.

at first, thought it might be something I changed on the NAS I'm mounting as a record directory, but same exact symptoms even when I set up using all local directories on the same physical disk.

no clue what I've done now but I've uploaded logs in case you are bored and have nothing better to do :-)

thank again :-)

[mvallevand]

Is there anyway you can run NextPVRServer as sudo?

At first I thought the error was ffmpeg but the transcoding continues way past the error. When I look at the error

Code:

2019-12-11 16:42:41.427    [ERROR][20]    System.ComponentModel.Win32Exception (13): Permission denied
   at System.Diagnostics.Process.set_PriorityClassCore(ProcessPriorityClass value)
   at System.Diagnostics.Process.set_PriorityClass(ProcessPriorityClass value)
   at NShared.Extend.RequestHandlers.TranscoderHLS.InitiateTranscode(String& reason)
   at NShared.Extend.RecordingRequestHandler.StreamRecordingInitiate(Dictionary`2 parameters)

It seems that NextPVR is trying to set the priority, maybe this isn't allowed?

Martin

[rjbeep]

Is there anyway you can run NextPVRServer as sudo?

At first I thought the error was ffmpeg but the transcoding continues way past the error.  When I look at the error

Code:

2019-12-11 16:42:41.427    [ERROR][20]    System.ComponentModel.Win32Exception (13): Permission denied
   at System.Diagnostics.Process.set_PriorityClassCore(ProcessPriorityClass value)
   at System.Diagnostics.Process.set_PriorityClass(ProcessPriorityClass value)
   at NShared.Extend.RequestHandlers.TranscoderHLS.InitiateTranscode(String& reason)
   at NShared.Extend.RecordingRequestHandler.StreamRecordingInitiate(Dictionary`2 parameters)

It seems that NextPVR is trying to set the priority, maybe this isn't allowed?
Martin

Hi Martin,

Very interesting. Ran with sudo and no errors. Works just fine. I'd love to know more about why that makes a difference.

Regardless, continued thanks for all your help!
Richard 

[sub]

It seems that NextPVR is trying to set the priority, maybe this isn't allowed?

It is setting the priority. Every previous build has too though, and it hasn't been a problem in the past. It may have been something changed with the most recent macOS update though.

I'll disable this for the Mac for the next build, so it gets the default priority.