Jump to content

Playback is crashing after update.

Zabell

By Zabell
in Linux

 Share
Go to solution Solved by dbt816,

Recommended Posts

Zabell

Zabell   0

Posted
Posted

Hello,

 

I recently updated my Emby server to version 3.0.5911.

Now when i play any kind of video, the playback crashes after a random interval of time (around 1 minute of playback).

 

Video Error

There was an error playing the video.

I have not been successful in locating this error in any log on my Linux server, even with debugging toggled on.

/ Zabell

Link to comment
Share on other sites
thefirstofthe300

thefirstofthe300   291

Posted
Posted (edited)

I have the exact same error.  I think it has something to do client side as it is affecting all clients, browser and Android, yet FFMpeg isn't failing, just quitting.  Android complains about a problem with hardware decoding.  FFmpeg version is 3.0.

 

Server log: https://owncloud.danielseymour.info/index.php/s/kCN9aULGVJiJpH4

ffmpeg log: https://owncloud.danielseymour.info/index.php/s/uNBnl686dNL7RRv

Edited by thefirstofthe300
Link to comment
Share on other sites
Zabell

Zabell   0

Posted
  • Author
Posted

Here is last 25 lines after my playback stopped.

2016-04-01 09:37:36.1896 Info HttpServer: HTTP GET http://zevo.dk:8096/emby/Items/194476f5609be84b863f9af785c68a0f/Images/primary?height=300&tag=8bd4e8a00b6ed9aedb3ebc4edccfa49b&quality=90&accept=webp. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36
2016-04-01 09:37:36.1914 Info HttpServer: HTTP Response 200 to 94.18.241.196. Time: 2ms. http://zevo.dk:8096/emby/Items/194476f5609be84b863f9af785c68a0f/Images/primary?height=300&tag=8bd4e8a00b6ed9aedb3ebc4edccfa49b&quality=90&accept=webp
2016-04-01 09:37:36.3069 Info HttpServer: HTTP GET http://zevo.dk:8096/emby/Videos/4d8bfcec7abc5252e5ef97339b677c31/stream.mp4?Static=true&mediaSourceId=4d8bfcec7abc5252e5ef97339b677c31&deviceId=7da2bdb5e99b18087322d5a2e750034aebc08624. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36
2016-04-01 09:37:36.8870 Info HttpServer: HTTP GET http://zevo.dk:8096/emby/Videos/4d8bfcec7abc5252e5ef97339b677c31/stream.mp4?Static=true&mediaSourceId=4d8bfcec7abc5252e5ef97339b677c31&deviceId=7da2bdb5e99b18087322d5a2e750034aebc08624. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36
2016-04-01 09:37:36.8896 Info HttpServer: HTTP Response 206 to 94.18.241.196. Time: 3ms. http://zevo.dk:8096/emby/Videos/4d8bfcec7abc5252e5ef97339b677c31/stream.mp4?Static=true&mediaSourceId=4d8bfcec7abc5252e5ef97339b677c31&deviceId=7da2bdb5e99b18087322d5a2e750034aebc08624
2016-04-01 09:37:36.9397 Info HttpServer: HTTP GET http://zevo.dk:8096/emby/Videos/4d8bfcec7abc5252e5ef97339b677c31/stream.mp4?Static=true&mediaSourceId=4d8bfcec7abc5252e5ef97339b677c31&deviceId=7da2bdb5e99b18087322d5a2e750034aebc08624. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36
2016-04-01 09:37:36.9442 Info HttpServer: HTTP Response 304 to 94.18.241.196. Time: 5ms. http://zevo.dk:8096/emby/Videos/4d8bfcec7abc5252e5ef97339b677c31/stream.mp4?Static=true&mediaSourceId=4d8bfcec7abc5252e5ef97339b677c31&deviceId=7da2bdb5e99b18087322d5a2e750034aebc08624
2016-04-01 09:37:36.9581 Info HttpServer: HTTP GET http://zevo.dk:8096/emby/Videos/4d8bfcec7abc5252e5ef97339b677c31/stream.mp4?Static=true&mediaSourceId=4d8bfcec7abc5252e5ef97339b677c31&deviceId=7da2bdb5e99b18087322d5a2e750034aebc08624. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36
2016-04-01 09:37:37.0048 Info HttpServer: HTTP POST http://zevo.dk:8096/emby/Sessions/Playing. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36
2016-04-01 09:37:37.0598 Info HttpServer: HTTP Response 204 to 94.18.241.196. Time: 55ms. http://zevo.dk:8096/emby/Sessions/Playing
2016-04-01 09:38:28.5327 Info HttpServer: HTTP POST http://zevo.dk:8096/emby/Sessions/Playing/Stopped. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36
2016-04-01 09:38:28.5421 Debug App: ReportPlaybackStopped PlaySessionId: 
2016-04-01 09:38:28.5600 Info HttpServer: HTTP Response 204 to 94.18.241.196. Time: 27ms. http://zevo.dk:8096/emby/Sessions/Playing/Stopped
2016-04-01 09:38:32.3520 Debug HttpServer: Exiting HttpConnection.OnReadInternal because nread=0. ConnectionId: 28c09bdd614a4da78a89cd60fd2bd7c1
2016-04-01 09:38:32.3520 Info HttpServer: HTTP Response 500 to 94.18.241.196. Time: 56045ms (slow). http://zevo.dk:8096/emby/Videos/4d8bfcec7abc5252e5ef97339b677c31/stream.mp4?Static=true&mediaSourceId=4d8bfcec7abc5252e5ef97339b677c31&deviceId=7da2bdb5e99b18087322d5a2e750034aebc08624
2016-04-01 09:38:43.2175 Debug SessionManager: Disposing session controller WebSocketController
2016-04-01 09:38:43.3143 Debug HttpServer: Exiting HttpConnection.OnReadInternal because nread=0. ConnectionId: 11bb175be01d4755abd70f49bf7c71df
2016-04-01 09:38:43.3143 Debug HttpServer: Exiting HttpConnection.OnReadInternal because nread=0. ConnectionId: 4912e75d8bcb473dac299556d4a3ce95
2016-04-01 09:38:43.3143 Debug HttpServer: Exiting HttpConnection.OnReadInternal because nread=0. ConnectionId: c3ceb69125534f748b1fecdd0beb9fd4
2016-04-01 09:38:43.3143 Debug HttpServer: Exiting HttpConnection.OnReadInternal because nread=0. ConnectionId: ad140bf12c0a4b5e8784ad045f561439
2016-04-01 09:38:43.3143 Debug HttpServer: Exiting HttpConnection.OnReadInternal because nread=0. ConnectionId: 2b2168e54df04c1fa9aee5791c8efcac
2016-04-01 09:38:43.3143 Debug HttpServer: Exiting HttpConnection.OnReadInternal because nread=0. ConnectionId: 9e70d91ab7704b07980aa29d9a2dd84c
2016-04-01 09:39:24.8322 Debug HttpServer: Exiting HttpConnection.OnReadInternal because nread=0. ConnectionId: 637e980409004d96aa17a6d3900d1c52
2016-04-01 09:39:24.8322 Info HttpServer: HTTP Response 500 to 94.18.241.196. Time: 107874ms (slow). http://zevo.dk:8096/emby/Videos/4d8bfcec7abc5252e5ef97339b677c31/stream.mp4?Static=true&mediaSourceId=4d8bfcec7abc5252e5ef97339b677c31&deviceId=7da2bdb5e99b18087322d5a2e750034aebc08624
2016-04-01 09:39:38.0133 Debug HttpServer: Exiting HttpConnection.OnReadInternal because nread=0. ConnectionId: 2914a053e8414a26b37bd2b3f1202128
Link to comment
Share on other sites
slaecker

