Re: [Ntop-dev] Ntop runs, but can't be reached from http

Thu, 23 Mar 2006 10:29:22 -0800

Ok, so DNS should not be the problem then. I also tried to restart and shut down my server, but that did not help. Sometimes it runs for some hours, and sometimes just for some minutes.
 
- Thomas
----- Original Message -----
Sent: Thursday, March 23, 2006 12:09 AM
Subject: RE: [Ntop-dev] Ntop runs, but can't be reached from http

There's nothing special about ntop - it simply uses whatever name resolution is offered by the host (i.e. the /etc/resolv.conf configuration) via the standard C library calls (e.g. gethostbyip()).
 
To prevent the queue from growing too large, we cut it off if there are 4K awaiting - this handles an intial burst when ntop starts up, without wasting too much space if there is a DNS problem.
 
If name resolution fails - for whatever reason - then the queue will build.  If the problem is transient (gets fixed), then ntop will work the queue and it will decrease.  If the problem doesn't get fixed, it will eventually max out the queue and issue the warning message.
 
 
Sounds like you need to reboot your box - this cures all kinds of ills.
 
-----Burton
 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Kiellerup
Sent: Wednesday, March 22, 2006 4:26 PM
To: [email protected]
Subject: Re: [Ntop-dev] Ntop runs, but can't be reached from http

Well, that might be the problem. I have no local DNS for my eternal network on ETH2 yet. The resolv.conf has 2 external DNS records on the ETH0. Do I need a internal DNS to make it work, or can I somehow link to the external DNS?
 
The strange thing about it is that NTOP has been running fine for about a month or so and suddenly makes these errors?
 
- Thomas
----- Original Message -----
Sent: Wednesday, March 22, 2006 10:23 PM
Subject: RE: [Ntop-dev] Ntop runs, but can't be reached from http

You have some kind of problem with your name resolution - either no access to a dns server, etc. something like that.
 
Check /etc/resolv.conf and use nslookup or dig to make sure those work.  There is some info on this in docs/FAQ.
 
-----Burton

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Kiellerup
Sent: Wednesday, March 22, 2006 2:19 PM
To: [email protected]
Subject: [Ntop-dev] Ntop runs, but can't be reached from http

I have the past few weeks experienced some errors with NTOP. It keeps running the service, but sometimes I can't reach it with http. Then I have to stop the service with the zap command, and start it again. I tried to locate the problem with the command grep ntop /var/log/messages and it shows this:
 
**WARNING** Address resolution queue is full [4096 slots]
Addresses in excess won't be resolved - ntop continues
segfault at 0000000000000030 rip 00002aaaac39661d rsp 0000000044003b00 error 6
 
Its running on a Gentoo system, and keep track of about 150 users. Do anyone have any idea why this error orcurs? I'm very new to linux, so be gentle ;-)
 
- Thomas

_______________________________________________
Ntop-dev mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev

_______________________________________________
Ntop-dev mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev
_______________________________________________
Ntop-dev mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev

Reply via email to