Skip to content
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.

Sign up for GitHub

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

Jump to bottom

rubygems-proxy.torquebox.org is down #100

Open
aboltart opened this issue Dec 18, 2019 · 8 comments
Open

rubygems-proxy.torquebox.org is down #100

aboltart opened this issue Dec 18, 2019 · 8 comments

Comments

@aboltart
Copy link 

 gem install psych
Fetching: psych-3.1.0-java.gem (100%)
  jar dependencies for psych-3.1.0-java.gemspec . . .
Dec 18, 2019 4:45:23 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFO: I/O exception (java.net.SocketException) caught when processing request to {}->http://rubygems-proxy.torquebox.org:80: Connection reset
Dec 18, 2019 4:45:23 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFO: Retrying request to {}->http://rubygems-proxy.torquebox.org:80
Dec 18, 2019 4:48:20 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFO: I/O exception (java.net.SocketException) caught when processing request to {}->http://rubygems-proxy.torquebox.org:80: Connection reset
Dec 18, 2019 4:48:20 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
@aleksandrs-ledovskis
Copy link

aleksandrs-ledovskis commented Dec 18, 2019 •
edited
Loading

(Temporary?) workaround is to force rubygems-releases mirror in Maven's settings.xml

Something like this in ~/.m2/settings.xml

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                      https://maven.apache.org/xsd/settings-1.0.0.xsd">
  <mirrors>
    <mirror>
      <id>rubygems-releases-mirror</id>
      <name>RubyGems Releases mirror</name>
      <url>https://repo.maven.apache.org/maven2</url>
      <mirrorOf>rubygems-releases</mirrorOf>
    </mirror>
  </mirrors>
</settings>

Afterwards, the regular gem install psych succeeds.
Also, when checking hairy details of org.codehaus.plexus.classworlds.launcher.Launcher dependency:copy-dependencies dependency:list execution (the Java execution point that calls the demised torquebox.org repo) confirms the flip:

[DEBUG] Using mirror rubygems-releases-mirror (https://repo.maven.apache.org/maven2) for rubygems-releases (http://rubygems-proxy.torquebox.org/releases).

Offending line is https://github.com/torquebox/jruby-maven-plugins/blob/bb80f25e856f48bb08e954daa9301b4de4eb1768/ruby-tools/src/main/java/de/saumya/mojo/ruby/gems/DefaultGemManager.java#L43

@aboltart aboltart mentioned this issue Dec 18, 2019
Closed
@fatalglitch
Copy link

Any update here? This is preventing the build of several containers that require this to update

This was referenced Dec 18, 2019
Open
Open
@mshirlaw
Copy link

mshirlaw commented Dec 19, 2019 •
edited
Loading

Any updates here? Also unable to install multiple gems via gradle

Could not GET 'http://rubygems-proxy.torquebox.org/releases/rubygems/asciidoctor-diagram/1.2.1/asciidoctor-diagram-1.2.1.gem'. Received status code 503 from server: Service Temporarily Unavailable
Could not GET 'http://rubygems-proxy.torquebox.org/releases/rubygems/asciidoctor/1.5.8/asciidoctor-1.5.8.gem'. Received status code 503 from server: Service Temporarily Unavailable

✗ curl http://rubygems-proxy.torquebox.org/releases/rubygems
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>503 Service Temporarily Unavailable</title>
</head><body>
<h1>Service Temporarily Unavailable</h1>
<p>The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.</p>
<hr>
<address>Apache/2.2.15 (Red Hat) Server at rubygems-proxy.torquebox.org Port 80</address>
</body></html>

@Moulick
Copy link

Moulick commented Dec 19, 2019

@aleksandrs-ledovskis any way how to force this for gradle too ?

@aleksandrs-ledovskis
Copy link

@Moulick I don't have any JRuby project that is managed by Gradle, but cursory search leads to following SO post - https://stackoverflow.com/q/12522676

maybeec added a commit to devonfw/devonfw.github.io that referenced this issue Jan 5, 2020
@maybeec
try mirroring rubygems repo
ee122e8 
jruby/jruby-maven-plugins#100 (comment)
@Mobe91
Copy link

Mobe91 commented Jan 6, 2020

@Moulick Did you get it to work with Gradle? Still having issues with it..

@Moulick
Copy link

Moulick commented Jan 7, 2020

@Mobe91 to not stop the whole development floor, I had to advise our devs to just commit that 2mb file to their respective git repo(s) and get moving.
Our other solution was to get this gem into our own private maven repo which was already configured in our gradle file, but we were unable to push that gem to our private maven.

Question: Is is even possible to push a gem file to a maven repo? if I have a pom.xml etc

@deivid-rodriguez
Copy link
Contributor

I think this has been ok for a while now, I think it can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@aboltart @fatalglitch @mshirlaw @aleksandrs-ledovskis @deivid-rodriguez @Mobe91 @Moulick