Emby Server Crashes watching live TV

[bshaf 4]

As the topic title indicates, Emby server will crash about 5 minutes after i tune to a channel. By crash i mean the video stream will freeze and i can't connect any emby client (browser, shield, fire tv) to the server. I get the 'server not found' response. If I remote into the server it appears the server is still running, but the CPU and memory usage are through the roof (see attached screen shot). The issues doesn't appear to be channel specific and is 100% repeatable with any emby client... I basically don't have TV right now. Tv has been running perfect for the last 2 years, then about a week ago it started doing this (which I think lines up with when the latest update was installed).

 

I've tried fully uninstalling the update and re-installing it, but I get the exact same results. 

 

I've attached the various logs. As a reference point I tuned to channel 570, then about 5mins in the screen froze and I couldn't re-establish a connection. 

 

Any help would be much appreciated!

embyserver-63700544654.txt

hardware_detection-63700544666.txt

ffmpeg-transcode-fe042c9e-25de-4cf1-9088-6efab4a6964d_1.txt

[bshaf 4]

Ok.... So i've been doing more tests tonight. It appears the issue is only with cable channels. The local channels appear to work fine.

 

In my configuration i have a HDHomeRun Prime and an HDHomeRun Connect Quatro (both with the latest firmware) and am using the Schedule Direct service for my guide (if that helps).

 

I wish I was a little smarter reading the logs...

[bshaf 4]

I'm starting to be less hopefully that i'm going to resolve this. Does anyone know how to get previous versions of Emby server? I guess I'll just go back a version or two for now until someone can take a look at this.

[denz 501]

Can you turn off hardware acceleration and see does it happen.

 

Any reason why is emby theatre not direct playing  ?

 

I compared it with my logs and my emby server ip is 192.168.1.2 and in your logs it is 127.0.0.1 but your clients are 192.168.0. 

Edited August 7, 2019 by denz

[bshaf 4]

Hey denz,

Just tried to turn hardware acceleration off and no change.

 

Yeah... i'm not sure why its not direct playing, but I just checked and my Shield its direct streaming just fine and still causes the issue. 

 

My server has a static IP that is 192.168.0.... which i see in the embyserver logs... where do you see 127.0.0.1?

 

Thanks for trying to help!

Edited August 7, 2019 by bshaf

[denz 501]

For emby theatre once the video starts click on the osd click cog and select stats for nerds to see why is it transcoding.

 

I was sure it said 127. I must have one of my logs opened accidentally bit weird.

 

If even with hardware acceleration disabled not working @@Luke will need to assist. There must be something particular with that channel what about if you record from that channel and try to play is there a same issue

[Luke 42078]

Can you try the downloaded version of emby theater from our website, rather than the store app? Thanks.

[bshaf 4]

Thanks @@Luke that fixed direct streaming with Emby Theater. But that version will still cause the server to crash when tuned to cable channels. And to be clear, its not just one or two specific channels... it appears to be all channels except local channels... for whatever reason.

 

@@Luke - any thoughts on the server crashing issue? I think it has to be something with the latest version of Emby Server becuase its been solid for like 2 years and I didn't change anything (at least intentionally). 

[Luke 42078]

Does windows event viewer have any entries about it?

[bshaf 4]

I think so... I ran the failure scenario a couple times and i think this event correlates with respect to timing... Thoughts? Does this mean anything to you?

[bshaf 4]

I was reading more about that error and most of the recommendations were to run a windows repair.... so i just completed that. I was hopeing that would fix my problem but no. Still happens. This is very frustrating...

[bshaf 4]

I'm starting to get less confident that my issue is due to a bad setting or some weird setup. I've had solid TV for such a long time i'm pretty sure it has to do with the latest update. That was the only thing i can tell that changed. Is there a way i can install the prior version? I need to get my TV working again.

[Luke 42078]

Are you sure that's all from windows event viewer?

[bshaf 4]

Yeah. I'm not the best at the event viewer, but this is what I did.

 

- rebooted server to ensure i had a clean start

- went into event viewer and saw 0 errors in the last hour.

- opened an Emby client and tuned to one of the cable channels

- saw the issue propagate and saw the CPU usage jump and the memory usage for emby server climb to over 5GB and saw the client session stop streaming. I waited about 2 additional minutes in that state.

- I stoped the emby server in task manager

- Opened event view and still saw 0 errors in the 'last hour' column. 

[bshaf 4]

I ran the failure scenario again, but this time i enabled debug logging hoping that might provide more insight. It's weird... sometimes it issue occurs after tuning to the channel for 5-10 seconds... and other times it takes ~3-5 minutes. I wonder if it has to do with corrupt fames or something. Anyway, let me know if these logs help at all, or if anyone has any other suggestions to try. Thanks again. 

 

