Ubuntu 16.04, Tried upgrading to emby-server-deb_3.6.0.2_amd64.deb

[ssg99si 4]

Emby won't start after trying to upgrade to 3.6.0.2. I can't find the logs but the service status output complains about SQLLite3:

 

sti@STIBOX01:~/Downloads$ sudo 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 Sun 2018-08-12 09:55:49 EDT; 21min ago

  Process: 21935 ExecStart=/opt/emby-server/bin/emby-server (code=dumped, signal=ABRT)

 Main PID: 21935 (code=dumped, signal=ABRT)

 

Aug 12 09:55:49 STIBOX01 emby-server[21935]:    at SQLitePCL.SQLite3Provider_sqlite3.NativeMethods..cctor()

Aug 12 09:55:49 STIBOX01 emby-server[21935]:    --- End of inner exception stack trace ---

Aug 12 09:55:49 STIBOX01 emby-server[21935]:    at SQLitePCL.SQLite3Provider_sqlite3.NativeMethods.sqlite3_libversion_number()

Aug 12 09:55:49 STIBOX01 emby-server[21935]:    at SQLitePCL.SQLite3Provider_sqlite3.SQLitePCL.ISQLite3Provider.sqlite3_libversion_number()

Aug 12 09:55:49 STIBOX01 emby-server[21935]:    at SQLitePCL.raw.SetProvider(ISQLite3Provider imp)

Aug 12 09:55:49 STIBOX01 emby-server[21935]:    at EmbyServer.Program.Main(String[] args)

Aug 12 09:55:49 STIBOX01 emby-server[21935]:    at EmbyServer.Program.<Main>(String[] args)

Aug 12 09:55:49 STIBOX01 systemd[1]: emby-server.service: Main process exited, code=dumped, status=6/ABRT

Aug 12 09:55:49 STIBOX01 systemd[1]: emby-server.service: Unit entered failed state.

Aug 12 09:55:49 STIBOX01 systemd[1]: emby-server.service: Failed with result 'core-dump'.

sti@STIBOX01:~/Downloads$

 

[ssg99si 4]

Actually it looks to be the same is this issue here: https://emby.media/community/index.php?/topic/55197-emby-wont-start-after-reboot/

 

I am not sure how to fix it though, doesn't look like it was resolved. 

 

sti@STIBOX01:/opt/emby-server/bin$ sudo /opt/emby-server/bin/emby-server

 

Unhandled Exception: System.TypeInitializationException: The type initializer for 'NativeMethods' threw an exception. ---> System.ArgumentOutOfRangeException: Version's parameters must be greater than or equal to zero.

Parameter name: revision

   at System.Version..ctor(Int32 major, Int32 minor, Int32 build, Int32 revision)

   at System.Environment.<>c.<.cctor>b__79_0()

   at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode)

   at System.Lazy`1.ExecutionAndPublication(LazyHelper executionAndPublication, Boolean useDefaultConstructor)

   at System.Lazy`1.CreateValue()

   at SQLitePCL.SQLite3Provider_sqlite3.NativeMethods.TryLoadFromArchDirectory(String baseDirectory)

   at SQLitePCL.SQLite3Provider_sqlite3.NativeMethods..cctor()

   --- End of inner exception stack trace ---

   at SQLitePCL.SQLite3Provider_sqlite3.NativeMethods.sqlite3_libversion_number()

   at SQLitePCL.SQLite3Provider_sqlite3.SQLitePCL.ISQLite3Provider.sqlite3_libversion_number()

   at SQLitePCL.raw.SetProvider(ISQLite3Provider imp)

   at EmbyServer.Program.Main(String[] args)

   at EmbyServer.Program.<Main>(String[] args)

Aborted (core dumped)

 

[ssg99si 4]

sti@STIBOX01:/opt/emby-server/bin$ sqlite3 --version

3.22.0 2018-01-22 18:45:57 0c55d179733b46d8d0ba4d88e01a25e10677046ee3da1d5b1581e86726f2alt1

 

[Luke 42077]

How did you update to 3.6.0.2?

[ssg99si 4]

I just tried deleting everything and just running: dpkg -i emby-server-deb_3.6.0.2_amd64.deb

 

There definitely is some sort of conflict with emby starting and the hauppauge tuners

[Luke 42077]

Why do you feel this relates to hauppauge? or how did you come to that conclusion?

[ssg99si 4]

Seeing the same errors as these guys in this thread here: https://emby.media/community/index.php?/topic/55197-emby-wont-start-after-reboot/

 

