What am I supposed to do about an Internal server error from GitLab?

Matthew Selsky Matthew.Selsky at twosigma.com
Tue Dec 5 14:24:46 UTC 2017

On Mon, Dec 04, 2017 at 10:38:13PM -0800, Hal Murray via devel wrote:
> Subject: ntpsec | Pipeline #14729097 has failed for master | 3c1cc3c8
> From: GitLab <gitlab at mg.gitlab.com>
> Commit: 3c1cc3c8 ( https://gitlab.com/NTPsec/ntpsec/commit/3c1cc3c8317faa48ce8
> e5b8ef7909c16cb04deab )
> Commit Message: Fix ntpq -c direct -c mrulist to output seconds...
> Commit Author: Hal Murray
> Removing build/
> Removing ntpd/version.h
> Removing wafhelpers/.autorevision-cache
> HEAD is now at 3c1cc3c Fix ntpq -c direct -c mrulist to output seconds
> remote: Internal server error
> fatal: unable to access 'https://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@gitlab.com/NTPsec/ntpsec.git/': The requested URL returned error: 500
> section_end:1512453213:get_sources

You can retry the specific job that failed via https://gitlab.com/NTPsec/ntpsec/-/jobs/$job and click retry.  There was no reported gitlab outage last night (per http://twitter.com/gitlabstatus, but this sort of thing isn't abnormal to occur periodically.


More information about the devel mailing list