---
name: "gulm_tool"
section: "8"
platform: "linux"
package: "gulm"
version: "1.03.00-2"
release: "Debian 4.0 (Etch)"
platforms: ["linux"]
url: "https://new.carta.tech/gulm_tool"
---

# gulm\_tool(8)

**NAME** gulm\_tool - Interface to Grand Unified Lock Manager

**SYNOPSIS** **gulm\_tool** command \[options\]

**DESCRIPTION** **gulm\_tool** is an interface to a variety of options available to running **lock\_gulmd** servers.

The second parameter for most commands is the hostname or IP of the server followed by the port at which it runs.  Keep in mind that in the simplest setup, there are three servers running on a host.  For this, there is a short hand for the default server ports.  So you can use "core", "ltpx", and "lt000" through "lt256" for the port value instead of the actual number.  If you are using different ports for the **lock\_gulmd** servers, you will need to use the numbers.  If you don't specify the port, "core" is assumed.

**COMMANDS**

**Commands that only core understands**

**shutdown** *server*:core This command is use to stop a gulm server cleanly.  This can only be sent to the "core" port.

The use of this command is the proper way to shutdown gulm servers.  It is preferred over the use of SIGTERM.  Any other method will result in a fencing action against the server node.

**nodelist** *server*:core Get a list of the nodes currently logged into the master server.

**nodeinfo** *server*:core *node name* Get information for a single node.

**servicelist** *server*:core Get list of services connected to this node.

**foreceexpire** *server*:core *node name* Force the node to move into the Expired State.  This will cause the node to be fenced.

**Commands that can be sent to any server**

**getstats** *server:port* This gets a list of whatever statistics the specified server carries.

**setverb** *server:port* *verbose\_flags* Sets which types of messages can be logged.

*verbose flags* is a comma separated list of the possible flags.  If a flag is prefixed with a '-', it is unset, other wise it is set.  The special flag 'clear' unsets all verbosity flags.  Any flag that is not recognized is ignored.

The verbosity flags for gulm:

| | |
| --- | --- |
| Network | Basic network related messages |
| Network2 | More specific network messages |
| Network3 | A debug message for nearly every packet |
| Fencing | When calling out to the fencing sub-system |
| Heartbeat | Every heartbeat sent and received |
| Locking | Various internal informational messages about the locks |
| Forking | Anytime a child processes is spawned |
| ServerState | Print out a message when ever the server changes state, saying what state it is now in. |
| JIDMap | Details of each JID Mapping request |
| LockUpdates | Lock requests sent to slaves |
| LoginLoops | Messages related to searching for and becoming the Master |
|  |
| ReallyAll | All messages above |
| Default | same as -v "Network,Fencing,Forking" |
| All | same as -v "ReallyAll,-Network3,-LockUpdates" |

Since Network3, and LockUpdates are so verbose, and rarely needed, they are excluded from the 'All' flag.

Do not use ReallyAll unless you are willing to deal with 100M and larger log files.  A loaded system can produce up to a megabyte a minute with the ReallyAll flag.

**Commands that only gulm\_tool understands**

**version** or **-V** Print out the version information of this program.

**--help** or **-h** Print out the commands with brief descriptions.

**SEE ALSO** [lock\_gulmd(8)](/lock_gulmd/8.md)