Symptom:
After the password of user omm for logging in to the database is changed, log in to DeviceManager immediately to query events and alarms immediately. However, the query times out.
Diagnosis:
View the /var/log/oam/oam-u/oam-gaussdb/run/gaussdb.log file. The log content is as follows:
If the GaussDB log shows that user omm fails to log in using the new password, the possible cause is that a service user is using the old password. As a result, user omm is locked.
Cause:
User omm of GaussDB is locked. As a result, services are abnormal.
Solution:
Perform the following operations on the active node:
Change the value of failed_login_attempts in the /opt/dfv/oam/oam-u/oam-gaussdb/data/postgresql.conf file to 0, as shown in the following figure.
Run the su - ommdba -s /bin/bash command to switch to user su - ommdba -s /bin/bash, as shown in the following figure.
Run the gs_ctl reload command to reload the configuration file.
Run the gsql -d postgres -p 21600 -h 127.0.0.1 -U ommdba command, enter the password of user ommdba to access the database, and run the ALTER USER omm ACCOUNT UNLOCK command to unlock user omm.
Check After Recovery:
Check whether services are running properly. Use the new password to log in to the omm database and check whether the login is successful.
