Bug 251668 - net-mgmt/net-snmp daemon stop answering requests
Summary: net-mgmt/net-snmp daemon stop answering requests
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Ryan Steinmetz
Depends on:
Reported: 2020-12-07 13:58 UTC by Boris Tassou
Modified: 2020-12-17 08:44 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (zi)

config file (6.87 KB, text/plain)
2020-12-07 13:58 UTC, Boris Tassou
no flags Details
ktrace snmp process (9.44 KB, text/plain)
2020-12-17 08:42 UTC, Boris Tassou
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Boris Tassou 2020-12-07 13:58:56 UTC
Created attachment 220345 [details]
config file


On some FreeBSD 12.1 hosts, daemon snmpd stop answering request.
I need to restart it with a specific method :
kill -3 $(cat /var/run/net_snmpd.pid)
service snmpd restart

Withtout that, the restart command get stuck.
No information in the /var/log/snmpd.log file.

Informations :
freebsd-version -kr 

pkg info | grep net-snmp
net-snmp-5.9,1                 Extendable SNMP implementation

all my nodes with net-snmp have this issue.

I don't know where to search to debug this issue.

In attachment, the config file.

Comment 1 Ryan Steinmetz freebsd_committer freebsd_triage 2020-12-07 14:13:52 UTC
You can try running ktrace against it and then using kdump to display the results.

It would be interesting to see what it is doing whenever it seems like it has stopped responding.
Comment 2 Boris Tassou 2020-12-07 14:43:41 UTC
Thanks for the tip, i comment my cron job and when the problem come back i will check with ktrace when a send a request
Comment 3 Boris Tassou 2020-12-17 08:42:46 UTC
Created attachment 220658 [details]
ktrace snmp process
Comment 4 Boris Tassou 2020-12-17 08:44:13 UTC
The problem came back this morning, so i used this command : ktrace -p 74695 -f ktrace-snmp.log

(the log file is in attachments).

I haven't run the command very long because i don't know if it usefull.

Thanks for the help