On Wednesday 05 January 2005 17:24, Patrick Shanahan wrote:

* Jan Elders [01-05-05 04:44]:

...

Can somebody tell me how to reset ntop running as daemon (SuSE 9.2) ?

Try the YasT/2 RunLevel Editor That I tried already. Then, RunLevel Editor tells me that ntop is not running anymore. However when I give the command "ntop -A -u wwwrun" it tells me : ========= Initializing gdbm databases **FATAL_ERROR** No password for admin user - please re-run ntop in non-daemon mode first ========= So apparently it still "remembers" somewhere that I had set it to daemon mode. Also re-booting does not help.

Any additional suggestions how to get back in non-daemon mode ? TIA and Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Thursday 06 January 2005 13:58, Patrick Shanahan wrote: //cut

...

However when I give the command "ntop -A -u wwwrun" it tells me : ========= Initializing gdbm databases **FATAL_ERROR** No password for admin user - please re-run ntop in non-daemon mode first ========= So apparently it still "remembers" somewhere that I had set it to daemon mode. Also re-booting does not help.

No, your logic is faulty, you are initiating ntop as non-daemon (?reporting) mode.

To see if ntop or ntopd is running, "ps aux|grep -i ntop" This gives : root 7736 0.0 0.1 1708 600 pts/4 S+ 14:05 0:00 grep -i ntop

Now what ? Thanks for your help, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Thursday 06 January 2005 14:12, Patrick Shanahan wrote:

* Jan Elders [01-06-05 08:08]: //cut

You have achieved your objective: ntop/notpd is *not* running

ps. you are surely not logging in as 'root' ????

Now I am confused :-( Whether I am logged in as root or as myself (= jrm), I get : jrm@MEDION:~> ntop -A -u wwwrun Thu Jan 6 14:37:49 2005 Initializing gdbm databases Thu Jan 6 14:37:49 2005 **FATAL_ERROR** No password for admin user - please re-run ntop in non-daemon mode first jrm@MEDION:~> We have just established that ntop is NOT running !!?? Am I missing something here ? Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Thursday 06 January 2005 15:00, Patrick Shanahan wrote:

* Jan Elders [01-06-05 08:46]:

...

Now I am confused :-(

Why?

Sorry. I'll try to be more specific. 1. I was interested in the functionality of ntop. 2. So, I started it with just the command "ntop" and .... it ran OK right away. 3. I could look at its data by using the ://localhost:3000 web interface and I liked it very much. 4. In that webinterface I also saw the possibility to indicate that it should run as a daemon. I did set that indication. So far so good. 5. But when I had to reboot the system, I got an errormessage about password setting for ntop and it was not activated anymore. It was then, that I discovered that I should have started in the very beginning by giving the command "ntop -A -u wwwrun" to set the right password. So apparently I had started the whole thing in the wrong way. :-( 6. Then I used RunLevel Editor to deactivate ntop and - just to be sure - rebooted. Then I gave the command I should have given in the beginning : ntop -A -u wwwrun which replied to me :  Initializing gdbm databases  **FATAL_ERROR** No password for admin user - please re-run ntop in non-daemon mode first 7. Not knowing what to do next, I decided to de-install ntop (with YaST) completely, and after that, re-installed it. 8. THEN the very first thing I did was ntop -A -u wwwrun which replied to me again :  Initializing gdbm databases  **FATAL_ERROR** No password for admin user - please re-run ntop in non-daemon mode first. 9. This is where I started my question of this thread, because the "fatal error" message gave me the impressing that the system still thinks that it is running in daemon mode. 10. So now I am confused. Ntop ran initially, but after having indicated in ntop's web interface that it should run as a daemon I screwed it up apparently and cannot even resolve it by removing and reinstalling ntop. Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Thursday 06 January 2005 17:35, Mike wrote:

...

On Thursday 06 January 2005 16:31, Jan Elders wrote:  Initializing gdbm databases  **FATAL_ERROR** No password for admin user - please re-run ntop in non-daemon mode first. 9. This is where I started my question of this thread, because the "fatal error" message gave me the impressing that the system still thinks that it is running in daemon mode.

How about going into /var/lib/ntop and deleting all the .db files? Then it would have to re-create them when you start it.

Whoa, that's a crude measure. But, YES ! That did the trick, now ntop is running fine again. Thanks for the suggestion, Mike. Greetings, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Thursday 06 Jan 2005 13:44, Jan Elders wrote:

jrm@MEDION:~> ntop -A -u wwwrun

Jan, as Patrick has explained, this command is trying to *start* ntop. why are you trying to start it if you don't want it running? -- Pob hwyl / Best wishes Kevin Donnelly www.kyfieithu.co.uk - Meddalwedd Rhydd yn Gymraeg www.cymrux.org.uk - Linux Cymraeg ar un CD!