To Start the LifeKeeper GUI Server
If the LifeKeeper GUI Server is not running, type the following command as root:
/opt/LifeKeeper/bin/lkGUIserver start
This command starts all LifeKeeper GUI Server daemon processes on the server being administered if they are not currently running. A message similar to the following is displayed.
# Installing GUI Log
# LK GUI Server Startup at:
# Mon May 8 14:14:46 EDT 2006
# LifeKeeper GUI Server Startup completed at:
# Mon May 8 14:14:46 EDT 2006
Once the LifeKeeper GUI Server is started, all subsequent starts of LifeKeeper will automatically start the LifeKeeper GUI Server processes.
Troubleshooting
The LifeKeeper GUI uses Ports 81 and 82 on each server for its administration web server and Java remote object registry, respectively. If another application is using the same ports, the LifeKeeper GUI will not function properly. These values may be changed by editing the following entries in the LifeKeeper default file /etc/default/LifeKeeper.
GUI_WEB_PORT=81 GUI_RMI_PORT=82
To Stop the LifeKeeper GUI Server
If the LifeKeeper GUI Server is running, type the following command as root:
/opt/LifeKeeper/bin/lkGUIserver stop
This command halts all LifeKeeper GUI Server daemon processes on the server being administered if they are currently running. The following messages are displayed.
# LifeKeeper GUI Server Shutdown at:
# Fri May 19 15:37:27 EDT 2006
# LifeKeeper GUI Server Shutdown Completed at:
# Fri May 19 15:37:28 EDT 2006
LifeKeeper GUI Server Processes
To verify that the LifeKeeper GUI Server is running, type the following command:
ps -ef | grep runGuiSer
You should see output similar to the following:
root 2805 1 0 08:24 ? 00:00:00 sh/opt/LifeKeeper/bin/runGuiSer
To see a list of the other GUI Server daemon processes currently running, type the following command:
ps -ef | grep S_LK
You should see output similar to the following:
root 30228 30145 0 11:20 ? 00:00:00 java -Xint -Xss3M
-DS_LK=true -Djava.rmi.server.hostname=thor48 …
Post your comment on this topic.