upgrade to 4.0.1.0 results in fresh install

[pr3dict 33]

Soooo I'm using Debian - installed 4.0.1.0 over 3.x.x.x... When I go to :8096 it starts the install wizard as if I don't have a configured server. I don't even know where to begin diagnosing this...

 

Any idea?

[pr3dict 33]

Thats my init.d script to start emby... Is it wrong? In /var/lib/ I have /emby and /emby-server...

#!/bin/bash
### BEGIN INIT INFO
# Provides:          emby-server
# Required-Start:    $remote_fs $local_fs $network
# Required-Stop:     $remote_fs $local_fs $network
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: starts instance of Emby
# Description:       starts instance of Emby
### END INIT INFO


# chkconfig: 2345 20 80
#The above indicates that the script should be started in levels 2, 3, 4, and 5, #that its start priority should be 20, and that its stop priority should be 80.
# Load the VERBOSE setting and other rcS variables
. /lib/init/vars.sh

# Define LSB log_* functions.
# Depend on lsb-base (>= 3.0-6) to ensure that this file is present.
. /lib/lsb/init-functions

NAME=emby-server
CONF_FILE=/etc/${NAME}.conf
DEFAULT_FILE=/etc/default/${NAME}

# Source Emby server default configuration
. $DEFAULT_FILE

# Source Emby server user configuration overrides
if [[ -f $CONF_FILE ]]; then
  . $CONF_FILE
else
  echo "${CONF_FILE} not found using default settings.";
fi

# Path of emby binary
EMBYSERVER=/usr/bin/emby-server
PIDFILE=${EMBY_PIDFILE-/var/run/emby-server.pid}

case "$1" in
  start)
    log_daemon_msg "Starting $NAME daemon"
    if [[ -s $PIDFILE ]] && [[ -n "$(ps -p $(cat $PIDFILE) -o pid=)" ]]; then
      log_daemon_msg "apparently already running"
      log_end_msg 0
      exit 0
    fi
    exec $EMBYSERVER start &
    sleep 2
    if [[ -s $PIDFILE ]] && [[ -n "$(ps -p $(cat $PIDFILE) -o pid=)" ]]; then
      log_end_msg 0
    else
      log_end_msg 1
    fi
    ;;
  stop)
    log_daemon_msg "Stopping $NAME daemon"
    if [[ ! -s $PIDFILE ]] ||  [[ -z "$(ps -p $(cat $PIDFILE) -o pid=)" ]]; then
      [[ -e $PIDFILE ]] && rm -rf $PIDFILE
      log_success_msg "apparently already stopped"
      log_end_msg 0
      exit 0
    fi
    PID=$(cat $PIDFILE)
    CPIDS=$(pgrep -P $PID)
    sleep 2 && kill -KILL $CPIDS
    kill -TERM $CPIDS > /dev/null 2>&1
    sleep 2
    if [[ -z "$(ps -p $PID -o pid=)" ]]; then
      rm -rf $PIDFILE
      log_end_msg 0
    else
      log_end_msg 1
    fi
    ;;
  status)
    status_of_proc -p $PIDFILE "$EMBYSERVER" "$NAME"
    exit $? # notreached due to set -e
    ;;
  restart|force-reload)
    $0 stop || exit $?
    $0 start || exit $?
    ;;
  *)
    echo "Usage: /etc/init.d/emby-server {start|stop|status|restart|force-reload}" >&2
    exit 3
    ;;
esac

[Luke 37116]

Do you have server logs from before and after?

[pr3dict 33]

Both folders have logs in them. Which one should I grab them from?

[Luke 37116]

if it is two different folders then that is our answer, two different data paths. how did you install the older version?

[pr3dict 33]

Way back when I did apt-get and then at some point I got it from wget and the link, aka manually... That was probably a year ago I started doing the wget method...

 

The 4.0.1.0 was a wget... But this is the only one that made it look like a fresh install.

 

Which folder is the newer version. Emby-server or emby?

[Luke 37116]

Check one log file from each. The Emby Server version will be printed at the top of the log file. The one with 4.0.X will be the newer one.

[pr3dict 33]

See attached for both of them. The /emby one is the older one When I depackaged the emby-server I guess it left that one where it was?

 

 

embyserver Old Update.txt

embyserver New Update.txt

[Luke 37116]

Ok yea it would have been better to uninstall. If you can symlink the old program data path to the new one, then that could potentially allow you to upgrade.

[pr3dict 33]

I honestly just want the config to work so I don't have to invite everyone back to the server.

[Luke 37116]

Ok then try what I suggested. You should be able to upgrade doing that. 

[pr3dict 33]

Ok then try what I suggested. You should be able to upgrade doing that. 

 

Sorry I'm still a little confused... I have two installations right now. Should I delete the emby-server folder and then..? What do I do from there? Should I just copy the old data folder to the new one?

 

And then what do I do with the old one, just leave the old /emby folder there?

Edited February 14, 2019 by pr3dict

[pr3dict 33]

So I uninstalled everything and deleted the /emby-server and /emby folders... Reinstalled 4.0.1.0 and added replaced the data folder with the old one...

 

After starting the server it said it was upgrading the database andddddddd - Same issue. It shows up as a fresh install once its done.

 

Any ideas?

[Luke 37116]

Are you sure you got the folders right?

[pr3dict 33]

Yeah... After I went through the wizard all my users were there at the main login screen but all the media folders are gone and other settings are also defaulted... I pointed the metadata path to where it should be and I did a library scan. just waiting for all my media info to show up now.

[Luke 37116]

Apologies for the disruption. Thanks for the feedback.