Check the firewall on the box.
Thank you
Gary Douglas
On Nov 22, 2005, at 10:34 AM, Gianni Jacklone wrote:
OK, so I compiled by source. set the permissions on my db directory
and fired up ntop. It does not seem to be dying now all of a
sudden. But when I try to go the web ui, I get a connection refused
in my browser, which is weird because netstat shows ntop listening
on the correct ports. When I telnet from the localhost to port 80 I
get a web page back. So it seems ntop is accepting connections from
the localhost but not from remote hosts.
Any ideas what's up?
Thanks,
Gianni
Burton Strauss wrote:
Then it isn't really building w/o tcp-wrappers. Compile from the
ntop
source (@ SourceForge) and try again.
-----Burton
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of
Gianni Jacklone
Sent: Monday, November 21, 2005 4:29 PM
To: [email protected]
Subject: Re: [Ntop] ntop won't remain running for too long
Hi Burton,
ntop version 3.2
I recompiled without tcp-wrapper support (using FreeBSD's port
system) but
my log seems to still show ntop trying to read /etc/hosts.allow,
and it
still dies after a while. From my /var/log/messages:
Nov 21 16:37:31 stats ntop[3458]: THREADMGMT[t154313728]: WEB:
Server connection thread running [p3458]
Nov 21 16:37:31 stats ntop[3458]: WEB: ntop's web server is now
processing requests
Nov 21 16:37:31 stats ntop[3458]: THREADMGMT[t154314752]: RRD:
Data collection thread starting [p3458]
Nov 21 16:37:31 stats ntop[3458]: THREADMGMT[t154315264]: NPS
(1,rl0): pcapDispatch thread starting [p3458]
Nov 21 16:37:31 stats ntop[3458]: THREADMGMT[t154315264]: NPS
(1,rl0): pcapDispatch thread running [p3458]
Nov 21 16:37:41 stats ntop[3458]: THREADMGMT[t154315776]: RRD:
Started thread for throughput data collection
Nov 21 16:37:41 stats ntop[3458]: THREADMGMT[t154314752]: RRD:
Data collection thread running [p3458]
Nov 21 16:37:41 stats ntop[3458]: THREADMGMT[t154315776]: RRD:
Throughput data collection: Thread starting [p3458]
Nov 21 16:37:41 stats ntop[3458]: THREADMGMT[t154315776]: RRD:
Throughput data collection: Thread running [p3458] Nov 21 16:37:42
stats
ntop[3458]: warning: can't get client address: Bad file descriptor
Nov 21
16:37:43 stats ntop[3458]: warning: /etc/hosts.allow, line 23:
can't get client address: Bad file descriptor Nov 21 16:38:14
stats last
message repeated 21 times Nov 21 16:38:37 stats last message
repeated 8
times Nov 21 16:50:35 stats last message repeated 76 times Nov 21
16:57:34
stats last message repeated 75 times Nov 21 16:57:35 stats kernel:
pid 3458
(ntop), uid 65534: exited on signal 11 Nov 21 16:57:35 stats
kernel: rl0:
promiscuous mode disabled
Thanks,
Gianni
Burton Strauss wrote:
Which version of ntop is this?
Give it a try without the top-wrapper - it sounds like that isn't
allowing connections... (note that you may need to work from the
real source for that).
-----Burton
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Gianni Jacklone
Sent: Monday, November 21, 2005 12:51 PM
To: [email protected]
Subject: [Ntop] ntop won't remain running for too long
Hello,
I just installed ntop 3.2 on FreeBSD 5.4 using the ports package,
and the install went smooth. I started up ntop just fine, and was
able to browse the web interface, so far so good. But after about
a minute, ntop crashes. I have left all the defaults alone,
except explicitly setting the HTTP and HTTPS ports to 80 and 443
respectively.
Here are some highlights from /var/log/messages
Nov 21 13:43:06 stats ntop[499]: warning: can't get client
address: Bad file descriptor Nov 21 13:43:07 stats ntop[499]:
warning: /etc/hosts.allow, line
23: can't get client address: Bad file descriptor Nov 21
13:43:35 stats last message repeated 14 times Nov 21 13:45:44
stats last message repeated 21 times Nov 21 13:47:11 stats last
message repeated
35 times Nov 21 13:47:14 stats kernel: pid 499 (ntop), uid 65534:
exited on signal 11 Nov 21 13:47:14 stats kernel: rl0:
promiscuous mode disabled
after that last message, ntop has stopped.
Has anyone ever experienced this? I imagine perhaps some tuning
is in order to get ntop to run stable? Also could this be from a
lack of hardware resources? I only have 512MB of Ram on this box,
but it will be dedicated to ntop.
Thanks in advance,
Gianni Jacklone
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
