Jump to content

Emby going offline after adding TV Series


Prutsium

Recommended Posts

Prutsium

Hello all,

 

I am quite new to Emby but must see cool program and wish i had discovered that long ago :).

 

Anyway i am running latest beta on an Ubuntu (Studio) installation where the media is on an nas (SMB connection)

I have a quite large collection of movies and series and when i have only the movies within Emby all works perfect without issues.

The fun starts when i add the Tv Series as it add's them starts scanning and seems to work but at the moment i go over the webinterface to the series folder Emby crashes.

Resulting in: 

● emby-server.service - Emby Server is a personal media server with apps on just about every device.
   Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Wed 2019-02-13 21:27:02 CET; 11h ago
 Main PID: 29604 (code=killed, signal=SEGV)
 
Feb 13 20:53:31 media-N61Vg emby-server[29604]: Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint
Feb 13 20:53:31 media-N61Vg emby-server[29604]: Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 0.0006101 seconds
Feb 13 20:53:31 media-N61Vg emby-server[29604]: Info App: All entry points have started
Feb 13 20:53:31 media-N61Vg emby-server[29604]: Application started. Press Ctrl+C to shut down.
Feb 13 20:53:31 media-N61Vg emby-server[29604]: Hosting environment: Production
Feb 13 20:53:31 media-N61Vg emby-server[29604]: Content root path: /opt/emby-server/system/
Feb 13 20:53:58 media-N61Vg emby-server[29604]: Workgroup Name = fritsie/
Feb 13 20:53:58 media-N61Vg emby-server[29604]: Workgroup Name = workgroup/
Feb 13 21:27:02 media-N61Vg systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Feb 13 21:27:02 media-N61Vg systemd[1]: emby-server.service: Failed with result 'signal'.
 
The last bit in the log files (but doesnt show really an error i believe)
2019-02-14 09:08:32.311 Info HttpResultFactory: Setting range response values for smb://nas2/Video/Series/The 100/Season 4/The.100.S04E09.WEB-DL.x264-FUM[ettv]/The.100.S04E09.WEB-DL.x264-FUM[ettv].mp4. RangeRequest: bytes=0- Content-Length: 319096714, Content-Range: bytes 0-319096713/319096714

2019-02-14 09:08:32.311 Debug HttpResultFactory: Transmit file smb://nas2/Video/Series/The 100/Season 4/The.100.S04E09.WEB-DL.x264-FUM[ettv]/The.100.S04E09.WEB-DL.x264-FUM[ettv].mp4

2019-02-14 09:08:32.405 Info HttpServer: HTTP GET http://127.0.0.1:8096/Items/File?Id=smb%3A%2F%2Fnas2%2FVideo%2FSeries%2FThe+100%2FSeason+4%2FThe.100.S04E09.WEB-DL.x264-FUM%5Bettv%5D%2FThe.100.S04E09.WEB-DL.x264-FUM%5Bettv%5D.mp4. UserAgent: Lavf/58.12.100

2019-02-14 09:08:33.318 Info HttpResultFactory: Setting range response values for smb://nas2/Video/Series/The 100/Season 4/The.100.S04E09.WEB-DL.x264-FUM[ettv]/The.100.S04E09.WEB-DL.x264-FUM[ettv].mp4. RangeRequest: bytes=319096655- Content-Length: 59, Content-Range: bytes 319096655-319096713/319096714

2019-02-14 09:08:33.332 Info HttpServer: HTTP Response 206 to 127.0.0.1. Time: 928ms. http://127.0.0.1:8096/Items/File?Id=smb%3A%2F%2Fnas2%2FVideo%2FSeries%2FThe+100%2FSeason+4%2FThe.100.S04E09.WEB-DL.x264-FUM%5Bettv%5D%2FThe.100.S04E09.WEB-DL.x264-FUM%5Bettv%5D.mp4

2019-02-14 09:08:33.338 Info HttpServer: SocketException: http://127.0.0.1:8096/Items/File?Id=smb%3A%2F%2Fnas2%2FVideo%2FSeries%2FThe+100%2FSeason+4%2FThe.100.S04E09.WEB-DL.x264-FUM%5Bettv%5D%2FThe.100.S04E09.WEB-DL.x264-FUM%5Bettv%5D.mp4

2019-02-14 09:08:33.338 Info HttpServer: HTTP Response 206 to 127.0.0.1. Time: 2032ms. http://127.0.0.1:8096/Items/File?Id=smb%3A%2F%2Fnas2%2FVideo%2FSeries%2FThe+100%2FSeason+4%2FThe.100.S04E09.WEB-DL.x264-FUM%5Bettv%5D%2FThe.100.S04E09.WEB-DL.x264-FUM%5Bettv%5D.mp4

2019-02-14 09:08:33.381 Info HttpServer: HTTP GET http://127.0.0.1:8096/Items/File?Id=smb%3A%2F%2Fnas2%2FVideo%2FSeries%2FThe+100%2FSeason+4%2FThe.100.S04E09.WEB-DL.x264-FUM%5Bettv%5D%2FThe.100.S04E09.WEB-DL.x264-FUM%5Bettv%5D.mp4. UserAgent: Lavf/58.12.100

2019-02-14 09:08:33.386 Info HttpResultFactory: Setting range response values for smb://nas2/Video/Series/The 100/Season 4/The.100.S04E09.WEB-DL.x264-FUM[ettv]/The.100.S04E09.WEB-DL.x264-FUM[ettv].mp4. RangeRequest: bytes=1297645- Content-Length: 317799069, Content-Range: bytes 1297645-319096713/319096714

