Date: Wed, 12 Sep 2001 10:35:23 +0200 From: "Chojin" <freebsd@tarakan-network.com> To: <freebsd-questions@FreeBSD.ORG>, <freebsd-hackers@FreeBSD.ORG> Subject: Re: Problem with snmpd Message-ID: <003701c13b65$dd8e7100$0245a8c0@chojin>
next in thread | raw e-mail | index | archive | help
I launched in debug mode #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l /var/log/snmpd.log You can see my snmpd.log at http://www.tarakan-network.com/snmpd.log (as it is too big for ML) There are so many informations I can't detect the problem :pp ----- Original Message ----- From: "Jean-Francois Dive" <jef@linuxbe.org> To: "Chojin" <freebsd@tarakan-network.com> Cc: <freebsd-questions@FreeBSD.ORG>; <freebsd-hackers@FreeBSD.ORG> Sent: Wednesday, September 12, 2001 9:53 AM Subject: Re: Problem with snmpd > i think it is possible to start the snmpd and not send it to backgroud, > and see if it does printout some error messages..Otherwise use the truss > command to follow the syscalls made by the daemon while processing your > request, this could point you to a problem.. > > JeF > > On Wed, 12 Sep 2001, Chojin wrote: > > > snmpd.log is empty... > > > > I did #netstat -an | grep 161 > > udp4 0 0 *.161 *.* > > > > port 161 exists then it should work... > > > > ----- Original Message ----- > > From: "Jean-Francois Dive" <jef@linuxbe.org> > > To: "Chojin" <freebsd@tarakan-network.com> > > Cc: <freebsd-questions@FreeBSD.ORG>; <freebsd-hackers@FreeBSD.ORG> > > Sent: Wednesday, September 12, 2001 3:21 AM > > Subject: Re: Problem with snmpd > > > > > > > Hi, > > > > > > So you have any traces in a log file or something similar ? > > > > > > JeF > > > > > > On Tue, 11 Sep 2001, Chojin wrote: > > > > > > > Hello, > > > > > > > > I have a problem with snmpd. > > > > > > > > In fact, one day, for unknown reason ( I didn't modify any setting ), > > snmpd > > > > didn't work anymore: > > > > When I do a snmpwalk or snmpget to public@localhost it doesn't respond. > > > > I checked snmpd, recreated snmpd.conf and launched again snmpd with -c > > > > and -l to be sure it uses the correct files. > > > > But even if snmpd is in background process, public@localhost doesn't > > work. > > > > I don't have any firewall rule that block it. > > > > > > > > #snmpwalk localhost public > > > > Timeout: No Response from localhost > > > > #snmpget localhost public SysName > > > > Timeout: No Response from localhost. > > > > > > > > After I upgraded my system from 4.3-STABLE to 4.4-RC, it didn't change > > > > anything for snmpd. > > > > > > > > If someone has got any idea... > > > > > > > > Best regards, > > > > > > > > Chojin > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003701c13b65$dd8e7100$0245a8c0>