nv-l

Re: [nv-l] Starting from Nvevents killed the nvserverd-Daemon

2002-04-12 09:33:43
Subject: Re: [nv-l] Starting from Nvevents killed the nvserverd-Daemon
From: "James Shanks" <jshanks AT us.ibm DOT com>
To: nv-l AT lists.tivoli DOT com
Date: Fri, 12 Apr 2002 09:33:43 -0400
Did it actually kill nvserverd or are you just getting that pop-up 
message?  Do ovstatus nvserverd to make sure.
nvevents has a heartbeat mechanism which queries nvserverd periodically to 
see if it is up, especially if a request it has made times out.
That's when you get the pop-up.  Hitting OK just resets the timer for the 
retry of the query in nvevents; "Cancel" just cancels the timer.   Neither 
one has any real effect on the connection itself. 

Anyway, it sounds to me as though you have a socket connection problem of 
some kind, but I have little idea what you could have changed in Nvevents 
to make that occur.  I would restore the app-defaults copy to the way it 
was shipped and see if that helps. You will find the "as shipped" version 
in
/usr/OV/newconfig/IBM-RUN/Nvevents .

The way I recommend that you experiment with the Nvevents app-defaults is 
to copy it to your $HOME directory and modify that local copy only.  Then 
run
         xrdb -merge Nvevents 
after you change it to merge it in with your personal X-defaults.    Then 
test by just typing in  "nvevents" from the command line and running a 
local copy outside the NetView GUI until you are satisfied with what you 
have.  If you have to run the entire GUI to see what changes you have 
made, then you can run one with a read-only map while the main NetView is 
unaffected.  Only when you are completely sure of your changes, would I 
replace the Nvevents in app-defaults with the one you have changed.

Hope this helps

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group
 





Ulrich.Eisenberger AT LVA-Braunschweig DOT de
04/12/2002 09:03 AM

 
        To:     nv-l AT lists.tivoli DOT com
        cc: 
        Subject:        [nv-l] Starting from Nvevents killed the 
nvserverd-Daemon

 

Hi folks,

after little tests with the Ruleset-Editor and changes in the
/app-defaults/Nvevents - file the Event-Viewer will never starts up.
Following error appears after the Start from NetView 6.0.2:

Daemon Error
The nvevents server daemon(nvserverd) is not running.
Restart it with the command: /ovstart nvserverd
...
Followed by the OK an CANCEL Button

Maybe i've pressed the cancel-button!

After typing the ovstart-command at the prompt nvserverd is still running,
after typing nvevents at the prompt a further error message appear:

Error: Object "" does not have windowed ancestor

and nothing else happens, only the nvserverd - daemon is down again!


May anyone help me?


Greetings

Ulrich Eisenberger

LVA Braunschweig
Email: Ulrich.Eisenberger AT LVA-Braunschweig DOT de


---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe AT lists.tivoli DOT com
For additional commands, e-mail: nv-l-help AT lists.tivoli DOT com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)





<Prev in Thread] Current Thread [Next in Thread>