2024-10-14, 06:16 PM
You cannot. You are starting another instance. If you look at all the "paths", they aren't the same as when Jellyfin is run via systemctl.
It is starting another instance and it is running out of the home directory of whatever user you are starting Jellyfin as when you use "jellyfin" to start it. systemctl status jellyfin is the proper, and only, way to check the running status of Jellyfin.
What is the output of these commands.
Code:
[20:00:09] [INF] [1] Main: Program data path: /root/.local/share/jellyfin
[20:00:09] [INF] [1] Main: Log directory path: /root/.local/share/jellyfin/log
[20:00:09] [INF] [1] Main: Config directory path: /root/.config/jellyfin
[20:00:09] [INF] [1] Main: Cache path: /root/.cache/jellyfin
It is starting another instance and it is running out of the home directory of whatever user you are starting Jellyfin as when you use "jellyfin" to start it. systemctl status jellyfin is the proper, and only, way to check the running status of Jellyfin.
What is the output of these commands.
Code:
sudo journalctl -u jellyfin -n 200 --no-pager
sudo ss -tulpn | grep 8096