In the scenario tied to the logs i tuned to channel 600 and it failed withing about 3 mins.

embyserver.txt

hardware_detection-63701025508.txt

hardware_detection-63701025506.txt

ffmpeg-directstream-a081b830-d643-40d6-af4a-94856a80757e_1.txt

Edited August 10, 2019 by bshaf

[bshaf 4]

Ok. Now i'm 100% confident that its the software. I just did a complete clean install of windows 10 and did a fresh install of Emby server... and sure enough the issue still happens.

 

@@Luke Is there a way i can install an older version till this gets resolved? I need to do something here so i can watch TV again. This is painful.

Edited August 11, 2019 by bshaf

[bshaf 4]

Ok.. out of pure desperation i've starting to poke around at the log files and found a couple things of interest.

 

First, @@denz is right! There is a call for a SocketException to a 127 IP address. Any ideas how this could be? My server and all my clients are 192....

 

The other thing that's interesting is "MediaEncoder: ProcessRun 'ffprobe' Execute:" that also points to a 127 IP address and it ends with "MediaEncoder: ProcessRun 'ffprobe' Process exited with code 0"

 

This stuff seemed weird. Let me know if anyone has ideas?

 

 

 

2019-08-11 09:28:29.075 Info HttpServer: HTTP Response 204 to 192.168.0.113. Time: 15ms. http://192.168.0.91:8096/emby/Sessions/Playing/Progress
2019-08-11 09:28:29.078 Info MediaEncoder: ProcessRun 'ffprobe' Execute: C:\Users\shafl\AppData\Roaming\Emby-Server\system\ffprobe.exe -analyzeduration 3000000 -i "http://127.0.0.1:8096/LiveTv/LiveStreamFiles/19336193fb014cac8a818a258b1218c1/stream.ts"-threads 0 -v info -print_format json -show_streams -show_format -show_data
2019-08-11 09:28:29.247 Info MediaEncoder: ProcessRun 'ffprobe' Started.
2019-08-11 09:28:29.347 Info HttpServer: HTTP GET http://127.0.0.1:8096/LiveTv/LiveStreamFiles/19336193fb014cac8a818a258b1218c1/stream.ts. UserAgent: Lavf/58.12.100
2019-08-11 09:28:30.351 Info MediaEncoder: ProcessRun 'ffprobe' Process exited with code 0
2019-08-11 09:28:30.394 Info HttpServer: HTTP Response 200 to 192.168.0.113. Time: 1333ms. http://192.168.0.91:8096/emby/LiveStreams/MediaInfo
2019-08-11 09:28:30.403 Info HttpServer: HTTP GET http://192.168.0.91:8096/emby/Users/c48bbb2a593343089cc810ccdb2f28b5/Items/26044. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.8 Chrome/73.0.3683.119 Electron/5.0.0 Safari/537.36
2019-08-11 09:28:30.404 Info HttpServer: HTTP Response 200 to 192.168.0.113. Time: 1ms. http://192.168.0.91:8096/emby/Users/c48bbb2a593343089cc810ccdb2f28b5/Items/26044
2019-08-11 09:28:30.456 Info HttpServer: SocketException: http://127.0.0.1:8096/LiveTv/LiveStreamFiles/19336193fb014cac8a818a258b1218c1/stream.ts
2019-08-11 09:28:30.458 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 1112ms. http://127.0.0.1:8096/LiveTv/LiveStreamFiles/19336193fb014cac8a818a258b1218c1/stream.ts
2019-08-11 09:28:39.242 Info HttpServer: HTTP POST http://192.168.0.91:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.8 Chrome/73.0.3683.119 Electron/5.0.0 Safari/537.36
2019-08-11 09:28:39.244 Info HttpServer: HTTP Response 204 to 192.168.0.113. Time: 2ms. http://192.168.0.91:8096/emby/Sessions/Playing/Progress
2019-08-11 09:28:49.243 Info HttpServer: HTTP POST http://192.168.0.91:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.8 Chrome/73.0.3683.119 Electron/5.0.0 Safari/537.36
2019-08-11 09:28:49.244 Info HttpServer: HTTP Response 204 to 192.168.0.113. Time: 1ms. http://192.168.0.91:8096/emby/Sessions/Playing/Progress
2019-08-11 09:28:59.492 Info HttpServer: HTTP POST http://192.168.0.91:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.8 Chrome/73.0.3683.119 Electron/5.0.0 Safari/537.36
2019-08-11 09:28:59.493 Info HttpServer: HTTP Response 204 to 192.168.0.113. Time: 1ms. http://192.168.0.91:8096/emby/Sessions/Playing/Progress
2019-08-11 09:29:09.765 Info HttpServer: HTTP POST http://192.168.0.91:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.8 Chrome/73.0.3683.119 Electron/5.0.0 Safari/537.36
2019-08-11 09:29:09.766 Info HttpServer: HTTP Response 204 to 192.168.0.113. Time: 1ms. http://192.168.0.91:8096/emby/Sessions/Playing/Progress
2019-08-11 09:29:14.746 Info HttpServer: HTTP POST http://192.168.0.91:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.8 Chrome/73.0.3683.119 Electron/5.0.0 Safari/537.36
2019-08-11 09:29:14.748 Info HttpServer: HTTP Response 204 to 192.168.0.113. Time: 1ms. http://192.168.0.91:8096/emby/Sessions/Playing/Progress

