That's just a pass through from gdbm to ntop, so I would suspect a
corrupted gdbm file.
Set tracelevel: -t 5 and check the log - the last thing it's attempting
to open/read is probably the problem child.
-----Burton
enediel gonzalez wrote:
Hello
I have had ntop installed and working properly, but now I face the
following problem, I restart the ntop and it recreates the database, and
waiting for less than a minute I see the output
gdbm fatal: lseek error
after that ntop stops.
What should I do to fix this problem?
Thanks in advance for any answer
Enediel
Linux user 300141
Debian GNU/Linux
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
