Plugin Installs Failing

[Steve Rogers]

Any plugin that I try to download results in the following error:

java.net.SocketException: Connection reset
	at java.net.SocketInputStream.read(SocketInputStream.java:210)
	at java.net.SocketInputStream.read(SocketInputStream.java:141)
	at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
	at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
	at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
	at sun.net.www.MeteredStream.read(MeteredStream.java:134)
	at java.io.FilterInputStream.read(FilterInputStream.java:133)
	at sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(HttpURLConnection.java:3454)
	at sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(HttpURLConnection.java:3447)
	at org.apache.commons.io.input.ProxyInputStream.read(ProxyInputStream.java:78)
	at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1245)
Caused: java.io.IOException: Failed to load http://updates.jenkins-ci.org/download/plugins/script-security/1.69/script-security.hpi to /opt/tomcat/.jenkins/plugins/script-security.jpi.tmp
	at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1250)
Caused: java.io.IOException: Failed to download from http://updates.jenkins-ci.org/download/plugins/script-security/1.69/script-security.hpi (redirected to: http://ftp-nyc.osuosl.org/pub/jenkins/plugins/script-security/1.69/script-security.hpi)
	at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1284)
	at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1832)
	at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:2110)
	at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1806)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:111)
	at java.lang.Thread.run(Thread.java:748)

i am able to retrieve the resource manually via WGET.  This is a brand new install of jenkins in tomcat on CENTOS7.  Out curiosity I looked at our existing jenkins install and am getting a similar error there.  I have checked and rechecked that the Update Site URL is correct.

Thanks

[Mark Waite]

It may be worth checking the directory permissions to confirm that the Jenkins user can still write to that directory.  You may also want to check that the disc has available free space and available inodes to allow new files to be created. 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0e51b53c-440a-4b60-a5a1-2c60a406c1ab%40googlegroups.com.

[Steve Rogers]

Yes, plenty of space and permissions are correct.  I should have added in the original that I can install manually by downloading the plugin file directly and then uploading into jenkins.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGeBdtXzCzN7w87sR3MRw7MzvUGy90boBYQj17uv8Mnwg%40mail.gmail.com.

[Mark Waite]

That's surprising.  Could you check the permissions from inside Jenkins by creating a freestyle job that runs on master and attempts to create and delete a file named /opt/tomcat/.jenkins/plugins/script-security.jpi.tmp ?

For me, the directory name '/opt/tomcat/.jenkins/' is surprising. Most Jenkins installations in servers do not use a '.jenkins' directory to store the Jenkins home directory. However, I've never hosted Jenkins under the /opt/tomcat/ directory. That may be the typical directory name for that configuration.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPWe7DRU-Hz5574ZLvanvKXzs8tUui7z00r-3pWsiPNwV2jbRw%40mail.gmail.com.

[Steve Rogers]

I'll give that a try.  I believe /opt/tomcat/.jenkins was the default.  I then just linked that to /home/jenkins.  Our old system where I am getting the same error is a windows install, so it seems more likely something in our network.

Thanks for your help.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFxGkje5wZ0QhDVkuHZG0hrySxmcemFpi1ZDrUVKfSiUA%40mail.gmail.com.

[Jan Monterrubio]

Could it be an http vs https problem? We had some of those with maven before. 

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPWe7DRHU3OJ6piZpTVimYS8DROVszrBecn5v84-wy%2BXzu%3D-0g%40mail.gmail.com.

[Steve Rogers]

That was my first guess too. I tried with both. 

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CADgiF9LMqkEwsjdDZzMX-V6bNr%2BS_ng1%3Dg_VEp2XM_zO9DrxvA%40mail.gmail.com.

[Markus Boos]

We had a similar error (failed to download plugins) last week (see my post in this list) and it occurred several times on our instances.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPWe7DTvzjuB-dAUx2nFykHG1BgxaM%2BUS9JEya-VJzxEVCbwWw%40mail.gmail.com.

--

Markus Boos
Oberwilerstrasse 1
8330 Pfäffikon
+41 78 689 44 12

[Mohtashim S]

Looks like our not open / url blocked.

Try to access the Jenkins update plugin url or test it with the curl command and you should noticed that it is blocked. If blocked opening the firewall / proxy policy to allow the Jenkins update url may help you overcome the problem.

You may have to do this manually in offline mode

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALCEi_CzeQeRcyDRQybCRbnqqGtb2mTYCj2CoXAzu-i4dCJ9qA%40mail.gmail.com.

[Steve Rogers]

I changed the configuration to point directly to /home/jenkins (plugin installs still fail) and then added the freestyle job as you suggested which successfully created and deleted the file at the path suggested, so it appears permissions are not the problem.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFxGkje5wZ0QhDVkuHZG0hrySxmcemFpi1ZDrUVKfSiUA%40mail.gmail.com.

[Steve Rogers]

For the sake of completeness, this turned out to be blocked at our firewall based on a list of banned IP addresses.  This still seems strange as I was able to curl the update files directly from that machine without issue.  The firewall (Palo Alto) seemed to not like the redirects to mirrors and terminated the connection.  When we bypassed that rule everything worked as expected, so I just did all my updates and reactivated the rule.