[Happy2Play 9780]

Since localhost and 127.0.0.1 are one in the same I can only assume it has something to do with your livetv configuration. As all the 127.0.0.1 entries point to "h t t p://127.0.0.1:8096/LiveTv/LiveStreamFiles/19336193fb014cac8a818a258b1218c1/stream.ts" livetv stream files.

[Luke 42078]

Ok.. out of pure desperation i've starting to poke around at the log files and found a couple things of interest.

 

First, @@denz is right! There is a call for a SocketException to a 127 IP address. Any ideas how this could be? My server and all my clients are 192....

 

The other thing that's interesting is "MediaEncoder: ProcessRun 'ffprobe' Execute:" that also points to a 127 IP address and it ends with "MediaEncoder: ProcessRun 'ffprobe' Process exited with code 0"

 

This stuff seemed weird. Let me know if anyone has ideas?

 

 

 

2019-08-11 09:28:29.075 Info HttpServer: HTTP Response 204 to 192.168.0.113. Time: 15ms. http://192.168.0.91:8096/emby/Sessions/Playing/Progress

2019-08-11 09:28:29.078 Info MediaEncoder: ProcessRun 'ffprobe' Execute: C:\Users\shafl\AppData\Roaming\Emby-Server\system\ffprobe.exe -analyzeduration 3000000 -i "http://127.0.0.1:8096/LiveTv/LiveStreamFiles/19336193fb014cac8a818a258b1218c1/stream.ts"-threads 0 -v info -print_format json -show_streams -show_format -show_data

2019-08-11 09:28:29.247 Info MediaEncoder: ProcessRun 'ffprobe' Started.

2019-08-11 09:28:29.347 Info HttpServer: HTTP GET http://127.0.0.1:8096/LiveTv/LiveStreamFiles/19336193fb014cac8a818a258b1218c1/stream.ts. UserAgent: Lavf/58.12.100

2019-08-11 09:28:30.351 Info MediaEncoder: ProcessRun 'ffprobe' Process exited with code 0

2019-08-11 09:28:30.394 Info HttpServer: HTTP Response 200 to 192.168.0.113. Time: 1333ms. http://192.168.0.91:8096/emby/LiveStreams/MediaInfo

2019-08-11 09:28:30.403 Info HttpServer: HTTP GET http://192.168.0.91:8096/emby/Users/c48bbb2a593343089cc810ccdb2f28b5/Items/26044. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.8 Chrome/73.0.3683.119 Electron/5.0.0 Safari/537.36

2019-08-11 09:28:30.404 Info HttpServer: HTTP Response 200 to 192.168.0.113. Time: 1ms. http://192.168.0.91:8096/emby/Users/c48bbb2a593343089cc810ccdb2f28b5/Items/26044

2019-08-11 09:28:30.456 Info HttpServer: SocketException: http://127.0.0.1:8096/LiveTv/LiveStreamFiles/19336193fb014cac8a818a258b1218c1/stream.ts

2019-08-11 09:28:30.458 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 1112ms. http://127.0.0.1:8096/LiveTv/LiveStreamFiles/19336193fb014cac8a818a258b1218c1/stream.ts

2019-08-11 09:28:39.242 Info HttpServer: HTTP POST http://192.168.0.91:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.8 Chrome/73.0.3683.119 Electron/5.0.0 Safari/537.36

2019-08-11 09:28:39.244 Info HttpServer: HTTP Response 204 to 192.168.0.113. Time: 2ms. http://192.168.0.91:8096/emby/Sessions/Playing/Progress

2019-08-11 09:28:49.243 Info HttpServer: HTTP POST http://192.168.0.91:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.8 Chrome/73.0.3683.119 Electron/5.0.0 Safari/537.36

2019-08-11 09:28:49.244 Info HttpServer: HTTP Response 204 to 192.168.0.113. Time: 1ms. http://192.168.0.91:8096/emby/Sessions/Playing/Progress

2019-08-11 09:28:59.492 Info HttpServer: HTTP POST http://192.168.0.91:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.8 Chrome/73.0.3683.119 Electron/5.0.0 Safari/537.36

2019-08-11 09:28:59.493 Info HttpServer: HTTP Response 204 to 192.168.0.113. Time: 1ms. http://192.168.0.91:8096/emby/Sessions/Playing/Progress

