please wait while jenkins is restarting- waiting long

Question

I updated some plugins and restarted the jenkins but now it says:

Please wait while Jenkins is restarting

Your browser will reload automatically when Jenkins is ready.

It is taking too much time (waiting from last 40 minutes). I have only 1 project with around 20 builds. I have restarted jenkins many times and worked fine but now it stucks. Is there any way out to kill/suspend jenkins to avoid this wait?

Try refreshing/reloading your jenkins website. Sometimes the auto refresh doesn't work at that part. — André Stannek, Jun 27 '13 at 13:19

molholm · Accepted Answer · 2015-11-19T07:06:29.743

21

I had a very similar issue when using jenkins build-in restart function. To fix it I killed the service (with crossed fingers), but somehow it kept serving the "Please wait" page. I guess it is served by a separate thread, but since i could not see any running java or jenkins processes i restarted the server to stop it.

After reboot jenkins worked but it was not updated. To make it work it I ran the update again and restarted the jenkins service manually - it took less than a minute and worked just fine...

Jenkins seems to have a number of bugs related to restarting, and at least one unresolved: jenkins issue

edited Nov 19 '15 at 07:06

answered Nov 05 '13 at 13:04

molholm

1,992
3
25
29

1

+1 I did `service jenkins restart` and that didn't help, but after rebooting the server Jenkins started up fine. – Scott Weldon Nov 18 '15 at 22:12
Just like windows OS , even Mac and Linux needs restart to fix issues; some times :) – vikramvi Dec 05 '16 at 13:58
sorry this didn't work for me, but answer from johnnynemonic did the trick. I was updating the plugin and jenkins went kapput. – vikramvi Dec 05 '16 at 15:03

score 18 · Answer 2 · answered Jun 21 '16 at 15:22

18

Windows ONLY....

All the solutions here didn't work and restarting the server was not an option. If you are in the same situation.

I had to kill java.exe and restart the jenkins service. After I did this Jenkins reloaded several times and then went back to normal.

I was stuck on the jenkins restarting page for 10-ish minutes untill I did this.

Hope this helps.

answered Jun 21 '16 at 15:22

TheNoob

861
2
11
25

I also restarted the Jenkins service and it worked. It did take 3-4 minutes after I restarted the service for the page to load up, though. So make sure you're patient before moving on to something else. – Optimus Dec 11 '18 at 12:32

score 8 · Answer 3 · answered Jun 30 '16 at 14:01

8

I had a similar issue when updating plugins from the pluging update page and I marked the restart jenkins options. jenkins only showed the waiting message for a long time.

I solved the issue restoring .bak to .jpi files of the the plugins that I tried to update.

I did the follow in my jenkins

cd $JENKINS_HOME/plugins/

>sudo mv git.bak git.jpi
.
. (more plugins files)
.
>sudo mv ldap.bak ldap.jpi

>sudo /sbin/service jenkins restart

answered Jun 30 '16 at 14:01

johnnymnmonic

774
8
11

This has solved for me as well, Jenkins is super buggy wrt plugin update feature. Spent 3 hrs to come to this solution. Thanks a ton @johnnynemonic – vikramvi Dec 05 '16 at 14:59
This worked for me! this answer needs more upvotes! It only worked after I restored *ALL* .bak files – Doug Apr 10 '18 at 15:34

score 7 · Answer 4 · answered Dec 03 '13 at 20:24

7

Running this in the command line helped me:

service jenkins restart

answered Dec 03 '13 at 20:24

alberto56

2,997
3
28
47

score 2 · Answer 5 · edited May 21 '14 at 15:35

Check Event Viewer.

I found that my Java died.

Faulting application java.exe, version 7.0.250.17, time stamp 0x51c4b3fd, faulting module ntdll.dll, version 6.0.6002.18541, time stamp 0x4ec3e39f, exception code 0xc0000374, fault offset 0x000abc4f, process id 0x1188, application start time 0x01cee4f42968bc81.

Finally I found that it's Jenkins 1.540 problem. Don't use it. https://issues.jenkins-ci.org/browse/JENKINS-20630

score 1 · Answer 6 · answered Nov 30 '16 at 17:03

I faced the same issue after upgrading some plugins on Windows. Looking on jenkins.err.log it displayed this error

Exception in thread "main" java.io.IOException: Jenkins has failed to create a temporary file in C:\Users\builder\AppData\Local\Temp\
    at Main.extractFromJar(Main.java:350)
    at Main._main(Main.java:194)
    at Main.main(Main.java:91)
Caused by: java.io.IOException: There is not enough space on the disk
    at java.io.WinNTFileSystem.createFileExclusively(Native Method)
    at java.io.File.createTempFile(Unknown Source)
    at Main.extractFromJar(Main.java:347)
    ... 2 more

The problem was that the TEMP folder of the jenkins user had lots of temporary files. After cleaning that folder jenkins restarted correctly.

score 1 · Answer 7 · answered Oct 24 '17 at 17:04

1

just performed a restart on the server. That fixed the issue !

answered Oct 24 '17 at 17:04

Nabeel A.Rahman

181
3
14

score 1 · Answer 8 · answered Aug 05 '19 at 18:36

