The CAS is unable to be accessed after start-up following a double power outage.

2023-06-30 00:30:22 Published
  • 0 Followed
  • 0Collected ,559Browsed

Network Topology

Null

Problem Description

After a power outage in the local machine room, the cluster restarts with CAS E0760P0x version, but it"s discovered that the front end cannot be accessed.

Process Analysis

To troubleshoot the issue with the front-end not being accessible: 

1. Check the state of the dual hosts by running "crm status" and verify that it"s normal. 

2. Check the front-end logs in /var/log/tomcat/cas.log. The logs indicate an error message stating that the local address 127.0.0.1 cannot connect to the database.


3. Attempted to manually connect to the database according to instructions, but the same error message occurs.  


  1. Checked the mariadb logs, and found numerous similar printouts:

2023-02-08 17:32:49 4 [Warning] Aborted connection 4 to db: "unconnected" user: "unauthenticated" host: "127.0.0.1" (This connection closed normally without authentication)

  1. It can be determined that the problem is caused by the database service not functioning properly. After analyzing the code, it is found that during the server restart, the database partition was not mounted when mariadb was started, resulting in mariadb using an empty database and causing the issue.



Solution

1. Perform a "systemctl restart mariadb" to restart the database and restore it to its proper function. 

2. Disable the automatic start-up of mariadb by running "systemctl disable mariadb".

Please rate this case:   
0 Comments

No Comments

Add Comments: