Hi there,

I'm preparing a new Linux config to run ntop. My test system is a IBM Server
X335 with RedHat Enterprise AS 3.0 where I installed both ntop 3.0 (compiled
from source .tgz) and a recent CVS version.

A few weeks ago I had problems with the version 3.0 crashing after running
only a few minutes. I sent a bug report to ntop-dev but haven't heard
anything yet - see

    http://lists.ntop.org/pipermail/ntop-dev/2004-October/004975.html

Then the crashes became less frequent, it could run for hours before
crashing. I finally decided to run a cron job every 10 minutes to restart
ntop if it crashes. It ran without problems during last weekend and then it
started crashing a few times a day. Today it started crashing after running
only a few minutes again.  ;-(

Today I tried both version 3.0 and 3.0.053 (recent CVS) and they both crash
after running only a few minutes.

All these crashes don't show anything interesting in the logs; the ntop
processes simply disappear. And it will crash even if I don't use the
built-in web server to see pages.

So my questions are:

    - has anyone else seen this?

    - is it possible that a certain pattern of traffic or a specific packet
could crash ntop like that? Since it runs sometimes for days, and then only
for a few minutes, I suspect it may have to do with some weird traffic that
is not always present.

I'm running with --no-mac and the traffic I'm sniffing is a mirror port on a
switch. Memory doesn't seem to be an issue - the machine has 512 megs of
RAM, nothing else is sunning on it and according to top, ntop uses about 50
megs of RAM, there is some free memory almost and no swap is used - that's
with a version that is running OK, I don't know if this changes just before
a crash.

I start ntop with the following command (with real addresses instead of the
xxx's):

/usr/local/ntop3/bin/ntop -i eth1 --user ntop --daemon
   --db-file-path /var/ntop/ntop3 -i eth1
   -m xxx.xxx.0.0/16,xxx.xxx.xxx.0/22, xxx.xxx.xxx.0/23, xxx.xxx.xxx.0/24
   --trace-level 5 --use-syslog=local1 --http-server 3003
   --filter-expression-in-extra-frame --no-mac --track-local-hosts
   --disable-schedyield --max-table-rows 50 --refresh-time 300
   --access-log-file /var/ntop/ntop3/access.log

Any help would be greatly appreciated!

Regards,

Marc.
-- 
Marc Mazuhelli
Computer security analyst
Service des technologies de l'information
Universit� de Sherbrooke

_______________________________________________
Ntop mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop

Reply via email to