Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
500 Service Error - when try to save a testrun #191
WARNING: do not publically report security issues in the bug tracker!
Description of problem
generated a testcase. Want to create a testrun. If i push "save" button to store my testrun "500 Service Error" pops up.
Component (web, API, etc)
Kiwi Docker Image @ Debian 8.0 System
Version or commit hash (if applicable)
How often reproducible
Steps to Reproduce
Error pops ub
i can create testcases, create users.... but i cant save test run
first off all, sorry for my late replay. i wasn´t in office this morning.
@xbln : i didnt changed test_case_status nor test_case_run_status
@atodorov : what do you mean by "latest master"? where do i find the traceback/log.file? DEBUG is activited. I didnt change/modify anything with language.
i tried to update the container with:
but i got this error:
Should i try to reinstall kiwi docker-image?
thx for your fast support!
With DEBUG=True traceback should be printed in the browser instead getting a 500 error page.
Try rebuilding the docker image from the latest checkout from git.
I would always suggest to use the latest https://github.com/MrSenko/kiwi-docker docker image. For that repository you need a login. You can ask Alex for the credencials.
To use the latest "official" image, preferably on a standard environment like the digitalocean docker droplet, will help to find out bugs by isolating them from errors made by rebuilding the image on a home grown environment.
For error tracking it was very useful for me adding a phpmyadmin container to the installation.
@jehoff when you have DEBUG=True in your settings Django will not display a 500 page but a traceback and an autogenerated page in the browser. The fact that you are not seeing this means your settings have not been changed. Inside the running container Python traceback should be printed in
You can try running Kiwi TCMS locally and see if you can reproduce:
Is there more user-friendly way to check the log? I'm not an expert in web-docker stuff, but for me it looks like overhead to go into docker container for the logs, I would expect them to be in real filesystem\in some mounted docker volume, which is accessible from outside of the container
It is not too hard to step "inside" the running container. Just type
You can also copy content from inside a running container to your host filesystem by typing
We're working on making this easier to detect programatically and be reported to us automatically via Sentry. When done you can switch to your own Sentry credentials and debug yourself.
The easiest way is to set DEBUG=True and have the traceback in the browser. This is the standard Django practice.
You are using a Docker container to run software so it is understandable that logs and other files will be inside the docker container. Exposing these directories via volumes and mounting them on the host will probably work (you have to update your docker-compose.yml to configure that) but be aware this can have all sorts of issues with file ownership and permissions between the host and the container not to mention SELinux. Also this kind of mapping isn't universally applicable to everyone because we have no idea in what environment do you run your docker compose or even if you use compose at all.
Will do, this is definitely a good suggestion.