Re: Failed to connect to the agentx master agent (/var/agentx/master)

Just in case anyone had questions about my snmpd.conf.  Here it is
below.  The comments have been stripped out, but line 36 is the trapsink
line as mentioned in the original e-mail. 
 
Thanks, 
Rich 
 
----------------------------------------------------------------------------------------------------------

# snmpd.conf 
syslocation Server Room 
syscontact Sysadmin (root@localhost) 
 
rocommunity public 127.0.0.1 
 
trapsink host.name.server.com public 
 
master agentx 
 
com2sec demouser default public 
 
group demogroup v1 demouser 
 
view all included .1 
 
access demogroup "" any noauth exact all all all 
 
----------------------------------------------------------------------------------------------------------

 
 
 
 
>>> On Tue, Jan 10, 2006 at  8:04 am, in message
<[email protected]>, wellhouse, richard wrote: 
 
 
 
>>> On Mon, Jan 9, 2006 at  4:05 pm, in message
<[email protected]>, wellhouse, richard wrote: 
 
Hi, 
 
I am using net-snmp v5.2.2 on a SLES 9 SP2 system.  When I boot my
server I get the following message in the snmpd.log. 
 
snmpd:  create_trap_session: Unknown host
(udp:host.name.server.com:162) 
/opt/novell/snmp/snmpd.conf: Line 36: Error: cannot create trapsink:
host.name.server.com 
Turning on AgentX master support 
NET-SNMP version 5.2.2 
 
In my /var/log/boot.msg file snmpd load with no errors, BUT when the
subagent load I get the following error. 
 
Starting NDS SNMP Subagent ... 
Please Wait... 
Warning: Failed to connect to the agentx master agent
(/var/agentx/master): Unknown host (/var/agentx/master) 
(No such file or directory) 
Warning: Failed to connect to the agentx master agent
(/var/agentx/master): Unknown host (/var/agentx/master) 
(No such file or directory) 
Done 
 
I do have a /var/agentx/master file. 
 
Some additional notes.  If I stop the subagent and stop snmpd and then
restart them without restarting the system they all load fine with no
errors.  I have another server using the same configuration and I do not
get the above errors when booting.  All loads fine on the second
system.  One visual difference I have seen is the /var/agentx/master
file on the working system looks like this. 
 
[Mon Jan 09 16:00:24]<~> # ll /var/agentx 
total 0 
srwxr-xr-x  1 root root 0 Jan  6 15:37 master= 
 
[Mon Jan 09 16:00:31]<~> # 
 
On the failing system it looks like this. 
 
Server B:/var/log #  ll /var/agentx 
total 1 
drwx------   2 root root  72 Jan  9 15:34 . 
drwxr-xr-x  21 root root 624 Jan  6 11:23 .. 
srwxr-xr-x   1 root root   0 Jan  9 15:34 master 
 
Notice the = (equals sign)?  Not sure if that adds any clues or
not.  Again the one with the = sign works fine during boot. 
 
Any thoughts? 
 
Thanks, 
Rich 
 
 




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users