unix socket or tcp socket complains that
"AgentX master agent failed to respond to ping" and tries to
re-register. The mib does not work and can not be queried with this
problem.
After uninstalling the rebuilt rpm's and installing from a src.tgz,
the problem still occurs. Aft
Hi all,
I am using net-snmp 5.4.2.1 on RHEL 5.3 64 bit platform. Recently I moved
one of my mib table to sub-agent which connects master agent on tcp:705. But
while doing a walk on that table the sub-agent dies by outputting below
messages:
*AgentX master agent failed to respond to ping
On Thu, 2005-04-28 at 22:06, W Raul S wrote:
> There is no authentication between the sub-agent and the master
> agent, and yes, "master agentx" is enabled and started from within the
> master agent.
OK - so when you start the master agent, does it create the named
socket /var/agentx/master ?
And
Hello Dave,
The socket is created when the master agent starts up. It is not
deleted (as usual) when the master agent shutsdown. Observing this i
instead used the -x option to specify a tcp port, which checking
through netstat, established a connection to the sub-agent process.
Raul
On 4/29/05,
On Fri, 2005-04-29 at 14:23, W Raul S wrote:
> The socket is created when the master agent starts up. It is not
> deleted (as usual) when the master agent shutsdown.
That's what I half suspected. Normally the master agent *should*
delete the socket when it closes down cleanly (I think).
What h
a) It successfully creates the socket.
b) The agent does 'connect', but fails to register. Note netstat's
output for the sub-agent app 'rmApps-subDemo' for when the master
agent and sub-agent are connected. (see below)
After shutting down the sub-agent and master agent, the socket
'master' does no
On Fri, 2005-04-29 at 14:40, W Raul S wrote:
> a) It successfully creates the socket.
> b) The agent does 'connect', but fails to register.
Hmmm...
OK - Try running both the master agent and subagent in the
foreground ("-f -Le" or equivalent), and with packet dumps
turned on ("-d"). Those are fo
agent on tcp:705. But
> while doing a walk on that table the sub-agent dies by outputting below
> messages:
>
> *AgentX master agent failed to respond to ping. Attempting to
> re-register.
> ..
> ..
> NET-SNMP version 5.4.2.1 AgentX subagent connected
> ..
> ..
>
