[JENKINS-38315] Please wait while Jenkins is getting ready to work

[timja]

Sorry, the Component/s is incorrect, nothing on the list matched.

I'm constantly getting
Please wait while Jenkins is getting ready to work
Your browser will reload automatically when Jenkins is ready.
I'm on rhel7 3.10.0-327.22.2.el7.x86_64

A vmware machine on an ESX cluster.

current jdk installed is jdk-8u101-linux-x64.rpm
[root@ftdcslbinf523 cbsunix]# rpm -qa | grep java
tzdata-java-2016e-1.el7.noarch
python-javapackages-3.4.1-11.el7.noarch
[root@ftdcslbinf523 cbsunix]# rpm -qa | grep jdk
jdk1.8.0_101-1.8.0_101-fcs.x86_64
[root@ftdcslbinf523 cbsunix]# java -version
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)

Installing jenkins-2.7.4-1.1.noarch.rpm

I've also tried java 1.7, Oracle linux 6.8 and jenkins-2.9-1.1.noarch.rpm

---

Originally reported by andrewj100, imported from: Please wait while Jenkins is getting ready to work

• status: Resolved
• priority: Major
• resolution: Not A Defect
• resolved: 2016-09-27T20:34:33+00:00
• imported: 2022/01/10

[timja]

markewaite:

You'll likely need to review the log files, and make initial guesses of what is failing. Many users run successfully on Red Hat 7 with JDK 8. I suspect there is something distinct in your environment which the logs may identify.

[timja]

andrewj100:

Hi Mark,
I’d agree with you that this is likely to be something related to the environment that’s causing this issue. The logs are precisely the problem I’m having, I’m not seeing any messages that are giving me a good starting point. I’ve left Jenkins running for about 12 hours hoping something would cause a timeout to occur that may point to a hung process or something.

So fat today I’ve done a back to back test on
jdk-7u79-linux-x64.rpm
and
jdk-8u101-linux-x64.rpm

I got the same behaviour from both.
I'll attach some output from the logs.

If I just run that war file I get
[root@ftdcslbinf523 jenkins]# /usr/java/jdk1.7.0_79/bin/java -jar jenkins.war --debug
Running from: /usr/lib/jenkins/jenkins.war
webroot: $user.home/.jenkins
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at Main._main(Main.java:246)
at Main.main(Main.java:91)
Caused by: java.lang.NumberFormatException: For input string: "true"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:492)
at java.lang.Integer.parseInt(Integer.java:527)
at winstone.cmdline.Option.intArg(Option.java:291)
at winstone.Launcher.initLogger(Launcher.java:411)
at winstone.cmdline.CmdLineParser.parse(CmdLineParser.java:83)
at winstone.Launcher.getArgsFromCommandLine(Launcher.java:359)
at winstone.Launcher.main(Launcher.java:332)
... 6 more

But I expect that’s more down to one of the args missing.

I'll add the out put from a command line startup rather than using the init.d script.

[timja]

andrewj100:

As another attempt I've build a VM running scientific linux 7 and installed jdk 8.
jdk-8u101-linux-x64.rpm
Jenkins did not start.
Some other documentation mentioned jna was needed by Hudson so I installed that, still no start.

So I went back to some older versions using the following install/uninstall

yum erase jenkins
shutdown -r now
yum install
service jenkins start

jenkins-1.642.1-1.1.noarch.rpm - working
jenkins-1.651.1-1.1.noarch.rpm - working
jenkins-1.651.3-1.1.noarch.rpm - working
jenkins-2.7.1-1.1.noarch.rpm - not working
jenkins-2.9-1.1.noarch.rpm - not working

So I went back to my original redhat machine and installed jenkins-1.651.3-1.1.noarch.rpm and it started up fine.
I'd installed jna on that so as a test I removed it, rebooted and jenkins started.

So something has changed between jenkins-1.651.3-1.1.noarch.rpm and jenkins-2.7.1-1.1.noarch.rpm that seems to only be affecting my servers, it would be interesting to know what it is.

[timja]

andrewj100:

Just uploaded package_list which contains the output of rpm -qa if that will help find a missing or down rev package or lib.

[timja]

danielbeck:

This is an issue tracker, not a support site. Consider asking on #jenkins on Freenode, or emailing the jenkinsci-users mailing list.