2024-08-14, 01:53 AM
(This post was last modified: 2024-08-14, 02:37 AM by 4r5hw45twh. Edited 5 times in total.)
(2024-08-14, 01:50 AM)TheDreadPirate Wrote: You need to put "sudo" in front of the ss command so that it lists the PID as well.
Code:chris@rat-trap:~$ ss -tulpn | grep 8096
tcp LISTEN 0 512 *:8096 *:*
chris@rat-trap:~$ sudo ss -tulpn | grep 8096
tcp LISTEN 0 512 *:8096 *:* users:(("jellyfin",pid=3641666,fd=504))
And then you need to kill the PID that is still running because it is preventing the new instance from starting. Whatever is running now is not the new instance and you are still using the old data from the flatpak.
Ok, after a 6th reboot and re-doing commands a few times, I finally have a Dashboard that says 19.9.9. The only problem left now is....how do I point JF to my media hard drives? Before updating, they showed up on /media/username/ but now I don't see them there. On my machine, they're at /dev/sda2 and /dev/sdb1. They're already mounted. JF sees "/media/username" but not the drives there. I tried your suggestion from another post here: https://forum.jellyfin.org/t-jellyfin-ca...36#pid1736 because that OP had the same exact issue.
EDIT: Followed this Reddit reply and the issue is now fixed with seeing the drives: https://www.reddit.com/r/jellyfin/commen...n/hhmlqdw/
OK, NOW.....how do I prevent all of this from happening ever again? Entire night was ruined from a measly upgrade that I needed. How can I properly upgrade the server version next time without alllllllll this hassle?