Jump to content

Search the Community

Showing results for tags 'forced to restart'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • Non-Emby General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support


  • Emby Blog

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 1 result

  1. Hi, When I noticed 5870 was released, I installed that one (was running the previous 5868 version). I'd read about the database upgrade process on the blog, so I gave it over 10 minutes to do its thing after the initial start. After the CPU usage had gone down to mere <3% I browsed to the settings page. I noticed there was another new update (5871), so I upgraded to that one as well. First thing I noticed when logging on (could have been the same in 70, didn't care to check), is that the collections icon had changed to a default 'play' image. Second thing is that the (home) page loaded extremely slowly, and the thumbnails for the series came through pretty slowly. If I click on a series (or any place with a lot of thumbnails) the images come in slowly, and some don't show up at all. If I open up the episode where the thumbnail is missing the file itself also refuses to play. If I go to an episode with thumbnail, they also refuse to play. Same with any movie. In fact, after clicking to 'play' any media, just a waiting circle appears, and it never goes away, even when navigating to another page. If you click "server options" the overview page looks all weird. I'm forced to close the tab, and open a new one. Looking for another file to play will display the circle again, but this time the details page will be blank and you're unable to do anything: Even the sidebar looks odd. When you close this tab, and try to browse to Emby again, the page will just keep on loading ("waiting for available socket"). And then I'm forced to stop the server... Theme music does stil play automatically when navigating to a series where it's available. If I restart the server I will be able to play an episode or 2. Or a movie. But the moment I had one, and try another it'll time out and get unresponsive again. Forcing a restart. I've tried Chrome, Edge, and the iOS app. Nothing particular in the logfiles except for the occasional socketexception: *** Error Report *** Version: 3.0.5871.0 Command line: /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server Operating system: Unix Processor count: 8 64-Bit OS: True 64-Bit Process: True Program data path: /var/db/emby-server Mono: 4.2.2 (Stable Sat Jan 16 12:57:01 UTC 2016) Application Path: /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe Write failure System.IO.IOException at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) <0x815b8ede0 + 0x0013c> in <filename unknown>:0 at SocketHttpListener.Net.ResponseStream.InternalWrite (System.Byte[] buffer, Int32 offset, Int32 count) <0x815b8ed30 + 0x0009a> in <filename unknown>:0 at SocketHttpListener.Net.ResponseStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) <0x815b8c770 + 0x001f5> in <filename unknown>:0 at System.IO.Stream.InternalCopyTo (System.IO.Stream destination, Int32 bufferSize) <0x81aba20b0 + 0x00053> in <filename unknown>:0 at System.IO.Stream.CopyTo (System.IO.Stream destination, Int32 bufferSize) <0x81aba1e30 + 0x000b5> in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.IO.Stream:CopyTo (System.IO.Stream,int) at MediaBrowser.Server.Implementations.HttpServer.StreamWriter.WriteToInternal (System.IO.Stream responseStream) <0x81aba1b70 + 0x0005a> in <filename unknown>:0 InnerException: System.Net.Sockets.SocketException The socket has been shut down at System.Net.Sockets.Socket.Send (System.Byte[] buffer, Int32 offset, Int32 size, SocketFlags flags) <0x815b8f050 + 0x00103> in <filename unknown>:0 at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) <0x815b8ede0 + 0x000ad> in <filename unknown>:0 ... which I hadn't seen before either. But it didn't appear in the attached one. Basically, what did the upgrade to 5670/1 do, and how can I get everything back working? Is there any way to make the logfiles more verbose, because they don't seem to hold any value in this case (as far as I can see). server-63591591935.txt server-63591594436.txt
  • Create New...