Search the Community

I have Emby running on a Windows server 2016 in a data center. I am always connecting to the external port with ssl enabled. After streaming for some time on any given day the external port within Emby closes and I cant access the server remotely. I have to RDP into the server and restart Emby to get the port to open again. When I RDP in I can see Emby on the LAN port. Windows firewall has the external port open and the network firewall has the port open. I know its somewhere in Emby that has the problem. I used to use the auto restart plugin to restart Emby server every 24 hours but now that that is gone i have to do it manually. Does anyone have any recommendations to a good fix for this problem in the current version of Emby?

Hello, I have a fresh install of Emby server 3.4.1.0 on a Raspberry Pi 3B+ with Raspbian Stretch (2018-06-27). I'm trying to play videos on an Apple TV 4th generation (A1625 32GB) running the current tvOS (11.4 15L577) with a new install of the Emby app. All my media files are h264 in mp4 containers. I turned off transcoding permission for the Emby user to ensure direct play. I've tried a variety of different files, and I always get the same result: it starts off playing normally, then after a few seconds I start seeing flickers of a gray screen that says: "Oops. Something went wrong. Maximum call stack size exceeded." These occur just for 1 or 2 frames at a time, one every few seconds, with normal video in between. This continues for a minute or two, then the app crashes to the Apple TV home screen. If I try to fast-forward, the app hangs for a long time (10+ seconds) as though it's going to resume play, then crashes without playing. Server logs attached (Log1.txt is fast-forwarding, Log2.txt is just playing). I'm not sure how to provide logs from the Apple TV. Everything about my system is plain vanilla (fresh installs, no customization, nothing weird) so it's odd to find such a debilitating error. Are others having trouble with the Emby Apple TV app? If I can provide any further info please let me know. Thanks, Robert Log1.txt Log2.txt