slaecker   0

Posted
Posted

Same issue here on Arch Linux when playing different movies and tv episodes via Web Interface on LAN or Android app to Chromecast.

 

Via web interface the video first gets played normally but after some time (somewhere around 10-30 seconds, depends on the source video) the error message is shown:

5700fc7cd7c6a_embyplaybackerror20160403.

It's German for "Video error. There was a problem with video playback."

 

Via Android/Chromecast after the same playback times the picture gets black and that's it. Pause and Play doesn't do anything. When jumping on the timeline the video plays for some seconds and crashes again.

 

Arch Linux is fully updated (Emby 3.0.5911 / ffmpeg 3.0).

After receiving the error message on several movies and tv episodes I tried downgrading emby to the most recent version I had installed before: 3.0.5882. As the error still occured I downgraded ffmpeg from 3.0 to 2.8.6 but the issue remains.

 

Server Log:

https://dl.dropboxusercontent.com/u/257805/emby-logs/server-63595288286.txt

 

Transcode Logs:

https://dl.dropboxusercontent.com/u/257805/emby-logs/transcode-21e60a1c-9acb-44d2-9d61-f7dbad343739.txt

https://dl.dropboxusercontent.com/u/257805/emby-logs/transcode-34b38a7c-bdf4-4dc6-9421-c7058e3a50e6.txt

https://dl.dropboxusercontent.com/u/257805/emby-logs/transcode-befda62a-5b44-4ea9-99d3-17099e70d3db.txt

 

