mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[Issue]: 10.8.0 upgrade breaks; cannot start - permissions and not start - permissions issue #3895
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cegfault on GitHub (Jun 11, 2022).
Please describe your bug
Upgrading to 10.8.0 simply via
apt upgradecause a break, where jellyfin could no longer start. From journalctl (see full message below):Okay, so chdir or chroot jail doesn't have the right permissions. so I found
/var/lib/jellyfinwas owned byjellyfin:adm, but files/directories underneath are owned byjellyfin:jellyfin, and I see "User" and "Group" in/lib/systemd/system/jellyfin.serviceare both "jellyfin", so let's try that:Still errors out, but this time it's different (see full message dump below):
Interesting, so I see
/etc/jellyfin/logging.default.jsonis owned byjellyfin:root, along with several other files in/etc/jellyfin, and the directory is owned byjellyfin:adm, so let's try that:and... nope. Now I get:
This process continues for some time. Now I'm getting (full logs below):
Okay, plugins issue.
And now I get:
Not entirely sure what to do about that one.......
TL;DR there's something funky going on with this upgrade, and it's broken my entire install. Jellyfin won't start.
Jellyfin Version
10.8.0
if other:
No response
Environment
Jellyfin logs
And then this:
And finally:
and finally:
@miceZipper commented on GitHub (Jun 13, 2022):
+1
@microtechno9000 commented on GitHub (Jun 13, 2022):
Also have this issue, upgraded via apt yesterday and now Jellyfin is unresponsive with permission errors as above
Ubuntu 20.04.4 LTS
@brimur commented on GitHub (Jun 15, 2022):
Just did a clean install of Jellyfin on Ubuntu Server 20.04.4 LTS and I am getting this error too and log directory is empty so I've no idea what to do
@crobibero commented on GitHub (Jun 15, 2022):
Likely related to https://github.com/jellyfin/jellyfin/issues/7503
Should be fixed by https://github.com/jellyfin/jellyfin/pull/7887
@microtechno9000 commented on GitHub (Jun 21, 2022):
Tried the solution listed in #7503, although that hasn't resolved the issue with 10.8.0
edit: can't roll back Jellyfin to a previous version using apt and the repo, for some reason both debian and ubuntu dont have anything other than 10.8.0 in the stable repo??
Why would you remove 10.7 from the stable repo
https://repo.jellyfin.org/releases/server/debian/versions/stable/meta/
https://repo.jellyfin.org/releases/server/ubuntu/versions/stable/meta/
@microtechno9000 commented on GitHub (Jun 29, 2022):
@cegfault have you updated to 10.8.1?
I just did on Ubuntu 20.04 and it has not resolved the permissions issue. Keen to see if it has for anyone else.
@rsvcoder commented on GitHub (Jul 24, 2022):
I had similar issue; but it was not exactly the same.
jellyfin.service: Changing to the requested working directory failed: No such file or directory
It was above.
SO I followed these steps to resolve mine:
created these folders manually:
/var/lib/jellyfin
/var/log/jellyfin
/var/cache/jellyfin
/var/lib/jellyfin/data
/var/lib/jellyfin/metadata
Then following commands:
sudo apt purge jellyfin-web
sudo apt update
sudo apt install jellyfin-web
sudo systemctl restart jellyfin.service
Give permissions:
chown jellyfin /var/lib/jellyfin
chown jellyfin /var/log/jellyfin
chown jellyfin /var/cache/jellyfin
chown jellyfin /var/lib/jellyfin/data
chown jellyfin /var/lib/jellyfin/metadata
Mine started working with this.
@JustJoostNL commented on GitHub (Aug 4, 2022):
Same for me on latest version, lets hope it gets fixed soon!
@jellyfin-bot commented on GitHub (Feb 20, 2023):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.
@AshleighTheCutie commented on GitHub (Feb 20, 2023):
I'm having this issue too, but it randomly occurred last night with nothing being changed. It first appeared as a database access error, and then spiraled worse from there.
EDIT: Jellyfin version 10.8.9-1 on Debian 11.
@jellyfin-bot commented on GitHub (Aug 20, 2023):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.
@synkoptik commented on GitHub (Oct 12, 2023):
This worked for me.. just fix the typo on "jellyfine" to jellyfin