Jump to content

Server Crash


Go to solution Solved by Luke,

Recommended Posts

Animosity022
Posted

Looks like I had a crash while is was doing something with a backdrop?

 

 

 

2017-04-02 18:58:39.6812 Info HttpServer: HTTP Response 200 to 192.168.86.200. Time: 99ms. http://192.168.86.30:8096/emby/Items/a39e480f82b6a79ae281f453900b4beb/Images/Primary?maxHeight=720&tag=1ddea74ba2dc6b1acd21740896ba0c36&quality=90

2017-04-02 18:58:39.7032 Error HttpServer: Error processing request
        *** Error Report ***
        Version: 3.2.10.0
        Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -ffmpeg /usr/bin/ffmpeg -ffprobe /usr/bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh
        Operating system: Unix 3.16.0.4
        64-Bit OS: True
        64-Bit Process: True
        Mono: 4.8.0 (Stable 4.8.0.520/8f6d0f6 Wed Mar 15 16:18:35 UTC 2017)
        Processor count: 8
        Program data path: /var/lib/emby-server
        Application directory: /usr/lib/emby-server/bin
        System.IO.IOException: Sharing violation on path /var/lib/emby-server/metadata/library/a3/a39e480f82b6a79ae281f453900b4beb/backdrop.jpg
          at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32 bufferSize, System.Boolean anonymous, System.IO.FileOptions options) [0x0025f] in <f712f98eb8e445c8918edaf595bbe465>:0
          at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32 bufferSize, System.IO.FileOptions options) [0x00000] in <f712f98eb8e445c8918edaf595bbe465>:0
          at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32 bufferSize, System.Boolean useAsync) [0x00000] in <f712f98eb8e445c8918edaf595bbe465>:0
          at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare,int,bool)
          at Emby.Common.Implementations.IO.ManagedFileSystem.GetFileStream (System.String path, MediaBrowser.Model.IO.FileOpenMode mode, MediaBrowser.Model.IO.FileAccessMode access, MediaBrowser.Model.IO.FileShareMode share, System.Boolean isAsync) [0x00022] in <c581a2e329524a4aac600dd76c20d524>:0
          at MediaBrowser.Providers.Manager.ImageSaver+<SaveImageToLocation>c__async2.MoveNext () [0x00196] in <717a5ec297804ac49588744a781e7d98>:0
        --- End of stack trace from previous location where exception was thrown ---
:

 

 

Is there more info that is needed? 

Posted

Thanks, we'll take a look at it.

Animosity022
Posted

I got closer to figure out a use case for making the issue happen.

 

Basically when I had the crashes occur, I was using the reports and searching for missing metadata/corrupt items I had in my library based on their runtime.

 

I was able get a crash to occur once and the error to log this morning by going:

 

Top Menu -> Reports -> List Episodes. Sort by runtime.

 

Find some episodes that haven't aired yet.

 

Click on that episode's name on the left.

 

That gives me a sharing error and sometimes it just crashes.

 

Here are the 2 logs. One crash. One threw an error but stayed p.

 

 

server-63626947200.txt

server-63626977698.txt

Posted

Thanks for the info. We'll take a look.

  • 1 month later...
linds1234
Posted

Thanks @@Luke

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
×
×
  • Create New...