Jump to content

Ubuntu


Luke

Recommended Posts

BLADONVENET

Hi Luke, is there a known fix for this issue: Emby (via Web Browser) displays a blank/white screen.

 

Tried it on Chrome from 2 computers, 3 different android tablets/phones with chrome. 

 

It only seems to work for a few minutes after i reboot my server.

 

im using Ubuntu 17.10 with Emby 3.3.1.0 (latest version available as of today). 

 

Im stil using port 8096 (note: i did attempt to change this via the Web UI but it wouldnt remember the change to the http port. under my config xml it is still listed as port 8096). Im also trying to access this via my local network from IP:8096.

 

Tested again, rebooted server and emby works so far, and less than 5 minutes later its not working again. 

 

 

 

 

Link to comment
Share on other sites

Hi Luke, is there a known fix for this issue: Emby (via Web Browser) displays a blank/white screen.

 

Tried it on Chrome from 2 computers, 3 different android tablets/phones with chrome. 

 

It only seems to work for a few minutes after i reboot my server.

 

im using Ubuntu 17.10 with Emby 3.3.1.0 (latest version available as of today). 

 

Im stil using port 8096 (note: i did attempt to change this via the Web UI but it wouldnt remember the change to the http port. under my config xml it is still listed as port 8096). Im also trying to access this via my local network from IP:8096.

 

Tested again, rebooted server and emby works so far, and less than 5 minutes later its not working again. 

Hi there, can you please attach the emby server log when this happens? you can learn how to do that here:

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

Thanks.

Link to comment
Share on other sites

I'd been running Emby 100% successfully on my old Linux server under Ubuntu 14.04, and have since retired that server and am setting up a new (to me) server using Ubuntu 16.04. I've installed both the x64 release .deb (3.3.1.0) and the x64 beta .deb (3.3.1.4) and get the same failure. When I start "service emby-server start" I'm able to initially get to http://hands:8096 and everything looks ok, then the webpage becomes unresponsive and a check of /var/log/syslog shows the following:

 

Mar 10 12:17:53 hands emby-server[1189]: Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal
Mar 10 12:17:53 hands emby-server[1189]: Info App: PRAGMA synchronous=1
Mar 10 12:17:53 hands emby-server[1189]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0219202 seconds
Mar 10 12:17:53 hands emby-server[1189]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
Mar 10 12:17:53 hands emby-server[1189]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0008311 seconds
Mar 10 12:17:53 hands emby-server[1189]: Info App: All entry points have started
Mar 10 12:18:14 hands kernel: [64928.675980] EmbyServer[1248]: segfault at 0 ip 00007f8fb7cbaad0 sp 00007f8ecfffbe98 error 4 in libc-2.23.so[7f8fb7c45000+1c0000]
Mar 10 12:18:14 hands systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Mar 10 12:18:14 hands systemd[1]: emby-server.service: Unit entered failed state.
Mar 10 12:18:14 hands systemd[1]: emby-server.service: Failed with result 'signal'.
 
I can restart emby-server but it dies again immediately ad infinitum..
 
Whats going on?
 
Thanks
Dave
 
Link to comment
Share on other sites

mastrmind11

I assume you're coming from the old mono install, in which case you need to purge everything prior to install.  ps, post the entire log from startup to death.

Link to comment
Share on other sites

I assume you're coming from the old mono install, in which case you need to purge everything prior to install.  ps, post the entire log from startup to death.

 

 

As I said, I'd been using Emby previously under 14.04, but am installing it on a new install of 16.04 on different hardware. Don't know what you mean by "purge everything prior to install.  ps, post the entire log from startup to death."... 

Link to comment
Share on other sites

Don't see any indication/error in the /var/lib/emby/logs log when the server dies.. I still only see an error

in /var/log/syslog.. But attached is the pertinant log from /var/lib/emby/logs

 

 

 Mar 10 12:17:53 hands emby-server[1189]: Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal
Mar 10 12:17:53 hands emby-server[1189]: Info App: PRAGMA synchronous=1
Mar 10 12:17:53 hands emby-server[1189]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0219202 seconds
Mar 10 12:17:53 hands emby-server[1189]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
Mar 10 12:17:53 hands emby-server[1189]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0008311 seconds
Mar 10 12:17:53 hands emby-server[1189]: Info App: All entry points have started
Mar 10 12:18:14 hands kernel: [64928.675980] EmbyServer[1248]: segfault at 0 ip 00007f8fb7cbaad0 sp 00007f8ecfffbe98 error 4 in libc-2.23.so[7f8fb7c45000+1c0000]
Mar 10 12:18:14 hands systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Mar 10 12:18:14 hands systemd[1]: emby-server.service: Unit entered failed state.
Mar 10 12:18:14 hands systemd[1]: emby-server.service: Failed with result 'signal'.

