GSX Server Guard is locking-up or experiencing delays when starting with a debug message stating it is waiting for a write lock to complete. This is caused by the IBM Domino Server ID file being locked by another program, usually the IBM Domino server, preventing access to the Server ID file. If the Server ID file is not password protected, you can avoid this delay by adjusting a specific parameter in GSX Server Guard 7.6.1+. If you are running an older version, it can also be done by adjusting the delay in which GSX Server Guard waits to utilize the Server ID file; this allows the Domino server more time to finish its transactions before GSX Server Guard starts.
This article will provide you with options to prevent GSX Server Guard from conflicting with the IBM Domino server for access to the Server ID file, avoiding a write lock.
- Waiting for write lock in debug
- GetStats:01 ti="0051CD3C-CA257E2D" sq="000000FE" THREAD [0C6C:0002-0FD4] WAITING FOR WRITE LOCK ON RWSEM 0x02A2
How to Solve the Issue
If the IBM Domino Server ID file has no password and you have GSX Server Guard 7.6.1 simply clear the password protected box in the general tab. If you are using a version prior this you can delay the startup of GSX Server Guard by adjusting the Domino startup times. See the workaround below.
Clearing the Password Protected Box:
- Launch the GSX Server Guard 7.6.1+ interface.
- On the General tab, locate item 3) Password status.
- Remove the checkmark from the Domino is password protected box:
Workaround for pre-GSX Server Guard 7.6.1:
- Launch the GSX Server Guard interface.
- Select the Shutdown tab.
- Locate the Domino server timers section and set the Start delay to 5 minutes:
- This parameter can be adjusted to match the startup time of your Domino server and its components.
Increasing this delay will allow the Domino server more time to finish its transactions with the Server ID file before GSX Server Guard starts.