i would love to use emby server, if it working properly... I cant use Emby, because it crashing all the time. When i start a movie-after stop, then start other, the server is crashing. I tried playing this movies whit Plex and worked, but i dont like Plex. PLZ help me to use this awsome server!! My system: DietPi distribution on Raspberry pi 3, Distributor ID: Raspbian Description: Raspbian GNU/Linux 9.4 (stretch) Release: 9.4 Codename: stretch Emby Version: Version 3.3.1.0 ffmpeg version: ffmpeg version 3.2.10-1~deb9u1+rpt1 Mono runtime version: Mono JIT compiler version 5.10.1.20 I see this on ssh session terminal, when crash is coming: Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.036759] Internal error: Oops: 17 [#10] SMP ARM Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.107391] Process Threadpool work (pid: 7323, stack limit = 0xb5f72210) Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.111531] Stack: (0xb5f73d98 to 0xb5f74000) Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.115609] 3d80: 00007f38 806d1600 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.119741] 3da0: 00082dcf b5f73ec0 b25757c0 00082dcf b5f73e54 b5f73dc0 806d1620 806ce01c Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.123787] 3dc0: 00007f38 801ed940 b3f06a6c b6fc814c 80c069c4 80d0a08c 80c049c0 b5f72000 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.127845] 3de0: 00000000 90a5e05c 00000001 00000000 00000001 00000000 00010000 00000000 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.131922] 3e00: 00000001 b2575910 0000054d 00000000 00000121 00007f38 7fffffff b5f73e28 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.135949] 3e20: 801235c4 801e0000 b25757c0 b25757c0 00202436 b5f73ec0 00000121 80108224 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.139882] 3e40: b5f72000 00000000 b5f73e74 b5f73e58 806d214c 806d1324 806d2114 b25757c0 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.143890] 3e60: 00000000 931c4fc0 b5f73e94 b5f73e78 806fe240 806d2120 802aa224 802aa178 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.147846] 3e80: 00000000 00000000 b5f73ea4 b5f73e98 80657950 806fe204 b5f73f8c b5f73ea8 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.151730] 3ea0: 80658aa0 80657938 b5f73ec8 80c82021 fffffff7 00000001 6de206f2 00202436 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.155590] 3ec0: 00000000 00000000 00000001 00082dcf 0017f667 b5f73eb8 00000001 801ee188 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.159462] 3ee0: 00000000 00000000 00000000 b5f73ef8 80101850 80123188 b5f73f00 b6802e00 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.163284] 3f00: 00000001 00400040 80c02d00 0002f04e 0000000a 80c918c0 80c823f0 80c03d68 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.167115] 3f20: 80b84378 80c02080 b5f73ef8 00000000 8017a470 80b8c92c 00000000 00000000 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.170902] 3f40: 00000001 b6804180 00202436 8012377c b5f73f6c b5f73f60 8012377c 80184560 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.174608] 3f60: b5f73f94 b5f73f70 801754d8 801236e0 b5f73fb0 76412d80 00000000 6de206f2 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.178380] 3f80: b5f73fa4 b5f73f90 80658af0 806589e4 00000000 00000000 00000000 b5f73fa8 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.182084] 3fa0: 80108080 80658ad4 76412d80 00000000 00000021 6de206f2 00202436 00000000 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.185758] 3fc0: 76412d80 00000000 6de206f2 00000121 00000000 01feac80 00380ee0 6f12a820 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.189398] 3fe0: 00000000 6f12a7a8 00000000 76e2b984 80000010 00000021 00000000 00000000 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.218091] Code: e155000c 03a05000 e2117902 1a000039 (e5d50028) AND when i check emby status, after crash: ● emby-server.service - Emby Media Server Loaded: loaded (/lib/systemd/system/emby-server.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2018-04-17 11:29:23 CEST; 7s ago Process: 6922 ExecStopPost=/usr/bin/emby-server clear (code=exited, status=0/SUCCESS) Process: 6673 ExecStart=/usr/bin/emby-server start (code=exited, status=134) Main PID: 6673 (code=exited, status=134) Apr 17 11:29:23 DietPi-Kodi emby-server[6673]: Native stacktrace: Apr 17 11:29:23 DietPi-Kodi emby-server[6673]: Debug info from gdb: Apr 17 11:29:23 DietPi-Kodi emby-server[6673]: mono_gdb_render_native_backtraces not supported on this platform, unable to find gdb or lldb Apr 17 11:29:23 DietPi-Kodi emby-server[6673]: ================================================================= Apr 17 11:29:23 DietPi-Kodi emby-server[6673]: Got a SIGABRT while executing native code. This usually indicates Apr 17 11:29:23 DietPi-Kodi emby-server[6673]: a fatal error in the mono runtime or one of the native libraries Apr 17 11:29:23 DietPi-Kodi emby-server[6673]: used by your application. Apr 17 11:29:23 DietPi-Kodi emby-server[6673]: ================================================================= Apr 17 11:29:23 DietPi-Kodi systemd[1]: emby-server.service: Unit entered failed state. Apr 17 11:29:23 DietPi-Kodi systemd[1]: emby-server.service: Failed with result 'exit-code'. THX! ServerLog.txt FFmpegLog.txt reinstalled_ffmpegLog.txt reinstalled_serverLog.txt MorningServerLog_2018_04_18.txt

Hi all, I been running emby server Version 3.3.1.0 on a Synology DS1815+ with DSM 6.1.6-15266 Update 1, I have been experiencing random server crash when a few things are happening, ie Auto organised process kicks off, system back whne using backup and restore. I have had issue free run since installation over a year back. Nothing has changes on the hardware side, only changes to the system are synology DSM updates which are performed regularly. I have check the files and see several errors, see attached log files. Thanks in advance Pablo server-6359467003.txt server-6365909675.txt server-63659520000.txt unhandled-bafeff2f......txt

I added a few new movies recently and now whenever I click on Movies, I get a Segmentation Fault and then shutdown. It will run just fine up till then. I can click into every other section, just Movies is affected. Segmentation fault [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. Any thoughts how to troubleshoot this. I did notice that one of the new movies does not have any art to it, so I am wondering if it is dealing with that? I did end up removing the BoxArt and Cover Art plugins, but that didn't help. The only plugin I have now is the Trailers one.

greets. emby fresh debian 9 install (and reinstall) libraries for epub, video and audio via NAS SMB consistent crash withiin moments requiring service emby-server restart. two most recent log files attached. assistance greatly appreciated, tnx! ~tcm server-63652982530.txt server-63652982708.txt

Hello, I am running an emby server (premier), and it is crashing almost every hour. The server is running Ubuntu 16.04 with 4 vcpu and 8g of ram - Vultr I have attached the server log for reference, For some reason it has alot of errors. Any help would be greatly appreciated. If you need anymore information please ask . Thank you! system log.txt another crash.txt

Hi, I am hoping this is the right place to ask. I am trying to install emby for the first time and facing some issues. I am using docker and ansible to get it working. Ansible script is pretty simple - name: Install Emby docker: name: emby image: emby/embyserver:latest state: reloaded pull: always privileged: yes restart_policy: always volumes: - "{{ appdata }}/emby/test:/config:rw" - "/tmp:/tmp:rw" - "{{ media }}:/media:ro" ports: - "8096:8096" #host:container - "8920:8920" env: APP_UID: 1050 APP_GID: 1050 APP_USER: "{{dockeruser}}" VERSION: latest The "APPDATA" folder is a CIFS mount on the remote NAS, the all required folders are created and dockeruser has access and permissions to write. bash-4.4# cd /config/ bash-4.4# ls -lah total 4.0K drwxrwxr-x 2 dockeruser dockeruser 0 Dec 26 2017 . drwxr-xr-x 41 root root 4.0K Dec 26 02:46 .. drwxrwxr-x 2 dockeruser dockeruser 0 Dec 26 2017 cache drwxrwxr-x 2 dockeruser dockeruser 0 Dec 26 2017 config drwxrwxr-x 2 dockeruser dockeruser 0 Dec 26 2017 data drwxrwxr-x 2 dockeruser dockeruser 0 Dec 26 2017 localization drwxrwxr-x 2 dockeruser dockeruser 0 Dec 26 2017 logs But I get an exception on startup of emby: 2017-12-26T02:46:45.103737485Z *** Error Report *** 2017-12-26T02:46:45.103745195Z Version: 3.2.60.0 2017-12-26T02:46:45.103749733Z Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /config -restartpath /usr/lib/emby-server/restart.sh 2017-12-26T02:46:45.103755378Z Operating system: Unix 3.16.0.4 2017-12-26T02:46:45.103759083Z 64-Bit OS: True 2017-12-26T02:46:45.103762662Z 64-Bit Process: True 2017-12-26T02:46:45.103766230Z User Interactive: False 2017-12-26T02:46:45.103770132Z Mono: 4.8.1 (Stable 4.8.1.0/22a39d7 Sun Oct 1 17:55:43 UTC 2017) 2017-12-26T02:46:45.103775094Z Processor count: 2 2017-12-26T02:46:45.103779418Z Program data path: /config 2017-12-26T02:46:45.103783731Z Application directory: /usr/lib/emby-server/bin 2017-12-26T02:46:45.103787682Z System.AggregateException: One or more errors occurred. ---> SQLitePCL.pretty.SQLiteException: Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown. 2017-12-26T02:46:45.103793143Z at SQLitePCL.pretty.SQLiteException.CheckOk (SQLitePCL.sqlite3 db, System.Int32 rc) [0x0001a] in <926d5dc8f35f4aae9a6008f11f233fd0>:0 2017-12-26T02:46:45.103797254Z at SQLitePCL.pretty.SQLiteException.CheckOk (SQLitePCL.sqlite3_stmt stmt, System.Int32 rc) [0x00006] in <926d5dc8f35f4aae9a6008f11f233fd0>:0 2017-12-26T02:46:45.103801365Z at SQLitePCL.pretty.StatementImpl.MoveNext () [0x00056] in <926d5dc8f35f4aae9a6008f11f233fd0>:0 2017-12-26T02:46:45.103805152Z at SQLitePCL.pretty.DatabaseConnection.ExecuteAll (SQLitePCL.pretty.IDatabaseConnection This, System.String sql) [0x0001d] in <926d5dc8f35f4aae9a6008f11f233fd0>:0 2017-12-26T02:46:45.103811208Z at Emby.Server.Implementations.Data.ManagedConnection.ExecuteAll (System.String sql) [0x00000] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.103815564Z at Emby.Server.Implementations.Data.BaseSqliteRepository.RunDefaultInitialization (Emby.Server.Implementations.Data.ManagedConnection db) [0x00079] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.103819573Z at Emby.Server.Implementations.Data.SqliteUserRepository.Initialize () [0x00008] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.103823603Z at Emby.Server.Implementations.ApplicationHost.GetUserRepository () [0x00027] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.103827786Z at Emby.Server.Implementations.ApplicationHost+<RegisterResources>d__308.MoveNext () [0x005ce] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.103831952Z --- End of stack trace from previous location where exception was thrown --- 2017-12-26T02:46:45.103873899Z at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.103898654Z at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104062434Z at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104067354Z at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104071357Z at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104075767Z at Emby.Server.Implementations.ApplicationHost+<Init>d__303.MoveNext () [0x0024c] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.104202780Z --- End of inner exception stack trace --- 2017-12-26T02:46:45.104461756Z at System.Threading.Tasks.Task.WaitAll (System.Threading.Tasks.Task[] tasks, System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken) [0x00242] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104468762Z at System.Threading.Tasks.Task.WaitAll (System.Threading.Tasks.Task[] tasks, System.Int32 millisecondsTimeout) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104472933Z at System.Threading.Tasks.Task.WaitAll (System.Threading.Tasks.Task[] tasks) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104477195Z at MediaBrowser.Server.Mono.MainClass.RunApplication (Emby.Server.Implementations.ServerApplicationPaths appPaths, MediaBrowser.Model.Logging.ILogManager logManager, Emby.Server.Implementations.StartupOptions options) [0x000d4] in <ce6ca2d6e906484ab100b2c0b72cc4b9>:0 2017-12-26T02:46:45.104481691Z at MediaBrowser.Server.Mono.MainClass.Main (System.String[] args) [0x00085] in <ce6ca2d6e906484ab100b2c0b72cc4b9>:0 2017-12-26T02:46:45.104723594Z ---> (Inner Exception #0) Busy: database is locked 2017-12-26T02:46:45.104743338Z SQLitePCL.pretty.SQLiteException: Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown. 2017-12-26T02:46:45.104748462Z at SQLitePCL.pretty.SQLiteException.CheckOk (SQLitePCL.sqlite3 db, System.Int32 rc) [0x0001a] in <926d5dc8f35f4aae9a6008f11f233fd0>:0 2017-12-26T02:46:45.104758565Z at SQLitePCL.pretty.SQLiteException.CheckOk (SQLitePCL.sqlite3_stmt stmt, System.Int32 rc) [0x00006] in <926d5dc8f35f4aae9a6008f11f233fd0>:0 2017-12-26T02:46:45.104763157Z at SQLitePCL.pretty.StatementImpl.MoveNext () [0x00056] in <926d5dc8f35f4aae9a6008f11f233fd0>:0 2017-12-26T02:46:45.104766973Z at SQLitePCL.pretty.DatabaseConnection.ExecuteAll (SQLitePCL.pretty.IDatabaseConnection This, System.String sql) [0x0001d] in <926d5dc8f35f4aae9a6008f11f233fd0>:0 2017-12-26T02:46:45.104770851Z at Emby.Server.Implementations.Data.ManagedConnection.ExecuteAll (System.String sql) [0x00000] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.104774649Z at Emby.Server.Implementations.Data.BaseSqliteRepository.RunDefaultInitialization (Emby.Server.Implementations.Data.ManagedConnection db) [0x00079] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.104795683Z at Emby.Server.Implementations.Data.SqliteUserRepository.Initialize () [0x00008] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.104801831Z at Emby.Server.Implementations.ApplicationHost.GetUserRepository () [0x00027] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.104805745Z at Emby.Server.Implementations.ApplicationHost+<RegisterResources>d__308.MoveNext () [0x005ce] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.104809863Z --- End of stack trace from previous location where exception was thrown --- 2017-12-26T02:46:45.104814200Z at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104819577Z at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104823695Z at System.Runtime.CompilerServices.TaskAwaiter. If I don't mount the location of the emby APPDATA (where I want to store DB files etc...) then emby seems to start. but this isn't ideal at all I don't want to keep this data in the VM or in Docker. Please help. server-63649853436.txt unhandled_f3903ef0-3e41-4099-954d-13d897bd6838.txt

I just recently started to install a lot of the plug-ins that I uninstalled after Emby was being unstable for me (about a year ago maybe). 3.2.36.0 has been pretty stable up until now. So I install maybe 10 plugins that are relatively benign (Auto boxset, theme songs, etc), and now Emby has been crashing within a minute or two of startup. I'm not sure what's going on, but I just need a stable Emby to use. Log files included. crashes.zip

Hello, My TV model is: UE32H6400 and I have been running the community app version 2.2.2 for couple months now with no issue at all. First of all I was excited to read that now the app is available in the official samsung store for users in UK and I am now running version 0.109 at the same time. Its very handy that I didn't had to delete the community app and have them both installed, as some problems I have with version 0.109 are non existent on 2.2.2 Those in detail: 1) I have noticed when I am running version 0.109, from time to time when I am browsing through my library, the server app on my dedicated windows pc crashes and I have to manually re-start it (only the app, not the PC). Maybe that's a server issue as I have also noticed that it happens after upgrading to 3.2.36.0. 2) Version 2.2.2 starts 3D movies just fine as long as you have configured each movie properly through the metadata manager menu -in my case it's the HSBS option- so you don't have to manually choose this with your remote control. I can't seem to be able to run any 3D movie with version 0.109 3) In version 0.109, when a movie is playing I don't seem to be able to view the progress bar when I pause the movie. I also can't choose a specific chapter or use the playback bar to move further ahead onto another segment of the movie. Fast forward buttons on the remote seem to be ok. 4) I would love to have an option in version 0.109 to increase the subtitles size if possible. All my movies are MP4 with AAC 5.1 audio, 2000 to 2500 bitrate H264 encoding so direct play works flawless on both TV apps and on my iPhone app as well. Another really nice thing I have noticed is that the video playback looks crispier and sharper through the 0.109 app comparing it to the 2.2.2 version. Now that I am thinking of it, the only thing differently I did when I have installed the new 0.109 app, is that I've used the PIN option to connect to my EMBY server. I can also try disconnect and connect manually with my local IP just to see if that makes any difference for the above issues although I don't think it would be related. All those are minor problems of course. I am happy having both apps installed, I just thought to share my testing results with you guys for future improvements. Thanks again for all your hard work, EMBY as always is awesome!!

I'm having a lot of trouble with a new Xiaomi Mi Box (Android TV) -- the app is very unstable on this device (which is weird since I rarely have issues on my Shield or Fire TV). It crashes so frequently the app isn't really usable. I have NOT submitted a crash report from within the app yet, but I did do the built-in Android "Report" that happens after a force close ("Emby isn't responding."). It was submitted around 2017-10-19 19:55 MST (Pacific Daylight) -- are you able to look at that report for debug information? I'll get a report sent from within the app in the next day or so.

About 20 minutes ago noticed that emby-server is not running, restarting the server makes it appear "active" using service status, but it crashes immediately after that. I've been running Emby on Zesty (4.10.0-20-generic x86_64) for about 3 weeks now, had no issues before, so I'm not sure what caused this. sudo service emby-server status shows this Б≈▐ emby-server.service - Emby Media Server Loaded: loaded (/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled) Active: inactive (dead) since Tue 2017-05-16 21:30:34 MSK; 9min ago Process: 10617 ExecStopPost=/usr/bin/emby-server clear (code=exited, status=0/SUCCESS) Process: 10571 ExecStart=/usr/bin/emby-server start (code=exited, status=0/SUCCESS) Main PID: 10571 (code=exited, status=0/SUCCESS) п╪п╟п╧ 16 21:30:31 HTPC systemd[1]: Started Emby Media Server. п╪п╟п╧ 16 21:30:31 HTPC su[10571]: Successful su for emby by root п╪п╟п╧ 16 21:30:31 HTPC su[10571]: + ??? root:emby п╪п╟п╧ 16 21:30:31 HTPC su[10571]: pam_unix(su:session): session opened for user emby by (uid=0) I attached the log from /var/lib/emby-server/logs. Thanks in advance! log.txt

Library type “video and photo” make crash ,once i delete it and build a new library in the type "movie",it work find again.but i cant browse photo on my server with this setting. also,it seems crash as the time i just access(if the library type set as "video and photo"),because if i restart emby service,wait for like ten minute,then i access from remote(WAN),still can load the homepage for 10 second before it go crash.so i assumes my access make it crash. i dont know which log i should upload,i just upload 3 of them all before it back to no crash. 1.txt 2.txt 3.txt

Hi guys, I'm worthless at Linux overall but trying to learn more and more so bear with me in this case and I barely know how to read the log file either so ...... >.> My issue is that my Emby-server randomly just stops working on my Ubuntu 17.04. I try to run "sudo service emby-server start" when it stops working but that doesn't help so I have to restart my whole server. ​I have my shares mapped via fstab if that helps anything but I guess this isn't the issue as the same shares have been used by Plex earlier and worked like a charm. My Emby server is like 2 weeks old and I have had it updated 2 times I think but no update solved it. I have attached a Log-file that I took right after I restarted my server. Any help I can get is much appreciated! Log.txt

Hi there Every night my emby-server service on my Pi 3 stops running and needs to be restarted. It seems to be during the library scan. Can anyone provide some insight as to what's happening here. I haven't enabled the debug logging option. I have also disabled real time monitoring, as I saw that mentioned in a similar older thread. I am also running openvpn on the device. Could that be causing some form of conflict, or maybe overloading the capabilities of the Pi 3? When it's running, it has no issues at all. Only that I need to restart it ever day as at some point it just disappears. These are all the logs I have since I started running the server on the Pi a few days ago. Happy to provide any other information, or do whatever troubleshooting to help. server-63627284127.txt server-63627292800.txt server-63627360805.txt server-63627379200.txt server-63627443467.txt server-63627465600.txt server-63627497816.txt server-63627546658.txt server-63627552000.txt server-63627592630.txt

Hi I don't know if they are related but I've been having a few crashes per week for a while now. I use Ubunru 16.04 64bit with the 4.10 series kernel on an Intel i7 6700K with 32 GB of ram. The crashes seem kindda random... I could see that It was re-encoding media last time it crashed, fetching images and I had a user on that were transcoding af movie... Ubuntu always remains stable and I keep the system updated so it should have the newest versions of everything from the repository... I've checked the drives for space issues they all have at least 39 GB of free space... I've attached two of the latest logs of crashes I could get and I will provide more the next time it happens if needed... Thanks in advance -Compix LOG_server-63627724800.txt LOG_server-63627984000.txt

I have been using Emby/MB on FreeBSD for several years without any issues, but after upgrading to 3.2.4 it crashes every time I enter itemdetails.html for a new movie or TV show. When the process crashes, the primary cover image turns into a "broken image" icon on the client (using Google Chrome), whereas the rest of the images (season covers etc.) simply remain empty. After restarting Emby and reloading the page, all the images are there. It was working fine in 3.1.2. I skipped a couple of versions and went directly to 3.2.4, so I'm not sure which version introduced the issue. The mono process silently dies, and even with debug logging activated, nothing interesting seems to get written to the log file (server-X.txt): 2017-02-26 19:17:56.9407 Info HttpServer: HTTP GET http://moviebox:8096/emby/Users/44ce6b51025040a9990b93886f430537/Items/a2418600ad112d4aca7bb734166c02ef. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 2017-02-26 19:17:56.9609 Info HttpServer: HTTP Response 200 to 10.0.0.2. Time: 20ms. http://moviebox:8096/emby/Users/44ce6b51025040a9990b93886f430537/Items/a2418600ad112d4aca7bb734166c02ef 2017-02-26 19:17:56.9759 Info HttpServer: HTTP GET http://moviebox:8096/emby/Items/a2418600ad112d4aca7bb734166c02ef/ThemeMedia?userId=44ce6b51025040a9990b93886f430537&InheritFromParent=true. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 2017-02-26 19:17:56.9759 Info HttpServer: HTTP GET http://moviebox:8096/emby/Items/a2418600ad112d4aca7bb734166c02ef/CriticReviews?limit=1. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 2017-02-26 19:17:56.9764 Info HttpServer: HTTP GET http://moviebox:8096/emby/Items/a2418600ad112d4aca7bb734166c02ef/Similar?userId=44ce6b51025040a9990b93886f430537&limit=10&fields=PrimaryImageAspectRatio%2CUserData%2CCanDelete. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 2017-02-26 19:17:56.9780 Info HttpServer: HTTP Response 200 to 10.0.0.2. Time: 2ms. http://moviebox:8096/emby/Items/a2418600ad112d4aca7bb734166c02ef/ThemeMedia?userId=44ce6b51025040a9990b93886f430537&InheritFromParent=true 2017-02-26 19:17:56.9812 Debug JsonSerializer: Deserializing file /var/db/emby-server/data/critic-reviews/a2418600-ad11-2d4a-ca7b-b734166c02ef.json 2017-02-26 19:17:56.9825 Info HttpServer: HTTP GET http://moviebox:8096/emby/Items/a2418600ad112d4aca7bb734166c02ef/Images/Primary?maxHeight=792&tag=ddb56dcf4fbdd2b38fec2ffe4b71cecc&quality=90. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 2017-02-26 19:17:56.9825 Info HttpServer: HTTP GET http://moviebox:8096/emby/Items/a2418600ad112d4aca7bb734166c02ef/Images/Backdrop/0?tag=974bdc7724cf12c2ed2e37d49d5dc338&maxWidth=3740&quality=80. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 2017-02-26 19:17:56.9832 Debug App: ConvertImageToLocal item a2418600-ad11-2d4a-ca7b-b734166c02ef - image url: https://image.tmdb.org/t/p/original/wrlZRyyOnD24KQzo3OVi4lWyqdF.jpg 2017-02-26 19:17:56.9832 Info HttpClient: HttpClientManager GET: https://image.tmdb.org/t/p/original/wrlZRyyOnD24KQzo3OVi4lWyqdF.jpg 2017-02-26 19:17:56.9888 Info HttpServer: HTTP GET http://moviebox:8096/emby/Items/a2418600ad112d4aca7bb734166c02ef/Images/Logo?maxWidth=660&tag=3151e0db1cb7065187c03d7828f9d3c0&quality=90. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 2017-02-26 19:17:56.9888 Info HttpServer: HTTP GET http://moviebox:8096/emby/Items/a2418600ad112d4aca7bb734166c02ef/Images/Backdrop/0?maxWidth=4224&tag=974bdc7724cf12c2ed2e37d49d5dc338&quality=80. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 2017-02-26 19:17:56.9894 Debug App: ConvertImageToLocal item a2418600-ad11-2d4a-ca7b-b734166c02ef - image url: https://image.tmdb.org/t/p/original/wrlZRyyOnD24KQzo3OVi4lWyqdF.jpg 2017-02-26 19:17:56.9894 Info HttpClient: HttpClientManager GET: https://image.tmdb.org/t/p/original/wrlZRyyOnD24KQzo3OVi4lWyqdF.jpg 2017-02-26 19:17:56.9954 Info HttpServer: HTTP Response 200 to 10.0.0.2. Time: 20ms. http://moviebox:8096/emby/Items/a2418600ad112d4aca7bb734166c02ef/CriticReviews?limit=1 2017-02-26 19:17:57.0210 Info HttpServer: HTTP Response 200 to 10.0.0.2. Time: 45ms. http://moviebox:8096/emby/Items/a2418600ad112d4aca7bb734166c02ef/Similar?userId=44ce6b51025040a9990b93886f430537&limit=10&fields=PrimaryImageAspectRatio%2CUserData%2CCanDelete 2017-02-26 19:17:57.0379 Info HttpServer: HTTP GET http://moviebox:8096/emby/Items/df7222d4021c4c2e3d9aba6ded75beda/Images/Primary?maxWidth=352&tag=f1810865719d69094adfcb8af9eac15b&quality=90. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 2017-02-26 19:17:57.0380 Info HttpServer: HTTP GET http://moviebox:8096/emby/Items/4c22bd45036543094bbf55a23e06e69b/Images/Primary?maxWidth=352&tag=b1de23ad76a0692c79a4f42c7e1a0192&quality=90. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 2017-02-26 19:17:57.0395 Debug App: ConvertImageToLocal item df7222d4-021c-4c2e-3d9a-ba6ded75beda - image url: https://image.tmdb.org/t/p/original/a48HN0oeXQsqzsTsEnrvqt30570.jpg 2017-02-26 19:17:57.0395 Info HttpClient: HttpClientManager GET: https://image.tmdb.org/t/p/original/a48HN0oeXQsqzsTsEnrvqt30570.jpg 2017-02-26 19:17:57.0624 Info HttpServer: HTTP Response 200 to 10.0.0.2. Time: 74ms. http://moviebox:8096/emby/Items/a2418600ad112d4aca7bb734166c02ef/Images/Logo?maxWidth=660&tag=3151e0db1cb7065187c03d7828f9d3c0&quality=90 2017-02-26 19:17:57.0643 Info HttpServer: HTTP GET http://moviebox:8096/emby/Items/038cfa42995ba7467179f57d46bf5a52/Images/Primary?maxWidth=352&tag=9f711d979ac780213469745b42a0a27f&quality=90. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 2017-02-26 19:17:57.0658 Debug App: ConvertImageToLocal item 038cfa42-995b-a746-7179-f57d46bf5a52 - image url: https://image.tmdb.org/t/p/original/aaPzuXRHdyxamPMXqu70okPaqvB.jpg 2017-02-26 19:17:57.0658 Info HttpClient: HttpClientManager GET: https://image.tmdb.org/t/p/original/aaPzuXRHdyxamPMXqu70okPaqvB.jpg 2017-02-26 19:17:57.1116 Debug ProviderManager: Saving image to /var/db/emby-server/metadata/library/a2/a2418600ad112d4aca7bb734166c02ef/backdrop.jpg 2017-02-26 19:17:57.1131 Debug App: Saving /mnt/nfs/MOVIES/Outbreak (1995)/Outbreak.mkv to database. 2017-02-26 19:17:57.1168 Info HttpServer: HTTP Response 200 to 10.0.0.2. Time: 134ms. http://moviebox:8096/emby/Items/a2418600ad112d4aca7bb734166c02ef/Images/Primary?maxHeight=792&tag=ddb56dcf4fbdd2b38fec2ffe4b71cecc&quality=90 2017-02-26 19:17:57.1223 Info HttpServer: HTTP GET http://moviebox:8096/emby/Items/0703219a4573bdfe60d42fe12fdcdbb8/Images/Primary?maxWidth=352&tag=3377826a095372d0b57774e282257d86&quality=90. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 2017-02-26 19:17:57.1294 Debug App: ConvertImageToLocal item 0703219a-4573-bdfe-60d4-2fe12fdcdbb8 - image url: https://image.tmdb.org/t/p/original/yu8Q3ImFu3RJne585jjgeQO2Boo.jpg 2017-02-26 19:17:57.1294 Info HttpClient: HttpClientManager GET: https://image.tmdb.org/t/p/original/yu8Q3ImFu3RJne585jjgeQO2Boo.jpg 2017-02-26 19:17:57.1313 Debug ProviderManager: Saving image to /var/db/emby-server/metadata/library/a2/a2418600ad112d4aca7bb734166c02ef/backdrop.jpg Is there a way to enable additional debug logging, so that I can make a useful bug report? FreeBSD version is 11.0-RELEASE, and Emby has been installed from ports.

Hello, I'm using the latest OSMC for Raspberry Pi2 with the Emby for Kodi addon and when the library is scanning it just suddenly crashes and I see the sad face screen before starting all over again. Everything was working perfect before I update OSMC. I figured it might be an issue with the update so I did a fresh install and I'm still getting the same problems. The steps I followed were to download the img from OSMC, write to micro SD using WIn32 Disk Imager, install Emby for Kodi via file manager using Beta 1.0.5, login to my Emby Server via the addon, begin library update. This is the same process I followed before so I don't think there is any issue with how I'm executing everything. I have added a URL to the log file (and attached.txt) so hopefully someone can take a look and let me know if anything stands out. Kodi OS: OSMC latest version OSMC_TGT_rbp2_20170210 Emby Server: Version 3.2.7.0 Emby for Kodi: 1.0.5 repository Scan gets about 20-30% in for Movies and then crashes to sad face screen, process repeats itself every time. Log File: http://paste.osmc.io/inojukafey Any help is greatly appreciated! Thanks, Tman12 Kodi Log.txt

Hey, so lately my server has been crashing a lot... It started happening a few updates ago, but I don't know which update it started with because I had not been using it until about a week ago. So I have the server running on my 2011 Macbook Pro, and it has been working fine for me for a while with very few errors (some crashes here and there, but none like this). I keep my computer under my bed closed but still on so that everything can still be running. Now... when I close my computer the server will either stay running for a couple of hours or maybe a day or so or it will shutdown in minutes. When I open my computer again it's still running (shown in the taskbar and on activity monitor); however, when I click on any of the button from the taskbar icon it opens the page but it doesn't load. I'll either get a network loss error, localhost not active error, or a too many open files error. So I exit the server to shut it down completely wait a few seconds and then start it up again. Once I start it up, with any luck, I can get the page to load (but sometimes I have to exit and open more than once or completely reboot my computer to achieve this). What could be wrong? Logs attached below, I just updated to 3.2.5.0 Stable and its still doing the same thing. the logs from 2.26.17 are from version 3.2.1.0 and the one from 3.1.17 is from the latest version Emby Server Log 2.26.17 1 (63623664000).rtf Emby Server Log 2.26.17 2 (63623673690).rtf Emby Server Log 3.1.17 (63623931027).rtf Thanks!

Hi all. I'm very new to emby. Been running plex for a long time but on first impressions Emby looks amazing. My problem is that it constantly stops responding. It has run a full scan on movies and TV shows and generated the front end but if I attempt to identify anything that is showing the wrong movie or show it just crashes and I have to kill the app and restart it. It's unusable in its current state. It's a little random too in that sometimes I can edit a couple of items before it crashes. I can't be sure but I think it's crashed a couple of times without me doing anything. I can barely get 10 minutes out of it. Even just renaming a file through file manager on the qnap has caused it to crash. I have Emby v3.1.2.0 and qmono 4.6.2.7. If there are log files that might help identify the issue please can you tell me where they are? I'm gutted because it looks amazing. Any help would be massively appreciated.

Got a Lifetime subscription for xmas, was excited to get away from the annoying WMC interface and ads for the much nicer looking Theater for Windows. I searched and don't see any other topics about this. Electron crashes, after a few seconds windows offers to kill it, then emby crashes. Then I restart Theater. I can't see a pattern. Doesn't seem to be related to what's playing. 2 hours with nothing, 2 crashes in 20 minutes, once it was 2 seconds into it, but usually its mid show. One time chrome crashed afterwards. Rare to watch 2 things in a row without a crash. Nothing else running on the Win 7 PC, only emby, teamviewer, chrome, remote (LM/firefly). No security SW. How can i debug/gather logs? Thanks!

I've seen this a few times: I will start the apple tv emby client, or just try to drill down to a lower layer within the client: it will spin for a while then report an error message (eg. something like "trouble getting next up"). When I check my server I see the emby server app has crashed. Logs attached from 2 such incidents. Looks like freeing un-malloc'ed memory in both cases. btw I just noticed emby has been bumped to 3.1.2 as I'm about to post this! Hopefully this might still be useful... Mike Update: not the same as this crash: https://emby.media/community/index.php?/topic/42108-server-3085000-crash-on-connection-from-apple-tv-app-crash-log-available/ crashlogs.tgz

Hi, Just updated the media/emby-server port to 3.1.0, and the server keeps throwing an unhandled exception when starting (find the logs attached). Reverted back to 3.0.8500 in the meantime as that one works fine (server-63617782744 (8500 old success).txt). 2016-12-19 21:51:42.8663 Error App: LoaderException: Could not resolve type with token 0100005f 2016-12-19 21:51:42.8696 Error App: LoaderException: Could not load file or assembly or one of its dependencies. 2016-12-19 21:51:42.8696 Error App: LoaderException: Could not load file or assembly or one of its dependencies. 2016-12-19 21:51:42.8696 Error App: LoaderException: Could not load file or assembly or one of its dependencies. 2016-12-19 21:51:42.8696 Error App: LoaderException: Could not resolve type with token 01000128 2016-12-19 21:51:42.8696 Error App: LoaderException: Could not load file or assembly or one of its dependencies. 2016-12-19 21:51:44.4754 Error ServerManager: Error starting Http Server *** Error Report *** Version: 3.1.0.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 10.3.0.0 64-Bit OS: True 64-Bit Process: True Mono: 4.6.2 (Stable 4.6.2.7/08fd525 Mon Nov 28 22:44:12 UTC 2016) Processor count: 12 Program data path: /var/db/emby-server Application directory: /usr/local/lib/emby-server System.AggregateException: One or more errors occurred. ---> MediaBrowser.Model.Net.SocketCreateException: ProtocolNotSupported ---> System.Net.Sockets.SocketException: Protocol not supported at System.Net.Sockets.Socket..ctor (System.Net.Sockets.AddressFamily addressFamily, System.Net.Sockets.SocketType socketType, System.Net.Sockets.ProtocolType protocolType) [0x0005d] in <bd46d4d4f7964dfa9beea098499ab597>:0 at Emby.Common.Implementations.Net.SocketFactory.CreateSocket (MediaBrowser.Model.Net.IpAddressFamily family, MediaBrowser.Model.Net.SocketType socketType, MediaBrowser.Model.Net.ProtocolType protocolType, System.Boolean dualMode) [0x00000] in <9922445e90a448f2a17d005b1cc33d56>:0 --- End of inner exception stack trace --- at Emby.Common.Implementations.Net.SocketFactory.CreateSocket (MediaBrowser.Model.Net.IpAddressFamily family, MediaBrowser.Model.Net.SocketType socketType, MediaBrowser.Model.Net.ProtocolType protocolType, System.Boolean dualMode) [0x00047] in <9922445e90a448f2a17d005b1cc33d56>:0 at SocketHttpListener.Net.EndPointListener.CreateSocket () [0x00017] in <5e2146744a844faab36e869c2bc89d0d>:0 --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional (System.Boolean includeTaskCanceledExceptions) [0x00014] in <8f2c484307284b51944a1a13a14c0266>:0 at System.Threading.Tasks.Task`1[TResult].GetResultCore (System.Boolean waitCompletionNotification) [0x00034] in <8f2c484307284b51944a1a13a14c0266>:0 at System.Threading.Tasks.Task`1[TResult].get_Result () [0x0000b] in <8f2c484307284b51944a1a13a14c0266>:0 at SocketHttpListener.Net.EndPointManager.AddPrefixInternal (MediaBrowser.Model.Logging.ILogger logger, System.String p, SocketHttpListener.Net.HttpListener listener) [0x0006a] in <5e2146744a844faab36e869c2bc89d0d>:0 at SocketHttpListener.Net.EndPointManager.AddListener (MediaBrowser.Model.Logging.ILogger logger, SocketHttpListener.Net.HttpListener listener) [0x00030] in <5e2146744a844faab36e869c2bc89d0d>:0 ---> (Inner Exception #0) MediaBrowser.Model.Net.SocketCreateException: ProtocolNotSupported ---> System.Net.Sockets.SocketException: Protocol not supported at System.Net.Sockets.Socket..ctor (System.Net.Sockets.AddressFamily addressFamily, System.Net.Sockets.SocketType socketType, System.Net.Sockets.ProtocolType protocolType) [0x0005d] in <bd46d4d4f7964dfa9beea098499ab597>:0 at Emby.Common.Implementations.Net.SocketFactory.CreateSocket (MediaBrowser.Model.Net.IpAddressFamily family, MediaBrowser.Model.Net.SocketType socketType, MediaBrowser.Model.Net.ProtocolType protocolType, System.Boolean dualMode) [0x00000] in <9922445e90a448f2a17d005b1cc33d56>:0 --- End of inner exception stack trace --- at Emby.Common.Implementations.Net.SocketFactory.CreateSocket (MediaBrowser.Model.Net.IpAddressFamily family, MediaBrowser.Model.Net.SocketType socketType, MediaBrowser.Model.Net.ProtocolType protocolType, System.Boolean dualMode) [0x00047] in <9922445e90a448f2a17d005b1cc33d56>:0 at SocketHttpListener.Net.EndPointListener.CreateSocket () [0x00017] in <5e2146744a844faab36e869c2bc89d0d>:0 <--- Anything I can do to fix this? Is everyone else also experiencing this problem? Thank you server-63617781102.txt unhandled_abcf3070-649e-4189-a769-b1c2efb9e65e.txt server-63617782744 (8500 old success).txt

This has happened a couple of times in the last few weeks: I launch the (latest) apple tv emby app, scroll through some tv shows, but the app stops presenting shows to scroll down to before reaching the end of the available shows, then pops ups "error retrieving" (or similar). Then the server (same network) crashes: Dec 2 21:45:45 maxi Emby.Server.Mac[14133]: Emby.Server.Mac(14133,0xb6b33000) malloc: *** error for object 0x26d65d8c: pointer being freed was not allocated Dec 2 21:45:45 maxi Emby.Server.Mac[14133]: Emby.Server.Mac(14133,0xb7343000) malloc: *** error for object 0x16dda2bc: pointer being freed was not allocated Dec 2 21:45:45 maxi com.apple.xpc.launchd[1] (com.emby.server.32992[14133]): Service exited due to signal: Abort trap: 6 Crash log attached. OSX 10.11.6 Mike Emby.Server.Mac_2016-12-02-214556_maxi.crash.gz

Just finished installing emby server on a Raspberry Pi 3, but I am having frequent problems with the server crashing or the Pi freezing up. I am some what of a noob when it comes to Linux but I followed the installation instructions on a previous forum post. Attached are the server logs. Any help would be appreciated. server-63613372638.txt server-63613423040.txt