Can not start ntop. After start ntop I have the following problem:
Mon Mar 18 22:05:59 2013 NOTE: Interface merge enabled by default
Mon Mar 18 22:05:59 2013 Initializing gdbm databases
Mon Mar 18 22:05:59 2013 ERROR …open of /var/ntop/prefsCache.db failed: File open error
Mon Mar 18 22:05:59 2013 Possible solution: please use ‘-P <directory>’
Mon Mar 18 22:05:59 2013 FATAL_ERROR GDBM open failed, ntop shutting down…
Mon Mar 18 22:05:59 2013 CLEANUP[t140707982616768]: ntop caught signal 2 [state=2]
Mon Mar 18 22:05:59 2013 ntop is now quitting…
DENISLAV:~ # ntop Mon Mar 18 22:37:54 2013 NOTE: Interface merge enabled by default Mon Mar 18 22:37:54 2013 Initializing gdbm databases Mon Mar 18 22:37:54 2013 ERROR …open of /var/ntop/prefsCache.db failed: File open error Mon Mar 18 22:37:54 2013 Possible solution: please use '-P ’ Mon Mar 18 22:37:54 2013 FATAL_ERROR GDBM open failed, ntop shutting down… Mon Mar 18 22:37:54 2013 CLEANUP[t139753361340608]: ntop caught signal 2 [state=2] Mon Mar 18 22:37:54 2013 ntop is now quitting…
DENISLAV:~ # ntop Mon Mar 18 22:37:54 2013 NOTE: Interface merge enabled by default Mon Mar 18 22:37:54 2013 Initializing gdbm databases Mon Mar 18 22:37:54 2013 ERROR …open of /var/ntop/prefsCache.db failed: File open error Mon Mar 18 22:37:54 2013 Possible solution: please use '-P ’ Mon Mar 18 22:37:54 2013 FATAL_ERROR GDBM open failed, ntop shutting down… Mon Mar 18 22:37:54 2013 CLEANUP[t139753361340608]: ntop caught signal 2 [state=2] Mon Mar 18 22:37:54 2013 ntop is now quitting…
DENISLAV:~ # ntop
Mon Mar 18 22:51:23 2013 NOTE: Interface merge enabled by default
Mon Mar 18 22:51:23 2013 Initializing gdbm databases
Mon Mar 18 22:51:23 2013 ERROR …open of /var/ntop/prefsCache.db failed: File open error
Mon Mar 18 22:51:23 2013 Possible solution: please use ‘-P <directory>’
Mon Mar 18 22:51:23 2013 FATAL_ERROR GDBM open failed, ntop shutting down…
Mon Mar 18 22:51:23 2013 CLEANUP[t140140627196096]: ntop caught signal 2 [state=2]
Mon Mar 18 22:51:23 2013 ntop is now quitting…
DENISLAV:~ # ntop -A
Mon Mar 18 22:51:37 2013 NOTE: Interface merge enabled by default
Mon Mar 18 22:51:37 2013 Initializing gdbm databases
Mon Mar 18 22:51:37 2013 ERROR …open of /var/ntop/prefsCache.db failed: File open error
Mon Mar 18 22:51:37 2013 Possible solution: please use ‘-P <directory>’
Mon Mar 18 22:51:37 2013 FATAL_ERROR GDBM open failed, ntop shutting down…
Mon Mar 18 22:51:37 2013 CLEANUP[t140026020489408]: ntop caught signal 2 [state=2]
Mon Mar 18 22:51:37 2013 ntop is now quitting…
> DENISLAV:~ # ntop Mon Mar 18 22:37:54 2013 NOTE: Interface merge
> enabled by default Mon Mar 18 22:37:54 2013 Initializing gdbm databases
> Mon Mar 18 22:37:54 2013 ERROR …open of /var/ntop/prefsCache.db
> failed: File open error Mon Mar 18 22:37:54 2013 Possible solution:
> please use '-P ’ Mon Mar 18 22:37:54 2013 FATAL_ERROR GDBM open
> failed, ntop shutting down… Mon Mar 18 22:37:54 2013
> CLEANUP[t139753361340608]: ntop caught signal 2 [state=2] Mon Mar 18
> 22:37:54 2013 ntop is now quitting…
You’re still missing the CODE tags, but I think I might be able to make
some sense of this. Just for future reference, it also would be good to
pick a subject that wasn’t generic - something about ‘ntop’ in the
subject would probably help people determine if it’s a message they want
to read and try to help with.
The error message is indicating that /var/ntop/prefsCache.db cannot be
opened. I just tried this on my 12.2 system, and got the same error you
did - the directory isn’t created when installing the RPM, but if I start
with:
ntop -P .
then it works fine for me using the current directory.
Conclusion: Create /var/ntop and see if that helps. Or, as the error
message suggests, use the -P option to specify a path where the
configuration data should be stored.
On Mon, 18 Mar 2013 21:27:35 +0000, Ken Schneider wrote:
>> You’re still missing the CODE tags,
> Is it clearer now?
No.
I see from looking at it on the web side that the lines aren’t broken up
the way they are on the NNTP side.
Code tags are handled by the gateway to prefix each line with a space
(which is a standard way to tell a newsreader that the lines are not
continuous, but should be treated as if they were new lines).
There’s more reason to use them than just for readability on the web
interface.
Code tags are handled by the gateway to prefix each line with a space
(which is a standard way to tell a newsreader that the lines are not
continuous, but should be treated as if they were new lines).
There’s more reason to use them than just for readability on the web
interface.
Thanks for explaining that Jim. I had always wondered what output enclosed within
And adding them afterwards is of no use. When the original terminal text is not used for the copy/paste, all white space will be reduced already, never to be restored again.
And there are many reasons for the CODE tags:
. white space (columns, etc);
. fixed font (columns and important readability);
. no smileys;
. not URL interpreting;
. clear boundary between story telling and computer facts.;
. more …
