Jump to content

Search the Community

Showing results for tags 'linux'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 221 results

  1. DarkZrobe

    Identify Issues

    Emby Server Version 3.5.2.0 on Linux Mint 19 Tried to search the forums and find a answer but nothing was quite clear and the word Identify doesnt seem to be unique enough. Just got done rebuilding my whole linux server as I was attempting to upgrade from the older repo provided emby to the new one and wrecked everything. There really should be warnings for that on the install page or something. Too many results just say run the new version over the old one. Any who this time around I renamed everything so it would identify better with the automatic detection, however I have a few stragglers that need manual detection. When I use the identify tool I no longer seem to be able to immediately identify movies with IMDB id anymore. No results show up. I did see some forum posts back in February stating that emby doesnt search that database anymore (What happened?) But I wanted to confirm. So I attempted to use the movidb which does have the movie in its database but that doesnt return any results either. But I am not quite sure what that website uses for its "ID" as with IMDB I just used the number in the web address. One of the Movies in question is Frank Herberts Children of Dune: https://www.imdb.com/title/tt0287839/?ref_=fn_al_tt_1 https://www.themoviedb.org/tv/9156-frank-herbert-s-children-of-dune?language=en I cant seem to get the Emby Server to ID that. Soooo what am I doing wrong if anything. Also any way to make that back button in that Identify window actually go back to the search instead of closing the whole window? Really annoying.
  2. Around a week ago I installed Emby on my Kubuntu PC. I didn't understand Emby and thought that it would be an application. Instead it turned my machine into a Multimedia Server. So cool once it's set up it's always on and no maintenance. My needs are basic. All I want to do is to have a file linked to Emby and any movie in that file will stream to the devices on my home network. I do not want to stream remote for security purposes. I followed the install instructions on the internet where I downloaded the file and it was really easy. I did have trouble getting it connected to my Fire stick because the port was closed in my software firewall. I opened port I think it's 8095 in my software Firewall and then no problem hooking into the Amazon Fire stick. Not an Emby problem. Around a week later I bought a Roku Express for my daughter and installed in her TV. Emby wouldn't connect. I waited a few days and my router choked and I had to reboot it. A little later I went back to try to get Emby working and to my surprise, Wallah the Roku recognized and connected to the server with no prodding. Seemed my router needed to be reset. Lesson learned if I ever have trouble connecting a new device to Emby reset the router. I proceeded to install on my Android Phone and again it was brainless. It just recognized and entered Emby Server with no prodding. So fast it made my head spin. Emby is fantastic on Linux Kubuntu/Ubuntu. Basically I hooked a file up to synchronize and everything I copy to that file shows up on my devices to be streamed. It's running in the background no maintenance required. Also no glitches waking up from sleep either. On the Roku it's running fast. So anyway If you have Kubuntu or Ubuntu and want to simply use Emby to stream movies within your home network I recommend it highly. BTW the resolution of the movies look great.
  3. DreadManX

    New users can't transcode fast enough

    I'm running - Ubuntu 16.04.5 - Emby Server Version 3.5.2.0 - Dual Xeons X5660 @ 2.80GHz - 96 GB RAM The first user I created and the one I tied to Emby premier (if that matters), can transcode a 4k 30 FPS, video no problem. If I switch users in the same browser session, same tab (Chrome or Firefox) the video plays at 12-17 fps. I've done a side by side comparison of the users with the working user and everything is the same - I even tried the "user can manage server" setting. I'm at a loss as to why this is happening. Can anyone help me out here? What more info is needed?
  4. kornster

    Latest Media TvSeries

    Good afternoon all, I`ve recently moved back to Emby from Plex. Without going into too much detail plex continuously failed to stream on my local network to a chromecast on the same network and this is just a tip of the experience i`ve had with plex. The reason for this topic is that before i made the change, i`d recently downloaded a fair few complete tv series. Grey`s Anatomy, Seinfeld, BSG to name a few. The issue im trying to understand as i think i know what it is but i may be incorrect is that now that ive moved over, i only see Seinfeld as the latest media. I think and correct me if im wrong that the 'Date Added" for Seinfeld is the most recent so the Web Gui is showing only Seinfeld as all the episode under the main folder have the "Date Added" marking of 19/08/2018 and so thats all emby can show due to limitation. Is this correct? Latest Movies works perfect. I was just hoping to see a wider range of Latest Tv Shows. i`ve attached a screenshot Also im not sure if its required but the server is Ubuntu 18.04LTS. Its the Bionic Beaver release. There are no NFO or XML files in the tv series folder as i have checked that first thinking it might be that. administrator@white-forest:/disks/storage/plex/tvseries$ sudo find . -name "*.xml" -type f administrator@white-forest:/disks/storage/plex/tvseries$ sudo find . -name "*.nfo" -type f administrator@white-forest:/disks/storage/plex/tvseries$
  5. I've just installed a fresh install of emby on my ubuntu server, previously was running as a plex server (i'm hoping to switch) My media is located on a nas drive externally and i have mounts setup using cifs, i can access the external media by doing cd /media/plex/shows cd /media/plex/movies Both of these mounts show up in plex but during the emby configuration wizard browsing to /media shows only /media/CDRom Is this a permissions issue maybe? If so what user / permissions should i grant to access these mounts? Thanks
  6. Darkieth

    Server crashing within minutes

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

    Jolla App

    As there is no Topic under Apps I opened one here. Day by day there are more Sailfish users and it would be appropriate now to develope an App for it. Android is not a way to go as isnt iOS. Sailfish is more secure and far more usable as Android and iOS togheter. As far as I heared, cant tell myself, its not complicated to programm on Sailfish and I think the Sailfish SDK is even free to use: https://sailfishos.org/develop/sdk-overview/ Many thanks
  8. I have Emby on a nuc that is headless (no monitor). Ubuntu 18 Bionic Is there (or where is) the linux config file to tell Emby Server the paths to folders I want Emby to serve. do I need to share out these folders first, since it is on the same disk partition as Emby? I'd prefer not to have to share them, since they are are the same box, but if there is a reason to do it (besides not being able to find the Emby config file), I will. Thanks.
  9. Hi, Emby Server needs to stop creating metadata, cache, transcoding-temp directories automatically. I have my server paths set to:- Emby data: /srv/.config/emby cache: /media/cache metadata: /media/metadata transcoding-temp: /media/tmp With Emby's current control, the directories end up being:- cache: /media/cache/cache metadata: /media/metadata/metadata transcoding-temp: /media/tmp/transcoding-temp Ideal outcome:- cache: /media/cache metadata: /media/metadata transcoding-temp: /media/tmp/transcoding
  10. Preface: I haven't seen an upgrade of Emby pushed to my Ubuntu 16.04 server in some time, thought it was just taking awhile to push the packages to the OpenSUSE.org servers. I've found many threads referencing or explaining different ways people have switched from managed packages to several different methods of upgrading Emby, but I can't seem to find an original thread explaining what the situation is and why people are trying to migrate methods in all kinds of different ways. Sorry if I'm beating a dead horse here, but I can't seem to find any thread plainly epxlaining the situation and why/how I should be managing my server packages now. Thanks devs and community members.
  11. nikolasd

    Change Library Path

    I really dont't know if the titles corresponds accurately to my problem, so I will give a brief explanation of what happened. I have emby-server installed an an Ubuntu 16.04 Server. For long time, I had this server turned off. So I started it again and first thing I did was to update all packages. My latest version was installed by the repo that existed for Ubuntu package. But since this repo is no longer existing, I updated to the current version, by downloading the deb package and installing it. I think that this way, broke some things up, because here it is the situation I have right now. All my libraries after the update still exists, but cannot be updated. After searching around I found out that in the Metadata manager all my libraries have there path defined to /var/lib/emby-server/root/default, but the actual path is /var/lib/emby/root/default. I tried to change this path to the correct one, but It looks like that is not possible. I want to avoid deleting the libraries and recreating them, since there are a lot of libraries and mainly because almost all the metadata inside those libraries, were created by hand in a period of 2 years. As a work around I just created a symlink /var/lib/emby-server that points to /var/lib/emby/ but if there is some other more straightforward way it would be great.
  12. 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?
  13. I'm using Emby in a docker and just wanted to ask whether I can move the complete config folder to a new server and set up the docker in the exact same way, with the same paths for the library, user and permissions. Will that "just work"? I read about the backup and restore plugin, but I don't want to rescan my library.
  14. 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
  15. Hey Emby Sages, looking for some help figuring out why some flac files play via the web interface and some don't. The errors are presenting in Firefox 59.02. They do not occur via the Android App and when I download the offending file to the local storage I'm able to play it in the client's OS (Rhythmbox). docker logs -f [container name] doesn't yield anything past the success of the entrypoint script. Is there a way (possibly via attach?) that I can get a better look at what the decoding/encoding error might be? Thanks in advance Mike
  16. TheBrainninja

    Dropbox Sync Never Completes

    Howdy everyone, I've tried to use the sync feature a few times, with no success; the transcode seems to complete, but it fails on the Cloud & Folder Sync task every time. I went through the Dropbox plugin setup and everything seemed fine (generated App key and Secret, configured my Account), but then It shows the Transfer at 0%, with the scheduled task hanging at 3% forever. I checked through the logs and I can tell that some error occurs when it attempts to connect to Dropbox, but I'm honestly not sure how to interpret the error. 2018-03-19 00:27:59.355 Error HttpClient: Error ProtocolError getting response from https://api.dropboxapi.com/2/files/get_metadata *** Error Report *** Version: 3.3.1.0 Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -restartpath /usr/lib/emby-server/restart.sh Operating system: Unix 4.4.0.66 64-Bit OS: True 64-Bit Process: True User Interactive: False Mono: 4.8.1 (Stable 4.8.1.0/22a39d7 Tue May 2 22:26:20 UTC 2017) Processor count: 8 Program data path: /var/lib/emby-server Application directory: /usr/lib/emby-server/bin System.Net.WebException: The remote server returned an error: (409) Conflict. at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00064] in <5641e4edad4f4464ba58c620a7b8ea48>:0 at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x00014] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 System.Net.WebException at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00064] in <5641e4edad4f4464ba58c620a7b8ea48>:0 at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x00014] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 There are other errors listed too (further down) but this is the one that specifically seems relevant to the Dropbox action. Any ideas? I looked around, and none of the other sync error threads seemed to coincide with my issue.
  17. I finally, with the help of a friend (I have ZERO Linux experience) have set up Emby server on my R-Pi. I have it so it can read the drive I have plugged in (finally) and I have the folders associated with the appropriate movies, tv shows, music, etc. Everything works (Meta data shows, I can edit titles so it gets the proper meta data; the whole shabang) exactly as it did when I ran emby server on Windows 10, except when I go to play a video or song, it gives me this: "Playback Error - No compatible streams are currently available. Please try again later or contact your system administrator for details." I thought it could be a codec problem? I downloaded VLC to it and it will open the movie files, but barely play them. I figured the playback device did all the work and it was just drawing the actual movie file from the R-Pi, but perhaps the R-Pi is the thing doing all the work (and isn't powerful enough to do so?) WHAT DO I DO? Please and thanks. I appreciate it.
  18. Hello! I'm having a problem today while trying to setup emby on a "Feral Hosting" Server. If you look in the title you can see my main error.... I've made sure the files ffmpeg and ffprobe are executable. I'm not sure if emby has any permissions or not based on this piece from your emby wizard "For Linux on Arch Linux, CentOS, Debian, Fedora, OpenSuse, or Ubuntu, you must grant the Emby system user at least read access to your storage locations." This could be my main problem not too sure, but it got into my media folder just fine... I'm using the latest 3.4.2 build. I've also tried linking directly to the ffmpeg file itself with no luck. I'm a huge beginner when it comes to this stuff so I'm sorry if I haven't provided enough info about this problem
  19. Hello everyone! I'm new to Linux, so please forgive me if I've made a stupid mistake - but I'm having an awful time getting the latest versions of Emby to install on Ubuntu 17.10 Artful. Here is what happened: I had Emby running on 16.04 LTS, and attempted to perform an upgrade, and it went south. I didn't pay much attention to the error, and purged the installation, and started from scratch. That failed as well. I then started with a fresh 17.10 image on the same hardware. I received an error (I'll give details in a bit). I re-installed 16.04, and ran into the same error. Now I'm on different hardware, running into the same error. 1. Download X64 package from emby.media/downloads 2. Launch terminal 3. cd /home/emby/Downloads 3. sudo su 4. dpkg -i emby-server-deb_3.3.1.0_amd64.deb Note: Below is actually from when I attempted to install Beta - but the results are the same. (Reading database ... 131063 files and directories currently installed.) Preparing to unpack emby-server-deb_3.3.1.2_amd64.deb ... Failed to stop emby-server.service: Unit emby-server.service not loaded. Unpacking emby-server (3.3.1.2) over (3.3.1.0) ... Setting up emby-server (3.3.1.2) ... usermod: user emby is currently used by process 912 dpkg: error processing package emby-server (--install): subprocess installed post-installation script returned error exit status 8 Processing triggers for libc-bin (2.26-0ubuntu2) ... Processing triggers for ureadahead (0.100.0-20) ... Errors were encountered while processing: emby-server That's all it gives me. Any assistance would be greatly appreciated!
  20. I was just wondering because I have version 3.2.35.0 installed on an older system that is only 32-bit capable and it seems that I am unable to update further. I can understand if there is no longer a 32-bit version, I just wanted to see if I was missing something. Thanks in advance for your responses.
  21. ThermoDust

    Metadata Manager Blank

    Problem is the metadata manager is showing blank. https://1drv.ms/i/s!AtItXRNac1nKhopn5VBM5idumQ4K1g I tried removing the libraries and readding them. The scan shows complete. I rebooted a few times and still nothing. When you go into the meta data manager it shows blank. Log: https://1drv.ms/t/s!AtItXRNac1nKhopmXTJpmqpBV87EbQ
  22. KRDucky

    Fedora Atomic setup?

    Would anyone be so kind as to show/write how to setup an Emby server using Fedora Atomic? I am fixing to upgrade my system to the new AMD Ryzen 5 2400G and plan to transition Fedora Atomic. Fedora Atomic includes the os-tree system along with live updates which is a nice touch. --From Fedora: "Atomic Host from Project Atomic is a lightweight, immutable platform, designed with the sole purpose of running containerized applications." https://getfedora.org/en/atomic/ I want to run my application stack in containers. All pulling from my library data pool. (LVM2 array) My stack is usually, Emby - Sonarr - Sabnzbdplus - Cockpit - Organizr - SFTP server As the AMD Zen architecture has a good memory cryptography solution that seems to eliminate the vulnerability to VMs and containers running on an AMD platform, I figured it would be a good idea to containerize my server's services. Does anyone have a walkthrough or guide for how to accomplish this on Fedora Atomic?
  23. curtisghanson

    High CPU Usage when idle on 3.0.7200.0

    Hi all, Is anyone else experiencing unusually high CPU usage on 3.0.7200? It started on 3.0.71 but has not gone away since. It is extremely high even when nothing is going on, no users accessing the system, no scheduled tasks running, and no hung processes or transcodings found using 'ps aux |grep emby'. Here is a screenshot of htop: As you can see from the log, no activity is being logged. The only entries are me viewing the web interface. Anyone got any ideas? Mono Sgen: 4.4.2.11/f72fe45 Ubuntu: 14.04.5 LTS emby-server-log.txt
  24. doonze

    Best setup for transcoding on Linux

    So, I'm running an older low end gateway duel core system as my server. I'm running Debian 9, and don't plan on switching to anything else. While this works for my day to day needs, it can only really transcode one stream at a time. And makes a lot of noise from fans to do so. What I'm trying to get my head around is what hardware Emby can take the best advantage of running under Linux for transcoding multiple streams. I would like to have a system that could transcode 3-4 streams and keep up. My starting point would be a 8 Core processor with 32 GB ram transcoding on a SSD. What processor extensions do I need to look for that Emby can take advantage of? What's the best hardware acceleration to use? AMD better or Intel? Any motherboard hardware that can help? Can Emby take advantage of any GPU processing? If so, what cards are best? Mainly I want to make a big bad Emby streaming monster. But not sure what Emby can best take advantage of. Anyone who knows transcoding better then I do got any opinions? Thanks!
  25. 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
×
×
  • Create New...