Sonatype Nexus proxy problems

309 views
Skip to first unread message

Jonas Eriksson

unread,
Feb 22, 2016, 7:41:29 AM2/22/16
to Sakai Development

Hi,

 

We are in progress of proxying all repositories needed to build our sakai. We have setup a Sonatype Nexus 2.11.4-01 and it works great for many repositories, but not for the Sakai Maven Repository. It’s the same with snapshot and plugin repo.

 

Are the Sakai repos preventing use of a proxy like sonatype nexus?

 

Settings in our nexus:

 

Repository ID: sakai-maven2

Repository Name: Sakai Maven Repository

Repository Type: proxy

Repository Policy: Release

Repository Format: maven2

Contained in groups:

 

Remote URL: http://source.sakaiproject.org/maven2/

 

Status:

 

Status:

Unsuccessful.

Message:

No scraper was able to scrape remote (or remote prevents scraping).

Last run:

Mon Feb 22 2016 12:41:31 GMT+0100 (Central Europe Standard Time)

 

Regards

Jonas Eriksson
Systems Developer
ICT Services and System Development
Umeå universitet
jonas.e...@umu.se

www.its.umu.se

 

 

Matthew Buckett

unread,
Feb 22, 2016, 7:54:36 AM2/22/16
to Jonas Eriksson, Sakai Development
On 22 February 2016 at 12:40, Jonas Eriksson <jonas.e...@umu.se> wrote:
>
> We are in progress of proxying all repositories needed to build our sakai.
> We have setup a Sonatype Nexus 2.11.4-01 and it works great for many
> repositories, but not for the Sakai Maven Repository. It’s the same with
> snapshot and plugin repo.

We're running an older version of Nexus.

> Are the Sakai repos preventing use of a proxy like sonatype nexus?

We have a copy of Nexus proxying the Sakai repository without any
perceivable problems.

> Remote URL: http://source.sakaiproject.org/maven2/

All our settings look the same, except we are connecting to it on
https rather than http and we don't have remote indexes enabled on
this repository.

--
Matthew Buckett, VLE Developer, IT Services, University of Oxford

Charl Thiem

unread,
Feb 22, 2016, 8:02:07 AM2/22/16
to Jonas Eriksson, Sakai Development
Hi Jonas

We are also using an older version of Nexus, with exact same settings (we are also using http, not https)
Not having any issues...

Regards
Charl Thiem
Senior Developer
IT Infrastructure Manager






--
You received this message because you are subscribed to the Google Groups "Sakai Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sakai-dev+...@apereo.org.
To post to this group, send email to saka...@apereo.org.
Visit this group at https://groups.google.com/a/apereo.org/group/sakai-dev/.




See OpenCollab email disclaimer at http://www.opencollab.co.za/email-disclaimer

Jonas Eriksson

unread,
Feb 22, 2016, 10:45:33 AM2/22/16
to Matthew Buckett, Sakai Development
Thanks Matthew and Charl for your responses.

I guess I have to dig deeper to find the root cause.

Thanks
Jonas

-----Ursprungligt meddelande-----
Från: Matthew Buckett [mailto:matthew...@it.ox.ac.uk]
Skickat: den 22 februari 2016 13:54
Till: Jonas Eriksson <jonas.e...@umu.se>
Kopia: Sakai Development <saka...@apereo.org>
Ämne: Re: [sakai-dev] Sonatype Nexus proxy problems

Jonas Eriksson

unread,
Feb 26, 2016, 4:50:02 AM2/26/16
to Matthew Buckett, Sakai Development
Hi,

I have found the problem regarding our nexus proxy problem and if you upgrade your nexus you will face the same problem.

The source.sakaiproject.org responds with header value Server: openresty. If it changes to nginx the nginx scraper will match.

An alternative is to include /.meta/repository-metadata.xml so the nexus scraper match, but I guess you have to have a nexus-compatible repository then.

I have no idea how an older sonatype nexus scraper succeeds.

I've attached the debug log from our nexus.

Regards
Jonas

-----Ursprungligt meddelande-----
Från: Jonas Eriksson
Skickat: den 22 februari 2016 16:45
Till: 'Matthew Buckett' <matthew...@it.ox.ac.uk>
Kopia: Sakai Development <saka...@apereo.org>
Ämne: SV: [sakai-dev] Sonatype Nexus proxy problems

Thanks Matthew and Charl for your responses.

I guess I have to dig deeper to find the root cause.

Thanks
Jonas

-----Ursprungligt meddelande-----
Från: Matthew Buckett [mailto:matthew...@it.ox.ac.uk]
Skickat: den 22 februari 2016 13:54
Till: Jonas Eriksson <jonas.e...@umu.se>
Kopia: Sakai Development <saka...@apereo.org>
Ämne: Re: [sakai-dev] Sonatype Nexus proxy problems

nexus-scrape-log.txt

Jonas Eriksson

unread,
Mar 1, 2016, 7:16:25 AM3/1/16
to Matthew Buckett, Sakai Development
Hi,

Any comments on this problem?

Is it possible for you to replace the 'Server' header value 'openresty' with 'nginx' on the source.sakaiproject.org?
https://github.com/openresty/headers-more-nginx-module

You can easily verify the problem by running the latest nexus via docker: docker run -d -p 8081:8081 --name nexus sonatype/nexus:oss
https://hub.docker.com/r/sonatype/nexus/

Regards
Jonas

-----Ursprungligt meddelande-----
Från: saka...@apereo.org [mailto:saka...@apereo.org] För Jonas Eriksson
Skickat: den 26 februari 2016 10:50

Jonas Eriksson

unread,
Mar 18, 2016, 10:23:34 AM3/18/16
to Matthew Buckett, Sakai Development
Hi,

Just a follow up on this issue.
One should not read the logs too carefully... the nexus proxy works ok, even if it complains about not being able to scrape the site.
I guess is does a direct GET with the calculated artifact path.

Regards
Jonas

-----Ursprungligt meddelande-----
Från: Jonas Eriksson
Skickat: den 1 mars 2016 13:16
Till: Matthew Buckett <matthew...@it.ox.ac.uk>
Kopia: Sakai Development <saka...@apereo.org>
Ämne: SV: [sakai-dev] Sonatype Nexus proxy problems

Hi,

Any comments on this problem?

Is it possible for you to replace the 'Server' header value 'openresty' with 'nginx' on the source.sakaiproject.org?
https://github.com/openresty/headers-more-nginx-module

You can easily verify the problem by running the latest nexus via docker: docker run -d -p 8081:8081 --name nexus sonatype/nexus:oss https://hub.docker.com/r/sonatype/nexus/

Regards
Jonas

-----Ursprungligt meddelande-----
Från: saka...@apereo.org [mailto:saka...@apereo.org] För Jonas Eriksson
Skickat: den 26 februari 2016 10:50
Reply all
Reply to author
Forward
0 new messages