Jump to content

What's the proper way to update betas from github?


Go to solution Solved by Luke,

Recommended Posts

Posted

I'm trying to update my emby-server-beta by downloading the Emby.Mono.zip file from github, and uncompressing it on /usr/lib/emby-server/bin.

The problem is that when I try to start the server using systemctl, no errors show up and nothing is recorded on the logs, but the server doesn't start.

When I run /usr/bin/emby-server start, I get the following exception:

Unhandled Exception:
System.DllNotFoundException: libsqlite3.so
  at (wrapper managed-to-native) SQLitePCL.SQLite3Provider_sqlite3+NativeMethods:sqlite3_libversion_number ()
  at SQLitePCL.SQLite3Provider_sqlite3.SQLitePCL.ISQLite3Provider.sqlite3_libversion_number () [0x00000] in <52410a2b1f7d462f906372c31f57e9ab>:0
  at SQLitePCL.raw.SetProvider (SQLitePCL.ISQLite3Provider imp) [0x00000] in <27978e3674a44db399cf097c8ed0098b>:0
  at MediaBrowser.Server.Mono.MainClass.SetSqliteProvider () [0x00006] in <89e440eef0294109b8ac80aa540f992f>:0
  at MediaBrowser.Server.Mono.MainClass.Main (System.String[] args) [0x0001a] in <89e440eef0294109b8ac80aa540f992f>:0
[ERROR] FATAL UNHANDLED EXCEPTION: System.DllNotFoundException: libsqlite3.so
  at (wrapper managed-to-native) SQLitePCL.SQLite3Provider_sqlite3+NativeMethods:sqlite3_libversion_number ()
  at SQLitePCL.SQLite3Provider_sqlite3.SQLitePCL.ISQLite3Provider.sqlite3_libversion_number () [0x00000] in <52410a2b1f7d462f906372c31f57e9ab>:0
  at SQLitePCL.raw.SetProvider (SQLitePCL.ISQLite3Provider imp) [0x00000] in <27978e3674a44db399cf097c8ed0098b>:0
  at MediaBrowser.Server.Mono.MainClass.SetSqliteProvider () [0x00006] in <89e440eef0294109b8ac80aa540f992f>:0
  at MediaBrowser.Server.Mono.MainClass.Main (System.String[] args) [0x0001a] in <89e440eef0294109b8ac80aa540f992f>:0

libsqlite3.so is in the right place. 

  • Solution
Posted

Do not use the zips from github. Use the normal update method from your server installation. if you are on linux that means the usual apt get update

Posted

Found the problem. I should keep the original .config files

Posted

Do not use the zips from github. Use the normal update method from your server installation. if you are on linux that means the usual apt get update

 

Yeah, but I wanted to test 3.1.265-beta and the latest version on the apt repo is .261  :-)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...