Jump to content

Updating Emby on DSM6 Systems


solabc16
 Share

Recommended Posts

Evening

 

I've seen a few notes kicking around on this, here's a set of steps that will work with the new permissions model and avoid the need for WinSCP.

 

As I said somewhere else, it's good to see Synology are following one of the best practices we'd normally advocate for *nix systems.

- SSH to your Synology box and login as 'admin'.
- Switch to root with 'sudo -i'.
- Remove any existing downloads, e.g. 'rm Emby.Mono.zip*'
- Grab the latest server release, e.g. 'wget https://github.com/MediaBrowser/Emby/releases/download/3.0.5934/Emby.Mono.zip'.
- Stop Emby, using 'stop pkgctl-emby'.
- Extract the updated files, assuming default location, with '7z x Emby.Mono.zip -o/volume1/@appstore/emby/share/emby -y'.
- Start Emby, using 'start pkgctl-emby'.

EDIT (removed): - Update package with version number, e.g. "sed -i.bak 's/\(^version="\)[^"]*\("$\)/\1v3\.0\.5934\.0\2/' /var/packages/emby/INFO".

 

Here's a worked example for today's v3.0.5934 update:-

login as: admin
admin@192.168.236.105's password:

admin@JFK:~$ sudo -i
Password:

root@JFK:~# wget https://github.com/MediaBrowser/Emby/releases/download/3.0.5934/Emby.Mono.zip
    
    [output removed]

Saving to: 'Emby.Mono.zip.1'

100%[==============================================================================>] 17,718,901  5.19MB/s   in 3.9s

2016-05-03 22:00:15 (4.35 MB/s) - 'Emby.Mono.zip.1' saved [17718901/17718901]

root@JFK:~# stop pkgctl-emby
pkgctl-emby stop/waiting

root@JFK:~# 7z x Emby.Mono.zip -o/volume1/@appstore/emby/share/emby -y

[output removed]

Everything is Ok

Folders: 568
Files: 3388
Size:       49421341
Compressed: 17718901

root@JFK:~# start pkgctl-emby
pkgctl-emby start/running

root@JFK:~#

If you have ISO format media files in your media collection, then please refer to http://emby.media/community/index.php?/topic/28187-mbt-not-mounting-iso-when-pointing-at-synology-based-server/?p=328805 for an additional step you will need to take.

 

- James

Edited by solabc16
  • Like 2
Link to comment
Share on other sites

Afternoon, a couple of tweaks to the above to make the instructions clearer, following feedback from @@KRULL.

Link to comment
Share on other sites

Evening

 

Instructions updated to also include updating the version number, as seen in the package center UI.

 

e.g.

 

Before

 

572fc31bcd3b2_pkgcen_before.png

After

 

572fc335a45f8_pkgcen_after.png

 

- James

Link to comment
Share on other sites

Instructions updated to include additional step required if you have ISO files in your media collection.

 

- James

Link to comment
Share on other sites

Please DONT update the version in /var/packages/emby/INFO that'll eventually break your ability to update to newer synocommunity packages :/

Link to comment
Share on other sites

Morning @@cytec

 

That's not strictly true. The Emby binaries are already being updated manually by the user, as part of the current update process for the Synology platform. This has been the situation for some time, so the package version is unlikely to reflect the actually installed version of the software.

 

Updating the version number will simply prevent an unexpected rollback for those keeping their Emby binaries up-to-date, should another package appear with a different set of earlier Emby binaries. The package version reflects the version of Emby binaries, so if it is genuinely newer then it will still be applied.

 

- James

Link to comment
Share on other sites

@@solabc16 you should at least hint the users that they are changing stuff in a more or less closed environment. IF there will be a new Package it doesn't mean you'll automatically update to it. there are a few things that have to be true for Synology to consider it the Same package.... same name, higher version number etc. that's one reason why synocommunity appends an ongoing Revision at the end of the version.

 

 

Link to comment
Share on other sites

Afternoon @cytec

 

I do understand your point, but we're not at that juncture right now. The update process for users, once they have an initial version installed, is entirely manual via the shell.

 

This in itself breaks the notion of a closed loop environment, but is what we have right now and what we now working on addressing so we can deliver the best Emby experience to the Synology user base.

 

The Emby builds have consistent and reliable release versioning, so it makes sense to take advantage of this and keep the package versioning consistent rather than introduce an additional variable.

 

- James

Link to comment
Share on other sites

  • 2 weeks later...
  • 1 month later...
  • 1 month later...

All Synology users are recommended to use this going forward (if your model supports it).

 

Thanks for the heads up!

Will it be possible to update an existing version (which was installed and updated manually) with this new package, or do we need to remove the previous version prior to installing it?

Edited by bvanaerde
Link to comment
Share on other sites

Hello @@bvanaerde

 

You can install the Emby version of the Synology package in parallel, then migrate your configuration, should you choose to do so.

 

The only caveat is that you can't run them both at the same time, as they will both try and listen on the same network ports by default.

 

There's an article on the Wiki here on how to migrate: https://github.com/MediaBrowser/Wiki/wiki/Synology-:-Migrating-From-the-Community-Package

 

What Synology model do you have?

 

Best

- James

Edited by solabc16
Link to comment
Share on other sites

Great, there's even a wiki for migrating. I must have missed this somehow.

Will try it out shortly.

 

I'm using a Synology DS1515+

Link to comment
Share on other sites

For reference, the Emby package is completely self-contained and has no dependencies.

 

It's up to you what you do with the existing installation/dependencies once you've migrated.

 

Let us know how you get on @@bvanaerde.

 

- James

Link to comment
Share on other sites

The migration went smooth!

It's still doing the "clean database" task (probably because of the version update), but everything seems to be in place.

********************************************************************************
Script invoked as [./pkgmigrate] by [root].
File Version : 3.0.6300.0-1
********************************************************************************

This script will migrate your existing Emby Server configuration to the Emby LLC
version of the package. PLEASE ONLY USE AS DIRECTED BY SUPPORT                  

WARNING: Any existing configuration under your Emby LLC package installation    
will be overwritten.                                                            
                                                                                
Type [yes] and press return to continue: yes

Have you granted the user [embysvr] read/write access to your media libraries?
Do this by editing the folder permissions under [Control Panel->Shared Folder]

Type [yes] and press return to continue: yes

Making sure Emby Server is not running...
DONE

Validating directories...
>> Source: [/var/packages/emby/target/var]
>> Validating source: OK
>> Target: [/var/packages/EmbyServer/target/var]
>> Validating target: OK
DONE

Getting target volume...
>> Canonical path is: [/volume1/@appstore/EmbyServer/var]
>> Target volume is : [/volume1]
DONE

Backing up existing target...
>> Directory size is 2.5M
>> Filename [/volume1/EmbyServer_PreMigration_20160829T224336UTC.tgz]
>> Backup size is 192K
DONE

Migrating user data...
>> Removing existing target [/var/packages/EmbyServer/target/var/]
>> Transferring data to [/var/packages/EmbyServer/target/var/]
>> Recursively setting file and directory ownership.
DONE

Updating database...
>> Updating [data] column in [TypedBaseItems].
>> Updating [Path] column in [TypedBaseItems].
DONE

Starting Emby Server...
DONE

********************************************************************************
Your user data has been migrated succesfully. A backup of the original Emby LLC 
package data can be found at the location detailed above in TGZ format. Please  
refer to the section 'Backing up existing target...'.                           
********************************************************************************

And... it's already updating to 3.0.6400.0-1. Great!

Edited by bvanaerde
Link to comment
Share on other sites

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
 Share

×
×
  • Create New...