frankie64 9 Posted June 20, 2022 Posted June 20, 2022 after upgrading to emby-server-deb_4.7.3.0_amd64.deb (emby would no longer start, which by the way I think is coincidental) . I tried downgrading to no effect. I now see this error in the log file: "System.UnauthorizedAccessException: Access to the path '/var/lib/emby-server/logs/embyserver.txt' is denied." Any ideas on this? Frank. PS. i was working on install monit, after emby died again yesterday , although not sure this would impact this.
frankie64 9 Posted June 20, 2022 Author Posted June 20, 2022 So i did this chown -R emby:emby /var/lib/emby-server/ and restarted the service and it came up, however it lost all config. So i put premiere key in and did a backup restore and its back up. Not sure what happened at all. Frank
Luke 42077 Posted June 20, 2022 Posted June 20, 2022 Thanks for following up. Apologies for the disruption.
frankie64 9 Posted June 20, 2022 Author Posted June 20, 2022 (edited) so doing some more investigation, it looks like the server config changed from /var/lib/emby/ to /var/lib/emby-server/ , which is why my config was lost, was this a planned change on this revision? Frank Edited June 20, 2022 by frankkahle
Luke 42077 Posted June 20, 2022 Posted June 20, 2022 Hi, no, that didn't change here. Did you upgrade from a really old version?
Luke 42077 Posted June 20, 2022 Posted June 20, 2022 OK it's hard to say, but we'll look into it. Thanks.
frankie64 9 Posted June 21, 2022 Author Posted June 21, 2022 FYI, I just recently installed this on a brand new server, under version 4.7.1.0 , upgraded to 4.7.2.0 then to 4.7.3.0 which is when it broke. so it was in the /var/lib/emby directory until 4.7.3.0 when it decided to put things in /var/lib/emby-server directory. And it did not have the permissions to do that and thats when it broke. Frank
alucryd 315 Posted June 22, 2022 Posted June 22, 2022 (edited) @frankkahleIt was the very first directory we used a few years back, and today it is only used if it exists (so we don't break original installations). We have nothing that creates this directory on our end, did you perhaps create it (or install a very old emby package, I mean several years old)? Edited June 22, 2022 by alucryd
frankie64 9 Posted June 23, 2022 Author Posted June 23, 2022 So On 6/22/2022 at 12:25 PM, alucryd said: @frankkahleIt was the very first directory we used a few years back, and today it is only used if it exists (so we don't break original installations). We have nothing that creates this directory on our end, did you perhaps create it (or install a very old emby package, I mean several years old)? So here is the thing, I took a brand new computer, installed ubuntu 20.04 LTS on it, then downloaded the 4.7.1.0 installer from your site, installed it. setup emby and did a restore from backup. everything worked fine. upgraded to 4.7.2.0 and restarted everything worked fine, upgraded to 4.7.3.0 and then it broke. I did not make any changes from default. Frank
Luke 42077 Posted June 23, 2022 Posted June 23, 2022 OK that's helpful info. Maybe there was something in the backup pointing to the old location.
frankie64 9 Posted June 23, 2022 Author Posted June 23, 2022 I have been using the backup plugin with emby.... And if that was the case why did it still work for 4.7.2.0 and then stop working for 4.7.3.0 Frank PS. I am an senior IT guy BTW.
alucryd 315 Posted June 23, 2022 Posted June 23, 2022 Not sure how the backup plugin could create that directory, emby shouldn't have permission to write anything at the root of /var/lib. There really is nothing on our end which could create that dir, we create the emby user which points to /var/lib/emby: getent group emby > /dev/null 2>&1 || groupadd -r emby getent passwd emby > /dev/null 2>&1 && usermod -c 'Emby Server' -g emby -d /var/lib/emby -m -s /usr/sbin/nologin emby getent passwd emby > /dev/null 2>&1 || (useradd -r -c 'Emby Server' -g emby -d /var/lib/emby -m -s /usr/sbin/nologin emby && passwd -l emby > /dev/null) getent group video > /dev/null 2>&1 && usermod -aG video emby getent group render > /dev/null 2>&1 && usermod -aG render emby And then the /var/lib/emby-server is only referenced in the startup script, where it checks if it exists and only points to it if it does (never creating it at any point): if [ -z "$EMBY_DATA" ]; then if [ -d /var/lib/emby-server ]; then export EMBY_DATA=/var/lib/emby-server else export EMBY_DATA=/var/lib/emby fi fi I'm positive this is not our deb creating it, triple checked all our scripts in case we still had an old remnant somewhere, but I found nothing.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now