Hello, I''m working through some of the documentation for the ldap-agent at http://www.redhat.com/docs/manuals/dir-server/ag/7.1/snmp.html (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: /opt/fedora-ds/slapd-instance/logs/config/dse.ldif so I changed the server value to be just /opt/fedora-ds/slapd-instance. 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? Kevin -- Kevin M. Myer Senior Systems Administrator Lancaster-Lebanon Intermediate Unit 13 http://www.iu13.org
Kevin M. Myer wrote:> Hello, > > I''m working through some of the documentation for the ldap-agent at > http://www.redhat.com/docs/manuals/dir-server/ag/7.1/snmp.html > (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: > /opt/fedora-ds/slapd-instance/logs/config/dse.ldif > > 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: server /opt/redhat-ds/slapd-phonebook/logs 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 something like: ./ldapagent /opt/redhat-ds/ldap-agent.conf -NGK> > 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? > > Kevin >
Nathan, I''m not sure if it matters what directory the agent is invoked from but the results are the same, if invoked with a full path, or if already in the bin/slapd/server directory: # cat /opt/fedora-ds/slapd-instance/config/ldap-agent.conf server /opt/fedora-ds/slapd-instance/logs # ./ldap-agent /opt/fedora-ds/slapd-instance/config/ldap-agent.conf ldap-agent: Error opening server config file: /opt/fedora-ds/slapd-instance/logs/config/dse.ldif # cat /opt/fedora-ds/slapd-instance/config/ldap-agent.conf server /opt/fedora-ds/slapd-instance # ./ldap-agent /opt/fedora-ds/slapd-instance/config/ldap-agent.conf ldap-agent: Started as pid 25012 And a minor nit, the documentation talks about ldapagent and the binary is actually ldap-agent. Kevin -- Kevin M. Myer Senior Systems Administrator Lancaster-Lebanon Intermediate Unit 13 http://www.iu13.org
Kevin M. Myer wrote:> Nathan, > > I''m not sure if it matters what directory the agent is invoked from > but the results are the same, if invoked with a full path, or if > already in the bin/slapd/server directory: > > # cat /opt/fedora-ds/slapd-instance/config/ldap-agent.conf > server /opt/fedora-ds/slapd-instance/logs > # ./ldap-agent /opt/fedora-ds/slapd-instance/config/ldap-agent.conf > ldap-agent: Error opening server config file: > /opt/fedora-ds/slapd-instance/logs/config/dse.ldifDoh! I didn''t notice this before, but the docs are incorrect. The "server" parameter should point to the instance directory, not the logs directory. In your case, it should be set to "/opt/fedora-ds/slapd-instance".> > # cat /opt/fedora-ds/slapd-instance/config/ldap-agent.conf > server /opt/fedora-ds/slapd-instance > # ./ldap-agent /opt/fedora-ds/slapd-instance/config/ldap-agent.conf > ldap-agent: Started as pid 25012 > > And a minor nit, the documentation talks about ldapagent and the > binary is actually ldap-agent.I''ll get documentation bugs filed for these issues. -NGK> > > Kevin >