Stream: troubleshooting

Topic: Unable to publish dataset - possible EZID issue

view this post on Zulip jamie jamison (Jul 09 2025 at 16:09):

Still on 5.14 and payara5.  I'm running into an issue publishing datasets.

#|2025-07-08T19:05:28.937+0000|SEVERE|Payara 5.2022.4|edu.harvard.iq.dataverse.DatasetPage|_ThreadID=96;_ThreadName=http-thread-pool::jk-connector(3);_TimeMillis=1752001528937;_LevelValue=1000;|
  CommandException, when attempting to update the dataset: This dataset may not be published due to an error when contacting the <a href=https://ezid.cdlib.org target="_blank"/> EZID </a> Service. Please try again.
edu.harvard.iq.dataverse.engine.command.exception.CommandException: This dataset may not be published due to an error when contacting the <a href=https://ezid.cdlib.org target="_blank"/> EZID </a> Service. Please try again.
        at edu.harvard.iq.dataverse.engine.command.impl.AbstractDatasetCommand.registerExternalIdentifier(AbstractDatasetCommand.java:193)

I'm wondering if the doi settings in domain.xml have changed.
Mine look like:
<jvm-options>-DProtocol=doi</jvm-options>
<jvm-options>-Ddoi.provider=EZID</jvm-options>
<jvm-options>-Ddoi.password=**</jvm-options>
<jvm-options>-Dcom.ctc.wstx.returnNullForDefaultNamespace=true</jvm-options>
<jvm-options>-Ddoi.username=*</jvm-options>

Thank you,

Jamie Jamison
UCLA Dataverse

view this post on Zulip Philip Durbin 🚀 (Jul 09 2025 at 16:15):

Hoboy. EZID. Only supported in California. :smile:

view this post on Zulip Philip Durbin 🚀 (Jul 09 2025 at 16:15):

Is the EZID service up and working?

view this post on Zulip Philip Durbin 🚀 (Jul 09 2025 at 16:16):

Also, when was the last time published worked for you? And has anything changed?

view this post on Zulip Philip Durbin 🚀 (Jul 09 2025 at 17:43):

Oh good, Jim is helping here as well: https://groups.google.com/g/dataverse-community/c/gdTnvT5TAgM/m/SiuYx_E4BgAJ

view this post on Zulip jamie jamison (Jul 09 2025 at 19:47):

Jim was very helpful. I've gotten the userid, password and baseurl set. I just need to figure out how dataverse.pid.ezid.api-url is set. What ever I have for that is still incorrect.

view this post on Zulip Philip Durbin 🚀 (Jul 09 2025 at 19:49):

https://guides.dataverse.org/en/5.14/installation/config.html#dataverse-pid-ezid-api-url says it defaults to https://ezid.cdlib.org

view this post on Zulip jamie jamison (Jul 09 2025 at 20:10):

I have that. The other one I'm confused about is Ddataverse.pid.permalink.base-url. This isn't the same as the old base-url?

Documentation (https://guides.dataverse.org/en/5.14/installation/config.html#dataverse-pid-permalink-base-url) has:

dataverse.pid.permalink.base-urlhttps://guides.dataverse.org/en/5.14/installation/config.html#dataverse-pid-permalink-base-url

When using PermaLinks, this setting can be used to configure an external resolver. Dataverse will associate a PermaLink PID with the URL: <dataverse.pid.permalink.base-url>/citation?persistentId=perma:<permalink>. The default value is your Dataverse site URL, which will result in PermaLinks correctly resolving to the appropriate dataset page.

To set this option, issue a command such as:

./asadmin create-jvm-options '-Ddataverse.pid.permalink.base-url=https\://localresolver.yourdataverse.org'

So that would be url=https\://localresolver.dataverse.ucla.edu ?

view this post on Zulip jamie jamison (Jul 14 2025 at 20:23):

I contacted UC Berkeley, the other campus using EZID. They sent some examples and I've tried adding those but I'm still getting the error:
[#|2025-07-14T20:12:04.845+0000|SEVERE|Payara 5.2022.4|edu.harvard.iq.dataverse.DatasetPage|_ThreadID=97;_ThreadName=http-thread-pool::jk-connector(4);_TimeMillis=1752523924845;_LevelValue=1000;|
CommandException, when attempting to update the dataset: This dataset may not be published due to an error when contacting the <a href=https://ezid.cdlib.org target="_blank"/> EZID </a> Service. Please try again.
edu.harvard.iq.dataverse.engine.command.exception.CommandException: This dataset may not be published due to an error when contacting the <a href=https://ezid.cdlib.org target="_blank"/> EZID </a> Service. Please try again.

It's probably something obviouse but I haven't found the problem yet.

Can I share my domain.xml file with anyone just to get someother eyes on the problem.

-jamie

view this post on Zulip Philip Durbin 🚀 (Jul 14 2025 at 20:28):

Hmm, is there any more in server.log? That's pretty much the complete error?

view this post on Zulip jamie jamison (Jul 14 2025 at 21:13):

The entire error is too long to fit here. I've attached it as a text file.
payara5-error.txt

view this post on Zulip jamie jamison (Jul 14 2025 at 21:28):

What I think it comes down to is that I still don't have ezid setup correctly

view this post on Zulip Philip Durbin 🚀 (Jul 15 2025 at 13:08):

Hmm, I don't like the look of this:

String edu.ucsb.nceas.ezid.EZIDException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

view this post on Zulip Philip Durbin 🚀 (Jul 15 2025 at 13:09):

For @Yuyun Wirawati there was something wrong with a HTTP SSL cert: https://groups.google.com/g/dataverse-community/c/xD1gfiD5H-U/m/56aSTXkFEgAJ

view this post on Zulip Philip Durbin 🚀 (Jul 15 2025 at 13:10):

And there was a similar cert error here when trying to add a harvesting client: https://groups.google.com/g/dataverse-community/c/lpYLX4RkxO4/m/5KTRZQ-3AQAJ

view this post on Zulip Yuyun Wirawati (Jul 16 2025 at 01:19):

hmm, same error message.
For us, we replaced the cacerts.jks ( /usr/local/payara5/glassfish/domains/domain1/config/cacerts.jks) to new version. Connection to DataCite was restored, and we could publish again.

Last updated: Oct 30 2025 at 06:21 UTC