mirror of
https://gitlab.com/allianceauth/allianceauth.git
synced 2025-07-09 12:30:15 +02:00
Update troubleshooting.md
This commit is contained in:
parent
cd738137c0
commit
4f876b648b
@ -8,31 +8,6 @@ To record DEBUG messages in the log file, alter a setting in your auth project's
|
|||||||
|
|
||||||
## Common Problems
|
## Common Problems
|
||||||
|
|
||||||
### I'm getting error 500 when trying to connect to the website on a new installation
|
|
||||||
|
|
||||||
*Great.* Error 500 is the generic message given by your web server when *anything* breaks. The actual error message is hidden in one of your auth project's log files. Read them to identify it.
|
|
||||||
|
|
||||||
### Failed to configure log handler
|
|
||||||
|
|
||||||
Make sure the log directory is writeable by the allianceserver user: `chmown -R allianceserver:allianceserver /path/to/myauth/log/`, then restart the auth supervisor processes.
|
|
||||||
|
|
||||||
### Groups aren't syncing to services
|
|
||||||
|
|
||||||
Make sure the background processes are running: `supervisorctl status myauth:`. If `myauth:worker` or `myauth:beat` do not show `RUNNING` read their log files to identify why.
|
|
||||||
|
|
||||||
### Task queue is way too large
|
|
||||||
|
|
||||||
Stop celery workers with `supervisorctl stop myauth:worker` then clear the queue:
|
|
||||||
|
|
||||||
```shell
|
|
||||||
redis-cli FLUSHALL
|
|
||||||
celery -A myauth worker --purge
|
|
||||||
```
|
|
||||||
|
|
||||||
Press Control+C once.
|
|
||||||
|
|
||||||
Now start the worker again with `supervisorctl start myauth:worker`
|
|
||||||
|
|
||||||
## Steps to Check Logs for Errors
|
## Steps to Check Logs for Errors
|
||||||
|
|
||||||
### Locate the Logs:
|
### Locate the Logs:
|
||||||
@ -62,6 +37,31 @@ Troubleshooting Tips
|
|||||||
|
|
||||||
**Important Note: Before sharing logs publicly, sanitize any sensitive information such as usernames, passwords, or API keys.**
|
**Important Note: Before sharing logs publicly, sanitize any sensitive information such as usernames, passwords, or API keys.**
|
||||||
|
|
||||||
|
### I'm getting error 500 when trying to connect to the website on a new installation
|
||||||
|
|
||||||
|
*Great.* Error 500 is the generic message given by your web server when *anything* breaks. The actual error message is hidden in one of your auth project's log files. Read them to identify it.
|
||||||
|
|
||||||
|
### Failed to configure log handler
|
||||||
|
|
||||||
|
Make sure the log directory is writeable by the allianceserver user: `chmown -R allianceserver:allianceserver /path/to/myauth/log/`, then restart the auth supervisor processes.
|
||||||
|
|
||||||
|
### Groups aren't syncing to services
|
||||||
|
|
||||||
|
Make sure the background processes are running: `supervisorctl status myauth:`. If `myauth:worker` or `myauth:beat` do not show `RUNNING` read their log files to identify why.
|
||||||
|
|
||||||
|
### Task queue is way too large
|
||||||
|
|
||||||
|
Stop celery workers with `supervisorctl stop myauth:worker` then clear the queue:
|
||||||
|
|
||||||
|
```shell
|
||||||
|
redis-cli FLUSHALL
|
||||||
|
celery -A myauth worker --purge
|
||||||
|
```
|
||||||
|
|
||||||
|
Press Control+C once.
|
||||||
|
|
||||||
|
Now start the worker again with `supervisorctl start myauth:worker`
|
||||||
|
|
||||||
### Proxy timeout when entering email address
|
### Proxy timeout when entering email address
|
||||||
|
|
||||||
This usually indicates an issue with your email settings. Ensure these are correct and your email server/service is properly configured.
|
This usually indicates an issue with your email settings. Ensure these are correct and your email server/service is properly configured.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user