2019-08-11 09:29:09.765 Info HttpServer: HTTP POST http://192.168.0.91:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.8 Chrome/73.0.3683.119 Electron/5.0.0 Safari/537.36

2019-08-11 09:29:09.766 Info HttpServer: HTTP Response 204 to 192.168.0.113. Time: 1ms. http://192.168.0.91:8096/emby/Sessions/Playing/Progress

2019-08-11 09:29:14.746 Info HttpServer: HTTP POST http://192.168.0.91:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.8 Chrome/73.0.3683.119 Electron/5.0.0 Safari/537.36

2019-08-11 09:29:14.748 Info HttpServer: HTTP Response 204 to 192.168.0.113. Time: 1ms. http://192.168.0.91:8096/emby/Sessions/Playing/Progress

The server sometimes sends internal requests to itself over 127.0.0.1. that's nothing to worry about.

[bshaf 4]

Thanks @@Luke for the info. Any idea what's causing my server to crash then?

[bshaf 4]

@@Luke - is there something else i can provide to help debug this issue?

[bshaf 4]

Alright... i'm about on week 3 with Emby crashing whenever i try and watch TV... this is getting very frustrating and i may need to start looking for another solution. I keep attempting to look for things in the log that may be a clue as to what is going on (but i'm just not technical enough to understand what is going on).

 

My logs do contain a couple entries of this error report. Looking at the timestamps it appears this error gets logged when I start emby server and not when the server crashes after trying to watch TV. Does anyone have any idea???

 

 

 

2019-08-15 18:57:01.784 Info HttpServer: HTTP Response 404 to 192.168.0.103. Time: 1ms. http://192.168.0.91:8096/emby/Items/b8e706f866b4ee5b4ccfe7985c27f31d/Images/Primary?Accept=webp&PercentPlayed=24&EnableImageEnhancers=true&MaxHeight=300&Tag=0c4fdfd11cb6933606e7f2330bd0ab61
2019-08-15 18:57:01.788 Info HttpServer: HTTP GET http://192.168.0.91:8096/emby/Items/0e4efc536c6094f59384ea71e5d155dd/Images/Primary?Accept=webp&PercentPlayed=58&EnableImageEnhancers=true&MaxHeight=300&Tag=f46154081adc67b914e114e6357d8b18. UserAgent: Dalvik/2.1.0 (Linux; U; Android 9; SHIELD Android TV Build/PPR1.180610.011)
2019-08-15 18:57:01.789 Error HttpServer: Error processing request
 *** Error Report ***
 Version: 4.2.1.0
 Command line: C:\Users\shafl\AppData\Roaming\Emby-Server\system\EmbyServer.dll
 Operating system: Microsoft Windows NT 6.2.9200.0
 64-Bit OS: True
 64-Bit Process: True
 User Interactive: True
 Runtime: file:///C:/Users/shafl/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll
 Processor count: 4
 Program data path: C:\Users\shafl\AppData\Roaming\Emby-Server\programdata
 Application directory: C:\Users\shafl\AppData\Roaming\Emby-Server\system
 MediaBrowser.Common.Extensions.ResourceNotFoundException: MediaBrowser.Common.Extensions.ResourceNotFoundException: 0 does not have an image of type Primary
    at MediaBrowser.Api.Images.ImageService.GetImage(ImageRequest request, Int64 itemId, BaseItem item, Boolean isHeadRequest)
    at Emby.Server.Implementations.Services.ServiceController.GetTaskResult(Task task)
    at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost appHost, IRequest httpReq, IResponse httpRes, RestPath restPath, String responseContentType, CancellationToken cancellationToken)
    at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IRequest httpReq, ReadOnlyMemory`1 urlString, ReadOnlyMemory`1 host, ReadOnlyMemory`1 localPath, CancellationToken cancellationToken)
 Source: MediaBrowser.Api
 TargetSite: Void MoveNext()

[bshaf 4]

@@Luke - its starting to sound like you are the only one that will be able to help me. Please help.

 

To be honest, i'm surprised no one else is having this issue. I don't feel like i'm using Emby in a unique way.

[ebr 16177]

@@softworkz do we have an idea what is going on here?

 

bshaf - the error you posted above is unrelated and not a problem.

[bshaf 4]

Thanks @@ebr and @@softworkz for taking a look.

 

Here are a fresh set of logs with debugging enabled.

 

 

- @ 9:56 I streamed a channel that works fine (channel 505)

- @ 10:00 I streamed a channel that crashes the server (channel 570 ESPN)

 

embyserver-63701633163.txt

ffmpeg-directstream-21aae040-38ad-43f5-a432-c4546ad4ae80_1.txt

hardware_detection-63701632517.txt