-
Bug
-
Resolution: Fixed
-
Major
-
Linux 2.6.18-402.el5 and 2.6.32-504.16.2.el6.x86_64
jdk1.8.0_72
Google Chrome browser for UI.
Also on 1.654
We have two Jenkins instances in operation. One was at revision 1.651 and the other was at Jenkins 1.652. The servers themselves are Linux 2.6.18-402.el5 and 2.6.32-504.16.2.el6.x86_64 Operating system.
I upgraded the Jenkins to 1.653 and checked the restart option through the web UI. The system appeared to come up and run normally, but as the day progresses, the machines began to seem sluggish. I decided to use the
option to see if this would have a benefit. Instead, I got a White Screen of Death (WSoD=The web UI would not time out and remained blank/white). I did the same thing to the other server and saw the same result.http://<hostname>:8080/restart
I logged into the machine command line for both servers, killed the Jenkins process, moved the ${JENKINS_HOME}/jenkins.war to ${JENKINS_HOME}/jenkins.war.new, copied the ${JENKINS_HOME}/jenkins.war.bak to ${JENKINS_HOME}/jenkins.war, and executed "rm -f nohup.out; nohup java -jar jenkins.war" to restart the process. I then rolled back the slave.jar version (to 2.53.2) on all the slave machines and restarted their connections to the master server as well.
The system recovered and the Jenkins UI was again visible. Based on this experience, I would say there is an issue with the 1.653 release of Jenkins that can cause the White Screen of Death issue very repeatably in our environments after a restart command.
- is related to
-
-
- Resolved
-
-
-
- Resolved
-
[JENKINS-33597] White Screen of Death (in the web UI) when updating to Jenkins 1.653
Brian Wilson
added a comment - I've added the core support plugin zip file from my private VM test. This VM has the same plugins as our other two servers (they are all configured the same) with the exception that the others don't have the core support plugin (yet).
Brian Wilson
added a comment - I've added the core support plugin zip file from my private VM test. This VM has the same plugins as our other two servers (they are all configured the same) with the exception that the others don't have the core support plugin (yet). I've installed the Jenkins 1.654 revision to our test server and still get the WSoD (White Screen of Death) on the second restart command (i.e. if I install any plugins, issue a restart on the URL line, or in some other way restart the Jenkins instance). This is a critical error for our installations.
Brian Wilson
added a comment - - edited I've installed the Jenkins 1.654 revision to our test server and still get the WSoD (White Screen of Death) on the second restart command (i.e. if I install any plugins, issue a restart on the URL line, or in some other way restart the Jenkins instance). This is a critical error for our installations. Same thing on 1.654, please fix it!
This issue is already fixed on https://issues.jenkins-ci.org/browse/JENKINS-19248
and here: https://issues.jenkins-ci.org/browse/JENKINS-19511,
sagi winogron
added a comment - - edited Same thing on 1.654, please fix it!
This issue is already fixed on https://issues.jenkins-ci.org/browse/JENKINS-19248
and here: https://issues.jenkins-ci.org/browse/JENKINS-19511 , Confirmed. The WSoD did not occur on our test Linux platform when we installed 1.655 release and did a restart on the URL line. Thank you!
Brian Wilson
added a comment - - edited Confirmed. The WSoD did not occur on our test Linux platform when we installed 1.655 release and did a restart on the URL line. Thank you! Brian Wilson
added a comment - Confirmed this has been resolved in the 1.655 release. I tested this on a Linux RHEL5 platform which had previously shown the WSoD issue. With the upgrade to 1.655, the system returned and displayed the UI properly after a restart from the UI URL line. I tried two restarts just to make sure this continued to work and observed no UI issues.
Brian Wilson
added a comment - Confirmed this has been resolved in the 1.655 release. I tested this on a Linux RHEL5 platform which had previously shown the WSoD issue. With the upgrade to 1.655, the system returned and displayed the UI properly after a restart from the UI URL line. I tried two restarts just to make sure this continued to work and observed no UI issues. 
I've been able to spin up a private VM with a similar profile:
Linux 2.6.18-402.el5
jdk1.8.0_66
etc.
I went through the web UI update from 1.652 to 1.653 and checked the restart button. The system seemed to restart and the 1.653 revision did show in the lower right corner. When I executed the "http://<host_name>:8080/restart" option, I again got the blank white web UI screen. This has happened on three different Master servers very consistently. I think there is a serious issue with the 1.653 release.