<p>OK, a good week-end does its job as usual: My issue was indeed caused by my company proxy (a good thing would be to add this requirement in the jenkins doc, i might have  missed it anyway).
So the fix is actually simple, just need to add the correct options to the jenkins start command, as in:</p>

<pre><code>-Dhttp.proxyHost=&lt;your_proxy_ip_here&gt; -Dhttp.proxyPort=&lt;your_proxy_port_here&gt; -Dhttps.proxyHost=&lt;your_proxy_ip_here&gt; -Dhttps.proxyPort=&lt;your_proxy_port_here&gt;
</code></pre>

<p>Full example:</p>

<pre><code>/usr/bin/java -Djava.net.preferIPv4Stack=true -Dhttp.proxyHost=10.21.92.40 -Dhttp.proxyPort=3128 -Dhttps.proxyHost=10.21.92.40 -Dhttps.proxyPort=3128 -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080
</code></pre>

<p>tcpdump was the savior here (+ a colleague :) )</p>

CC BY-SA 4.0
2019-10-07T07:57:14.783Z
2019-10-07T07:57:14.783Z
Pier
<p>I've been trying to get a simple jenkins master node to start but it keeps getting stuck at the "Please wait while Jenkins is getting ready to work".</p>

<p>My setup is nothing exotic:
jenkins is installed inside a LXC hosted by a proxmox 6 instance.
10Go of RAM, 4CPU, 10G of hdd, debian 9</p>

<p>I increased the lxc specs just in case (I started with 4G of RAM and 2 CPU)</p>

<p>I tried a lot of different things such as:</p>

<ol>
<li>Stop / start the jenkins soft</li>
<li>Stop / start the container</li>
<li>installing using debian package</li>
<li>Install using the war (see my service file below, only used for the war install style)</li>
<li>Installing on centos 7</li>
<li>Installing on qemu</li>
</ol>

<p>Service file:</p>

<pre><code>[Unit]
Description=Jenkins Daemon

[Service]
ExecStart=/usr/bin/java -jar /home/jenkins/jenkins.war --logfile=/home/jenkins/jenkins.log
User=jenkins

[Install]
WantedBy=multi-user.target
</code></pre>

<p>The log doesn't contain any error except a WARNING :</p>

<pre><code>2019-10-03 12:05:38.516+0000 [id=1] WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath
</code></pre>

<p>But it always ends at being stuck at this page.</p>

<p>I've searched the web but my google fu seems bad today so here I am.</p>

<p>This sounds crazy to me, jenkins install is supposed to be easy and quite forward, but I can't make it works ...</p>

<p>[Edit]
Might be a connection issue, we saw jenkins trying to connect to an ec2 instance... we have some proxy, but did not found the correct options (in Java command) to get through it, any tips welcome</p>

CC BY-SA 4.0
2019-10-04T04:54:59.130Z
Which log are you looking at?
papanito
CC BY-SA 4.0
2019-10-04T05:46:43.620Z
@papanito : /var/log/jenkins.log
Pier
CC BY-SA 4.0
2019-10-04T20:18:00.353Z
What about /home/jenkins/jenkins.log ?
schaiba
CC BY-SA 4.0
2019-10-05T06:11:34.350Z
Arf yes sorry, too many tests... whatever logs, they always contains the same anyway ..
Pier
CC BY-SA 4.0
2019-10-06T13:54:26.160Z
what does `journalctl` tell you?
papanito
CC BY-SA 4.0
2019-10-06T17:25:58.620Z
@papanito Nothing much than jenkins service has started...
Pier
<jenkins><containers>
jenkins stuck "Please wait while Jenkins is getting ready to work"
Pier
# jenkins stuck "Please wait while Jenkins is getting ready to work"

(Asked by: username_0 on 2019-10-03)

I've been trying to get a simple jenkins master node to start but it keeps getting stuck at the "Please wait while Jenkins is getting ready to work".
My setup is nothing exotic:
jenkins is installed inside a LXC hosted by a proxmox 6 instance.
10Go of RAM, 4CPU, 10G of hdd, debian 9
I increased the lxc specs just in case (I started with 4G of RAM and 2 CPU)
I tried a lot of different things such as:

Stop / start the jenkins soft
Stop / start the container
installing using debian package
Install using the war (see my service file below, only used for the war install style)
Installing on centos 7
Installing on qemu

Service file:
[Unit]
Description=Jenkins Daemon

[Service]
ExecStart=/usr/bin/java -jar /home/jenkins/jenkins.war --logfile=/home/jenkins/jenkins.log
User=jenkins

[Install]
WantedBy=multi-user.target

The log doesn't contain any error except a WARNING :
2019-10-03 12:05:38.516+0000 [id=1] WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath

But it always ends at being stuck at this page.
I've searched the web but my google fu seems bad today so here I am.
This sounds crazy to me, jenkins install is supposed to be easy and quite forward, but I can't make it works ...
[Edit]
Might be a connection issue, we saw jenkins trying to connect to an ec2 instance... we have some proxy, but did not found the correct options (in Java command) to get through it, any tips welcome

**Tags:** jenkins, containers

> **Comments:**
> **username_1**: Which log are you looking at?  
> **username_0**: @username_1 : /var/log/jenkins.log  
> **username_2**: What about /home/jenkins/jenkins.log ?  
> **username_0**: Arf yes sorry, too many tests... whatever logs, they always contains the same anyway ..  
> **username_1**: what does `journalctl` tell you?  
> **username_0**: @username_1 Nothing much than jenkins service has started...  

---

## 1 answers

### Answer by username_0 on 2019-10-07. Score: 1 | Accepted answer

OK, a good week-end does its job as usual: My issue was indeed caused by my company proxy (a good thing would be to add this requirement in the jenkins doc, i might have  missed it anyway).
So the fix is actually simple, just need to add the correct options to the jenkins start command, as in:
-Dhttp.proxyHost= -Dhttp.proxyPort= -Dhttps.proxyHost= -Dhttps.proxyPort=

Full example:
/usr/bin/java -Djava.net.preferIPv4Stack=true -Dhttp.proxyHost=10.21.92.40 -Dhttp.proxyPort=3128 -Dhttps.proxyHost=10.21.92.40 -Dhttps.proxyPort=3128 -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080

tcpdump was the savior here (+ a colleague :) )


---

