At least on AIX, there was a problem with nvsecd falling down
and leaving the rest of the daemons up. It was fixed in 5.1.1.
The workaround was to restart nvsecd.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking



Hello!

I have installed some NetView-clients on Sun Solaris 2.6 and 7 workstations. The
NV-server is running Solaris 2.6. Netview version is 5.1.

The install performed OK, and we are able to run the clients - most of the time!
But sometimes, after closing a session, the GUI will not come back up the next
time. Whether it is started through the Tivoli Framework or on the commandline
(nv6000) it just complains : "ERROR : can not connect to daemons".

Running 'nvstatus' reveals nvsecd is not running. After starting this daemon
again on the server, the NV client again starts. But it is rather annoying.

Has anyone else experienced this, and/or have any suggestion to why nvsecd has
to be restarted ?

--

Mikael Dalsgard
    ___ ___
   /  /\\  |
  /  /  /  |
 /  / // /\|
/__/ // / \
\__\// // /  Ark Norge AS
 \--\  / /   Divisjon Skrivervik Data          +47 22 18 58 00 (switchboard)
  \  \  /    Postboks 3885 Ullevaal Stadion    +47 22 18 64 26 (direct)
   \__\/     0805 OSLO
             Norway