corosync-qdevice - Can't init nss (xxxx): security library: bad database.

Solution Verified - Updated -

Issue

When trying to start the corosync-qdevice service it fails

[root@fastvm-rhel-8-4-135 ~]# systemctl start corosync-qdevice
Job for corosync-qdevice.service failed because the control process exited with error code.
See "systemctl status corosync-qdevice.service" and "journalctl -xe" for details.
[root@fastvm-rhel-8-4-135 ~]#

And the log file shows that 'Can't init nss...' error.

Sep  1 11:07:19 fastvm-rhel-8-4-135 systemd[1]: Starting Corosync Qdevice daemon...
Sep  1 11:07:19 fastvm-rhel-8-4-135 corosync-qdevice[155264]: Can't init nss (-8174): security library: bad database.
Sep  1 11:07:19 fastvm-rhel-8-4-135 systemd[1]: corosync-qdevice.service: Main process exited, code=exited, status=1/FAILURE
Sep  1 11:07:19 fastvm-rhel-8-4-135 systemd[1]: corosync-qdevice.service: Failed with result 'exit-code'.
Sep  1 11:07:19 fastvm-rhel-8-4-135 systemd[1]: Failed to start Corosync Qdevice daemon.

Environment

Red Hat Enterprise Linux 7-9 High Availability or Resilient Storage clusters registered in a quorum device

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content