Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts

  • ezidstatus 7:22 am on January 9, 2017 Permalink  

    N2T binder/resolver down 

    At 9:34pm PDT last night the N2T binder/resolver suffered a database failure.  At 7:00am PDT this morning EZID was temporarily disconnected from N2T, meaning that EZID identifier operations will now succeed normally, with no further internal server errors.  The only effect is that newly-registered ARK identifiers will not resolve.  When N2T is back online, any ARK identifiers created during the outage will automatically be registered with N2T.  DOI identifiers are unaffected.

  • ezidstatus 2:18 pm on November 8, 2016 Permalink  

    Intermittent errors noticed, addressed 

    An identifier subsystem that EZID talks to has been returning intermittent errors for the last day or so, which to EZID clients look like internal server errors.  Because these errors are intermittent, we’ve added some extra retry logic in EZID to shield EZID users from them.  In the meantime, we’re continuing to investigate the problems with the subsystem.

  • ezidstatus 6:57 pm on September 16, 2016 Permalink  

    DataCite Metadata Store problems fixed 

    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.

  • ezidstatus 10:59 am on September 16, 2016 Permalink  

    Errors registering DOIs with DataCite Metadata Store 

    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.

  • ezidstatus 12:39 pm on July 12, 2016 Permalink  

    Momentary database outage 

    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.

  • ezidstatus 10:25 am on June 22, 2016 Permalink  

    DOI registrations delayed a few hours 

    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.

  • ezidstatus 10:32 am on May 25, 2016 Permalink  

    EZID back up 

    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.

  • ezidstatus 10:27 am on May 25, 2016 Permalink  

    Technical difficulties 

    EZID is having some technical difficulties.  We’re investigating the problem now.

  • ezidstatus 9:54 am on January 25, 2016 Permalink  

    Another LDAP problem 

    The LDAP server that EZID uses again stopped accepting password changes and other updates.  The problem has been resolved.

  • ezidstatus 11:57 am on December 21, 2015 Permalink  

    LDAP semi-outage fixed 

    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.

Compose new post
Next post/Next comment
Previous post/Previous comment
Show/Hide comments
Go to top
Go to login
Show/Hide help
shift + esc