-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to install plugins from https://ftp.halifax.rwth-aachen.de/ #3935
Comments
Hello, can you share with us on our private email jenkins-infra-team@googlegroups.com the IP(s) you're using? |
you mean my public IP? |
Sent on the provided email. |
We are checking if it could not be related to #3930 |
We have the initialization_completed file so we dont need to download the plugins everytime, yesterday we deployed a new jenkins version and we forced to reinstall the plugins and we have 25 instances. Do you believe this could cause a ip block? if yes, is it possible to remove from blacklist? we wont install plugins all the time |
another possibility is to build an image with all plugins previously installed right? |
Hello @felipenferri,
That might be the case yes, we're taking a closer look, we'll keep you informed.
Yes it should work in the mean time. |
I believe that is the preferred technique so that your Jenkins infrastructure does not depend on downloading plugins from the Jenkins update center during startup. When the plugins are not included in the container image already, then your Jenkins controller will fail to start if it cannot download plugins. |
If those 25 instances share the public IP address, this might indeed cause a (temporary) ban because it looks like abuse or misconfiguration. I'd say the rules aren't very strict (in the sense that it takes a lot of effort/abuse to trigger a ban), but if you have lots of instances this obviously complicates things. As I'm not in the business of installing/maintaining Jenkins instances, could you please share your opinion on this? Is adding a HTTP cache (transparent proxy), or a full-blown private mirror server, a way to go? Could you package a Jenkins installation in a pre-built image (VM, Docker, ...)? I'm very open to suggetions, as having a few GBit/sec more or less (and in this case, it's far less) doesn't really hurt the server. On the other side, it also doesn't look right to serve the same files over and over again (to the same host). |
I (temporarily?) increased the threshold by 10x and hope that we can find a common ground based on the recent insights. |
@felipenferri: @C-Otto confirmed that your IP was indeed blocked, it should be good now. As noted by @MarkEWaite, building your image with plugins integrated in it is far better than downloading them for each new instance. You can take a look at how we're doing it for our own controller image there for example: https://github.com/jenkins-infra/docker-jenkins-weekly/blob/main/Dockerfile |
I could download now, thank you, Im also starting ito develop a CI pipeline to build the image |
Good, many thanks for opening the issue and confirming it is fixed for you! |
Service(s)
Update center
Summary
We are getting a lot of errors to download plugins from https://ftp.halifax.rwth-aachen.de/, can you please check?
INFO: I/O exception (java.net.SocketException) caught when processing request to {s}->https://ftp.halifax.rwth-aachen.de:443: Network is unreachable
Feb 06, 2024 5:15:09 PM org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {s}->https://ftp.halifax.rwth-aachen.de:443
Feb 06, 2024 5:15:10 PM org.apache.http.impl.execchain.RetryExec execute
INFO: I/O exception (java.net.SocketException) caught when processing request to {s}->https://ftp.halifax.rwth-aachen.de:443: Network is unreachable
Feb 06, 2024 5:15:10 PM org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {s}->https://ftp.halifax.rwth-aachen.de:443
Reproduction steps
Try to restart Jenkins pod and check init container
The text was updated successfully, but these errors were encountered: