Jump to content

Anybody upgraded on ubuntu to 4.0.0.2 ?


Recommended Posts

Posted

Wondering if people have feedback on new version of Emby and upgrade process?

 

Thx 

Posted

I'm on the beta released just prior, only a few changes were made from that to 4.0.0.2.  When I upgraded, I actually reinstalled (via docker with a new volume).  I had read that an upgrade to the database wouldn't have the same benefits as the database being built from scratch (that may have changed).  I just did a backup from the plugin, and backed up the statistic data, then after install, I restored those backups.  It took a little while for the library to rebuild, even though I have metadata saved with media files.  I don't remember how long, but it was a few hours for sure.

Posted

I waited 30 seconds after posting this message and upgrades my server  :rolleyes:

 

So far so good !  Even tho It tool literally 30 seconds surprising, and I was afraid something went bad. 

Posted

Thanks for the feedback.

Posted

Thanks for the feedback.

 

@@Luke

 

Speaking of "afraid something went bad"

 

How can I make sure I run the latest code and installation went well?

I see Version 4.0.0.2

 

Here is command line output FYI:

 sudo dpkg -i emby-server-deb_4.0.0.2_amd64.deb 
(Reading database ... 244272 files and directories currently installed.)
Preparing to unpack emby-server-deb_4.0.0.2_amd64.deb ...
Removed symlink /etc/systemd/system/multi-user.target.wants/emby-server.service.
Unpacking emby-server (4.0.0.2) over (3.5.3.0) ...
Setting up emby-server (4.0.0.2) ...
Installing new version of config file /etc/emby-server.conf ...
usermod: no changes
Created symlink from /etc/systemd/system/multi-user.target.wants/emby-server.service to /usr/lib/systemd/system/emby-server.service.
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for ureadahead (0.100.0-19) ...
Posted

That's the correct installation.

plaidstallion
Posted

What is the actual update procedure for Linux? It is pointing me to the website to download the new installation package and shutdown emby server. Do I have to do a fresh install?

Posted

What is the actual update procedure for Linux? It is pointing me to the website to download the new installation package and shutdown emby server. Do I have to do a fresh install?

 

Hi, you simply install the latest on top of your existing version. Thanks !

plaidstallion
Posted (edited)

Hi, you simply install the latest on top of your existing version. Thanks !

Oh perfect. Do I need to back anything up first? If so where are the settings for that?

 

So just to be safe I made a backup of the /var/lib/emby folder then ran the command.

 

Now it says this when I try to connect:

 

"Emby Server is upgrading your database. Please try again in a minute or."

 

...which I assume is normal

 

Edit: And now all good. Thanks!

Edited by plaidstallion
Posted

Thanks for the feedback!

Posted (edited)

hm, i have issues.

 