1

In Command prompt execute this

C:\>service jenkins restart

Or

You can go for Service currently running in your machine( Win + R ) seach for Jenkins and Click on restart

answered Aug 05 '19 at 18:36

Lova Chittumuri

2,994
1
30
33

score 1 · Answer 9 · answered Jun 15 '20 at 23:33

1

For me, the cause seemed to be having lots of old job build logs hanging around. To clean them up, I ran:

cd $JENKINS_HOME/jobs
find -name 'builds' | xargs -n 1 bash -c 'rm -rf $0/[1-9]*'

Then I stopped and started Jenkins again, and it came up within a minute.

Credit to: https://stackoverflow.com/a/39230597/2255242

answered Jun 15 '20 at 23:33

Jack Davidson

4,613
2
27
31

That's pretty drastic. It deletes ALL your builds. It should also be noted that you shouldn't try this while Jenkins is running. – Steven the Easily Amused Aug 23 '22 at 22:58

score 1 · Answer 10 · answered Jun 30 '20 at 19:49

1

This is an old thread.. but my personal recommendation is to WAIT before attempting to do anything (such as restarting service, etc).

I wasted hours once trying to fix something that turned out to be not an issue in the first place. In the end, I messed things up and wasted a lot of time.

Just because you see errors in the logs doesn't necessarily mean that you need to take action.

The upgrade took about 45 minutes in the end for me. All i did at one point was refreshing my browser window. It can take a while.

Just my opinion

answered Jun 30 '20 at 19:49

xav

812
8
9

I've also found this to be the case. – Beans Feb 10 '22 at 04:51
This was also my experience recently. I was losing patience and kept trying to find what's wrong, restarted the thing after 30-40 minutes. There was no proxy issue, etc. Restarts of various kinds didn't work. Saw this, started it all up and went to lunch. Shortly after I got back it all came together without further messing. (I'll guestimate it was going about 50-60 minutes. Thank you for your response! – Pete Kelley Dec 09 '22 at 18:03

score 0 · Answer 11 · answered Jun 24 '16 at 14:44

0

On Win 10: Stopping with the service command from the command line reported failure to stop the service, but I was able to stop it from services.msc (running as administrator). The updates were applied. Sorry, no definitive answer from me. YMMV.

answered Jun 24 '16 at 14:44

Jason Young

439
1
8
18

score 0 · Answer 12 · answered Jan 19 '18 at 11:01

0

I used TCPView and killed process that was using port 8080. BAsically it was all Java.exe from Jenkins. Killed all processes and restarted Jenkins Service

answered Jan 19 '18 at 11:01

SamirBhatt

66
6

score 0 · Answer 13 · answered Nov 20 '18 at 15:48

0

try to restart that inside windows services console, it will work

answered Nov 20 '18 at 15:48

kaisfarza

73
1
7

score 0 · Answer 14 · answered Jun 28 '19 at 06:09

I have observed the same issue after installing a plugin and opting to restart the jenkins when no jobs are running. When I looked at the jenkins server process, it was running fine and no issues. On restarting the jenkins service using the below command and reloading the browser, Jenkins was up.

sudo service jenkins restart

score 0 · Answer 15 · answered Aug 23 '22 at 22:54

If Jenkins is taking an unusually long time to restart the best recourse is to check the generated logs to see what may be wrong. However, even that may be of little help because many plugins try to be "quiet" by default, even if they are furiously working to load content. So if all else fails, you may have to resort to manually disabling plugins.

However here is a free tip: Some plugins are known to be messy. For example the Job Config History plugin we observed to write hundreds of thousands of records for both job configuration changes AND agent changes. Removing this plugin, and deleting the configHistory folder fixed one problem where our startup literally took > 4 hours.

In our case, the problem was we were launching ephemeral agents (via docker and/or kubernetes). Each new "agent" was treated as a configuration change. With thousands of agents per day, it didn't take long to fill up a substantial part of the disk with history that never was effectively cleared.

There are other plugins that leak data in this way. And you can also create self-inflicted wounds, e.g. by using a standalone process to remove "obsolete" files. An example where we were "bitten" is a process that tried to discard old build records, but did an incomplete job - and was "warring" with the running Jenkins process. Jenkins will try breaking its neck to load a build.xml record that is empty or incomplete.

Three more tips:

You can install the monitoring plugin. Often when the jenkins UI proper didn't start, we were able to see the /monitoring in action.
Likewise, /userContent can often be loaded even when the rest of the UI is not fully up.
Don't rule out bad actors. It just takes one aggressive script that tries, e.g. to load the entire build history and ship it back via a REST call to effectively deny service to all other UI users.

score -1 · Answer 16 · edited Oct 21 '22 at 09:38

-1

I try to fix a file named hudson.model.UpdateCenter.xml located /var/lib/jenkins

I change the URL to https://mirrors.tuna.tsinghua.edu.cn/jenkins/updates/update-center.json

Finally, restart Jenkins. it solves my problem

edited Oct 21 '22 at 09:38

Ali

922
1
9
24

answered Feb 20 '20 at 13:22

ZIJING QIN

1

please wait while jenkins is restarting- waiting long

16 Answers16

Linked