From 4f876b648bcb539ea1521f1a7bbab83eebb1bf90 Mon Sep 17 00:00:00 2001 From: AnomicDev Date: Sun, 14 Apr 2024 00:53:16 +0000 Subject: [PATCH] Update troubleshooting.md --- docs/maintenance/troubleshooting.md | 50 ++++++++++++++--------------- 1 file changed, 25 insertions(+), 25 deletions(-) diff --git a/docs/maintenance/troubleshooting.md b/docs/maintenance/troubleshooting.md index 040a26e2..6c860586 100644 --- a/docs/maintenance/troubleshooting.md +++ b/docs/maintenance/troubleshooting.md @@ -8,31 +8,6 @@ To record DEBUG messages in the log file, alter a setting in your auth project's ## 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 ### 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.** +### 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 This usually indicates an issue with your email settings. Ensure these are correct and your email server/service is properly configured.