first my emby directory was /var/lib/emby but in the past i recognized already that emby doesn`t like this much anymore and prefer /var/lib/emby after update it started the assistant. So i Moved the Directory to its need and restarted emby, it still asked for language and my name, but showd my it still knows my paths and that it is updating my DB.

Now it still knows my user, but all Logins are broken, just a still logged in Browser made me able to login and change the password of my admin User.

 

After logging in with it it messsed up my user rights.

 

I guess i have to restore my gladly made backup 

 

anyone any hints how to resolve these issues?

 

 

edit: fixed it with restoring my backup and  adding the path  /var/lib/emby to /etc/embyserver.conf

Edited by schamane
Posted

Glad you resolved it, and I apologize for the trouble. Thanks !

Posted

After seeing all the issues with metadata I was nervous about doing the upgrade to 4.0 but I bit the bullet anyway. Just completed the upgrade on a Ubuntu 18.04 LXC container, took about two minutes and it went without a hitch. Emby seems noticeably faster to navigate.

Posted

Thanks for the feedback !

Posted
hello

just trying to go from Emby Server 3.5..... to 4.0.0.2 as suggested by ES itself but get the following 'operation not permitted' error.

Have tried uninstalling ES 3.x totally and then installing a fresh 4.x but no luck. If I run it again I get a different file mentioned but the same error.

Any ideas? I'm probably doing something wrong :(

thanks

Ian

 

Screen cap:

 

Welcome to Ubuntu 18.10 (GNU/Linux 4.18.0-13-generic x86_64)

  System information as of Sat Jan 19 15:01:22 GMT 2019

  System load:  0.18              Processes:             149

  Usage of /:   30.6% of 1.79TB   Users logged in:       0

  Memory usage: 31%               IP address for enp3s0: 192.168.1.103

  Swap usage:   0%

0 packages can be updated.

0 updates are security updates.

Last login: Sat Jan 19 12:54:55 2019 from 192.168.1.168

 

ian@mediaserver:~$ sudo dpkg -i emby-server-deb_4.0.0.2_amd64.deb

[sudo] password for ian:

(Reading database ... 172576 files and directories currently installed.)

Preparing to unpack emby-server-deb_4.0.0.2_amd64.deb ...

Unpacking emby-server (4.0.0.2) ...

dpkg: error processing archive emby-server-deb_4.0.0.2_amd64.deb (--install):

 unable to open '/opt/emby-server/system/dashboard-ui/bower_components/emby-webcomponents/themes/blueradiance/theme.css.dpkg-new': Operation not permitted

Processing triggers for libc-bin (2.28-0ubuntu1) ...

Errors were encountered while processing:

 emby-server-deb_4.0.0.2_amd64.deb

ian@mediaserver:~$
Posted

just tried ES 3.5.3.0 which I still had in Downloads with same result, it's definitely me :((

ian@mediaserver:~/Downloads$ sudo dpkg -i emby-server-deb_3.5.3.0_amd64.deb
[sudo] password for ian:
(Reading database ... 172576 files and directories currently installed.)
Preparing to unpack emby-server-deb_3.5.3.0_amd64.deb ...
Unpacking emby-server (3.5.3.0) ...
dpkg: error processing archive emby-server-deb_3.5.3.0_amd64.deb (--install):
 unable to open '/opt/emby-server/system/System.IO.Compression.Native.a.dpkg-new': Operation not permitted
Processing triggers for libc-bin (2.28-0ubuntu1) ...
Errors were encountered while processing:
 emby-server-deb_3.5.3.0_amd64.deb
ian@mediaserver:~/Downloads$
Posted

doh! what an idiot! a newbie mistake.....

 

disabled SophosAV with

sudo /opt/sophos-av/bin/savdctl disable

 

checked it was not active with

sudo /opt/sophos-av/bin/savdstatus

 

ran ES 4.0.0.2 install and everything went ok!

Posted

Upgrade isn't taking for me. I'm on a vanilla Ubuntu 18.04 LTS. My library is on an NFS share.

 

Here is the output:

dpkg -i sudo dpkg -i emby-server-deb_4.0.0.2_amd64.deb
(Reading database ... 115121 files and directories currently installed.)
Preparing to unpack emby-server-deb_4.0.0.2_amd64.deb ...
Synchronizing state of emby-server.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable emby-server
Unpacking emby-server (4.0.0.2) over (3.5.3.0) ...
Setting up emby-server (4.0.0.2) ...
Installing new version of config file /etc/emby-server.conf ...
usermod: no changes
Synchronizing state of emby-server.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable emby-server
Created symlink /etc/systemd/system/multi-user.target.wants/emby-server.service → /usr/lib/systemd/system/emby-server.service.
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for ureadahead (0.100.0-20) ...
sudo systemctl status -l emby-server
● 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 Sat 2019-01-19 13:43:10 EST; 50s ago
  Process: 2117 ExecStart=/opt/emby-server/bin/emby-server (code=dumped, signal=ABRT)
 Main PID: 2117 (code=dumped, signal=ABRT)

Jan 19 13:43:10 emby emby-server[2117]:    at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirectory, Func`2 errorRewriter)
Jan 19 13:43:10 emby emby-server[2117]:    at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode)
Jan 19 13:43:10 emby emby-server[2117]:    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
Jan 19 13:43:10 emby emby-server[2117]:    at Emby.Server.Implementations.Logging.FileLogger..ctor(String path)
Jan 19 13:43:10 emby emby-server[2117]:    at Emby.Server.Implementations.Logging.SimpleLogManager.ReloadLogger(LogSeverity severity, CancellationToken cancellationToken)
Jan 19 13:43:10 emby emby-server[2117]:    --- End of inner exception stack trace ---
Jan 19 13:43:10 emby emby-server[2117]:    at System.Threading.Tasks.Task.WaitAllCore(Task[] tasks, Int32 millisecondsTimeout, CancellationToken cancellationToken)
Jan 19 13:43:10 emby emby-server[2117]:    at EmbyServer.Program.Main(String[] args)
Jan 19 13:43:10 emby systemd[1]: emby-server.service: Main process exited, code=dumped, status=6/ABRT
Jan 19 13:43:10 emby systemd[1]: emby-server.service: Failed with result 'core-dump'.
Posted

 

Upgrade isn't taking for me. I'm on a vanilla Ubuntu 18.04 LTS. My library is on an NFS share.

 

Here is the output:

dpkg -i sudo dpkg -i emby-server-deb_4.0.0.2_amd64.deb
(Reading database ... 115121 files and directories currently installed.)
Preparing to unpack emby-server-deb_4.0.0.2_amd64.deb ...
Synchronizing state of emby-server.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable emby-server
Unpacking emby-server (4.0.0.2) over (3.5.3.0) ...
Setting up emby-server (4.0.0.2) ...
Installing new version of config file /etc/emby-server.conf ...
usermod: no changes
Synchronizing state of emby-server.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable emby-server
Created symlink /etc/systemd/system/multi-user.target.wants/emby-server.service → /usr/lib/systemd/system/emby-server.service.
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for ureadahead (0.100.0-20) ...
sudo systemctl status -l emby-server
● 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 Sat 2019-01-19 13:43:10 EST; 50s ago
  Process: 2117 ExecStart=/opt/emby-server/bin/emby-server (code=dumped, signal=ABRT)
 Main PID: 2117 (code=dumped, signal=ABRT)