server-63656298516.txt

Edited by daveinlv
Link to comment
Share on other sites

Hi @@Luke is possible to run the test and live version of the server back to back yet... or does one still overwrite the other?

Link to comment
Share on other sites

mastrmind11

Hi @@Luke is possible to run the test and live version of the server back to back yet... or does one still overwrite the other?

You can certainly do this if you run 1 standalone and 1 docker, or 2 dockers.  Just be mindful of one overwriting the meta of the other.

Link to comment
Share on other sites

 

Don't see any indication/error in the /var/lib/emby/logs log when the server dies.. I still only see an error

in /var/log/syslog.. But attached is the pertinant log from /var/lib/emby/logs

 

 

 Mar 10 12:17:53 hands emby-server[1189]: Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal
Mar 10 12:17:53 hands emby-server[1189]: Info App: PRAGMA synchronous=1
Mar 10 12:17:53 hands emby-server[1189]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0219202 seconds
Mar 10 12:17:53 hands emby-server[1189]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
Mar 10 12:17:53 hands emby-server[1189]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0008311 seconds
Mar 10 12:17:53 hands emby-server[1189]: Info App: All entry points have started
Mar 10 12:18:14 hands kernel: [64928.675980] EmbyServer[1248]: segfault at 0 ip 00007f8fb7cbaad0 sp 00007f8ecfffbe98 error 4 in libc-2.23.so[7f8fb7c45000+1c0000]
Mar 10 12:18:14 hands systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Mar 10 12:18:14 hands systemd[1]: emby-server.service: Unit entered failed state.
Mar 10 12:18:14 hands systemd[1]: emby-server.service: Failed with result 'signal'.

 

The Same here. New installation within the 16.04.

I had the same issue since the latest three emby released version.

The issue seems related to some thumbnail creation.

In the beginning I was thinking some bad codec during the movie analysis. After I noticed that even if I delete the file, if the image thumbnail is retrivied (also if not showned) this crash occurrs.

There is a way to confirm this hypotesis?

Link to comment
Share on other sites

Hi

 

I am running Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-116-generic x86_64)

 

My Emby server keeps dying with the following unhanded exception:
 

System.MissingMethodException: bool MediaBrowser.Common.Security.ISecurityManager.get_IsMBSupporter()
at System.Runtime.CompilerServices.AsyncVoidMethodBuilder.Start[TStateMachine] (TStateMachine& stateMachine) [0x0002c] in <f56c876907e742b0aa586f051fcce845>:0
at MediaBrowser.Plugins.MovieThemeVideos.EntryPoints.LocalMovieThemeVideoEntryPoint.NewItemTimerCallback (System.Object state) [0x00024] in <651c00d9fd87460c84ac716c88089c98>:0
at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00007] in <f56c876907e742b0aa586f051fcce845>:0
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00008] in <f56c876907e742b0aa586f051fcce845>:0
at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00074] in <f56c876907e742b0aa586f051fcce845>:0
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <f56c876907e742b0aa586f051fcce845>:0
System.MissingMethodException
at System.Runtime.CompilerServices.AsyncVoidMethodBuilder.Start[TStateMachine] (TStateMachine& stateMachine) [0x0002c] in <f56c876907e742b0aa586f051fcce845>:0
at MediaBrowser.Plugins.MovieThemeVideos.EntryPoints.LocalMovieThemeVideoEntryPoint.NewItemTimerCallback (System.Object state) [0x00024] in <651c00d9fd87460c84ac716c88089c98>:0
at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00007] in <f56c876907e742b0aa586f051fcce845>:0
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00008] in <f56c876907e742b0aa586f051fcce845>:0
at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00074] in <f56c876907e742b0aa586f051fcce845>:0
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <f56c876907e742b0aa586f051fcce845>:0 

This started happening after the latest Emby server update.
 
Full log here: server.log

Edited by Brazer
Link to comment
Share on other sites

@@androx please attach the emby server log, thanks.

here the log

 

and the long list of crashes


