[django] Internal server error / permission denied
See original GitHub issueI’ve noticed a periodic internal server error on some instances.
At first sight it seems that some processes crash and exit because they can’t write to logs for permission reasons. It seems the permission of some logs change from www-data
to root
at some point. Further investigation is needed.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Django + Apache Internal Server Error: Permission denied
What's the LOG_ROOT in the settings look like? I feel like your app is trying to access the absolute directory /debug.log which is...
Read more >Django + Apache Internal Server Error: Permission denied ...
[Solved]-Django + Apache Internal Server Error: Permission denied-django ... The problem is in your settings.py in the file, in the section that controls...
Read more >Django Deployment on Ubuntu 16.04 with web server Nginx
The "permission denied" error is/was probably caused by the absence of the socket (/home/teddycrepineau/contoursandcolors/contoursandcolors.sock). This socket ...
Read more >Django admin Server Error (500) when saving
Your app wasn't able to restart properly due to its tmp/uwsgi.pid being out of sync. I fixed that by running cd ~/apps/ibp; pgrep...
Read more >Permission error on live server - Using Django
You then need to verify that if the file doesn't exist in the identified location, where it does exist and modify the code...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
After https://github.com/openwisp/ansible-openwisp2/commit/17a9099b895d4fc90314737cf341cd776f58c01a I have not noticed this problem anymore, so I think it’s ok to close this issue now, I will reopen if I encounter it again.
@atb00ker the problem I found manifests on running instances, not during installation, the only thing we can do now is collect information and understand how to replicate this issue, if it can be replicated.