Gitlab CE Omnibus Started to Get 503 Error The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!Set gitlab external web port numberApache as a reverse proxy for GitLab OmnibusGitlab backup file location (Omnibus installation)How to setup Gitlab-omnibus with non-bundled web-server?Gitlab Omnibus, can't view most commits (500) and very slowGitlab omnibus update error (8.0.1 to 8.0.2)Using GitLab Omnibus behind NginxGitlab omnibus fails to add ssh keyGitlab Omnibus login broken after updateNo prometheus in Gitlab Omnibus
Would an alien lifeform be able to achieve space travel if lacking in vision?
Student Loan from years ago pops up and is taking my salary
how can a perfect fourth interval be considered either consonant or dissonant?
University's motivation for having tenure-track positions
What aspect of planet Earth must be changed to prevent the industrial revolution?
What is the padding with red substance inside of steak packaging?
Can each chord in a progression create its own key?
Why can't wing-mounted spoilers be used to steepen approaches?
US Healthcare consultation for visitors
Why don't hard Brexiteers insist on a hard border to prevent illegal immigration after Brexit?
Variable with quotation marks "$()"
Are there continuous functions who are the same in an interval but differ in at least one other point?
How can a C program poll for user input while simultaneously performing other actions in a Linux environment?
Did the UK government pay "millions and millions of dollars" to try to snag Julian Assange?
Is this wall load bearing? Blueprints and photos attached
ELI5: Why do they say that Israel would have been the fourth country to land a spacecraft on the Moon and why do they call it low cost?
Sub-subscripts in strings cause different spacings than subscripts
Do warforged have souls?
Can the DM override racial traits?
How to handle characters who are more educated than the author?
Separating matrix elements by lines
First use of “packing” as in carrying a gun
Homework question about an engine pulling a train
Does Parliament hold absolute power in the UK?
Gitlab CE Omnibus Started to Get 503 Error
The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Set gitlab external web port numberApache as a reverse proxy for GitLab OmnibusGitlab backup file location (Omnibus installation)How to setup Gitlab-omnibus with non-bundled web-server?Gitlab Omnibus, can't view most commits (500) and very slowGitlab omnibus update error (8.0.1 to 8.0.2)Using GitLab Omnibus behind NginxGitlab omnibus fails to add ssh keyGitlab Omnibus login broken after updateNo prometheus in Gitlab Omnibus
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I've installed GitLab on a CentOS 7 using the Omnibus installer a few months ago. It has ran fine but, today it started to throw a 503 error page when I visit the main page to login.
I ran the gitlab-ctl status command and I don't see anything jumping out at me that shows there is a problem. Does anyone know where to go from here?
# gitlab-ctl status
run: alertmanager: (pid 4591) 14837s; run: log: (pid 4590) 14837s
run: gitaly: (pid 4580) 14837s; run: log: (pid 4579) 14837s
run: gitlab-monitor: (pid 4574) 14837s; run: log: (pid 4572) 14837s
run: gitlab-workhorse: (pid 4583) 14837s; run: log: (pid 4581) 14837s
run: logrotate: (pid 15028) 436s; run: log: (pid 4567) 14837s
run: nginx: (pid 4573) 14837s; run: log: (pid 4571) 14837s
run: node-exporter: (pid 4584) 14837s; run: log: (pid 4582) 14837s
run: postgres-exporter: (pid 4568) 14837s; run: log: (pid 4566) 14837s
run: postgresql: (pid 4593) 14837s; run: log: (pid 4592) 14837s
run: prometheus: (pid 4586) 14837s; run: log: (pid 4585) 14837s
run: redis: (pid 4562) 14837s; run: log: (pid 4560) 14837s
run: redis-exporter: (pid 4576) 14837s; run: log: (pid 4575) 14837s
run: sidekiq: (pid 4559) 14837s; run: log: (pid 4558) 14837s
run: unicorn: (pid 23104) 1s; run: log: (pid 4577) 14837s
I went on to use gitlab-ctl tail per suggestions in comments and found references to a stale unicorn pid file. Simply restarting all services with gitlab-ctl restart made the 503 error go away and all is well after that. Still not sure why unicorn decided to crash though.
centos7 gitlab
asked Apr 8 at 15:10
SciGuyMcQSciGuyMcQ
1163
New contributor
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I've installed GitLab on a CentOS 7 using the Omnibus installer a few months ago. It has ran fine but, today it started to throw a 503 error page when I visit the main page to login.
I ran the gitlab-ctl status command and I don't see anything jumping out at me that shows there is a problem. Does anyone know where to go from here?
# gitlab-ctl status
run: alertmanager: (pid 4591) 14837s; run: log: (pid 4590) 14837s
run: gitaly: (pid 4580) 14837s; run: log: (pid 4579) 14837s
run: gitlab-monitor: (pid 4574) 14837s; run: log: (pid 4572) 14837s
run: gitlab-workhorse: (pid 4583) 14837s; run: log: (pid 4581) 14837s
run: logrotate: (pid 15028) 436s; run: log: (pid 4567) 14837s
run: nginx: (pid 4573) 14837s; run: log: (pid 4571) 14837s
run: node-exporter: (pid 4584) 14837s; run: log: (pid 4582) 14837s
run: postgres-exporter: (pid 4568) 14837s; run: log: (pid 4566) 14837s
run: postgresql: (pid 4593) 14837s; run: log: (pid 4592) 14837s
run: prometheus: (pid 4586) 14837s; run: log: (pid 4585) 14837s
run: redis: (pid 4562) 14837s; run: log: (pid 4560) 14837s
run: redis-exporter: (pid 4576) 14837s; run: log: (pid 4575) 14837s
run: sidekiq: (pid 4559) 14837s; run: log: (pid 4558) 14837s
run: unicorn: (pid 23104) 1s; run: log: (pid 4577) 14837s
I went on to use gitlab-ctl tail per suggestions in comments and found references to a stale unicorn pid file. Simply restarting all services with gitlab-ctl restart made the 503 error go away and all is well after that. Still not sure why unicorn decided to crash though.
centos7 gitlab
asked Apr 8 at 15:10
SciGuyMcQSciGuyMcQ
1163
New contributor
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Is the disk full? Have you looked at the logs?/var/log/gitlabor rungitlab-ctl tail.
– Aaron Copley
Apr 8 at 15:46
thanks, I did eventually find the tail command then looked in /var/log/gitlab/unicorn and found a stale unicorn pid file message
– SciGuyMcQ
Apr 8 at 16:40
1
It's ok to post a self-answer - it will be very usable for future readers.
– kubanczyk
Apr 9 at 7:54
add a comment |
I've installed GitLab on a CentOS 7 using the Omnibus installer a few months ago. It has ran fine but, today it started to throw a 503 error page when I visit the main page to login.
I ran the gitlab-ctl status command and I don't see anything jumping out at me that shows there is a problem. Does anyone know where to go from here?
# gitlab-ctl status
run: alertmanager: (pid 4591) 14837s; run: log: (pid 4590) 14837s
run: gitaly: (pid 4580) 14837s; run: log: (pid 4579) 14837s
run: gitlab-monitor: (pid 4574) 14837s; run: log: (pid 4572) 14837s
run: gitlab-workhorse: (pid 4583) 14837s; run: log: (pid 4581) 14837s
run: logrotate: (pid 15028) 436s; run: log: (pid 4567) 14837s
run: nginx: (pid 4573) 14837s; run: log: (pid 4571) 14837s
run: node-exporter: (pid 4584) 14837s; run: log: (pid 4582) 14837s
run: postgres-exporter: (pid 4568) 14837s; run: log: (pid 4566) 14837s
run: postgresql: (pid 4593) 14837s; run: log: (pid 4592) 14837s
run: prometheus: (pid 4586) 14837s; run: log: (pid 4585) 14837s
run: redis: (pid 4562) 14837s; run: log: (pid 4560) 14837s
run: redis-exporter: (pid 4576) 14837s; run: log: (pid 4575) 14837s
run: sidekiq: (pid 4559) 14837s; run: log: (pid 4558) 14837s
run: unicorn: (pid 23104) 1s; run: log: (pid 4577) 14837s
I went on to use gitlab-ctl tail per suggestions in comments and found references to a stale unicorn pid file. Simply restarting all services with gitlab-ctl restart made the 503 error go away and all is well after that. Still not sure why unicorn decided to crash though.
centos7 gitlab
asked Apr 8 at 15:10
SciGuyMcQSciGuyMcQ
1163
New contributor
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I've installed GitLab on a CentOS 7 using the Omnibus installer a few months ago. It has ran fine but, today it started to throw a 503 error page when I visit the main page to login.
I ran the gitlab-ctl status command and I don't see anything jumping out at me that shows there is a problem. Does anyone know where to go from here?
# gitlab-ctl status
run: alertmanager: (pid 4591) 14837s; run: log: (pid 4590) 14837s
run: gitaly: (pid 4580) 14837s; run: log: (pid 4579) 14837s
run: gitlab-monitor: (pid 4574) 14837s; run: log: (pid 4572) 14837s
run: gitlab-workhorse: (pid 4583) 14837s; run: log: (pid 4581) 14837s
run: logrotate: (pid 15028) 436s; run: log: (pid 4567) 14837s
run: nginx: (pid 4573) 14837s; run: log: (pid 4571) 14837s
run: node-exporter: (pid 4584) 14837s; run: log: (pid 4582) 14837s
run: postgres-exporter: (pid 4568) 14837s; run: log: (pid 4566) 14837s
run: postgresql: (pid 4593) 14837s; run: log: (pid 4592) 14837s
run: prometheus: (pid 4586) 14837s; run: log: (pid 4585) 14837s
run: redis: (pid 4562) 14837s; run: log: (pid 4560) 14837s
run: redis-exporter: (pid 4576) 14837s; run: log: (pid 4575) 14837s
run: sidekiq: (pid 4559) 14837s; run: log: (pid 4558) 14837s
run: unicorn: (pid 23104) 1s; run: log: (pid 4577) 14837s
I went on to use gitlab-ctl tail per suggestions in comments and found references to a stale unicorn pid file. Simply restarting all services with gitlab-ctl restart made the 503 error go away and all is well after that. Still not sure why unicorn decided to crash though.
centos7 gitlab
centos7 gitlab
asked Apr 8 at 15:10
SciGuyMcQSciGuyMcQ
1163
New contributor
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 8 at 15:10
SciGuyMcQSciGuyMcQ
1163
New contributor
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Apr 8 at 16:39
SciGuyMcQ
asked Apr 8 at 15:10
SciGuyMcQSciGuyMcQ
1163
New contributor
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 8 at 15:10
SciGuyMcQSciGuyMcQ
1163
asked Apr 8 at 15:10
SciGuyMcQSciGuyMcQ
1163
1163
New contributor
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Is the disk full? Have you looked at the logs?/var/log/gitlabor rungitlab-ctl tail.
– Aaron Copley
Apr 8 at 15:46
thanks, I did eventually find the tail command then looked in /var/log/gitlab/unicorn and found a stale unicorn pid file message
– SciGuyMcQ
Apr 8 at 16:40
1
It's ok to post a self-answer - it will be very usable for future readers.
– kubanczyk
Apr 9 at 7:54
add a comment |
1
Is the disk full? Have you looked at the logs?/var/log/gitlabor rungitlab-ctl tail.
– Aaron Copley
Apr 8 at 15:46
thanks, I did eventually find the tail command then looked in /var/log/gitlab/unicorn and found a stale unicorn pid file message
– SciGuyMcQ
Apr 8 at 16:40
1
It's ok to post a self-answer - it will be very usable for future readers.
– kubanczyk
Apr 9 at 7:54
1
1
Is the disk full? Have you looked at the logs?
/var/log/gitlab or run gitlab-ctl tail.– Aaron Copley
Apr 8 at 15:46
Is the disk full? Have you looked at the logs?
/var/log/gitlab or run gitlab-ctl tail.– Aaron Copley
Apr 8 at 15:46
thanks, I did eventually find the tail command then looked in /var/log/gitlab/unicorn and found a stale unicorn pid file message
– SciGuyMcQ
Apr 8 at 16:40
thanks, I did eventually find the tail command then looked in /var/log/gitlab/unicorn and found a stale unicorn pid file message
– SciGuyMcQ
Apr 8 at 16:40
1
1
It's ok to post a self-answer - it will be very usable for future readers.
– kubanczyk
Apr 9 at 7:54
It's ok to post a self-answer - it will be very usable for future readers.
– kubanczyk
Apr 9 at 7:54
add a comment |
1 Answer
1
active
oldest
votes
I was able to fix the issue to get back up and running but, I'm unsure of the root cause.
first I used gitlab-ctl tail and found that there was a log message stating there was a stale unicorn PID file. This basically told me that unicorn application server had crashed for some reason or another.
I restarted all gitlab services with gitlab-ctl restart which takes a few minutes to properly shutdown and restart all services and eventually I was able to use GitLab under normal conditions again.
answered 17 hours ago
SciGuyMcQSciGuyMcQ
1163
New contributor
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
SciGuyMcQ is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962043%2fgitlab-ce-omnibus-started-to-get-503-error%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I was able to fix the issue to get back up and running but, I'm unsure of the root cause.
first I used gitlab-ctl tail and found that there was a log message stating there was a stale unicorn PID file. This basically told me that unicorn application server had crashed for some reason or another.
I restarted all gitlab services with gitlab-ctl restart which takes a few minutes to properly shutdown and restart all services and eventually I was able to use GitLab under normal conditions again.
answered 17 hours ago
SciGuyMcQSciGuyMcQ
1163
New contributor
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I was able to fix the issue to get back up and running but, I'm unsure of the root cause.
first I used gitlab-ctl tail and found that there was a log message stating there was a stale unicorn PID file. This basically told me that unicorn application server had crashed for some reason or another.
I restarted all gitlab services with gitlab-ctl restart which takes a few minutes to properly shutdown and restart all services and eventually I was able to use GitLab under normal conditions again.
answered 17 hours ago
SciGuyMcQSciGuyMcQ
1163
New contributor
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I was able to fix the issue to get back up and running but, I'm unsure of the root cause.
first I used gitlab-ctl tail and found that there was a log message stating there was a stale unicorn PID file. This basically told me that unicorn application server had crashed for some reason or another.
I restarted all gitlab services with gitlab-ctl restart which takes a few minutes to properly shutdown and restart all services and eventually I was able to use GitLab under normal conditions again.
answered 17 hours ago
SciGuyMcQSciGuyMcQ
1163
New contributor
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I was able to fix the issue to get back up and running but, I'm unsure of the root cause.
first I used gitlab-ctl tail and found that there was a log message stating there was a stale unicorn PID file. This basically told me that unicorn application server had crashed for some reason or another.
I restarted all gitlab services with gitlab-ctl restart which takes a few minutes to properly shutdown and restart all services and eventually I was able to use GitLab under normal conditions again.
answered 17 hours ago
SciGuyMcQSciGuyMcQ
1163
New contributor
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 17 hours ago
SciGuyMcQSciGuyMcQ
1163
New contributor
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 17 hours ago
SciGuyMcQSciGuyMcQ
1163
answered 17 hours ago
SciGuyMcQSciGuyMcQ
1163
1163
New contributor
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
SciGuyMcQ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
SciGuyMcQ is a new contributor. Be nice, and check out our Code of Conduct.
SciGuyMcQ is a new contributor. Be nice, and check out our Code of Conduct.
SciGuyMcQ is a new contributor. Be nice, and check out our Code of Conduct.
SciGuyMcQ is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962043%2fgitlab-ce-omnibus-started-to-get-503-error%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Is the disk full? Have you looked at the logs?
/var/log/gitlabor rungitlab-ctl tail.– Aaron Copley
Apr 8 at 15:46
thanks, I did eventually find the tail command then looked in /var/log/gitlab/unicorn and found a stale unicorn pid file message
– SciGuyMcQ
Apr 8 at 16:40
1
It's ok to post a self-answer - it will be very usable for future readers.
– kubanczyk
Apr 9 at 7:54