Introduction

This document serves as a Root Cause Analysis for the Primo service interruption experienced by Ex Libris customers on March 1,  2018

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.

Event Timeline

Service interruption was experienced by Ex Libris customers served by the Primo MT CA01 instance at the Canada Data Center during the following hours: 

March 1^st, 2018 from 7:00 AM until 7:40 AM CST time.

During the event, the 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:

Following incorrect configuration in one of the components, the Database didn’t succeed to connect to the Front Ends,  which caused impact to the service.

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 fixed the incorrect configuration
• Full Audit was executed on the environments to verify that there are no misconfigurations in other environments.

Customer Communication

ExLibris 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/