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
WASABI Sandbox: Permission denied on Result delete #180
Comments
After triing a |
I see three way of dealing with this:
The first solution seems the easiest one but I don't know if this implies changes in every processors. |
Given the multiplicity of cases and the fact that core should leave without server, it does not seem appropriate to set permission there.
Worker and app
|
Hi @Tointoin, I gave it another look and:
However, the lines you mentionned inside The startup script for the server, uses the However, the celery startup script do not use these parameters. Can you try passing these parameters to celery inside Thanks! |
Alright, thanks for your help @gnuletik. After applying this patch on sandbox:
I fixed this error on with:
After that I got other errors such as:
Should I apply:
??? @yomguy, does it seem ok for you to set worker's As @gnuletik mentioned, Was it necessary to ensure Celery auto-reloader in dev mode for closed issue #113? |
NB:
|
Hi @Tointoin,
I gave a closer look on @yomguy's commit about live reload and found something: So, we may update the string to add the I can see two solutions:
The second one may be better but I'm not aware of all the implications. |
Hi @gnuletik,
Before keeping celery's parameters in one place, I also tried to modify this file to test on starting a new instance. Passing This appears in both cases:
The concerned file is defined in settings and should be created by Django logger. |
During the 2 last devs of the celery worker start command, I have decided to not use the uid and gid options because it has indeed a important implication on media and log access rights. But this was mainly to be able to switch between the PROD and DEBUG mode without having permission issue between root and www-data users. The fact is that for some parts, the app and the worker containers can sometimes use the same dirs and then need to be run by the same user. Of course, at the end, we should have the 2 containers using the same permissions and then managing access rights of each directory by hand. I propose to improve this now using the your both propositions. I will commit this during the day and update the sandbox. After that, you will have to manage access rights on your own if switching between the modes. |
… Signoff: Antoine Grandry and Guillaume Pellerin
OK @Tointoin then please merge my last commit. |
I already did same changes so I rebased my branch on your commit before the PR. |
… Signoff: Antoine Grandry and Guillaume Pellerin
On sandbox instance @yomguy:
While deleting a Result from admin in browser, I got this Permission error since add of
pre_delete
signal:Is their a way to give the needed permission on Result's file creation ?
Is API's linux user is
www-data
?The text was updated successfully, but these errors were encountered: