From: Tania O. <ta...@ce...> - 2001-07-24 02:25:33
|
Thank you very much, John and Dave, for your replies. > You could check this by doing ls -l /var/agentx/master after > starting the master agent up. You should see something like: > > srwxr-xr-x 1 root root 0 Jul 23 12:41 /var/agentx/master I did this - it seems that /var/agentx/master is not being created at all. > So if the master agent is not the net-snmp master agent, then it is hard to > > say where the socket gets created. So would it be correct to say that the master agent is responsible for creating the socket completely independently of net-snmp? That it is not done inside one of the net-snmp library functions that the master calls (i.e. init_agent(), init_snmp(), init_master_agent())? I can't see any place in the master agent code where the method of communication with the net-snmp subagent is set up, so I am wondering if it is actually done inside one of those calls. I plan to try tracing through those calls today to see if I can figure out what is going on. > My initial guess would be that the master agent doesn't have enough > permissions to create /var/agentx/master. I neglected to say earlier that I am running both the master and subagent as root. > Or possibly that it's listening on the AgentX TCP port (705) instead > of the AgentX named pipe (/var/agentx/master) > > In which case, you'd have to run our subagent using > > snmpd -X -x 705 ..... I tried this (with great excitement), but got: subagent_pre_init: Invalid local port (Connection refused) Thanks again. If anything else comes to mind, please let me know. Tania |