Goodbye evening entertainment  <_<

Link to comment
Share on other sites
mostlyharmless

mostlyharmless   0

Posted
Posted

Recently started seeing the same issue. So far it looks limited to Chrome and the Android clients. If I use Safari, the iOS client, or the new tvOS client everything works fine.

 

Server Log:

http://hastebin.com/hodizumete.coffee

 

The HTTP 500 response seems to come right before the "Video Error" modal but I'm not sure.

Link to comment
Share on other sites
Zabell

Zabell   0

Posted
  • Author
Posted

Just updated my server to Emby 3.0.5912 and tested on three devices.

 

Chrome: Playback error

Nexus 5X android: HW acceleration error

Android TV: Unable to play

Link to comment
Share on other sites
slaecker

slaecker   0

Posted
Posted

I also checked on 3.0.5912 and the issue is still there. I can confirm that it works for non Chrome/Android devices, in my case everything is fine streaming via a PS3 (but the old WiFi chip causes lag so it's not fun to watch there). Hope you guys will fix this issue sooner than later.

Link to comment
Share on other sites
derfbn

derfbn   0

Posted
Posted (edited)

same issue here.

cannot playback via webbrowser, fails after 1-2minutes. "Unable to write data to the transport connection: The socket has been shut down."

 

I am running up-to-date arch.

chromium(49.0.2623.110) fails

chrome-dev(51.0.2693.2 dev) fails

firefox(45.0.1) fails 

 

i opened chromium development tools, following error occurs:

:8096/emby/videos/d537d7ce53cd918a97a26963630dd250/stream.mkv?DeviceId=f5ce…c40b6336bd9&api_key=bacc72516e044fe98e0ccca25296f6a3&CopyTimestamps=true:1 GET http://192.168.1.100:8096/emby/videos/d537d7ce53cd918a97a26963630dd250/stre…3cc40b6336bd9&api_key=bacc72516e044fe98e0ccca25296f6a3&CopyTimestamps=truenet::ERR_INVALID_CHUNKED_ENCODING

 

server.log http://hastebin.com/udazegeyib.avrasm

 

I tested on my android too, fails on chrome and firefox.

Edited by derfbn
Link to comment
Share on other sites
Luke Emby Team

Luke   37022

Posted
Posted

you may want to try different versions of the mono runtime just in case there's an issue there.

Link to comment
Share on other sites
  • Solution
dbt816

dbt816   2

Posted
  • Solution
Posted

you may want to try different versions of the mono runtime just in case there's an issue there.

 

On Arch Linux, the recent upgrade from mono 4.2 to 4.4 breaks playback. Emby 3.0.5912 runs fine on 4.2

  • Like 2
Link to comment
Share on other sites
thefirstofthe300

thefirstofthe300   291

Posted
Posted

And I can confirm that Emby is back to streaming flawlessly on LAN with Mono 4.2.

 

Sent from my Nexus 5X using Tapatalk

Link to comment
Share on other sites
Zabell

Zabell   0

Posted
  • Author
Posted

FYI, i have now tried three releases of mono 4.2.2.x and i still cannot play any videos on my arch linux server.

Link to comment
Share on other sites
slaecker

slaecker   0

Posted
Posted

FYI, i have now tried three releases of mono 4.2.2.x and i still cannot play any videos on my arch linux server.

For me downgrading to mono-4.2.2.30-2-x86_64 did the trick (the rest of the system is fully updated). Don't forget to restart emby-server.service after the downgrade.

Link to comment
Share on other sites
alucryd

alucryd   214

Posted
Posted

I can confirm downgrading to 4.2 fixes the playback issues. I was kinda getting desperate here, thx guys!

Link to comment
Share on other sites
  • 2 weeks later...
ElJef

ElJef   0

Posted
Posted

Running with mono 4.4, I ran into this issue on my FireTV devices. Shows would play for about 30 seconds, then recycle to the beginning, restarting the episode. Downgrading to 4.2 does make the issue go away.

I was able to catch the error at the time of recycle.
http://pastebin.com/mJJc9S6q

 

This same error appears with every 30 second recycle / restart.

Link to comment
Share on other sites
Luke Emby Team

Luke   37022

Posted
Posted

Running with mono 4.4, I ran into this issue on my FireTV devices. Shows would play for about 30 seconds, then recycle to the beginning, restarting the episode. Downgrading to 4.2 does make the issue go away.

 

I was able to catch the error at the time of recycle.

http://pastebin.com/mJJc9S6q

 

This same error appears with every 30 second recycle / restart.

 

4.4 is pre-release, you should remain on 4.2 until it's more stable. Thanks.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • Create New...