sscheib 11 Posted January 27, 2018 Share Posted January 27, 2018 (edited) Hello everybody, I couldn't find a place where to report bugs actually (bugzilla or similar) so I figured I simply post it here. Following behaviour can be observed when one tries to identify* too much series at once: - Emby Server will not respond anymore via the webinterface - Load of the server first goes up, then it drops to zero - Emby Server will remain in the state until you restart the service yourself again - After restarting the service the library.db is corrupted and a lot of file handels (see lsof) are still open for the dead process - One actually need to restart the server to bring it up again, even if you replace the library.db with one you backed up before - This bug is reproducible every time *Identify: - Click on three dots of a series - Click identify - Put in ID (I personally use thetvdb.com ID) - Select the proper show, which comes up from the search - Close the window - Repeat several times until emby becomes unresponsible (do it around ~8-10 times) Attached you find the server logs as well as the exception caught. @@Luke It was a bit of an hassle to find out which database was actually corrupted, as its not stated neither in the exception nor in the server log which database it is trying to load until it fails - or I simply didn't see it. I could only find out using another server log and check the sucessful loaded database order to determine the corrupt database. Server specs: #cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 45 model name : Intel® Core i7-3930K CPU @ 3.20GHz stepping : 7 microcode : 0x710 cpu MHz : 1222.875 cache size : 12288 KB physical id : 0 siblings : 12 core id : 0 cpu cores : 6 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid bogomips : 6400.42 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management: # cat /proc/meminfo MemTotal: 65518452 kB MemFree: 50388016 kB MemAvailable: 56825952 kB Buffers: 1088 kB Cached: 9314644 kB SwapCached: 0 kB Active: 8330692 kB Inactive: 6321148 kB Active(anon): 8154372 kB Inactive(anon): 6720 kB Active(file): 176320 kB Inactive(file): 6314428 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 8388604 kB SwapFree: 8388604 kB Dirty: 1844432 kB Writeback: 0 kB AnonPages: 5336144 kB Mapped: 186332 kB Shmem: 2824984 kB Slab: 306272 kB SReclaimable: 200604 kB SUnreclaim: 105668 kB KernelStack: 4704 kB PageTables: 19232 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 41147828 kB Committed_AS: 13077200 kB VmallocTotal: 34359738367 kB VmallocUsed: 203464 kB VmallocChunk: 34359492608 kB HardwareCorrupted: 0 kB AnonHugePages: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB DirectMap4k: 80616 kB DirectMap2M: 3512320 kB DirectMap1G: 65011712 kB Storage is mounted via latest plexdrive from gdrive. Also plexdrive and emby are lying in a ramdisk: #mount tmpfs on /var/lib/emby-server type tmpfs (rw,relatime,size=16777216k) tmpfs on /root/plexdrive type tmpfs (rw,relatime,size=3145728k) There is enough free storage available: #df -h tmpfs 3.0G 123M 2.9G 4% /root/plexdrive tmpfs 16G 2.6G 14G 17% /var/lib/emby-server logs.tar.gz Edited January 27, 2018 by sscheib Link to comment Share on other sites More sharing options...
Luke 37214 Posted January 27, 2018 Share Posted January 27, 2018 At this point i would suggest switching over to our new install packages: https://emby.media/linux-server.html They will run lighter and perform better, but it will require a brand new installation. You'd have to uninstall the current one first. Link to comment Share on other sites More sharing options...
sscheib 11 Posted January 27, 2018 Author Share Posted January 27, 2018 Hello Luke, is there somewhere some comparison of the two "versions"? I have no idea, what benefits that would give me/us and actually what are the differences. Also I am wondering if those new packages will be provided via repository or if we have to download them manually? Link to comment Share on other sites More sharing options...
Luke 37214 Posted January 27, 2018 Share Posted January 27, 2018 One is based on the mono runtime, the other is based on the newer Microsoft .NET Core runtime: https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-net-core-2-0/ So they are very different. A repository is possible for the future but that hasn't been the primary concern right now. Link to comment Share on other sites More sharing options...
sscheib 11 Posted January 27, 2018 Author Share Posted January 27, 2018 Alright, thanks for the clarification - i'll try it out right now. I guess the one running on mono is abandonned? Link to comment Share on other sites More sharing options...
Luke 37214 Posted January 27, 2018 Share Posted January 27, 2018 Well we are still pushing out new versions while trying to steer all new users to the new method. However if any major troubleshooting it's easier to do on the new package. Link to comment Share on other sites More sharing options...
sscheib 11 Posted January 27, 2018 Author Share Posted January 27, 2018 Thanks for the clarification. I'll move all my servers over to the new package. BTW: You really should do some major announcement somewhere in the emby app/webinterface (not in the news - we all know, not everybody is reading them on a regular basis), when running the old package, so that people will make the move. I just stumbled over the new package by coincidence when reporting this bug. Link to comment Share on other sites More sharing options...
Luke 37214 Posted January 27, 2018 Share Posted January 27, 2018 We dont' want to force people to switch unless there's a reason to, so that's why we haven't done that. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now