Troubleshooting

Enabling debug mode

There is a very verbose debug mode built into Sal. To enable it when using Docker, add the following to your startup command:

-e DOCKER_SAL_DEBUG=true

If you are using the legacy method, add the following to sal/settings.py:

DEBUG = True

This will cause any application error to throw up a detailled error (which will be returned by the preflight and postflight scripts if the error is on the client end). If you don't understand the error, post the full error to the Google Group.

NOTE: Enabling DEBUG = True also disables Nginx and instead uses the default Django Web Server.

Update Sal

You may be running a version with a known bug - install the latest version of both Sal and the Sal Scripts.

Docker: Check Logs in /tmp

Supervisord writes logs for salmain (gunicorn), nginx, the searchmaint job & itself to /tmp. Check these logs if the debug output does not contain the root cause exception, or for nginx errors.

Common issues

Resource constraints

• Description: If you are seeing supervisord consistently killing services as soon as they start up, it is likely that you are running up against resource constraints. If enabling DEBUG seems to solve this problem, it is even more likely to indicate resource issues as Nginx is no longer running in Debug (see above) and thus less resources are being consumed.
• Solution: Add more resources to your Sal compute
• Reference: Good Slack read starting here about the problem.