Table of Contents
Advertisement
Configuring the Subagent
If this parameter is not specified, the agent will write its logfile to the same
location as your subagent configuration file. The logfile will be named
ldap-agent.log
Make sure that the user as whom your subagent is running has write permission
to this directory.
server
The server setting specifes a Directory Server instance that you want to monitor.
You must use one server setting for each Directory Server instance. The subagent
requires at least one server setting to be specified in its configuration file. The
server setting should be set to the absolute path to the log directory of the
Directory Server instance you would like to monitor. For example:
server /opt/redhat-ds/slapd-phonebook/logs
Make sure that the user as whom you are running your subagent has read
permission to this directory.
Starting the Subagent
Once your master agent is running and you have created your subagent
configuration file, you are ready to start the subagent. To start your subagent, you
must run the
an argument. You must supply the absolute path to the configuration file:
./ldapagent /opt/redhat-ds/ldap-agent.conf
If you want to enable extra debug logging, you can specify the
startup:
./ldapagent -D /opt/redhat-ds/ldap-agent.conf
To stop your subagent, you must use the kill command against its process ID.
Your subagent will print its process ID in its logfile, or you can run
grep ldap-agent
Testing the Subagent
To test your subagent, you can use the Net-SNMP toolkit command-line utilities,
such as
for the Directory Server, you must configure them to load the Directory Server s
MIB file. The Directory Server s MIB file is located in server_root
472
Red Hat Directory Server Administrator's Guide • May 2005
.
program, specifying your subagent configuration file as
ldap-agent
to find the process ID.
and
snmpwalk
snmpget
. In order for these tools to display variable names
option during
-D
ps -ef |
/plugins/snmp
Advertisement
Table of Contents
Troubleshooting
