snmpd crashed upon reload

Purnendu <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <CAEe_9YE1bKEad76RfnCoYwC-y7KzqNS8+=m0f_K4DfeJJ7Qo9g@mail.gmail.com>
Hello all,


Thanks for your continuous support.



I am facing an issue with snmpd crashing upon snmpd reload.



I could avoid this issue by modifying the reload function

in snmpd and use reloadproc instead of killproc



reload(){

        echo -n $"Reloading $prog: "

#        killproc /usr/sbin/snmpd -HUP

#        RETVAL=$?

#        echo

#        return $RETVAL

         reloadproc /usr/sbin/snmpd

         return 0



}





However I am still not able to understand the issue with the

previous code. I have copied a snap of strace log below.



write(85, "Connection from <UNKNOWN> (Local IPC: /tmp/local-agent)\n", 56)
= 56

gettimeofday({946692039, 25235}, NULL)  = 0

send(92, "<174>Jan  1 02:00:39 snmpd[17582]: Connection from <UNKNOWN>
(Local IPC: /tmp/local-agent)\n", 91, MSG_NOSIGNAL) = 91

clock_gettime(CLOCK_MONOTONIC, {9359, 707021863}) = 0

--- SIGSEGV (Segmentation fault) @ 0 (0) -



*My environment :*

Target: Linux  2.6.34.10-WR4.3.0.0_standard #2 PREEMPT armv7l armv7l armv7l
GNU/Linux
Host: Linux  2.6.32-38-server #83-Ubuntu SMP on x86_64 GNU/Linux
OS: Windriver 4.4.1

NetSNMP Version: :5.4


Best Regards,

Purnendu Ghosh

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF

_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.