DateCite traced its problems registering DOIs to disk space issues and has corrected the situation. New DOI registrations via EZID again appear to be moving through normally and the backlog of pending registrations has been completely cleared.
DataCite is seeing errors with 500 status code for registrations in the MDS. While this always happens occasionally for a number of different reasons, the number of 500 errors has increased in the last 24 hours. The 500 status code means that DOI registration was not successful. They are looking into the issue and will post an update as soon as possible.
EZID’s backend database suffered a momentary outage at 12:24pm Pacific time. We are investigating why the high availability/replication mechanism did not shield EZID from this outage. But all appears to be running normally now.
The last few days some large-scale processing has been taking place in EZID, with the result that DOI registrations have been delayed up to 8 hours. We have adjusted the procesing to impact end users no more than a few minutes.
As a reminder, DOI registration backlogs may occur at any time. This is due to the twin facts that EZID queues DOI operations for background processing, and that EZID operates much faster than the DataCite and Handle systems it interacts with.
EZID is back up. Honestly, we’re not sure what the problem was. A machine reboot and the problem vanished. We’ll continue to investigate, though.
EZID is having some technical difficulties. We’re investigating the problem now.
The LDAP server that EZID uses again stopped accepting password changes and other updates. The problem has been resolved.
The LDAP authentication system that EZID uses suddenly, for unexplained reasons, stopped accepting updates, thus making it impossible for users to update their contact information or reset their passwords. The problem has been resolved now. We will continue to investigate the root cause.
For approximately 15 minutes, beginning at 8:42am this morning, EZID lost connectivity with its authentication subsystem. As a result, some (but not all) requests failed. The connectivity has been restored. We apologize for the disruption.
From DataCite: “We are currently experiencing some connection problem to the primary
handle server running at CNRI. […] About 10% of all DOI minting/updating requests are currently failing. We have contacted CNRI and trying to resolve the issue. Due to the distributed nature of handle system this should have caused only minimal affect on DOI resolution – if any.”
