Problems installing Grape¶
Are you running a support docker-engine and docker compose version?
Please check the Quickstart Checklist and down- or upgrade.
I don’t see any error messages¶
journalctl --follow --since='-15 minutes'
if you are running systemd or
tail -f /var/log/syslog
Grape is online but has problems¶
You can run the selftest for a quick overview:
in the browser: https://your_grape_server/debug/self-test/
(Note: only Grape admin users can access this page)
in the terminal:
python manage.py selftest
Problems using Grape, Error 500¶
Check if you can see an error in Sentry at the time the problem happened. It helps the Grape team if you have an error in sentry that correlates to you problem.
Problems after upgrading Grape¶
My Grape instance just show the “We are busy updating Grape” screen¶
Please check the output of the runtime container:
docker logs application_grape-runtime_1 | tail -n 30
Grape (gunicorn process) uses ~100%¶
First try restarting the grape-application by running
cd /data/grape/config/application && docker-compose restart
and wait until it comes back up.
If this does not help:
Inspect what the process is doing:
- Find the process id of
gunicornE.g. with ps (as root on the host machine)
ps aux | grep gunicorn
- Inspect it using strace
strace -p PID_OF_GUNICORN
A bug appeared after upgrading to a new version¶
Use your VM snapshot to recover the last working version.
If you don’t have a VM snapshot:
- Take a VM snapshot!
- Look up the previous release in the changelog or your inbox.
- Downgrade to that version, e.g.
grape install --custom-version onpremises-3.3.9
YMMV with this approach. Always make a backup before an upgrade!