Jan 19 13:43:10 emby emby-server[2117]:    at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirectory, Func`2 errorRewriter)
Jan 19 13:43:10 emby emby-server[2117]:    at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode)
Jan 19 13:43:10 emby emby-server[2117]:    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
Jan 19 13:43:10 emby emby-server[2117]:    at Emby.Server.Implementations.Logging.FileLogger..ctor(String path)
Jan 19 13:43:10 emby emby-server[2117]:    at Emby.Server.Implementations.Logging.SimpleLogManager.ReloadLogger(LogSeverity severity, CancellationToken cancellationToken)
Jan 19 13:43:10 emby emby-server[2117]:    --- End of inner exception stack trace ---
Jan 19 13:43:10 emby emby-server[2117]:    at System.Threading.Tasks.Task.WaitAllCore(Task[] tasks, Int32 millisecondsTimeout, CancellationToken cancellationToken)
Jan 19 13:43:10 emby emby-server[2117]:    at EmbyServer.Program.Main(String[] args)
Jan 19 13:43:10 emby systemd[1]: emby-server.service: Main process exited, code=dumped, status=6/ABRT
Jan 19 13:43:10 emby systemd[1]: emby-server.service: Failed with result 'core-dump'.

 

Hi there, this should have gotten far enough to generate a server log. can you please attach that? Thanks.

Posted

Hi there, this should have gotten far enough to generate a server log. can you please attach that? Thanks.

 

Is /var/lib/emby/logs/embyserver.txt the log you 're looking for? I only see output from 3.5 there. No entries during the upgrade.

 

I am able to downgrade to 3.5 without issue if that gives some indication on how far it gets.

Posted

Strange. As a test can you try rebooting the machine and see if that helps? Thanks.

Posted

I'm not sure this is the correct area to post this, so forgive if it is in the wrong area.

 

I'm having a few of issues from upgrading to 4.0.0.2 on Ubuntu 18.04.  The first issue is I had several movies/shows that I had to manually identify before, and the upgrade has ignored the previous metadata info.  Not a big deal, just time consuming when dealing with about 80 files to fix.

 

One major thing I'm having issues is that the media library scan is detecting only the backdrop files and not the media files and every folder that has backdrops except for tv shows.  My file structure is:

tv

|

|_show

   |

   |_season

   |  |

   |  |_episode.mkv

   |

   |_backdrops

         |

         |_theme.mkv

 

movies

|

|_movie_title

   |

   |_movie.mkv

   |

   |_backdrops

         |

         |_theme.mkv

 

anime

|

|_show

   |

   |_season

   |  |

   |  |_episode.mkv

   |

   |_backdrops

         |

         |_theme.mkv

 
Each one is its own library.  TV is set up as tv shows, movies is set up as movies, and anime is set up as mixed content.
 
I'm also having an issue with some that have a backdrop subdirectory and theme.mp3 and "show.mkv" in the main directory; the frontend will treat it like a folder.
 
5c43cc2a83478_Screenshotfrom201901191857
 
5c43cc4493b71_Screenshotfrom201901191902
 
5c43cc594a593_Screenshotfrom201901191902
 
Any idea on how to fix this?
Posted

Hi, we'll be getting an update out to resolve this, thanks !

Posted (edited)

I am running emby server v4 on an proxmox host as an unprivileged LXC (Ubuntu 18.04.1) (Hardware acceleration is set to off).

 

Art upgrading to v4 I got segfaults on startup emby service (but everything is working fine).

 

See dmesg:

 

[   77.693060] ffdetect[19621]: segfault at 60 ip 0000000000403a38 sp 00007ffe857501e0 error 4 in ffdetect[400000+15000]

[   77.767348] ffdetect[19627]: segfault at 60 ip 0000000000403a38 sp 00007ffdd6602030 error 4 in ffdetect[400000+15000]

 

 

And if am trying to call ffdetect I got his:

 

root@emby:/opt/emby-server/bin# ./ffdetect 

./ffdetect: error while loading shared libraries: libavutil.so.56: cannot open shared object file: No such file or directory

Edited by gismo33
sonicattack
Posted

Hi trouble with the install tried to install over 3.5.3 install seemed to go ok but when i tried to launch in browser got 

localhost refused to connect.

 

ERR_CONNECTION_REFUSED
 

So uninstalled and tried a fresh install again all went ok, rebooted and tried the browser with same result as above im on Ubuntu 18.04.1 LTS which is fully up to date.

 

I went back and did a fresh install of 3.5.3 and all went ok and went into emby setup with no issues.

any ideas appreciated

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