HP Serviceguard Quorum Server for Linux Version A.12.00.00 Release Notes, March 2014

Running the Quorum Server on a single system
Specifying a Log File
By default, Quorum Server runtime messages go to stdout and stderr. HP recommends that
you create a directory such as /var/adm/qs, then redirect stdout and stderr to a file in this
directory (for example, /var/adm/qs/qs.log) when you start the Quorum Server; see the sample
/etc/inittab entries in the examples below. Recommended pathnames are in Table 2 (page 13).
Running the Quorum Server
NOTE: If you have just installed the quorum server, or if you are adding new cluster nodes, or
implementing the alternate-subnet functionality (for a cluster running a version of Serviceguard that
supports it.
see “Compatibility with Serviceguard versions” (page 7)) you must update the authorization file
see “Creating and updating the authorization file” (page 14).
This section is not required if you are configuring quorum sever on Red Hat 6.0.
You must have root capability to run the Quorum Server. On a single system, configure the Quorum
Server to start up when the system on where it is installed restarts or reboots. Create an entry such
as the following in the /etc/inittab file:
• For RHEL 5 Linux
qs:345:respawn:/usr/local/qs/bin/qs >> /var/log/qs/qs.log 2>&1
NOTE: Nothing has to be done on RHEL 6 systems for Quorum Server to start up when the
system on which it is installed. As part of installation this is added to the “upstart.”
In RHEL 6, init from the sysvinit package has been replaced with “upstart”, an
event-based init system. This system handles the starting of tasks and services during boot,
stopping them during shutdown and supervising them while the system is running."
With this /etc/inittab is depricated.
• For SUSE Linux:
qs:345:respawn:/opt/qs/bin/qs >> /var/log/qs/qs.log 2>&1
Start the Quorum Server as follows:
init q
Verify the Quorum Server is running by checking the qs.log file. (Recommended log pathnames
are in Table 2 (page 13).)
cat /var/log/qs/qs.log
The log must contain entries such as the following, indicating that the Quorum Server has started:
Oct 04 12:25:06:0:main:Starting Quorum Server
Oct 04 12:25:09:0:main:Server is up and waiting for connections at port 1238
Creating and updating the authorization file
The Quorum Server reads the authorization file when it starts up. You need to create the file, on
the system(s) where the Quorum Server software resides, when you first install the Quorum Server,
and update it when you add nodes to a cluster the Quorum Server serves, or add or change the
IP addresses or hostnames by which the nodes communicate with the Quorum Server.
On a Red Hat Linux system, it must be /usr/local/qs/conf/qs_authfile.
On a SUSE Linux system, it must be /opt/qs/conf/qs_authfile.
14 HP Serviceguard Quorum Server for Linux version A.12.00.00 Release Notes