Red Hat Bugzilla – Bug 1296255
could not lock client with self-hosted LTS
Last modified: 2017-04-18 22:05:51 EDT
Description of problem:
When running hardware certification tests, if a system is both results server and test system, an error about locking is printed.
Version-Release number of selected component (if applicable):
still checking for workarounds or another cause of the same symptoms. Seen several times, it seems like there may be an additional condition.
Steps to Reproduce:
1. create a hardware certification from packages on the server, without registering any systems.
2. an error message is printed, explaining that the user must register a system before being able to select it for a cert
3. add the system itself as a test system
The results screen that is loaded next shows an error message immediately below the new hostname:
Error: could not lock client
no complaint about locking
Going to the page to launch tests (a single results file), there are no tests listed.
got the same error, is it possible to overcome?
Got the same error, is it possible to overcome?
Please, on the client, try:
$rhcert-backend print (answer yes if it asks to override locks)
Starting RedHatCertDaemon at 2016-07-19 13:37:13
The rhcert daemon is not running
The rhcert listener is not running
[root@r-dcs81 ~]# rhcert-backend print
No test results or plan to print
[root@r-dcs81 ~]# rhcertd start
Starting RedHatCertDaemon at 2016-07-19 13:37:35
Starting rhcert daemon
Starting rhcert listener
Starting RedHatCertDaemon at 2016-07-19 13:39:31
The rhcert daemon is running
The rhcert listener is running
Nothing happens, and I cant open UI.
This site can’t be reached
r-dcs81 took too long to respond.
How can I debug/reinstall rhcert?
Is httpd running? Try:
$systemctl restart httpd
systemctl start iptables.service solved the issue
p.s. I've seen same error.
After I've stopped #rhcertd stop
the lock file remained /var/lock/subsys/rhcert
After I had deleted /var/lock/subsys/rhcert, the issue has gone.