Constant 500 Errors


#1

Getting this on a daily basis. This seems to be a common problem with no solution that I’ve seen.
Have to login via SSH and restart, every time.


#2

Hi @skunkworks_ca Please add some more information about the 500 error from the logs. I’m going to assume that you have installed GitLab via the omnibus package.

When you next experience the 500 error, tail the logs on the server to gather the stack trace so that we can determine the source of the error:

sudo gitlab-ctl tail

This will allow the log entries to be displayed in the terminal when you reproduce the error. Please copy the errors that you discover here, ensuring to remove any sensitive data before posting :smiley:

Thanks!


#3

Hi @markglenfletcher, Making sure I understood your instructions properly…

When next we get the error, log in to the server as root via SSH and run that command which will output info needed to diagnose further?


#4

Run the command and reproduce the 500 error to log it to the terminal. It’ll save searching through the log files for the errors. From there it’ll be much easier to help. Thanks!

If the error is not easy to reproduce on command then you may need to search the logs at:

/var/log/gitlab/gitlab-rails/production.log

Search for ‘Internal Server Error’


#5

If the error is not easy to reproduce on command then you may need to search the logs at:

/var/log/gitlab/gitlab-rails/production.log
Search for ‘Internal Server Error’

String ‘Internal Server Error’ not present in production.log (Checked immediately after the error.)
Interestingly… this time the 500 error went away on a browser refresh a minute later.


#6

Please update if you find the error in the logs, tail the last 500 lines of the production.log straight after you see the 500 error. You should be able to find it :slight_smile:


#7

This is happening now on the main gitlab site, its quite frequent actually.


#8

Hi Gtilab,

We are testing Gitlab to export a single file from a repository at Gitlab.com. We use Python to do this.

It works great, but we do get regular Error 500’s. Logging in at gitlab.com won’t work either then.

The error messages we receive let us know that the problem is at Gitlab’s end. Is there anythin on our end we can do to prevent these messages?