close

Filter

loading table of contents...

Content Server Manual / Version 2110

Table Of Contents

2.2.4.2 Malfunctions of the Master Live Server

This scenario describes a Master Live Server malfunction. This error influences two processes:

  • publication: Publications are canceled as defective, blocked or cannot be carried out because the Master Live Server is not reachable.

  • replication: Replication is disabled. The Replication Live Servers stay online and the connected CAEs continue to operate with the already replicated content base.

Possible errors are:

Master Live Server Failure
Error behavior

The Replication Live Servers connected to the Master Live Server discontinues replication and attempts to log on again to the Master Live Server periodically in order to continue replication. Log attempts are written to the server log.

Publications are no longer possible and the publication which was running at the time of disruption fails. You will see an error message if you try to start a publication or publication preview with CoreMedia Studio .

Error correction To trigger a restart of the Master Live Server a deployment may use the Spring Boot health indicators provided below the URL :8081/actuator/health. You can find the list of available health indicator endpoints in the Actuator Endpoints section of the Section 4.10.1.1, “CoreMedia Health Indicator” in Operations Basics.

Table 2.1. Master Live Server failure


Master Live Server Deadlock

Error behavior

The clients hang up or receive error messages until the server is restarted.

Error correction

To trigger a restart of the Master Live Server a deployment may use the Spring Boot health indicators provided below the URL :8081/actuator/health. You can find the list of available health indicator endpoints in the Actuator Endpoints section of the Section 4.10.1.1, “CoreMedia Health Indicator” in Operations Basics.

Table 2.2. Master Live Server deadlock


Master Live Server Database Failure

Error behavior

Transactions which are active at the time of failure or which first notice the failure are terminated with an error. The error is passed to the server and clients. Further publications lead to errors. The Replication Live Server sdetect the malfunction andattempt to reconnect. You can see the login attempts in the server log. Transactions started after the server has detected the database failure are blocked until a new database connection is created. Clients (replication of the Live Server, publication, etc.) remain paused. Appropriate messages are written to the server log.

Error correction

To trigger a restart of the Master Live Server a deployment may use the Spring Boot health indicators provided below the URL :8081/actuator/health. You can find the list of available health indicator endpoints in the Actuator Endpoints section of the Section 4.10.1.1, “CoreMedia Health Indicator” in Operations Basics.

As soon as the database is available again the server creates new connections to the database (watch the server log) and blocked transactions are released. Note: Error-free operation after a database breakdown cannot be guaranteed, since external components are also affected (for example the JDBC driver).

Table 2.3. Database failure


Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.