This document serves as a Root Cause Analysis for the Alma service interruption experienced by Ex Libris customers on May 26, 2019
The goal of this document is to share our findings regarding the event, specify the root cause analysis, outline actions to be taken to solve the downtime event, as well as preventive measures Ex Libris is taking to avoid similar cases in future.
Intermediate service interruptions were experienced by Ex Libris customers served by the Alma EU00 instance at our European Data Center during the following time period:
May 26th, 2019 from 06:05 AM until 07:25 AM Amsterdam time
May 29th, 2019 from 01:04 PM until 01:38 PM Amsterdam time
During the event, Service was unavailable for the environment
Root Cause Analysis
Ex Libris Engineers investigated this event to determine the root cause analysis with the following results:
A code malfunction caused database error, resulted in disruption to the environment and required system restart to bring the application back to full functionality.
The code malfunction was fixed with an injection done on May 29th.
Technical Action Items and Preventive Measures
Ex Libris has taken the following action and preventive measures to avoid such an occurrence in future:
- Ex Libris engineers restarted all the environment components to restore the service.
- Code fix was injected on May 29th.
Ex Libris is committed to providing customers with prompt and ongoing updates during Cloud events. Ongoing and prompt updates on service interruptions appear in the system status portal at this address: http://status.exlibrisgroup.com/
These updates are automatically sent as emails to registered customers.
|June 5, 2019||Initial Publication|