User`s guide

12 – Troubleshooting

Tracing SANblade Manager GUI and Agent Activity (Debug)

FS0054601-00 E 12-15

3. Start the agent, again, without forking into the background. Redirect the stdout

and stderr properties to a file (see section 12.2.1, step 2). Send the file to

technical support.

# /usr/local/bin/qlremote > /AgentOutput.txt 2>&1

4. Open a second terminal to start the SANblade Manager GUI. Connect to the

host with the SANblade Manager GUI.

5. From the terminal you opened in step 1, press CTRL+C to stop the qlremote

agent. This causes the agent to clean up and terminate.

From a Solaris SPARC system, do the following to export agent activity:

1. Open a terminal (for example, xterm or eterm).

2. Do the following to stop the currently running qlremote agent:

a. Type the following and then press ENTER to determine the process identifier

(pid) of qlremote:

# ps -ef | grep qlremote

The pid displays, as in the following example. Note that in the example, the

pid is 227.

b. Type the following and then press ENTER. pid is the identifier returned in

step a.

# kill -TERM pid