Always getting error 500 on openarchives.org/Register/ValidateSite

[Pablo Bianchi]

Hi!

It seems there is an issue with the OAI-PMH Validator. On every base URL tried I get error 500 (internal server). But on my terminal I can't reproduce the issue on any of the base URL. For eg:

curl -I "https://demo.bibkat.no/cgi-bin/koha/oai.pl?verb=Identify"

return correctly an http response with a nice 200.

There is a bug on the site? How can I reproduce the http request sent to the baseURL using curl?

Best regards,

Pablo

[John Salter]

Hi Pablo,

I've just run the first stage check on my repository - and it works as expected.

I wonder if there is anything in your software stack that is blocking the validator requests - e.g. IP restrictions, or user-agent filtering?

From my logs, it uses "OAIPMH_Validator" as it's user-agent.

Cheers,
John

---

From: oai...@googlegroups.com <oai...@googlegroups.com> on behalf of Pablo Bianchi <pablo....@gmail.com>
Sent: 13 November 2021 04:49
To: oai...@googlegroups.com <oai...@googlegroups.com>
Subject: [OAI-PMH] Always getting error 500 on openarchives.org/Register/ValidateSite

 

--

---
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/CAH2zftG%2BspK8uZpftsD7Ak%3D6UL52JQqBYyRG1Xq8h1zuooPH2Q%40mail.gmail.com.

[Simeon Warner]

Hi Pablo, John,

I don't know why the validator is reporting a 500 response. The user agent is a good idea but doesn't seem to be the cause, the site responds OK with both user agent and from address as supplied;

curl -I -H "From: https://groups.google.com/d/forum/oai-pmh" -H "User-Agent: OAIPMH_Validator" 'https://demo.bibkat.no/cgi-bin/koha/oai.pl?verb=Identify'

The code for the validator is at https://github.com/zimeon/oaipmh-validator and hasn't changed in a long time,

Cheers,

Simeon

[John Salter]

Pablo,

Is there anything in the error logs for demo.bibkat.no relating to the 500 error?

 

If there is nothing then the 500 response might be an internal LWP::UserAgent response on the validator server - possibly something like an issue setting up HTTPS e.g. mismatch in TLS versions; no shared ciphers; non-trusted (by the validation server) root certificate (looks like demo.bibkat.no uses Let's Encrypt certs).

There may be a difference in what curl and LWP::UserAgent is using for the https setup?

 

I also note that the 'Identify' response from: https://demo.bibkat.no/cgi-bin/koha/oai.pl?verb=Identify  uses a different base URL in it's response:

<request verb='Identify'>https://demo.bibkat.no/opac/oai.pl</request>

<Identify>

  <repositoryName>Demo</repositoryName>

  <baseURL>https://demo.bibkat.no/opac/oai.pl</baseURL>

…

</Identify>

 

I don't think this would generate the 500 error, but it would create a different validation error.

 

Cheers,

John

To view this discussion on the web visit https://groups.google.com/d/msgid/oai-pmh/132e600a-4757-4033-b22a-da0c35a18ddan%40googlegroups.com.

[Lucas Carrizo]

Hi, how are you? I hope that you are fine. I am experimenting something similar to Pablo's issue. I am getting a HTTP 500 error when I try  "Validate Site". I am using OJS and this is the journal that I am trying to validate: https://revistas.unc.edu.ar/index.php/ConCienciaSocial/oai. I got the following message:

I tested in another two sites ( https://validator.oaipmh.com and http://oval.base-search.net/) but I see no errors on them. Can you help me with this?

Thank you!

[Simeon Warner]

I note that https://demo.bibkat.no/cgi-bin/koha/oai.pl no longer generates a 500 error when validation is attempted. There are errors (below) however.

Cheers,

Simeon

Initial validation checks (step 1)

baseURL is https://demo.bibkat.no/cgi-bin/koha/oai.pl
Validation only
Request logged from 128.84.116.66

Checking Identify response

REQUEST https://demo.bibkat.no/cgi-bin/koha/oai.pl?verb=Identify GET

PASS Administrator email address is 'po...@libriotech.no'

PASS Correctly reports OAI-PMH protocol version 2.0

FAIL baseURL supplied 'https://demo.bibkat.no/cgi-bin/koha/oai.pl' does not match the baseURL in the Identify response 'https://demo.bibkat.no/opac/oai.pl'. The baseURL you enter must EXACTLY match the baseURL returned in the Identify response. It must match in case (http://Wibble.org/ does not match http://wibble.org/) and include any trailing slashes etc.

PASS Datestamp granularity is 'seconds'

FAIL Bad earliestDatestamp: The earliestDatestamp in the identify response (2020-04-27 09:43:27) does not have the correct format for the time part of the UTCdatetime. The overall format must be YYYY-MM-DDThh:mm:ssZ.

The OAI-PMH data provider with base URL https://demo.bibkat.no/cgi-bin/koha/oai.pl has failed initial validation. Problems reported must be corrected before validation can continue.

Tue Feb 1 13:45:40 2022

[Simeon Warner]

The validator is now able to handle https://revistas.unc.edu.ar/index.php/ConCienciaSocial/oai , which passes initial validation.

Cheers,

Simeon

Initial validation checks (step 1)

baseURL is https://revistas.unc.edu.ar/index.php/ConCienciaSocial/oai

Validation only
Request logged from 128.84.116.66

Checking Identify response

REQUEST https://revistas.unc.edu.ar/index.php/ConCienciaSocial/oai?verb=Identify GET

PASS Administrator email address is 'concienc...@fcs.unc.edu.ar'

PASS Correctly reports OAI-PMH protocol version 2.0

PASS baseURL supplied matches the Identify response

PASS Datestamp granularity is 'seconds'

PASS Extracted earliestDatestamp 2018-10-11T12:15:10Z

PASS oai-identifier description for version 2.0 is being used

PASS namespace-identifier (repositoryIdentifier element) in oai-identifier declaration is ojs.revistas.unc.edu.ar

The OAI-PMH data provider with base URL https://revistas.unc.edu.ar/index.php/ConCienciaSocial/oai has passed initial validation. An email message has been sent to the administrator's email address shown above which includes a URL to continue validation and/or registration. The purpose of this email step is to ensure that only the administrator can change the registration record of a date provider, and to avoid the possibility of excessive use of the validation script against a data provider by some third party.

Tue Feb 1 13:48:18 2022