Search the Community
Showing results for tags 'Crashing'.
-
Fire TV Stick 4K (Gen2) crashing upon playback of opus 7.1 audio?
Intensiflying posted a topic in Android TV / Fire TV
Hi there, Recently I've been encountering issues with playback of Opus 7.1 audio on my Fire TV Stick 4K (2nd Gen). I'm wondering if this is a known issue or if anyone else has experienced similar crashes. I haven't found any reports of this specific problem here. Upon playback of videos with Opus 7.1 audio, my Fire TV Stick crashes entirely and subsequently restarts. This isn't limited to the Emby app, the entire Fire TV Stick crashes and restarts. After pressing play, the buffer wheel may show for a second, followed by a freeze. Finally, the screen turns black and the Fire TV Stick restarts. Unfortunately, the crash within the Emby for Android TV app happens too quickly to be able to use the send logs option. However, I've included logs from a sideloaded Emby for Android app, which also crashes during playback of opus 7.1 audio. Further context: I've only observed this issue with AV1 videos containing Opus 7.1 audio. 5.1 audio seems to play without problems (all tested files had AV1 video in an mkv container). This issue recently emerged; I was previously able to direct play AV1 with Opus 7.1 audio successfully. Playback works flawlessly using an external player like MPV. The crashing files play without issues on my PC (both in browser and using media players like VLC). I've tested various Emby app versions, both for Android TV (from the Fire TV store and sideloaded, including Beta) and Emby for Android (Sideloaded), and the crashes occurred with every app tested. My Fire TV Stick is up-to-date with the latest software updates. Interestingly, there have been a few instances where the same 7.1 audio that caused a crash just minutes before then played successfully. Yet trying again a few minutes later would trigger another crash. The crash seems to occur regardless of which of my two servers I stream from (one running version 4.8.1.0 and the other on Beta 4.9.0.5). The emby for android log that includes the crash states that everying is supported (supported=YES) which is backed up by the fact that these same files had no problem direct playing previously and can be also still be played via an external player. Emby server versions tested: 4.8.1.0 Stable 4.9.0.5 Beta Emby for Android TV app versions tested: 2.0.98a 2.0.93a 2.1.07a Beta Emby for Android app versions tested: 3.3.07 3.3.70 3.3.72 The crashing has occured on all versions I've tested. Fire TV Stick 4K OS: Fire OS 8.1.03 (RS8103/2083) Fire TV Home Version: 6500118.1 Media I've experienced having this issue: AV1 10bit video with Opus 7.1 audio in MKV format (1080p SDR) If any more info is needed, please let me know Thanks ~ Inten embyserver log - fire tv crash at 15.06.14.txt emby_android_1709130874679 - Log With Crash.txt -
Hello, i apologize i'm not sure to have the same problem but since version > 4.7.1 every day i have some crash also I notice this on my end : 2022-06-29 20:57:48.465 Info MediaProbeManager: ProcessRun 'ffprobe' Process exited with code 0 - Succeeded 2022-06-29 20:57:48.474 Error ProviderManager: Error in metadata saver *** Error Report *** Version: 4.7.5.0 Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb Operating system: Linux version 5.10.0-15-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 Framework: .NET 6.0.2 OS/Process: x64/x64 Runtime: opt/emby-server/system/System.Private.CoreLib.dll Processor count: 2 Data path: /var/lib/emby Application path: /opt/emby-server/system System.IO.IOException: System.IO.IOException: Read-only file system : '/mnt/share/xxxxxxxx.nfo' at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirectory, Func`2 errorRewriter) at Interop.CheckIo(Error error, String path, Boolean isDirectory, Func`2 errorRewriter) at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode) After that the service is down.
-
Every day or so I have to stop/start Emby service as the main menu stops showing up on all devices (mobile, smart tv, desktop client). I run tail -f and watch the logs but after a while emby seems to no longer load the main menu (on now, live tv, etc no longer appear), no errors are appearing in the log files. relaunching apps have no effect only restarting Emby works. I've had Emby running for up to 2 or 3 days at time but lately it seems to die every 18-20 hours or so. I don't think it's the ubuntu box it's running on as radarr and sonarr don't seem to have this issue. I have gone for months without them having issues, same for the plex server that I am trying to get away from if I can get Emby to work as expected. I'm happy to provide logs but I don't see any errors being sent to the log when this happens, Emby just goes off to la la land. What do I need to check? Thanks in advance.
-
option for quickly viewing tv guide in emby for android app
eeeeeesy posted a topic in Feature Requests
option for QUICKLY viewing tv guide without stopping the video in emby for android app currently this feature only exists on emby for android tv but is nowhere to be seen in emby for android. i would use emby for android tv but it keeps crashing every second time i open it. the other good thing about emby for android tv is i can see even more channels while in the quick view tv guide that is displayed over the video. -
Since yesterday the Webserver of my emby instance keeps crashing and I don't know why. I'm using the community Plugin on FreeNas atm. Installed is Version 4.3.1.0 I don't find a valid reason in the server logs for why it suddently started crashing... and decided to simply use that moment to move to a new jail with the offical Plugin on Version 4.4.3.0 installed, but I can't find a way to force trigger a Server Backup using the Server Backup plugin. I don't wanna wait 12+ hours to maybe get a backup. Isn't there a trigger button for that and if not, why? (Yes I am premiere user) I attached the Server Log, maybe you see the crash reason (but I'd prefer just migrating to a new Jail) embyserver.txt
-
Noticed something as of late, when trying to play videos through Roku they will 'cycle' through as though they're going to play then it will immediately crash the Emby app and then go right back to the Roku homescreen. It's random, because sometimes it will play the movie that I was just watching and other times it will do this. Roku software version is 9.0.0 build 4084-24, and Emby has been uninstalled and reinstalled. Sometimes restarting of the Roku fixes the issue. Anyone else experience this? I can do a debug log and send it if need be just need to enable Emby debug on the Roku and pull from there.
-
Hello, I picked up a new Android Box and set up Kodi and am trying to Emby for Kodi sync add-on and while it syncs the server will turn off. Kodi is a fresh install, I added the Sync via the repository. Then i allowed it to sync all of my media, it adds my movies and TV and crash some where between my TV shows and my Music. I have had to turn on my server 4 times tonight, and with kodi trying to sync it will crash in 20 minutes. embyserver.txt embyserver-63676182309.txt embyserver-63676182777.txt
-
Hello everyone. Having some issues with my Emby Server Version 3.2.16.0. I have a Roku that I push all of my media to and just recently the emby app hasn't been working. I've figured out that every time i can not play something i have to come upstairs because my Emby Server app has stopped running and I have to manually start the process again. I've attached the error log file with this that i got from http://localhost:8096/web/log.html - If anyone needs a ny more logs to have a look at please let me know. Emby Log.txt
- 37 replies
-
- emby server
- server
- (and 4 more)
-
Server lasts a few minutes before crashing and requiring a manual start. Been working fine and I haven't altered anything recently. Somewhat inept at reading logs so could anyone tell me what's causing it? Thanks in advance. EDIT: Currently been up for around 30 minutes without crashing, perhaps solved itself. System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer. ---> System.Net.Sockets.SocketException: Connection reset by peer --- End of inner exception stack trace --- at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.GetResult(Int16 token) at System.Net.FixedSizeReader.ReadPacketAsync(Stream transport, AsyncProtocolRequest request) at System.Net.Security.SslState.ThrowIfExceptional() at System.Net.Security.SslState.CheckThrow(Boolean authSuccessCheck, Boolean shutdownCheck) at System.Net.Security.SslState.CheckOldKeyDecryptedData(Memory`1 buffer) at System.Net.Security.SslState.HandleQueuedCallback(Object& queuedStateRequest) at System.Net.Security.SslState.FinishHandshakeRead(Int32 newState) at System.Net.Security.SslState.FinishHandshake(Exception e, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.RehandshakeCompleteCallback(IAsyncResult result) at System.Net.LazyAsyncResult.Complete(IntPtr userToken) at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken) at System.Net.AsyncProtocolRequest.CompleteUserWithError(Exception e) at System.Net.FixedSizeReader.ReadPacketAsync(Stream transport, AsyncProtocolRequest request) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location where exception was thrown --- at System.Threading.ThreadPoolWorkQueue.Dispatch() System.IO.IOException at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.GetResult(Int16 token) at System.Net.FixedSizeReader.ReadPacketAsync(Stream transport, AsyncProtocolRequest request) at System.Net.Security.SslState.ThrowIfExceptional() at System.Net.Security.SslState.CheckThrow(Boolean authSuccessCheck, Boolean shutdownCheck) at System.Net.Security.SslState.CheckOldKeyDecryptedData(Memory`1 buffer) at System.Net.Security.SslState.HandleQueuedCallback(Object& queuedStateRequest) at System.Net.Security.SslState.FinishHandshakeRead(Int32 newState) at System.Net.Security.SslState.FinishHandshake(Exception e, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.RehandshakeCompleteCallback(IAsyncResult result) at System.Net.LazyAsyncResult.Complete(IntPtr userToken) at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken) at System.Net.AsyncProtocolRequest.CompleteUserWithError(Exception e) at System.Net.FixedSizeReader.ReadPacketAsync(Stream transport, AsyncProtocolRequest request) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location where exception was thrown --- at System.Threading.ThreadPoolWorkQueue.Dispatch() InnerException: System.Net.Sockets.SocketException System.Net.Sockets.SocketException (104): Connection reset by peer 2018-07-28 13:50:47.091 Info Main: Application path: /opt/emby-server/system/EmbyServer.dll 2018-07-28 13:50:47.099 Info Main: Emby Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb Operating system: Unix 4.15.0.24 64-Bit OS: True 64-Bit Process: True User Interactive: True Processor count: 6 Program data path: /var/lib/emby Application directory: /opt/emby-server/system 2018-07-28 13:50:47.307 Info App: Application version: 3.6.0.2 2018-07-28 13:50:47.308 Info App: Loading assemblies 2018-07-28 13:50:47.330 Info App: File /var/lib/emby/plugins/Emby.Server.CinemaMode.dll has version 1.0.2.0 2018-07-28 13:50:47.330 Info App: File /opt/emby-server/system/plugins/Emby.Server.CinemaMode.dll has version 1.0.2.0 2018-07-28 13:50:47.330 Info App: File /var/lib/emby/plugins/OpenSubtitles.dll has version 1.0.2.0 2018-07-28 13:50:47.330 Info App: File /opt/emby-server/system/plugins/OpenSubtitles.dll has version 1.0.2.0 2018-07-28 13:50:47.330 Info App: File /var/lib/emby/plugins/IMVDb.dll has version 1.0.1.0 2018-07-28 13:50:47.330 Info App: File /opt/emby-server/system/plugins/IMVDb.dll has version 1.0.1.0 2018-07-28 13:50:47.342 Info App: Loading Emby.Server.CinemaMode, Version=1.0.2.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.Server.CinemaMode.dll 2018-07-28 13:50:47.342 Info App: Loading PodCasts, Version=1.1.4.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/PodCasts.dll 2018-07-28 13:50:47.342 Info App: Loading OpenSubtitles, Version=1.0.2.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/OpenSubtitles.dll 2018-07-28 13:50:47.342 Info App: Loading IMVDb, Version=1.0.1.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/IMVDb.dll 2018-07-28 13:50:47.342 Info App: Loading MediaBrowser.Plugins.Anime, Version=1.2.8.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/MediaBrowser.Plugins.Anime.dll 2018-07-28 13:50:47.342 Info App: Loading MBBackup, Version=1.2.3.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/MBBackup.dll 2018-07-28 13:50:47.342 Info App: Loading Lastfm, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Lastfm.dll 2018-07-28 13:50:47.342 Info App: Loading statistics, Version=2.0.5.1, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Statistics.dll 2018-07-28 13:50:47.342 Info App: Loading AutoBoxSets, Version=1.1.3.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/AutoBoxSets.dll 2018-07-28 13:50:47.342 Info App: Loading MediaBrowser.Api, Version=3.6.0.2, Culture=neutral, PublicKeyToken=null 2018-07-28 13:50:47.342 Info App: Loading MediaBrowser.WebDashboard, Version=3.6.0.2, Culture=neutral, PublicKeyToken=null 2018-07-28 13:50:47.342 Info App: Loading MediaBrowser.Model, Version=3.6.0.2, Culture=neutral, PublicKeyToken=null 2018-07-28 13:50:47.342 Info App: Loading MediaBrowser.Common, Version=3.6.0.2, Culture=neutral, PublicKeyToken=null 2018-07-28 13:50:47.342 Info App: Loading MediaBrowser.Controller, Version=3.6.0.2, Culture=neutral, PublicKeyToken=null 2018-07-28 13:50:47.342 Info App: Loading MediaBrowser.Providers, Version=3.6.0.2, Culture=neutral, PublicKeyToken=null 2018-07-28 13:50:47.342 Info App: Loading Emby.Photos, Version=3.6.0.2, Culture=neutral, PublicKeyToken=null 2018-07-28 13:50:47.342 Info App: Loading Emby.Server.Implementations, Version=3.6.0.2, Culture=neutral, PublicKeyToken=null 2018-07-28 13:50:47.342 Info App: Loading Emby.Server.MediaEncoding, Version=3.6.0.2, Culture=neutral, PublicKeyToken=null 2018-07-28 13:50:47.342 Info App: Loading Emby.Dlna, Version=3.6.0.2, Culture=neutral, PublicKeyToken=null 2018-07-28 13:50:47.342 Info App: Loading MediaBrowser.LocalMetadata, Version=3.6.0.2, Culture=neutral, PublicKeyToken=null 2018-07-28 13:50:47.342 Info App: Loading Emby.Notifications, Version=3.6.0.2, Culture=neutral, PublicKeyToken=null 2018-07-28 13:50:47.342 Info App: Loading MediaBrowser.XbmcMetadata, Version=3.6.0.2, Culture=neutral, PublicKeyToken=null 2018-07-28 13:50:47.342 Info App: Loading Emby.Server.Connect, Version=3.6.0.2, Culture=neutral, PublicKeyToken=null 2018-07-28 13:50:47.342 Info App: Loading Emby.Server.Sync, Version=3.6.0.2, Culture=neutral, PublicKeyToken=null 2018-07-28 13:50:47.500 Info SqliteUserRepository: Sqlite version: 3.24.0 2018-07-28 13:50:47.501 Info SqliteUserRepository: Sqlite compiler options: COMPILER=gcc-6.3.0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS5,ENABLE_JSON1,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_UNLOCK_NOTIFY,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MAX_SCHEMA_RETRY=25,MAX_VARIABLE_NUMBER=250000,OMIT_LOOKASIDE,SECURE_DELETE,THREADSAFE=1 2018-07-28 13:50:47.532 Info SqliteUserRepository: Default journal_mode for /var/lib/emby/data/users.db is wal 2018-07-28 13:50:47.534 Info SqliteUserRepository: PRAGMA synchronous=1 2018-07-28 13:50:47.549 Info AuthenticationRepository: Default journal_mode for /var/lib/emby/data/authentication.db is wal 2018-07-28 13:50:47.549 Info AuthenticationRepository: PRAGMA synchronous=1 2018-07-28 13:50:47.640 Info ActivityRepository: Default journal_mode for /var/lib/emby/data/activitylog.db is wal 2018-07-28 13:50:47.640 Info ActivityRepository: PRAGMA synchronous=1 2018-07-28 13:50:47.645 Info SqliteDisplayPreferencesRepository: Default journal_mode for /var/lib/emby/data/displaypreferences.db is wal 2018-07-28 13:50:47.645 Info SqliteDisplayPreferencesRepository: PRAGMA synchronous=1 2018-07-28 13:50:47.759 Debug XmlSerializer: Deserializing file /var/lib/emby/config/users/3e1877189f324bf39c09d62a15459328/policy.xml 2018-07-28 13:50:47.808 Info SqliteItemRepository: Default journal_mode for /var/lib/emby/data/library.db is wal 2018-07-28 13:50:47.809 Info SqliteItemRepository: PRAGMA synchronous=1 2018-07-28 13:50:47.897 Debug XmlSerializer: Deserializing file /var/lib/emby/config/encoding.xml 2018-07-28 13:50:48.005 Info HttpServer: Calling ServiceStack AppHost.Init 2018-07-28 13:50:48.539 Info HttpServer: Adding HttpListener prefix http://+:8096/ 2018-07-28 13:50:48.540 Info HttpServer: Adding HttpListener prefix https://+:8920/ 2018-07-28 13:50:48.845 Info Skia: SkiaSharp version: 1.60.0.0 2018-07-28 13:50:48.876 Info TaskManager: Daily trigger for Configuration Backup set to fire at 7/29/18 12:10:00 AM, which is 619.185401336667 minutes from now. 2018-07-28 13:50:48.908 Info TaskManager: Daily trigger for Calculate statistics for all users set to fire at 7/29/18 5:00:00 AM, which is 909.184861465 minutes from now. 2018-07-28 13:50:48.912 Info TaskManager: Daily trigger for Chapter image extraction set to fire at 7/29/18 2:00:00 AM, which is 729.184800156667 minutes from now. 2018-07-28 13:50:48.917 Info TaskManager: Daily trigger for Rotate log file set to fire at 7/29/18 12:00:00 AM, which is 609.18470195 minutes from now. 2018-07-28 13:50:48.923 Info MediaEncoder: FFMpeg: /opt/emby-server/bin/ffmpeg 2018-07-28 13:50:48.923 Info MediaEncoder: FFProbe: /opt/emby-server/bin/ffprobe 2018-07-28 13:50:48.923 Info MediaEncoder: Validating media encoder at /opt/emby-server/bin/ffmpeg 2018-07-28 13:50:48.926 Info MediaEncoder: Running /opt/emby-server/bin/ffmpeg -decoders 2018-07-28 13:50:48.985 Info MediaEncoder: Decoder available: mpeg2video 2018-07-28 13:50:48.990 Info MediaEncoder: Decoder available: h264_cuvid 2018-07-28 13:50:48.990 Info MediaEncoder: Decoder available: hevc_cuvid 2018-07-28 13:50:48.990 Info MediaEncoder: Decoder available: mpeg2_cuvid 2018-07-28 13:50:48.991 Info MediaEncoder: Decoder available: mpeg4_cuvid 2018-07-28 13:50:48.991 Info MediaEncoder: Decoder available: vc1_cuvid 2018-07-28 13:50:48.991 Info MediaEncoder: Decoder available: vp8_cuvid 2018-07-28 13:50:48.991 Info MediaEncoder: Decoder available: vp9_cuvid 2018-07-28 13:50:48.996 Info MediaEncoder: Decoder available: ac3 2018-07-28 13:50:48.996 Info MediaEncoder: Decoder available: aac 2018-07-28 13:50:48.997 Info MediaEncoder: Decoder available: mp3 2018-07-28 13:50:48.997 Info MediaEncoder: Decoder available: h264 2018-07-28 13:50:48.997 Info MediaEncoder: Decoder available: hevc 2018-07-28 13:50:49.002 Info MediaEncoder: Running /opt/emby-server/bin/ffmpeg -encoders 2018-07-28 13:50:49.055 Info MediaEncoder: Encoder available: libx264 2018-07-28 13:50:49.055 Info MediaEncoder: Encoder available: mpeg4 2018-07-28 13:50:49.055 Info MediaEncoder: Encoder available: msmpeg4 2018-07-28 13:50:49.057 Info MediaEncoder: Encoder available: aac 2018-07-28 13:50:49.057 Info MediaEncoder: Encoder available: libmp3lame 2018-07-28 13:50:49.057 Info MediaEncoder: Encoder available: libopus 2018-07-28 13:50:49.057 Info MediaEncoder: Encoder available: libvorbis 2018-07-28 13:50:49.058 Info MediaEncoder: Encoder available: srt 2018-07-28 13:50:49.058 Info MediaEncoder: Encoder available: h264_nvenc 2018-07-28 13:50:49.058 Info MediaEncoder: Encoder available: hevc_nvenc 2018-07-28 13:50:49.061 Info MediaEncoder: Encoder available: h264_vaapi 2018-07-28 13:50:49.061 Info MediaEncoder: Encoder available: hevc_vaapi 2018-07-28 13:50:49.061 Info MediaEncoder: Encoder available: h264_v4l2m2m 2018-07-28 13:50:49.061 Info MediaEncoder: Encoder available: libwebp 2018-07-28 13:50:49.061 Info MediaEncoder: Encoder available: ac3 2018-07-28 13:50:49.063 Info MediaEncoder: Running /opt/emby-server/bin/ffmpeg -protocols 2018-07-28 13:50:49.111 Info MediaEncoder: Encoder validation complete 2018-07-28 13:50:49.111 Info MediaEncoder: ffmpeg supported protocols: async,cache,concat,crypto,data,ffrtmphttp,file,ftp,gopher,hls,http,httpproxy,https,mmsh,mmst,pipe,rtmp,rtmps,rtmpt,rtmpts,rtp,srtp,subfile,tcp,tls,udp,udplite,unix,smb 2018-07-28 13:50:49.113 Info App: ServerId: b2136b5f44634897ad34c3300667d1cc 2018-07-28 13:50:49.184 Info App: Starting entry point MediaBrowser.WebDashboard.ServerEntryPoint 2018-07-28 13:50:49.186 Info App: Entry point completed: MediaBrowser.WebDashboard.ServerEntryPoint. Duration: 0.0015308 seconds 2018-07-28 13:50:49.186 Info App: Starting entry point Emby.Dlna.Main.DlnaEntryPoint 2018-07-28 13:50:49.193 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Sony Bravia (2012).xml 2018-07-28 13:50:49.300 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/foobar2000.xml 2018-07-28 13:50:49.300 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Sony Bravia (2014).xml 2018-07-28 13:50:49.301 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Sony Bravia (2013).xml 2018-07-28 13:50:49.302 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Sony PlayStation 3.xml 2018-07-28 13:50:49.302 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/DirecTV HD-DVR.xml 2018-07-28 13:50:49.303 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/MediaMonkey.xml 2018-07-28 13:50:49.303 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Sony Blu-ray Player 2013.xml 2018-07-28 13:50:49.304 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Marantz.xml 2018-07-28 13:50:49.304 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Denon AVR.xml 2018-07-28 13:50:49.305 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Sony PlayStation 4.xml 2018-07-28 13:50:49.305 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Sony Blu-ray Player 2016.xml 2018-07-28 13:50:49.306 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Sony Blu-ray Player.xml 2018-07-28 13:50:49.307 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Dish Hopper-Joey.xml 2018-07-28 13:50:49.307 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Linksys DMA2100.xml 2018-07-28 13:50:49.308 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Panasonic Viera.xml 2018-07-28 13:50:49.308 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Popcorn Hour.xml 2018-07-28 13:50:49.309 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/LG Smart TV.xml 2018-07-28 13:50:49.309 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Sony Blu-ray Player 2015.xml 2018-07-28 13:50:49.310 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Sony Bravia (2010).xml 2018-07-28 13:50:49.311 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/WDTV Live.xml 2018-07-28 13:50:49.311 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Sony Bravia (2011).xml 2018-07-28 13:50:49.312 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Default.xml 2018-07-28 13:50:49.312 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Samsung Smart TV.xml 2018-07-28 13:50:49.313 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Sharp Smart TV.xml 2018-07-28 13:50:49.314 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Xbox One.xml 2018-07-28 13:50:49.315 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna/system/Sony Blu-ray Player 2014.xml 2018-07-28 13:50:49.316 Debug XmlSerializer: Deserializing file /var/lib/emby/config/dlna.xml 2018-07-28 13:50:49.414 Info App: Entry point completed: Emby.Dlna.Main.DlnaEntryPoint. Duration: 0.2284628 seconds 2018-07-28 13:50:49.414 Info App: Starting entry point Emby.Server.Connect.ConnectEntryPoint 2018-07-28 13:50:49.416 Info App: Loading data from /var/lib/emby/data/connect.txt 2018-07-28 13:50:49.424 Info App: Loading data from /var/lib/emby/data/wan.dat 2018-07-28 13:50:49.432 Info App: Entry point completed: Emby.Server.Connect.ConnectEntryPoint. Duration: 0.0178785 seconds 2018-07-28 13:50:49.432 Info App: Core startup complete 2018-07-28 13:50:49.432 Info App: Post-init migrations complete 2018-07-28 13:50:49.432 Info App: Starting entry point Emby.Security.PluginSecurityManager 2018-07-28 13:50:49.432 Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 4.03E-05 seconds 2018-07-28 13:50:49.432 Info App: Starting entry point Emby.Server.CinemaMode.IntrosEntryPoint 2018-07-28 13:50:49.433 Info App: Entry point completed: Emby.Server.CinemaMode.IntrosEntryPoint. Duration: 0.0004143 seconds 2018-07-28 13:50:49.433 Info App: Starting entry point Emby.Security.PluginSecurityManager 2018-07-28 13:50:49.433 Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 4.05E-05 seconds 2018-07-28 13:50:49.433 Info App: Starting entry point Emby.Security.PluginSecurityManager 2018-07-28 13:50:49.433 Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 5.61E-05 seconds 2018-07-28 13:50:49.433 Info App: Starting entry point MBBackup.ServerEntryPoint 2018-07-28 13:50:49.433 Info App: Entry point completed: MBBackup.ServerEntryPoint. Duration: 3.18E-05 seconds 2018-07-28 13:50:49.433 Info App: Starting entry point Lastfm.ServerEntryPoint 2018-07-28 13:50:49.434 Info App: Entry point completed: Lastfm.ServerEntryPoint. Duration: 0.0007245 seconds 2018-07-28 13:50:49.434 Info App: Starting entry point AutoBoxSets.ServerEntryPoint 2018-07-28 13:50:49.436 Debug XmlSerializer: Deserializing file /var/lib/emby/plugins/configurations/AutoBoxSets.xml 2018-07-28 13:50:49.444 Info App: Entry point completed: AutoBoxSets.ServerEntryPoint. Duration: 0.0106408 seconds 2018-07-28 13:50:49.444 Info App: Starting entry point MediaBrowser.Api.ApiEntryPoint 2018-07-28 13:50:49.445 Info App: Entry point completed: MediaBrowser.Api.ApiEntryPoint. Duration: 0.00014 seconds 2018-07-28 13:50:49.445 Info App: Starting entry point Emby.Server.Implementations.News.NewsEntryPoint 2018-07-28 13:50:49.445 Info App: Entry point completed: Emby.Server.Implementations.News.NewsEntryPoint. Duration: 0.0003496 seconds 2018-07-28 13:50:49.445 Info App: Starting entry point Emby.Server.Implementations.LiveTv.EmbyTV.EntryPoint 2018-07-28 13:50:49.449 Info App: Loading live tv data from /var/lib/emby/data/livetv/timers 2018-07-28 13:50:49.459 Debug XmlSerializer: Deserializing file /var/lib/emby/config/livetv.xml 2018-07-28 13:50:49.533 Debug App: Ping test result to http://192.168.1.53:8096/system/ping. Success: True 2018-07-28 13:50:49.536 Debug App: Ping test result to http://192.168.1.53:8096/system/ping. Success: True 2018-07-28 13:50:49.537 Info Dlna: Registering publisher for urn:schemas-upnp-org:device:MediaServer:1 on 192.168.1.53 2018-07-28 13:50:49.629 Debug XmlSerializer: Deserializing file /var/lib/emby/root/default/FILM/options.xml 2018-07-28 13:50:49.683 Debug XmlSerializer: Deserializing file /var/lib/emby/root/default/Collections/options.xml 2018-07-28 13:50:49.684 Debug XmlSerializer: Deserializing file /var/lib/emby/root/default/LIVE/options.xml 2018-07-28 13:50:49.684 Debug XmlSerializer: Deserializing file /var/lib/emby/root/default/AUDIOBOOKS/options.xml 2018-07-28 13:50:49.684 Debug XmlSerializer: Deserializing file /var/lib/emby/root/default/MUSIC/options.xml 2018-07-28 13:50:49.689 Debug XmlSerializer: Deserializing file /var/lib/emby/root/default/TELEVISION/options.xml 2018-07-28 13:50:49.691 Info App: Entry point completed: Emby.Server.Implementations.LiveTv.EmbyTV.EntryPoint. Duration: 0.246232 seconds 2018-07-28 13:50:49.691 Info App: Starting entry point Emby.Server.Implementations.Library.DeviceAccessEntryPoint 2018-07-28 13:50:49.692 Info App: Entry point completed: Emby.Server.Implementations.Library.DeviceAccessEntryPoint. Duration: 0.0004407 seconds 2018-07-28 13:50:49.692 Info App: Starting entry point Emby.Server.Implementations.IO.LibraryMonitorStartup 2018-07-28 13:50:49.721 Info App: Entry point completed: Emby.Server.Implementations.IO.LibraryMonitorStartup. Duration: 0.0293442 seconds 2018-07-28 13:50:49.726 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint 2018-07-28 13:50:49.727 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint. Duration: 0.0009701 seconds 2018-07-28 13:50:49.727 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ExternalPortForwarding 2018-07-28 13:50:49.728 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ExternalPortForwarding. Duration: 0.00087 seconds 2018-07-28 13:50:49.728 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.KeepServerAwake 2018-07-28 13:50:49.728 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.KeepServerAwake. Duration: 0.0004245 seconds 2018-07-28 13:50:49.728 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier 2018-07-28 13:50:49.730 Info LibraryMonitor: Watching directory /media/plex/MEDIA 2/MEDIA/MUSIC/LIVE 2018-07-28 13:50:49.730 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier. Duration: 0.0021577 seconds 2018-07-28 13:50:49.730 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.RecordingNotifier 2018-07-28 13:50:49.732 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.RecordingNotifier. Duration: 0.0014267 seconds 2018-07-28 13:50:49.732 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ServerEventNotifier 2018-07-28 13:50:49.735 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ServerEventNotifier. Duration: 0.0030831 seconds 2018-07-28 13:50:49.735 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.StartupWizard 2018-07-28 13:50:49.736 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.StartupWizard. Duration: 0.0009777 seconds 2018-07-28 13:50:49.736 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.SystemEvents 2018-07-28 13:50:49.737 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.SystemEvents. Duration: 0.000376 seconds 2018-07-28 13:50:49.737 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UdpServerEntryPoint 2018-07-28 13:50:49.739 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UdpServerEntryPoint. Duration: 0.0021698 seconds 2018-07-28 13:50:49.739 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UsageEntryPoint 2018-07-28 13:50:49.740 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UsageEntryPoint. Duration: 0.0008534 seconds 2018-07-28 13:50:49.740 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier 2018-07-28 13:50:49.740 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier. Duration: 0.0001533 seconds 2018-07-28 13:50:49.740 Info App: Starting entry point Emby.Server.Implementations.Devices.DeviceManagerEntryPoint 2018-07-28 13:50:49.741 Info App: Entry point completed: Emby.Server.Implementations.Devices.DeviceManagerEntryPoint. Duration: 0.0011762 seconds 2018-07-28 13:50:49.741 Info App: Starting entry point Emby.Server.Implementations.Collections.CollectionManagerEntryPoint 2018-07-28 13:50:49.742 Info App: Entry point completed: Emby.Server.Implementations.Collections.CollectionManagerEntryPoint. Duration: 0.0012759 seconds 2018-07-28 13:50:49.742 Info App: Starting entry point Emby.Server.Implementations.Activity.ActivityLogEntryPoint 2018-07-28 13:50:49.746 Info App: Entry point completed: Emby.Server.Implementations.Activity.ActivityLogEntryPoint. Duration: 0.0032054 seconds 2018-07-28 13:50:49.746 Info App: Starting entry point Emby.Server.MediaEncoding.Api.ApiEntryPoint 2018-07-28 13:50:49.747 Info App: Entry point completed: Emby.Server.MediaEncoding.Api.ApiEntryPoint. Duration: 0.00097 seconds 2018-07-28 13:50:49.747 Info App: Starting entry point Emby.Notifications.Notifications 2018-07-28 13:50:49.747 Info App: Entry point completed: Emby.Notifications.Notifications. Duration: 0.0005609 seconds 2018-07-28 13:50:49.747 Info App: Starting entry point MediaBrowser.XbmcMetadata.EntryPoint 2018-07-28 13:50:49.747 Info App: Entry point completed: MediaBrowser.XbmcMetadata.EntryPoint. Duration: 0.0001676 seconds 2018-07-28 13:50:49.747 Info App: Starting entry point Emby.Security.PluginSecurityManager 2018-07-28 13:50:49.748 Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 5.13E-05 seconds 2018-07-28 13:50:49.748 Info App: Starting entry point Emby.Server.Sync.SyncManagerEntryPoint 2018-07-28 13:50:49.754 Info App: Sqlite version: 3.24.0 2018-07-28 13:50:49.754 Info App: Sqlite compiler options: COMPILER=gcc-6.3.0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS5,ENABLE_JSON1,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_UNLOCK_NOTIFY,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MAX_SCHEMA_RETRY=25,MAX_VARIABLE_NUMBER=250000,OMIT_LOOKASIDE,SECURE_DELETE,THREADSAFE=1 2018-07-28 13:50:49.755 Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal 2018-07-28 13:50:49.756 Info App: PRAGMA synchronous=1 2018-07-28 13:50:49.757 Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0097477 seconds 2018-07-28 13:50:49.757 Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint 2018-07-28 13:50:49.759 Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0014429 seconds 2018-07-28 13:50:49.759 Info App: All entry points have started 2018-07-28 13:50:49.862 Info LibraryMonitor: Watching directory /media/plex/MEDIA 1/MEDIA/TV SHOWS/720x265 2018-07-28 13:50:49.881 Info LibraryMonitor: Watching directory /media/plex/MEDIA 1/MEDIA/TV SHOWS/MIXED 2018-07-28 13:50:49.894 Info LibraryMonitor: Watching directory /media/plex/MEDIA 3/MEDIA/FILM/4K 2018-07-28 13:50:49.963 Info LibraryMonitor: Watching directory /media/plex/MEDIA 1/MEDIA/TV SHOWS/1080x265 2018-07-28 13:50:49.969 Info HttpClient: GET https://emby.media/community/index.php?/blog/rss/1-media-browser-developers-blog 2018-07-28 13:50:50.002 Info LibraryMonitor: Watching directory /media/plex/MEDIA 3/MEDIA/FILM/MIXED 2018-07-28 13:50:50.005 Info LibraryMonitor: Watching directory /media/plex/MEDIA 3/MEDIA/TV/4K 2018-07-28 13:50:50.008 Info LibraryMonitor: Watching directory /media/plex/MEDIA 3/MEDIA/TV/1080x265 2018-07-28 13:50:50.060 Info LibraryMonitor: Watching directory /media/plex/MEDIA 2/MEDIA/AUDIOBOOKS/ENGELSKA 2018-07-28 13:50:50.074 Info LibraryMonitor: Watching directory /media/plex/MEDIA 2/MEDIA/TV SHOWS/1080x265 2018-07-28 13:50:50.127 Info LibraryMonitor: Watching directory /media/plex/MEDIA 3/MEDIA/FILM/1080x265 2018-07-28 13:50:50.344 Info LibraryMonitor: Watching directory /media/plex/MEDIA 2/MEDIA/MUSIC/ARTISTS 2018-07-28 13:50:51.893 Info HttpServer: HTTP GET http://192.168.1.53:8096/web/strings/en-GB.json?v=1532778653047. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:51.893 Info HttpServer: HTTP GET http://192.168.1.53:8096/web/bower_components/emby-webcomponents/strings/en-gb.json?v=1532778653047. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:51.893 Info HttpServer: HTTP GET http://192.168.1.53:8096/web/favicon.ico. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:51.903 Debug HttpResultFactory: Transmit file /opt/emby-server/system/dashboard-ui/strings/en-GB.json 2018-07-28 13:50:51.903 Debug HttpResultFactory: Transmit file /opt/emby-server/system/dashboard-ui/favicon.ico 2018-07-28 13:50:51.903 Debug HttpResultFactory: Transmit file /opt/emby-server/system/dashboard-ui/bower_components/emby-webcomponents/strings/en-gb.json 2018-07-28 13:50:51.909 Info HttpServer: HTTP Response 200 to 192.168.1.61. Time: 16ms. http://192.168.1.53:8096/web/favicon.ico 2018-07-28 13:50:51.909 Info HttpServer: HTTP Response 200 to 192.168.1.61. Time: 19ms. http://192.168.1.53:8096/web/bower_components/emby-webcomponents/strings/en-gb.json?v=1532778653047 2018-07-28 13:50:51.909 Info HttpServer: HTTP Response 200 to 192.168.1.61. Time: 20ms. http://192.168.1.53:8096/web/strings/en-GB.json?v=1532778653047 2018-07-28 13:50:51.914 Info TaskManager: StartupTrigger fired for task: Check for plugin updates 2018-07-28 13:50:51.916 Info TaskManager: StartupTrigger fired for task: Check for application updates 2018-07-28 13:50:51.916 Info TaskManager: Queueing task PluginUpdateTask 2018-07-28 13:50:51.916 Info TaskManager: Queueing task SystemUpdateTask 2018-07-28 13:50:51.941 Info TaskManager: Executing Check for plugin updates 2018-07-28 13:50:51.941 Info TaskManager: Executing Check for application updates 2018-07-28 13:50:51.951 Info HttpClient: GET https://www.mb3admin.com/admin/service/EmbyPackages.json 2018-07-28 13:50:52.023 Debug App: No application update available. 2018-07-28 13:50:52.024 Info TaskManager: Check for application updates Completed after 0 minute(s) and 0 seconds 2018-07-28 13:50:52.041 Info TaskManager: ExecuteQueuedTasks 2018-07-28 13:50:52.072 Debug XmlSerializer: Deserializing file /var/lib/emby/config/branding.xml 2018-07-28 13:50:52.187 Info HttpServer: HTTP GET http://192.168.1.53:8096/emby/system/info/public. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:52.201 Info HttpServer: HTTP Response 200 to 192.168.1.61. Time: 14ms. http://192.168.1.53:8096/emby/system/info/public 2018-07-28 13:50:52.204 Info HttpServer: HTTP GET http://192.168.1.53:8096/emby/System/Info. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:52.316 Info App: App Activity: app: Emby Mobile, version: 3.6.0.2, deviceId: TW96aWxsYS81LjAgKFdpbmRvd3MgTlQgMTAuMDsgV2luNjQ7IHg2NCkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzY3LjAuMzM5Ni45OSBTYWZhcmkvNTM3LjM2fDE1MzI3Nzc0NDE5NjY1, deviceName: Chrome 2018-07-28 13:50:52.346 Debug XmlSerializer: Deserializing file /var/lib/emby/config/users/3e1877189f324bf39c09d62a15459328/config.xml 2018-07-28 13:50:52.400 Info HttpServer: HTTP Response 200 to 192.168.1.61. Time: 196ms. http://192.168.1.53:8096/emby/System/Info 2018-07-28 13:50:52.406 Info HttpServer: HTTP POST http://192.168.1.53:8096/emby/Sessions/Capabilities/Full. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:52.408 Info HttpServer: HTTP GET http://192.168.1.53:8096/emby/Users/3e1877189f324bf39c09d62a15459328. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:52.408 Info HttpServer: HTTP GET http://192.168.1.53:8096/emby/DisplayPreferences/usersettings?userId=3e1877189f324bf39c09d62a15459328&client=emby. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:52.414 Info HttpServer: WS http://192.168.1.53:8096/embywebsocket?api_key=87f329c23e8e435eac062530dd41c169&deviceId=TW96aWxsYS81LjAgKFdpbmRvd3MgTlQgMTAuMDsgV2luNjQ7IHg2NCkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzY3LjAuMzM5Ni45OSBTYWZhcmkvNTM3LjM2fDE1MzI3Nzc0NDE5NjY1. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:52.422 Debug HttpServer: Web socket connection allowed 2018-07-28 13:50:52.445 Debug SessionManager: Creating new WebSocketController 2018-07-28 13:50:52.472 Info HttpServer: HTTP Response 200 to 192.168.1.61. Time: 64ms. http://192.168.1.53:8096/emby/DisplayPreferences/usersettings?userId=3e1877189f324bf39c09d62a15459328&client=emby 2018-07-28 13:50:52.477 Info HttpServer: HTTP Response 200 to 192.168.1.61. Time: 69ms. http://192.168.1.53:8096/emby/Users/3e1877189f324bf39c09d62a15459328 2018-07-28 13:50:52.479 Info HttpServer: HTTP GET http://192.168.1.53:8096/emby/Users/3e1877189f324bf39c09d62a15459328. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:52.480 Info HttpServer: HTTP Response 200 to 192.168.1.61. Time: 1ms. http://192.168.1.53:8096/emby/Users/3e1877189f324bf39c09d62a15459328 2018-07-28 13:50:52.482 Info HttpServer: HTTP GET http://192.168.1.53:8096/emby/Users/3e1877189f324bf39c09d62a15459328. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:52.484 Info HttpServer: HTTP Response 200 to 192.168.1.61. Time: 1ms. http://192.168.1.53:8096/emby/Users/3e1877189f324bf39c09d62a15459328 2018-07-28 13:50:52.502 Info HttpServer: HTTP Response 204 to 192.168.1.61. Time: 97ms. http://192.168.1.53:8096/emby/Sessions/Capabilities/Full 2018-07-28 13:50:52.512 Info HttpServer: HTTP GET http://192.168.1.53:8096/emby/web/configurationpages?pageType=PluginConfiguration&EnableInMainMenu=true. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:52.515 Info HttpServer: HTTP GET http://192.168.1.53:8096/emby/Plugins. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:52.527 Info HttpClient: GET https://www.mb3admin.com/admin/service/EmbyPackages.json 2018-07-28 13:50:52.552 Info HttpServer: HTTP Response 200 to 192.168.1.61. Time: 39ms. http://192.168.1.53:8096/emby/web/configurationpages?pageType=PluginConfiguration&EnableInMainMenu=true 2018-07-28 13:50:52.562 Info HttpServer: HTTP GET http://192.168.1.53:8096/web/css/images/logoblack.png. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:52.563 Info HttpServer: HTTP Response 304 to 192.168.1.61. Time: 1ms. http://192.168.1.53:8096/web/css/images/logoblack.png 2018-07-28 13:50:53.177 Info TaskManager: Check for plugin updates Completed after 0 minute(s) and 1 seconds 2018-07-28 13:50:53.178 Info TaskManager: ExecuteQueuedTasks 2018-07-28 13:50:53.776 Info HttpServer: HTTP Response 200 to 192.168.1.61. Time: 1262ms (slow). http://192.168.1.53:8096/emby/Plugins 2018-07-28 13:50:53.780 Info HttpServer: HTTP GET http://192.168.1.53:8096/emby/web/configurationpages?pageType=PluginConfiguration. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:53.780 Info HttpServer: HTTP Response 200 to 192.168.1.61. Time: 1ms. http://192.168.1.53:8096/emby/web/configurationpages?pageType=PluginConfiguration 2018-07-28 13:50:53.891 Info HttpServer: HTTP GET http://192.168.1.53:8096/emby/System/Configuration. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:53.891 Info HttpServer: HTTP GET http://192.168.1.53:8096/emby/System/Logs. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:53.917 Info HttpServer: HTTP Response 200 to 192.168.1.61. Time: 26ms. http://192.168.1.53:8096/emby/System/Configuration 2018-07-28 13:50:53.919 Info HttpServer: HTTP Response 200 to 192.168.1.61. Time: 29ms. http://192.168.1.53:8096/emby/System/Logs 2018-07-28 13:50:54.548 Debug Dlna: Begin Sending Alive Notifications For All Devices 2018-07-28 13:50:54.561 Debug Dlna: Sent alive notification MediaServer - b2136b5f44634897ad34c3300667d1cc - http://192.168.1.53:8096/dlna/b2136b5f44634897ad34c3300667d1cc/description.xml 2018-07-28 13:50:54.561 Debug Dlna: Sent alive notification MediaServer - b2136b5f44634897ad34c3300667d1cc - http://192.168.1.53:8096/dlna/b2136b5f44634897ad34c3300667d1cc/description.xml 2018-07-28 13:50:54.561 Debug Dlna: Sent alive notification MediaServer - b2136b5f44634897ad34c3300667d1cc - http://192.168.1.53:8096/dlna/b2136b5f44634897ad34c3300667d1cc/description.xml 2018-07-28 13:50:54.561 Debug Dlna: Sent alive notification ContentDirectory - b2136b5f44634897ad34c3300667d1cc 2018-07-28 13:50:54.561 Debug Dlna: Sent alive notification ContentDirectory - b2136b5f44634897ad34c3300667d1cc 2018-07-28 13:50:54.561 Debug Dlna: Sent alive notification ConnectionManager - b2136b5f44634897ad34c3300667d1cc 2018-07-28 13:50:54.561 Debug Dlna: Sent alive notification ConnectionManager - b2136b5f44634897ad34c3300667d1cc 2018-07-28 13:50:54.561 Debug Dlna: Completed Sending Alive Notifications For All Devices 2018-07-28 13:50:56.164 Info HttpServer: HTTP GET http://192.168.1.53:8096/emby/System/Logs/Log?name=unhandled_6f53c478-aabf-40e9-880a-85b041e3aad9.txt. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 2018-07-28 13:50:56.171 Debug HttpResultFactory: Transmit file /var/lib/emby/logs/unhandled_6f53c478-aabf-40e9-880a-85b041e3aad9.txt 2018-07-28 13:50:56.171 Info HttpServer: HTTP Response 200 to 192.168.1.61. Time: 9ms. http://192.168.1.53:8096/emby/System/Logs/Log?name=unhandled_6f53c478-aabf-40e9-880a-85b041e3aad9.txt 2018-07-28 13:50:58.201 Info HttpServer: HTTP GET http://192.168.1.53:8096/emby/System/Logs/Log?name=embyserver.txt. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36
-
Hi, I have an issue with my episodes of South Park, I just added them to my library so this isn't a case of 'they used to work, now they don't', they haven't worked properly as of yet. I either get the 'an error occured loading this content' or it begins to play the episode without sound, then the sound begins around 15 seconds later (in sync) and a few seconds later the whole app crashes. I have attached the log - the latest crash occured at 11:00 / 11:01 but the log doesn't appear to have anything listed after 10:05 on a side note, maybe I'm just being stupid but Emby is no longer saving logs to the programdata > logs folder, the only ones present are from a few months ago
-
I'm running the emby server on my ubuntu 16.04 server. It has worked well a long time. I just did a "service emby-server restart" and I got a crash that looks like this ... $ service emby-server status ● 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: core-dump) since Mon 2018-05-14 19:44:42 PDT; 44s ago Process: 5232 ExecStart=/opt/emby-server/bin/emby-server (code=dumped, signal=ABRT) Main PID: 5232 (code=dumped, signal=ABRT) May 14 19:44:41 server emby-server[5232]: May 14 19:44:41 server emby-server[5232]: Unhandled Exception: System.IO.IOException: The system cannot open the device or fi May 14 19:44:41 server emby-server[5232]: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) May 14 19:44:41 server emby-server[5232]: at System.Threading.Mutex.MutexTryCodeHelper.MutexTryCode(Object userData) May 14 19:44:41 server emby-server[5232]: at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedClean May 14 19:44:41 server emby-server[5232]: at System.Threading.Mutex.CreateMutexWithGuaranteedCleanup(Boolean initiallyOwne May 14 19:44:41 server emby-server[5232]: at EmbyServer.Program.Main(String[] args) May 14 19:44:42 server systemd[1]: emby-server.service: Main process exited, code=dumped, status=6/ABRT May 14 19:44:42 server systemd[1]: emby-server.service: Unit entered failed state. May 14 19:44:42 server systemd[1]: emby-server.service: Failed with result 'core-dump'. I restarted my ubuntu server and the problem remained. I upgraded the emby-server using dpkg (3.3.1.0 -> 3.4.1.0). The problem still remains. I tried unsuccessfully to find my logs. I have no directory "/var/lib/emby-server". The report-a-problem guide doesn't help. What should I try next?
-
Server Crashing When trying to view music by artist via web portal
Epricesc posted a topic in Web App
Per my title: I am at work and trying to listen to music through the web portal. It's fine until I try to sort by artist. No list of artists load on the screen, I just get a spinning circle and then the server crashes. I've had no issues with the other music categories (by song/album). I now have to manually restart EMBY on my server when I get home to get it working again. Anyone have any explanation as to why this is happening? -
Hi All, My Pi3 is crashing on Emby's movie or TV library scan. Emby is not able to finish the activity (usually freezes around 70%) and I even lose SHH connection. To restart I have to unplug Pi. All files are on a ext4 external HDD with it's own power supply. I have performed a long fsck and HDD/data seems OK. I'm running on Version 3.2.19.0 on a clean (new) OSMC install and have used the official instructions to install Emby https://emby.media/c...l-instructions/ . Could anyone please take a look at the attached log? I can't find what's wrong. Log.txt
-
I've noticed that recently Emby has started to crash if I'm selecting somewhat rapidly between movies in my library. I'm by no means an Emby expert, but I have software experience so I checked the log file and found the below: 2017-01-23 07:14:06.4887 Error HttpServer: Error processing request *** Error Report *** Version: 3.1.2.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 4.4.0.59 64-Bit OS: True 64-Bit Process: True Mono: 4.6.2 (Stable 4.6.2.7/08fd525 Mon Nov 28 20:49:26 UTC 2016) Processor count: 8 Program data path: /var/lib/emby-server Application directory: /usr/lib/emby-server/bin System.IO.IOException: Unable to write data to the transport connection: The socket has been shut down. ---> System.Net.Sockets.SocketException: The socket has been shut down at System.Net.Sockets.Socket.EndSend (System.IAsyncResult result) [0x00033] in <bd46d4d4f7964dfa9beea098499ab597>:0 at System.Net.Sockets.NetworkStream.EndWrite (System.IAsyncResult asyncResult) [0x0005f] in <bd46d4d4f7964dfa9beea098499ab597>:0 --- End of inner exception stack trace --- at Mono.Security.Protocol.Tls.SslStreamBase.EndWrite (System.IAsyncResult asyncResult) [0x00057] in <1d0bb82c94e7435eb09324cf5ef20e36>:0 at Mono.Net.Security.Private.LegacySslStream.EndWrite (System.IAsyncResult asyncResult) [0x00006] in <bd46d4d4f7964dfa9beea098499ab597>:0 at Mono.Net.Security.Private.MonoSslStreamImpl.EndWrite (System.IAsyncResult asyncResult) [0x00006] in <bd46d4d4f7964dfa9beea098499ab597>:0 at System.Net.Security.SslStream.EndWrite (System.IAsyncResult asyncResult) [0x00006] in <bd46d4d4f7964dfa9beea098499ab597>:0 at System.IO.Stream.<BeginEndWriteAsync>m__8 (System.IO.Stream stream, System.IAsyncResult asyncResult) [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0 at (wrapper delegate-invoke) System.Func`3[System.IO.Stream,System.IAsyncResult,System.Threading.Tasks.VoidTaskResult]:invoke_TResult_T1_T2 (System.IO.Stream,System.IAsyncResult) at System.Threading.Tasks.TaskFactory`1+FromAsyncTrimPromise`1[TResult,TInstance].Complete (TInstance thisRef, System.Func`3[T1,T2,TResult] endMethod, System.IAsyncResult asyncResult, System.Boolean requiresSynchronization) [0x00002] in <8f2c484307284b51944a1a13a14c0266>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <8f2c484307284b51944a1a13a14c0266>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <8f2c484307284b51944a1a13a14c0266>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <8f2c484307284b51944a1a13a14c0266>:0 Is there anything that this error indicates that I could be doing differently to fix the situation? I've just started noticing this recently, and a quick restart of emby-server seems to fix it. But obviously, that is not desired to have to restart the service every 4 movies. Also, if there's anything else to check, please let me know and I'll post it. I'm running Emby on Ubuntu Server 16.04 FYI - ASUS mobo w/ i7-6700k Edit: From looking at other posts, it looks like mono sometimes affects stuff like this, but it looks like I'm running 4.6.2.7 which is not a version that folks have said causes problems. Checking the mono-project website I see 4.6.2.16 is released though, so my next step will be trying to update that. $ mono --version Mono JIT compiler version 4.6.2 (Stable 4.6.2.7/08fd525 Mon Nov 28 20:49:26 UTC 2016)
- 18 replies
-
Emby has been running fine until this noon. I made few changes to the folder and it stopped working. On top bar emby icon comes up, but when i click browse media library it disappears. I deleted the reinstalled app few times but still the same issue, can someone please help me with this issue? Thanks
-
I've tried using Emby for my Roku 3, both version 2.09 and 2.10, and while watching Live TV does work, the stream always continues to stream even long after I've exited the Emby channel on my Roku. Additionally, when I change channels, Emby always opens the live stream on another Tuner instead of the one it was using before. In other words, I have a CableCard and 6 tuners available. I can start a live tv stream in Emby on the Roku, change the channel 5 more times, and I've now consumed all my tuners. Upon changing the channel one more time, no tuners are available and the Emby channel on my Roku crashes. Is anyone else having this issue? It seems the Roku Emby channel is not telling the server to end the stream and stop using the tuner after I stop watching Live TV... I'm using ServerWMC (latest version as of this post), a Ceton InfiniTV 6 (6 channel CableCard tuner), Emby Server on my Windows 7 machine, and my Roku 3 running both the 2.09 and 2.10b of the Emby channel. What's even more interesting: Watching live tv through the Emby web portal always will end the stream and release the tuner once I change the channel/stop watching live tv in the browser. Anyone care to cuss/fuss/discuss?? Thanks!
-
Summary of the random crashing problem on Ubuntu and Debian
thefirstofthe300 posted a topic in Linux
If you are running an Ubuntu or Debian server and mono version 3.10 or older or 4.0 or newer and are experiencing random crashing of Emby with no errors in your logs, you might be experiencing an issue related to a bug in the kernel. Finally one of the Sonarr devs popped in and helped us figure out a possible solution to the problem. (that quote is from http://emby.media/community/index.php?/topic/19955-emby-crashing-ubuntu-server/page-5&do=findComment&comment=207271) Once users started upgrading their kernels to as new as 4.0, they reported that the stability of Emby has greatly improved. Here are some instructions on how to upgrade your kernel without having to do a distro upgrade: http://askubuntu.com/questions/119080/how-to-update-kernel-to-the-latest-mainline-version-without-any-distro-upgrade Also, a few users reported that they were still experiencing crashed even though they weren't running Emby in a VM. Many of them also reported that a kernel upgrade actually fixed their problem. If you are still having issues with Emby crashing after a kernel upgrade and you don't know why, please let us know.- 5 replies
-
- 4
-
- random
- random-crashing
-
(and 3 more)
Tagged with:
-
after upgrade to new Emby server WMC starting crashing i have updated the WMC app to the latest release and its crashing. firstly; After the new pic update it cause a crash when you go in to the show and it has to rebuild the tumbs it crashes and you have to load wmc back up and go in to the show and then you will see the season thumbs. Secondly if your watching a show it just crashes you reload wmc and the same show and it works. I don't know what is going on behind the scenes but something is not quite right. This is a fresh install(just did it to see if that was the issue). i have uploaded the log files did not know which ones so i have multiple for a better view
-
Hello all, Knowing my luck this is getting posted in the wrong place. I cant find help in any of the threads i looked in and searching didnt prove to be helpful. I am a new user and just downloaded media browser and media center master. From what I read it was recomended to download both. It seemed to not be working so I uninstalled MB and reinstalled it. The server works ok.in so much as I can access it online and add/delete folders. I do not however see it in windows media center. Ive been trying to download MB classic to see if that is what im missing but im told to installe from the program i want it in. i go to windows media center (vista 32) and WMC will freeze up and I need task manager to close it. I am very frustrated with this install. The images and reviews look really cool and i would love to have this to use. Im not very computer savy but i cant imagine an install to be this complicated. its gotta be me. please advise me what to do or what other info you may need. thank you.
-
My husband installed MB3 server for me and set everything up... it all worked great! Then he got a real server computer and put MB3 on that it worked great until that computer died. He put the old computer back up as our movie server and since then have nothing but issues! movies freeze while watching it on the app. He streams to chromcast and it freezes. My daughter and myself have had it freeze or pause several times during playing a movie. And at one time it showed up on my Xbox 360 and now I don't see the movies any more making it un-usable for MB3. Sometimes even though the server is up and running our web browsers and apps say its not up. And these issues are for everything... apps, linkpc.net and localhost Can someone help me figure out what is wrong. If I need to give more information I can. Things I do .... MB3 is up to date according to program. Version 3.0.5340.21263 We have the apps for both iOS and Android He uses linkpc.net for out of local connection. Is there something in the settings? Is it the computer itself? is it linkpc.net but other address caused the same issues. Help! He won't fix it. It's up to me to fix it. I love media brower and don't want to learn a new system for my movies!
-
Dear Team: First of all, thank you to all of you for putting this whole thing together. I have been a MB Classic user for some time and love your platform. I recently upgraded to MB3 and MBT from the MB Classic (version 2). Guys, MBT repeatedly crashes as one is browsing content and when one reaches around the 2200 title. I have over 5000 titles in my library. With MB Classic this never happened. Granted that MB Classic took quite a while to load given the approximately 18TB of content that I have, and MB3 and MBT load much faster. But at least with MB Classic (integrated within the Windows Media Center) when all the content loaded, one could browse them without the system crashing. Is there currently a limit for the number of titles one may have in their library for MBT and hence the reason why it crashes after around the 2200 title? All of my content comes in well organized folders that has all meta-data info, folder graphics and backdrops already included so I don't think it's MBT trying to download new info. Thanks for kindly looking into this. Regards, Mike