I used TMRTGCHO as community name before, but since I've got this problem I
use now public.
Request from localhost or any other interface doesn't work.
I cleaned snmpd.log, restarted snmpd:
#/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l
/var/log/snmpd.log

and a new one is located at http://www.tarakan-network.com/snmpd.log (I did
a snmpwalk and snmpget for public@localhost but no success)

----- Original Message -----
From: "Jean-Francois Dive" <[EMAIL PROTECTED]>
To: "Chojin" <[EMAIL PROTECTED]>
Sent: Wednesday, September 12, 2001 10:38 AM
Subject: Re: Problem with snmpd


> Hi (salut)
>
> In fact, i see some successfull request with the community:
> TMRTGCHO and no attemps with the localhost one... seems pretty odd. did
> you only got those requests from localhost not working ?
>
> Otherwise, purge the log file, be *sure* that no requests are comming from
> somewhere else and resart to see some failures...
>
> JeF
>
> On Wed, 12 Sep 2001, Chojin wrote:
>
> > I launched in debug mode
> > #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l
> > /var/log/snmpd.log
> > I attached snmpd.log
> > There are so many informations I can't detect the problem :pp
> >
> > ----- Original Message -----
> > From: "Jean-Francois Dive" <[EMAIL PROTECTED]>
> > To: "Chojin" <[EMAIL PROTECTED]>
> > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> > 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" <[EMAIL PROTECTED]>
> > > > To: "Chojin" <[EMAIL PROTECTED]>
> > > > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> > > > 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 [EMAIL PROTECTED]
> > > > > > with "unsubscribe freebsd-hackers" in the body of the message
> > > > > >
> > > > >
> > > >
> > >
> >
>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to