Raw proxy repository that is linked/proxy to a raw group repo of a different nexus instance

[Anastasia Matienzo]

I tried to create a raw proxy repository on a nexus instance (nexusA) that's proxying a raw group repo of a different nexus instance (nexusB).

In nexusA instance, I created this repository:
name: raw-proxy
format: raw
type: proxy
remote storage: http://nexusB:port/nexus/repository/raw-group/
Http authentication check box is checked.
Authentication type: Username
Username: admin username
Password admin password

When I try to download artifacts using this proxy (tried both curl and wget. both using admin credentials for downloading), i get the following message:
HTTP request sent, awaiting response... 503 Service Unavailable
2017-06-08 14:27:38 ERROR 503: Service Unavailable.

And in the logs:
org.sonatype.nexus.repository.raw.internal.RawProxyFacet - Failed to fetch: test.rpm
org.sonatype.nexus.repository.proxy.ProxyServiceException: HTTP/1.1 401 Unauthorized
        at org.sonatype.nexus.repository.proxy.ProxyFacetSupport.mayThrowProxyServiceException(ProxyFacetSupport.java:280) [org.sonatype.nexus.repository:3.2.0.01]
        at org.sonatype.nexus.repository.proxy.ProxyFacetSupport.fetch(ProxyFacetSupport.java:254) [org.sonatype.nexus.repository:3.2.0.01]
        at org.sonatype.nexus.repository.proxy.ProxyFacetSupport.fetch(ProxyFacetSupport.java:210) [org.sonatype.nexus.repository:3.2.0.01]
        at org.sonatype.nexus.repository.proxy.ProxyFacetSupport.get(ProxyFacetSupport.java:166) [org.sonatype.nexus.repository:3.2.0.01]
 
Any thought about this issue and/or creating a raw proxy repository that is proxying to a raw group repo of a different nexus instance?

[Jeffry Hesse]

I'm curious (because I see rpm in here), are you trying to proxy a Yum repo?

--
You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users...@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.
To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/15b174b8-4150-4d5f-81c7-732dae89c003%40glists.sonatype.com.
For more options, visit https://groups.google.com/a/glists.sonatype.com/d/optout.

[Anastasia Matienzo]

Not a yum repo. Just a regular raw group repo that has different files (e.g. .rpm, .html, .txt, .war).
I have two nexus instance, nexusA and nexusB.
nexusB has a raw-group repository with different files on it.. Now, i want to create a raw-proxy repo in nexusA that will proxy the raw-group repo of nexusB.
So when i download files from raw-proxy repo in nexusA, it will pull the artfacts from nexusB and cache it to nexusA..
But with this setup, i get the errors:

[Jeffry Hesse]

Hmmmm,

I went ahead and setup something pretty similar:

Nexus Repo A: 3.4.0-SNAPSHOT

raw-proxy

http auth: admin, admin123

remote storage: http://localhost:8084/repository/raw-group/

Nexus Repo B: 3.1.0

raw-group

member: raw-proxy (of (http://ftp.osuosl.org/pub/elrepo/elrepo/el7/x86_64/)

Turned off anon access to Nexus Repo B, as well. I was able to run: curl -O http://localhost:8081/repository/raw-proxy/repodata/repomd.xml

That gets me the xml file, no log spam like you are seeing. 

Our setups are likely off in some way (versions for one), mind elaborating a bit more though? Is the group on the Nexus Repo B side also sending http auth to something?

--

You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users...@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.

To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/3d0817b0-ee29-4055-92b3-701d6fa847a2%40glists.sonatype.com.

[Anastasia Matienzo]

I'm using version 3.2.0-01 for both nexusA and nexusB instances.

Setup is something like this:

Nexus Repo A: (http://hostnamea:8093/nexus)

raw-proxy

http auth: admin, admin123

remote storage: http://hostnameb:8093/nexus/repository/raw-group

Nexus Repo B: (http://hostnameb:8093/nexus)

raw-group

member:
raw-hosted (http://hostnameb:8093/nexus/repository/raw-hosted)

Tried: curl -v --user admin --password admin123 -O http://hostnamea:8093/nexus/repository/raw-proxy/test.rpm
Result: HTTP request sent, awaiting response... 503 Service Unavailable

[Jeffry Hesse]

If the http auth is setup on the raw-proxy, you shouldn't have to specify it via curl, unless you've also made auth a requirement on the raw-proxy on Nexus Repo A. Is that the case? Even if I remove anon access on Nexus Repo A, it works fine for me, adding the user and password on.

Also trying to replicate your curl command. Shouldn't it be curl -v -u admin:admin123 ?

Here is a gist of what I got: https://gist.github.com/DarthHater/ebcd41c1d0afb0d4375be50d08a31b2c

I'll give it a shot with the raw-hosted in a bit. I'm hesitant to say the version should matter at all, but maybe give it a shot with a newer version of Nexus Repo as well? 

--

You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users...@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.

To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/fb42801f-9cc0-41ad-8de8-cea298638eb7%40glists.sonatype.com.

[praveen kurrra]

Hi All, I have small question.

1) I upgraded from 2.14.03 to 3.2.1 . In 2.14.03 , I have lot of xml files in the repository but Xml files are not upgraded to 3.2.01. Can you please advise me how to get xml file in 3.2.01 version of sonatype nexus. Thanks

Thanks

Praveen

To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/CAHpWApe9b0QuMkBUPfkYEQHLTGSK69uNeDvC1%2BgnQC%3D86PqUBw%40mail.gmail.com.

[Jeffry Hesse]

Interesting. Just for complete clarity, what repo types are you using on both ends?