Installation guide

EMC NetWorker Release 8.1 SP1 Installation Guide 139
Verify the Installation
◆ For HP-UX Console clients:
a. In the NMC console, select Setup > Setup System Options.
b. Clear RPC ping by using UDP when connecting to NetWorker checkbox.
c. Click OK.
d. Try to connect to the NetWorker server in the NMC console.
Unable to start gstd process on Console server
This section describes how to troubleshoot when the Console client cannot connect to the
Console server because the gstd process will not start.
When the gstd daemon does not start on the Console server, review the gstd.raw,
db_output.log and web_ouput log files to obtain the exact error message.
The following directories contain the Console server log files:
◆ Solaris: /opt/LGTOnmc/logs
◆ AIX and Linux: /opt/lgtonmc/logs
◆ Windows: C:\Program Files\EMC NetWorker\Management\GST\logs
Common Console server start-up errors include:
◆ “Error: 'gstd: Internal error: could not get database handle.'” on page 139
◆ “Web server exited unexpectedly. Possible reasons include: previous instance of %s is
still running. Please see 'web_output' file in this product's logs directory for the web
server's output messages” on page 140
◆ “Error: error while loading shared libraries: libsasl2.so.2: wrong ELF class:
ELFCLASS64” on page 140
◆ “Warning: unable to detect Java Runtime Environment” on page 140
Error: 'gstd: Internal error: could not get database handle.'
This error appears when the dbsrv12 process cannot start. Review the db_output.log file
for specific errors.
Common reasons for this error include:
◆ Insufficient disk space in the file system that contains the NMC database directory.
◆ An orphaned dbsrv12 process is running on the Console server.
• On UNIX, end the process by sending the SIGTERM signal, kill -TERM.
Do not use kill -9.