Hiya,
We had a situation recently where a hard NFS mount suddenly became
unavailable (it was taken away without unmounting, I know, yuck).
After which found that the snmpd process was consuming 3.2% (which on
this particular host is 1 full CPU in a 32-CPU 69k - Solaris 9). Further
investigation revealed that the process is spending 100% of its time in
system, below is the prstat -m output that shows this.
PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG
PROCESS/NLWP
87 root 0.0 99 - - - - 0.7 - 356 0 0 0 snmpd/1
I tried trussing the process, but it says that out of 10 seconds, it
spent 0 percent of it in system and 0 in user space. This sounds
contradictory; However, I believe the process was spinning out of
control and was not able to register these calls with truss as it is too
busy.
$ sudo truss -c -p 87
^Csyscall seconds calls errors
-------- ------ ----
sys totals: .000 0 0
usr time: .000
elapsed: 10.230
I'm just wondering if this is expected behaviour of snmpd, in a
situation where an NFS mount becomes unavailable.
NetSNMP 5.2.1 / Solaris 9.
--
Dean.
-------------------------------------------------------
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
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