[651564.931505] EmbyServer[30167]: segfault at 0 ip 00007fe3a7720ad0 sp 00007fe38fcd6498 error 4 in libc-2.23.so[7fe3a76ab000+1c0000]
[651772.778992] EmbyServer[30216]: segfault at 0 ip 00007ff57652dad0 sp 00007ff55ff7b498 error 4 in libc-2.23.so[7ff5764b8000+1c0000]
[659136.923335] EmbyServer[32485]: segfault at 0 ip 00007f37842dead0 sp 00007f36b49d2498 error 4 in libc-2.23.so[7f3784269000+1c0000]
[659185.079773] EmbyServer[426]: segfault at 0 ip 00007f0b57103ad0 sp 00007f0ab77fa498 error 4 in libc-2.23.so[7f0b5708e000+1c0000]
[659369.016668] EmbyServer[521]: segfault at 0 ip 00007f0935a56ad0 sp 00007f08927f8498 error 4 in libc-2.23.so[7f09359e1000+1c0000]
[659624.937637] EmbyServer[631]: segfault at 0 ip 00007f60f4766ad0 sp 00007f6040ff7498 error 4 in libc-2.23.so[7f60f46f1000+1c0000]
[659624.937686] EmbyServer[709]: segfault at 0 ip 00007f60f4766ad0 sp 00007f60417f8498 error 4 in libc-2.23.so[7f60f46f1000+1c0000]
[659795.551413] EmbyServer[826]: segfault at 0 ip 00007fd06cf17ad0 sp 00007fcff1e20498 error 4 in libc-2.23.so[7fd06cea2000+1c0000]
[659845.210280] EmbyServer[899]: segfault at 0 ip 00007fc3f5327ad0 sp 00007fc3de539498 error 4 in libc-2.23.so[7fc3f52b2000+1c0000]
[659884.660012] EmbyServer[969]: segfault at 0 ip 00007f9f3388ead0 sp 00007f9f1b61f498 error 4 in libc-2.23.so[7f9f33819000+1c0000]
[659921.139135] EmbyServer[1001]: segfault at 0 ip 00007fb6f82f8ad0 sp 00007fb647ffd498 error 4 in libc-2.23.so[7fb6f8283000+1c0000]
[659953.907536] EmbyServer[1054]: segfault at 0 ip 00007f4cdfdd9ad0 sp 00007f4c2d761498 error 4 in libc-2.23.so[7f4cdfd64000+1c0000]
[659989.031460] EmbyServer[1104]: segfault at 0 ip 00007f0b83b3bad0 sp 00007f0ae1cd1498 error 4 in libc-2.23.so[7f0b83ac6000+1c0000]
[660064.235729] EmbyServer[1151]: segfault at 0 ip 00007f75c2787ad0 sp 00007f7546e8f498 error 4 in libc-2.23.so[7f75c2712000+1c0000]
[665515.955245] EmbyServer[1326]: segfault at 0 ip 00007f226e6a2ad0 sp 00007f21f3dac498 error 4 in libc-2.23.so[7f226e62d000+1c0000]
[665647.139381] EmbyServer[2716]: segfault at 0 ip 00007fe1a1229ad0 sp 00007fe18bbd5498 error 4 in libc-2.23.so[7fe1a11b4000+1c0000]

Log.txt

Link to comment
Share on other sites

@@Luke some additional information for you.

The fault happens exactly after I recall a thumbnail.

If I start the server and paste this line on the browser the crash occurs.

192.168.1.41:8096/emby/Items/ff1fa4d21ca2f05d74939e09f5197cd1/Images/Primary?maxHeight=303&maxWidth=202&tag=7ea1643a6ec7f6a8165315ac8a0485ce&quality=90%C2%A0

that produces a segmentation fault

 

[665647.139381] EmbyServer[2716]: segfault at 0 ip 00007fe1a1229ad0 sp 00007fe18bbd5498 error 4 in libc-2.23.so[7fe1a11b4000+1c0000]

 

Starting from this observation I tried to look for a visualized thumbnail i.e.

http://192.168.1.41:8096/emby/Items/070330e0999883509fd7e5e77a4bcc3c/Images/Primary?maxHeight=303&maxWidth=202&tag=5eef906a9a7e5a6ca0ea633311155e2d&quality=90

This of course is visualized and doesn't crash the running service.

The difference is that in this case I can find the directory /var/lib/emby/metadata/library/07/070330e0999883509fd7e5e77a4bcc3c that contains the poster.jpg