2019-02-14 09:08:33.414 Info HttpServer: SocketException: http://127.0.0.1:8096/Items/File?Id=smb%3A%2F%2Fnas2%2FVideo%2FSeries%2FThe+100%2FSeason+4%2FThe.100.S04E09.WEB-DL.x264-FUM%5Bettv%5D%2FThe.100.S04E09.WEB-DL.x264-FUM%5Bettv%5D.mp4

2019-02-14 09:08:33.414 Info HttpServer: HTTP Response 206 to 127.0.0.1. Time: 33ms. http://127.0.0.1:8096/Items/File?Id=smb%3A%2F%2Fnas2%2FVideo%2FSeries%2FThe+100%2FSeason+4%2FThe.100.S04E09.WEB-DL.x264-FUM%5Bettv%5D%2FThe.100.S04E09.WEB-DL.x264-FUM%5Bettv%5D.mp4

2019-02-14 09:08:33.416 Info MediaEncoder: ProcessRun 'ffprobe' Process exited with code 0

2019-02-14 09:08:33.969 Info HttpServer: HTTP GET http://192.168.98.120:8096/emby/Users/021f171218544c8dbcdce016d3288e78. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

2019-02-14 09:08:33.972 Info HttpServer: HTTP Response 200 to 192.168.98.120. Time: 3ms. http://192.168.98.120:8096/emby/Users/021f171218544c8dbcdce016d3288e78

2019-02-14 09:08:34.056 Info HttpServer: HTTP GET http://192.168.98.120:8096/emby/LiveTv/Channels?userId=021f171218544c8dbcdce016d3288e78&limit=1&ImageTypeLimit=1&EnableTotalRecordCount=false&EnableImages=false&EnableUserData=false. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

2019-02-14 09:08:34.195 Info HttpServer: HTTP GET http://192.168.98.120:8096/emby/Items/6c2a057148b4d7c20a207c789aba6d07/Images/Primary?maxHeight=135&maxWidth=240&tag=c9845b17f7bc6112617e39e8e18303a5&quality=90. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

2019-02-14 09:08:34.614 Debug App: ConvertImageToLocal item 22415 - image url: emby://collectionfoldercollage

2019-02-14 09:08:34.802 Info ImageProcessor: Creating image collage and saving to /var/lib/emby/cache/temp/372ce168b3404a92af55426f8a63314d.png

2019-02-14 09:08:34.949 Debug Skia: Opening smb://nas2/Video/Series/Battlestar Galactica Blood & Chrome/folder.jpg for decoding without forceCleanBitmap
 
Anyway i got no clue as when i remove the series folder it works.
Alternative i created an smaller series folder with just 4 series in it and same result. Also switched to different nas but same issue.
 
Thanks,
Jerome
 
Link to comment
Share on other sites

wilsonhomelab

HI Jerome,

 

I am new to Emby too. I may have a simular issue to you, but I am using Emby container in Unraid server.

 

https://r.tapatalk.com/shareLink?url=https%3A%2F%2Femby%2Emedia%2Fcommunity%2Findex%2Ephp%3F%2Ftopic%2F69954-Emby-container-stop-itself-after-browsing-movie-library&share_tid=69954&share_fid=77624&share_type=t

 

I may keep an eye on your thread.

 

Cheers,

Jason

 

Sent from Tapatalk

Link to comment
Share on other sites

Prutsium

As test i installed the 4.0.2.0 and resulted in the same.

Add some series .... try to play via browser one of them and stoppes directly.

 

Noticed one difference that the exit message is different:

 emby-server.service - Emby Server is a personal media server with apps on just about every device.
   Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Fri 2019-02-15 16:18:20 CET; 29s ago
  Process: 11012 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=SEGV)
 Main PID: 11012 (code=killed, signal=SEGV)
 
Feb 15 16:17:59 media-N61Vg emby-server[11012]: Info App: SyncRepository Initialize taking write lock
Feb 15 16:17:59 media-N61Vg emby-server[11012]: Info App: SyncRepository Initialize write lock taken
Feb 15 16:17:59 media-N61Vg emby-server[11012]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0179722 seconds
Feb 15 16:17:59 media-N61Vg emby-server[11012]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
Feb 15 16:18:00 media-N61Vg emby-server[11012]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0062719 seconds
Feb 15 16:18:00 media-N61Vg emby-server[11012]: Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint
Feb 15 16:18:00 media-N61Vg emby-server[11012]: Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 0.0008793 seconds
Feb 15 16:18:00 media-N61Vg emby-server[11012]: Info App: All entry points have started
Feb 15 16:18:20 media-N61Vg systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Feb 15 16:18:20 media-N61Vg systemd[1]: emby-server.service: Failed with result 'signal'.
Link to comment
Share on other sites

Prutsium

Small addition:

Tried a docker version > Same result

Installed latest beta > Same result

 

But i also notice that any file made by Emby like subtitles or Fanart are 0 bytes large.

The PC running emby server has full write rights as manual i can add files.

 

Still got no clue whats wrong.

Link to comment
Share on other sites

  • 2 weeks later...

Hi guys, I notice that you've set your libraries up with smb paths. As a test, can you instead try the following:

  • Mount the smb paths as a local share in the OS
  • Then add the local share path to Emby instead of the smb path

I think this issue is isolated to the SMB protocol. Please let me know how that compares. Thanks.

Link to comment
Share on other sites

Prutsium

Hi guys, I notice that you've set your libraries up with smb paths. As a test, can you instead try the following:

  • Mount the smb paths as a local share in the OS
  • Then add the local share path to Emby instead of the smb path

I think this issue is isolated to the SMB protocol. Please let me know how that compares. Thanks.

 

Hello Luke,

 

Can confirm after adding the shares to the OS instead of via Emby it's stable and Emby keeps running.

Link to comment
Share on other sites

Thanks for the feedback. It will take us a little while to get there, but ultimately this is going to become the preferred method to handle SMB.

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