Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errno::EACCES: Permission denied @ apply2files #24160

Open
andyhubbert941 opened this issue Mar 18, 2023 · 3 comments
Open

Errno::EACCES: Permission denied @ apply2files #24160

andyhubbert941 opened this issue Mar 18, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@andyhubbert941
Copy link

Steps to reproduce the problem

  1. Upgraded dockerised system to 4.1.1 from 4.1.0
  2. Checked Sidekiq to ensure all working
  3. Lots of error messages (>1000) with Errno::EACCES: Permission denied @ apply2files /app/www/public/system/cache/
  4. Tried restarting all dead jobs - same errors
    ...

Expected behaviour

None of these errors as previously

Actual behaviour

Getting these errors when nothing has changed to filesystem permissions

Detailed description

Error as above

Logs state exactly the same as sidekiq error

This just appears odd as everything is working as expected and I am able to upload images and post and have federated and home timelines with images and no issues front end

Wondering if I should be concerned? Didn't have this problem previously. Server has been down for ~48hrs due to some networking malfunctions but had a graceful and proper shutdown prior to this and no issues on restart

Nothing obvious showing but as it was posting errors and wasn't doing this prior to 4.1.1 then I have decided to submit a bug report - apologies this is my first so let me know if there is anything else you need

I've tried tootctl cache clear and still getting the same issue.

Specifications

Mastodon 4.1.1 Release on Docker

Image provided by Linuxserver.io

Base OS - Unraid

@andyhubbert941 andyhubbert941 added the bug Something isn't working label Mar 18, 2023
@ClearlyClaire
Copy link
Contributor

Do you have a stack trace for these errors (check sidekiq's logs)?

@andyhubbert941
Copy link
Author

Do you have a stack trace for these errors (check sidekiq's logs)?

Where would I find these logs?

@ThisIsMissEm
Copy link
Contributor

Do you have a stack trace for these errors (check sidekiq's logs)?

Where would I find these logs?

For docker, you'd use docker logshttps://docs.docker.com/engine/reference/commandline/logs/

As Sidekiq outputs it's logs to stdout / stderr.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants