Kevin M. Myer wrote:
I'm working through some of the documentation for the ldap-agent at
(although with Fedora Directory Server). I have a simple
ldap-agent.conf file in /opt/fedora-ds/slapd-instance/config. The
documentation states that a config item of "server" should be
specified that points to the log directory of the Directory Server
instance to be monitored. I found that it balked if I did that:
ldap-agent: Error opening server config file:
so I changed the server value to be just /opt/fedora-ds/slapd-instance.
The documentation states that the "server" parameter needs to be set to
the log directory of the slapd instance you want to monitor. Here is
the example from the Admin Guide:
How are you starting the subagent? Are you passing it the full path to
the ldap-agent config file you created? Your command should be
Error message goes away but now when I try to start ldap-agent, I get:
ldap-agent: Not started! Check log file for details.
And if I check the log file for details, I see:
2005-11-30 16:58:21 Starting ldap-agent...
The -D option generates no more additional information.
On the server, net-snmp is running, with agentx support, listening to
a socket in /var/agentx/master. The documentation states that version
5.2.1 is required, but I'm only running 5.1.2.
Now I found that if I disabled iptables on this server, the agent came
up, one time. Thought that was it but then I found if I killed it and
restarted it, it didn't come up. And then with iptables enabled
again, it did come up. And then it didn't. You get the picture - its
very inconsistent :)
So, anyone have this running reliably?