Actually, I've tried adding the -t option with 30, 60 and even 90. Still
nothing. I've checked a few more of the "exec" lines that I have in my
snmpd.conf and it looks like the output from them is being truncated at
around 25 or 30 lines. They originally all looked like this:
exec .1.3.6.1.4.1.2021.50 prtdiag /usr/platform/sun4u/sbin/prtdiag -v
exec .1.3.6.1.4.1.2021.51 prtconf /usr/sbin/prtconf -pv
exec .1.3.6.1.4.1.2021.52 ps /usr/bin/ps -ae -o user,pid,ppid,args
The first 'exec' truncated at about the 25th line, the third at about
the 32nd. I tried removing the OIDs from the 'exec' lines and walking
the extTable as well. It didn't get much futher:
$ snmpwalk -t90 beta extTable
UCD-SNMP-MIB::extIndex.1 = INTEGER: 1
UCD-SNMP-MIB::extIndex.2 = INTEGER: 2
UCD-SNMP-MIB::extIndex.3 = INTEGER: 3
UCD-SNMP-MIB::extNames.1 = STRING: prtdiag
UCD-SNMP-MIB::extNames.2 = STRING: prtconf
UCD-SNMP-MIB::extNames.3 = STRING: ps
UCD-SNMP-MIB::extCommand.1 = STRING: /usr/platform/sun4u/sbin/prtdiag -v
UCD-SNMP-MIB::extCommand.2 = STRING: /usr/sbin/prtconf -pv
UCD-SNMP-MIB::extCommand.3 = STRING: /usr/bin/ps -ae -o
user,pid,ppid,args
UCD-SNMP-MIB::extResult.1 = INTEGER: 0
Timeout: No Response from beta
It took a LOT longer than 90 seconds to timeout, so I suspect
'something' is going on. On the system running the agent, it doesn't
take that long to run the command - but it returns a decent amount of
output:
beta# timex /usr/sbin/prtconf -pv | wc
real 0.14
user 0.04
sys 0.10
686 1263 38022
beta#
On a lark I compiled my own version of net-snmp 5.1.1 and created a
Solaris package from it. It had exactly the same problem. For reference,
I'm using gcc 3.3.2 on Solaris 9 (the sunfreeware gcc package) and a
custom compiled OpenSSL of 0.9.7d. Here is my configure command:
./configure \
--with-openssl=/usr/local/ssl \
--with-mib-modules="host ucd-snmp/diskio" \
--enable-shared=yes --enable-static=yes \
--with-libwrap \
--with-default-snmp-version="3" \
--with-sys-contact="XXXXXXXXXXXXXXXXXXXXXX" \
--with-sys-location="Data Center" \
--with-logfile="/var/log/snmpd.log" \
--with-persistent-directory="/var/net-snmp" \
--with-install-prefix=/www/dest/net-snmp-5.1.1
I know all the other connectivity (SNMPv3, tcpwrappers, etc.) is fine.
After restarting the daemon with noone else hitting it first, I can walk
the "system" MIB without a problem.
If you have any other debugging methods etc., I have this setup in a
test environment and am willing to "break" anything/everything to get
this to work.
Thanks,
Tony
--
"Computer science is as much about computers as
astronomy is about telescopes" -- Edsger Dijkstra
---------------------------------------------------------
Anthony Tonns, UNIX Administrator - [EMAIL PROTECTED]
> -----Original Message-----
> From: Wes Hardaker [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 28, 2004 3:19 PM
> To: Anthony Tonns
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: agent hung up running "exec" process
>
> >>>>> On Wed, 28 Jul 2004 09:47:40 -0400, Anthony Tonns
> <[EMAIL PROTECTED]> said:
>
> Anthony> exec .1.3.6.1.4.1.2021.51 prtconf /usr/sbin/prtconf -pv
>
> Anthony> When I query this mib on the agent, becomes unresponsive (ie:
> Anthony> snmpwalk: Timeout). The subcommand stays running as a sub
> Anthony> process of the agent. If I kill the subcommand, the agent
> Anthony> spawns a new one and is still unresponsive.
>
> Is it just taking a long time? IE, if you increase the timeout of the
> snmpwalk with the -t flag (say, -t 30) does it return properly?
>
> --
> Wes Hardaker
> Sparta
>
>
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id040&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
