Re: Problems with OAI Validator

[Simeon Warner]

Hi Alan,

Thanks for your email and being the first person seeing this problem to look in your server logs -- it is interesting that you don't even see a request and, of course, suggests something on the validator end. See other recent messages on https://groups.google.com/g/oai-pmh

Your repo was not removed from the list. I suspect you only validated rather than registering.

Cheers,
Simeon


On 11/23/21, 3:38 AM, "bounce-12610...@list.cornell.edu on behalf of Orth, Alan (ILRI)" <bounce-12610...@list.cornell.edu on behalf of A.O...@cgiar.org> wrote:
Dear OpenArchives admins,

We're having problems validating our institutional repository on
OpenArchives.org. OAI is working correctly, but no matter what URL I
provide, the validator says "HTTP 500" (see screenshot). I don't even
see any requests in our server logs! By the way, we had previously
validated several months ago, but our repository no longer appears on
the list.

Our repository base URL is: https://cgspace.cgiar.org/oai/request

I would appreciate any guidance you can give on these issues. Thank you!

--
Alan Orth | ICT Linux Systems Administrator (consultant)
International Livestock Research Institute
a.o...@cgiar.org

[Orth, Alan (ILRI)]

Thank you, Simon. Interesting to see others having the same problem on
the validator! I definitely see no request in my server logs, and I
tried a few different domains on different servers that are under my
control. Definitely something wrong on the validator side.

Hope you can figure it out soon... thanks.

[John Salter]

Both the most recent reports have been for sites secured with a Let's Encrypt certificate.

The 500 response can be caused internally (i.e. on the Validator server) if the SSL connection cannot be established for some reason (incompatible TLS versions; no shared ciphers).

If it was part of an Apache stack making the remote request (which I think at this stage in the validation process it is?), in the error logs (on the Validator server) there may be something like:

500 Internal Server Error

Content-Type: ...
Client-Date: ...

Client-Warning: Internal response

I think checking the response headers for 'Client-Warning: Internal response' would indicate if it is a local or remote 500 - and calling $response->as_string might show exacly what is not working in the connection setup.

Cheers,
John

---

From: oai...@googlegroups.com <oai...@googlegroups.com> on behalf of Orth, Alan (ILRI) <A.O...@cgiar.org>
Sent: 23 November 2021 17:10
To: Simeon Warner <simeon...@cornell.edu>; OAI-PMH <oai...@googlegroups.com>
Cc: Ariyawansa, Udana (IWMI-WLE) <U.Ariy...@cgiar.org>; Yabowork, Abenet (ILRI) <A.Yab...@cgiar.org>
Subject: [OAI-PMH] Re: Problems with OAI Validator

 

--

---
You received this message because you are subscribed to the Google Groups "OAI-PMH" group.
To unsubscribe from this group and stop receiving emails from it, send an email to oai-pmh+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/oai-pmh/75a05881-6da0-d531-c3d5-5fd43d9fbb24%40cgiar.org.

[Simeon Warner]

I see that https://cgspace.cgiar.org/oai/request was successfully registered on Jan 9, 2022:

https://www.openarchives.org/Register/BrowseSites?viewRecord=https://cgspace.cgiar.org/oai/request

Cheers,

Simeon