Closed
Description
- Gitea version (or commit ref): 1.1.1 (using gitea:1.1.1 from docker hub)
- Git version: 2.8.3
- Operating system: Ubuntu as host system (but running official docker image)
- Database (use
[x]):- PostgreSQL
- MySQL
- MSSQL
- SQLite
- Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
- Log gist: (real org, repo and ips redacted)
[Macaron] 2017-05-09 11:54:12: Started POST /org/repo/compare/master...pr-test for 1.2.3.4
[Macaron] 2017-05-09 11:54:13: Completed /org/repo/compare/master...pr-test 302 Found in 1.06402539s
[Macaron] 2017-05-09 11:54:13: Started GET /org/repo/pulls/24 for 1.2.3.4
[Macaron] 2017-05-09 11:54:13: Completed /org/repo/pulls/24 500 Internal Server Error in 77.113788ms
[Macaron] 2017-05-09 11:54:14: Started GET /lms for 3.4.5.6
[Macaron] 2017-05-09 11:54:14: Completed /lms 200 OK in 4.469068ms
Description
The 500 internal server error only shows up on some repositories. I have tried on both try.gitea.io and on our self hosted gitea and PRs work just fine on a brand new small repo (like two tiny text files). However on some repositories it seems we always get 500 back.
Unfortunately there's no other information than the 500 Internal Server Error message in the log. Can I enable more verbose logging somehow or are there other logs to dig from? This is trivial for me to reproduce in our environment so should be easy for me to get to the bottom if I get some assistance in digging :)