search

Smiley-McSmiles / jellyman

Jellyman is a set of scripts to install/manage and update the jellyfin-combined tar.gz generic linux package
GNU General Public License v3.0
92 stars 4 forks source link

Trouble with Ubuntu 22.04.04 #122

Open cstackpole opened 1 month ago

cstackpole commented 1 month ago

Greetings, I have questions and multiple bug reports in this post.

My goal: Jellyfin was installed in a Ubuntu 22.04 VM. I want to migrate to physical host on Rocky 9.4.

First, I need to back-up and move the data. Jellyman was recommended to me as I'm migrating the OS.

I'm at step:

$ sudo ./setup.sh
[snip]
> Is Jellyfin CURRENTLY installed on this system?
[y/N] >>> y
> Where is Jellyfins intalled directory?
[/path/to/jellyfin/dir] >>>

[PS: bug report number 1 for typo ;-) "intalled" -> "installed"]

None of these paths work; the script rejects all of them.

$ sudo find / -type d -name jellyfin
/etc/jellyfin
/var/lib/jellyfin
/var/log/jellyfin
/var/cache/jellyfin
/opt/jellyfin
/usr/share/doc/jellyfin
/usr/share/jellyfin
/usr/lib/jellyfin

Not sure what to do...

How does it reject all of them? Like this (which also leads to bug report number 2 & 3):

> Where is Jellyfins intalled directory?
[/path/to/jellyfin/dir] >>> /etc/jellyfin
/etc/jellyfin/data/metadata does not exist
/etc/jellyfin/config does not exist
***ERROR*** - one or more directories not found...
> Would you like to try a different directory?
[Y/n] >>> y
> Saving your current metadata to --> /root/current-jellyfin-data.tar
./setup.sh: line 236: cd: null: No such file or directory
tar: data: Cannot stat: No such file or directory
tar: config: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

real    0m0.004s
user    0m0.003s
sys 0m0.001s
> Please enter the LINUX user for Jellyfin

Bug Report Number 2: When I enter 'y' to try a different directory, it clearly doesn't let me try a different directory. I Ctrl+C to break and try again with another path.

Bug Report Number 3: cd $currentJellyfinDirectory is null because it was never set.

I see the big warning that this is highly experimental. That makes me wonder if there's a different process I should be doing for a backup on the original host.

Recommendations on how to get this script to back up the Ubuntu 22.04.4 install? Recommendations on the migration to Rocky 9.4?

Thanks!

Smiley-McSmiles commented 1 month ago

Hmm well you definitely found some bugs. And yes, this feature is highly experimental because I cannot account for every type of setup as there are just too many ways to install Jellyfin. This is why I do not recommend migrating from one type of install to another type of install.

There is a Jellyfin wiki page that describes how to migrate, but it obviously doesn't describe how to migrate from every type of setup to every other type of setup.

So my recommendation to you is to simply start from scratch (As I had to do many times before I decided to make Jellyman in the first place) and just use Jellyman from now on and never have to worry about it as long as you keep up with backups (Or set up automatic backups with Jellyman)

I'm removing this feature entirely from Jellyman as of 1.9.2 as I think it is causing too many issues. Though I'm open to the idea of someone submitting a pull request if they figure out how to do it reliably.

I'm not going to close this issue, as I think others may be able to help you. But I would also recommend detailing the method you used to install Jellyfin in the first place, to better help the next person.

I appreciate the bug reports and the typos will be fixed thanks to you.