runtimesandbox 152 Posted October 29, 2020 Share Posted October 29, 2020 (edited) I recently rebuilt my emby server and as part of this changed the default folder locations for transcoding cache amongst other things. I restored a backup that had these paths configured (and they are the same on this new host) but unknown to me the folder permissions were wrong. Emby was able to start but ran painful slow and I kept get the "Check for application updates failed" error. It took me a while but I eventually figured out the folder permissions were wrong and emby could not access the new transcoding folder. I know there is a permissions check for when you change this folder through the GUI and it alerts you if emby doesn't have the right permissions, could we get an alert to show in the dashboard as a secondary check for this circumstance (ie a backup / restore has been done) so that we don't spend ages hunting down a silly issue. Edited October 29, 2020 by runtimesandbox 2 Link to comment Share on other sites More sharing options...
Luke 37058 Posted October 30, 2020 Share Posted October 30, 2020 HI, yes we can look at improving this. Can you please attach the emby server log? I'd like to see specifically what areas had the most trouble. Thanks. Link to comment Share on other sites More sharing options...
runtimesandbox 152 Posted October 30, 2020 Author Share Posted October 30, 2020 Have PM'd you the logs from that day. The folder that the permissions were wrong for was /mnt/data/emby. This doesn't appear in the logs but there is a lot of "Error LibraryMonitor: Error watching path:" errors Link to comment Share on other sites More sharing options...
Luke 37058 Posted October 30, 2020 Share Posted October 30, 2020 Ok the library monitor ones are nothing to worry about. The server will handle it just fine and continue onward. Link to comment Share on other sites More sharing options...
GWTPqZp6b 41 Posted October 31, 2020 Share Posted October 31, 2020 +1 for this, I literally stumbled on the same error in migrating to a dockerised setup. Sorry I didn't keep the logs, I just put this down to user error. Link to comment Share on other sites More sharing options...
Luke 37058 Posted October 31, 2020 Share Posted October 31, 2020 29 minutes ago, GWTPqZp6b said: +1 for this, I literally stumbled on the same error in migrating to a dockerised setup. Sorry I didn't keep the logs, I just put this down to user error. Thanks for the feedback. Link to comment Share on other sites More sharing options...
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