Hauppage does something to the kernel when it's drivers are installed. I am not the best with ubuntu server, not sure how to remove the hauppage drivers or revert to an older kernel. Would be cool to figure out why they would stop emby from starting though. 

 

This is what I got installed:

 

sti@STIBOX01:~$  dpkg --list | grep haup

ii  linux-headers-4.4.0-103201712162024                         4.4.0-103201712162024.0+mediatree+hauppauge                 all          Header files related to Linux kernel version 4.4.0

ii  linux-headers-4.4.0-103201712162024-generic                 4.4.0-103201712162024.0+mediatree+hauppauge                 amd64        Linux kernel headers with slipstreamed mediatree drivers for version 4.4.0 on 64 bit x86 SMP

ii  linux-image-4.4.0-103201712162024-generic                   4.4.0-103201712162024.0+mediatree+hauppauge                 amd64        Linux kernel image for version 4.4.0 on 64 bit x86 SMP

ii  linux-image-extra-4.4.0-103201712162024-generic             4.4.0-103201712162024.0+mediatree+hauppauge                 amd64        Linux kernel extra modules with slipstreamed mediatree drivers for version 4.4.0 on 64 bit x86 SMP

 

[ssg99si 4]

I might try to recreate this on a VM later. Recreation steps:

 

Install Ubuntu Server 16.04

Install Hauppauge Driver following these instructions: http://www.hauppauge.com/pages/support/support_linux.html

Install Emby Server:

1. Download emby-server-deb_3.6.0.2_amd64.deb
2. dpkg -i emby-server-deb_3.6.0.2_amd64.deb

Try to start emby server

[tdiguy 99]

I might try to recreate this on a VM later. Recreation steps:

 

Install Ubuntu Server 16.04

Install Hauppauge Driver following these instructions: http://www.hauppauge.com/pages/support/support_linux.html

Install Emby Server:

1. Download emby-server-deb_3.6.0.2_amd64.deb
2. dpkg -i emby-server-deb_3.6.0.2_amd64.deb

Try to start emby server

If you are going to go through the bother of re-creating it i would suggest the following mostly as curiosity.

build up the OS ( ubuntu )

save a snapshot of the vm

install the emby version you desire.

save a snapshot of the vm

install Hauppauge driver

 

This way you can experiment easily with order of install, like does it matter if hauppauge is installed first or emby first or will it simply not work installing both?

Just my 2 cents though which sometimes isnt worth the effort i put into typing it.

Edited August 14, 2018 by tdiguy

[Luke 42077]

Just to confirm, this happens just from installing hauppauge drivers, or does hauppauge software also need to be running?

[ssg99si 4]

Yep, just from installing. 

[ssg99si 4]

Just recreated this. It's definitely the Hauppauge driver/kernel. Steps taken:

 

Installed ubuntu server 16.04.5

Took snapshot

Installed emby:  emby-server-deb_3.6.0.2_amd64.deb

Emby started perfectly, took a snapshot

Installed Hauppauge driver, these steps:

• sudo add-apt-repository ppa:b-rad/kernel+mediatree+hauppauge
• After this first line, click enter when prompted to add this PPA.
• sudo apt-get update
• sudo apt-get install linux-image-mediatree
• sudo apt-get install linux-headers-mediatree

At this point, restarting the emby-server service still worked. After a reboot however, emby no longer starts and throws the same error as previous posts in this thread.

Thoughts? Should I just attempt to remove the hauppauge bits or is this worth troubleshooting? I could give ssh access if that would help. 

[Luke 42077]

Thanks, we'll look into this.

[ssg99si 4]

For anyone that is seeing this issue and wants to remove the Hauppauge "stuff" you can use these commands(in this order) to get back to the old kernel:

 

sudo apt-get remove linux-image-mediatree

sudo apt-get remove linux-headers-mediatree

sudo dpkg --remove linux-headers-4.4.0-131201807270420-generic

sudo dpkg --remove linux-headers-4.4.0-131201807270420

sudo dpkg --remove  linux-image-extra-4.4.0-131201807270420-generic

sudo dpkg --remove  linux-image-4.4.0-131201807270420-generic

 

Then reboot. I ran these and rebooted and emby started right up. This will probably stop the Hauppauge tuner from working however. 

 

The kernel version number may be different, you can find out what needs to be uninstalled by running:

dpkg -l | grep mediatree

Edited August 14, 2018 by ssg99si

[Luke 42077]

Thanks for the info.

[Luke 42077]

Are you still seeing this with the latest Hauppauge drivers?