Troubleshooting system issues: how do I clear system locks?

This article is intended for IT professionals who support an on-premise installation of Keystone's software.

If you are having any issues logging in to Keystone Client or if KeyNet is not responsive, one of the first things to check is for "write locks" that need to be cleared.

To identify and clear these locks, follow these steps:

1. Open a UniVerse shell / TCL prompt, or open a new Keystone Client session and run it in character-based mode.
   
   
2. Type LIST.READU EVERY and hit enter. This displays a list of all active group and record locks. Under the "group" locks, look for anything with "WR" in the Lmode column. These are usually at the top of the list:
   
   
   
   
3. To clear these WR locks, look for the user number in the Userno column and type UNLOCK USER <Userno> ALL (see example above: UNLOCK USER 2 ALL).
   
   
4. If KeyNet is still not loading, connect to the application server and restart the "Redback Scheduler*" service.   Once restarted, try connecting to KeyNet again.

5. You should repeat the above steps to make sure there are no WR locks.

Note: one way to check for active KC or KeyNet connections is by going to a command prompt and typing "netstat -a". Keystone Client connects on ports 992 & 6701. KeyNet typically is configured to use ports 8401 and 8402.