in the other case I can't find either the folder.

 

I tried to create the missing folder by hand and putting inside a poster.jpg (giving the right permission) without positive result. Once the line is requested via browser the system crash

 

To solve I need to close the browser ( to do not recall the page/link), go in metadata and delete the movie file.

If I import it again I can confirme that the crash happens  here

Mar 13 14:35:45 embyserver emby-server[22689]:     Metadata:
Mar 13 14:35:45 embyserver emby-server[22689]:       filename        : small_cover.jpg
Mar 13 14:35:45 embyserver emby-server[22689]:       mimetype        : image/jpeg
Mar 13 14:35:45 embyserver emby-server[22689]:     Stream #0:3: Video: mjpeg, yuvj444p(pc, bt470bg/unknown/unknown), 213x120, 90k tbr, 90k tbn, 90k tbc
Mar 13 14:35:45 embyserver emby-server[22689]:     Metadata:
Mar 13 14:35:45 embyserver emby-server[22689]:       filename        : small_cover_land.jpg
Mar 13 14:35:45 embyserver emby-server[22689]:       mimetype        : image/jpeg
Mar 13 14:35:45 embyserver emby-server[22689]:     Stream #0:4: Video: mjpeg, yuvj444p(pc, bt470bg/unknown/unknown), 600x882, 90k tbr, 90k tbn, 90k tbc
Mar 13 14:35:45 embyserver emby-server[22689]:     Metadata:
Mar 13 14:35:45 embyserver emby-server[22689]:       filename        : cover.jpg
Mar 13 14:35:45 embyserver emby-server[22689]:       mimetype        : image/jpeg
Mar 13 14:35:45 embyserver emby-server[22689]:     Stream #0:5: Video: mjpeg, yuvj444p(pc, bt470bg/unknown/unknown), 1067x600, 90k tbr, 90k tbn, 90k tbc
Mar 13 14:35:45 embyserver emby-server[22689]:     Metadata:
Mar 13 14:35:45 embyserver emby-server[22689]:       filename        : cover_land.jpg
Mar 13 14:35:45 embyserver emby-server[22689]:       mimetype        : image/jpeg
Mar 13 14:35:59 embyserver systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV
Mar 13 14:35:59 embyserver systemd[1]: emby-server.service: Unit entered failed state.
Mar 13 14:35:59 embyserver systemd[1]: emby-server.service: Failed with result 'signal'.


If I try to star the server, go in the metadata editor and there download the images the crash happens occurs again, but maybe this information from the log file is more useful

2018-03-13 14:42:17.227 Info HttpServer: HTTP GET http://192.168.1.41:8096/emby/Users/05295accba204164b48d033185e27c25/Items/1b29098ec5e093e22f3bcd7d2e58868e. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36
2018-03-13 14:42:17.236 Info HttpServer: HTTP Response 200 to 192.168.1.1. Time: 9ms. http://192.168.1.41:8096/emby/Users/05295accba204164b48d033185e27c25/Items/1b29098ec5e093e22f3bcd7d2e58868e 
2018-03-13 14:42:17.407 Info HttpServer: HTTP GET http://192.168.1.41:8096/emby/Items/1b29098ec5e093e22f3bcd7d2e58868e/RemoteImages/Providers. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36
2018-03-13 14:42:17.415 Info HttpServer: HTTP Response 200 to 192.168.1.1. Time: 8ms. http://192.168.1.41:8096/emby/Items/1b29098ec5e093e22f3bcd7d2e58868e/RemoteImages/Providers 
2018-03-13 14:42:17.454 Info HttpServer: HTTP GET http://192.168.1.41:8096/emby/Items/1b29098ec5e093e22f3bcd7d2e58868e/Images. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36
2018-03-13 14:42:17.854 Info ImageProcessor: Getting image size for item Movie smb://192.168.1.20/Harddisk/movie/english/Underworld Blood Wars.jpg

Some issue due to the resizing procedure of image processor?

Edited by androx
Link to comment
Share on other sites

  • 2 weeks later...

I'm on 3.3.1 currently and have noticed the when I shuffle a show, the same episode comes up every time for the first show. Subsequent episodes do appear to be random. 

Link to comment
Share on other sites

Say I goto the show Bubble Guppies and select Shuffle All... the episode the plays is always The Glitter Games! which happens to be season 4 episode 1... at the end of the that episode the next show is always random. It's like the first "random" episode of the Shuffle feature is the same for that show.

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...