2.3. Starting the Piranha Configuration Tool Service

2.3. Starting the Piranha Configuration Tool Service

After you have set the password for the Piranha Configuration Tool, start or restart the piranha-gui service located in /etc/rc.d/init.d/piranha-gui. To do this, type the following command as root:

/sbin/service piranha-gui start

or

/sbin/service piranha-gui restart

Issuing this command starts a private session of the Apache HTTP Server by calling the symbolic link /usr/sbin/piranha_gui -> /usr/sbin/httpd. For security reasons, the piranha-gui version of httpd runs as the piranha user in a separate process. The fact that piranha-gui leverages the httpd service means that:

  1. The Apache HTTP Server must be installed on the system.

  2. Stopping or restarting the Apache HTTP Server via the service command stops the piranha-gui service.

Warning

If the command /sbin/service httpd stop or /sbin/service httpd restart is issued on an LVS router, you must start the piranha-gui service by issuing the following command:

/sbin/service piranha-gui start

The piranha-gui service is all that is necessary to begin configuring an LVS cluster. However, if you are configuring the cluster remotely, the sshd service is also required. You do not need to start the pulse service until configuration using the Piranha Configuration Tool is complete. See Section 4.8, “Starting the Cluster” for information on starting the pulse service.


Note: This documentation is provided {and copyrighted} by Red Hat®, Inc. and is released via the Open Publication License. The copyright holder has added the further requirement that Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder. The CentOS project redistributes these original works (in their unmodified form) as a reference for CentOS-4 because CentOS-4 is built from publicly available, open source SRPMS. The documentation is unmodified to be compliant with upstream distribution policy. Neither CentOS-4 nor the CentOS Project are in any way affiliated with or sponsored by Red Hat®, Inc.