Troubleshooting Security Implementations - Internetworking Troubleshooting - page 761

• errors.postofficed —Errors occurring with the communication infrastructure.
• errors.sapd —Errors occurring during file management. This includes Oracle on the Director.
• errors.configd —Errors occurring during the configuration process of Sensors.
• errors.smid —Errors occurring with OpenView.
• errors.eventd —Errors occurring when trying to run an event. This is normally the paging process
but can be any script that you would like to run.
• errors.fileXferd —Errors with transferring files between the Sensor and the Director. This type of
file transfer normally happens when configuring the Sensor.
• errors.loggerd —Errors occurring while trying to log data to the log files.
• errors.nrConfigure —Errors occurring with the configuration graphical user interface (GUI).
Table 25-2 shows symptoms, possible problems, and suggested actions to be taken when troubleshooting
CiscoSecure IDS.
Table25-2 Troubleshooting NetRanger

Symptom Possible Problem Suggested Actions

Director not running
You see the
following error
message: “Cannot
write message to
Director, errno
=2.”

This error occurs when smid
tries to write to a socket that
does not exist. This may occur
because the Director's
nrdirmap application has not
created its communication
socket in /usr/nr/tmp because
the HP OpenView user
interface (ovw) was not started.

First ensure that the underlying
NetRanger services, such as
postofficed and smid, are
running by typing nrstatus at
the command line. If the
services are not running, type
nrstart to manually start them.
Then start HP OpenView by
typing ovw&at the command
line.

You see the
following error
message: “Cannot
write message to
Director, errno =
233.”

This error message is generated
when smid writes to a socket
whose buffer is overflowing.
This can occur when the
Director's nrdirmap
application is not running.

Ensure that the HP OpenView
user interface (ovw) is running
by executing ovw &. This will
automatically start nrdirmap.

You see the
following error
message: “Cannot
write message to
Director, errno =
239.”

This error message occurs
when smid and nrdirmap do not
have adequate permissions to
communicate via sockets in
/usr/nr/tmp.

Ensure that the smid process is
owned by user netrangr and that
nrdirmap runs as SUID
netrangr.