Jellyfin
Jellyfin Server Commands (Ubuntu/Debian)
[redigera | redigera wikitext]Starting the Jellyfin Server
[redigera | redigera wikitext]To start the Jellyfin service, use the following command:
sudo systemctl start jellyfin
Stopping the Jellyfin Server
[redigera | redigera wikitext]To stop the Jellyfin service, use:
sudo systemctl stop jellyfin
Restarting the Jellyfin Server
[redigera | redigera wikitext]To restart the Jellyfin server, execute the following command:
sudo systemctl restart jellyfin
This will provide information about whether the Jellyfin server is active or if any errors are present.
Enabling Jellyfin to Start on Boot
[redigera | redigera wikitext]To ensure Jellyfin starts automatically when your system boots, use the following command:
sudo systemctl status jellyfin
This will provide information about whether the Jellyfin server is active or if any errors are present.
Enabling Jellyfin to Start on Boot
[redigera | redigera wikitext]To ensure Jellyfin starts automatically when your system boots, use the following command:
sudo systemctl enable jellyfin
Disabling Jellyfin from Starting on Boot
[redigera | redigera wikitext]To prevent Jellyfin from starting automatically on boot, use:
sudo systemctl disable jellyfin
Troubleshooting Jellyfin Server Issues
[redigera | redigera wikitext]Troubleshooting Systemctl Failures
[redigera | redigera wikitext]Try looking in to logs and find out whats the error about:
How to View Log of a Service using journalctl
To view the log of a specific service of systemd, use journalctl with the -u command and service or unit name.
journalctl -u
In the above command, the -u flag, short for –unit is used to filter the journalctl output by a unit name.
For example, to print the log of the smbd daemon, I will replace the [unit-name] with jellyfin.service.
journalctl -u jellyfin.service
Worst case scenario
[redigera | redigera wikitext]If you encounter a failure when using `systemctl` to manage Jellyfin (e.g., systemctl reports an error while starting, stopping, or restarting), it may be due to a misconfiguration or corruption. To resolve this, you can try the following steps:
1. Purge Jellyfin
[redigera | redigera wikitext]NOTE: This will remove Jellyfin and may delete configuration files and settings. Make sure you have backups of your data before proceeding.
[redigera | redigera wikitext]If systemctl is not functioning properly and you want to completely reset Jellyfin, you can purge the Jellyfin package:
sudo apt purge jellyfin*
2. Remove Jellyfin Configuration and Cache Files
[redigera | redigera wikitext]If you need to completely remove Jellyfin, including its configuration and cache files, use:
NOTE: This will remove configuration files and settings. Make sure you have backups of your data before proceeding.
[redigera | redigera wikitext]sudo rm -rf /var/lib/jellyfin /var/log/jellyfin /etc/jellyfin /var/cache/jellyfin
3. Reinstall Jellyfin
[redigera | redigera wikitext]After purging and removing configuration files, you can reinstall Jellyfin by running:
curl https://repo.jellyfin.org/install-debuntu.sh | sudo bash