In 4 years of working on this product I have never seen anything like this. You
need to tell us how you got here. What were you doing before nvsecd started to
fail like this? Is this a new install? If so, then you need to review your
install logs and find out where it wnet wrong, because something is VERY wrong.
James Shanks
Tivoli (NetView for UNIX and NT) L3 Support
ytchew@mas.com.my (GroupIT - Chew Yean Tai) on 04/12/2000 12:40:01 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: NV-L@tkg.com
cc: (bcc: James Shanks/Tivoli Systems)
Subject: [NV-L] Problems starting nvsecd
Hi,
I have problems starting the nvsecd daemon and as a result, I couldn't start
any of the other NV daemons. The message that I got when I ran the 'nvsecd'
command was :
-------------------------
nvsecd: startTime value: 955513867.
FNS0644: Could not open message file
nvsecd: the Authentication protocol is 2-party
FNS0644: Could not open message file
FNS0644: Could not open message file.
FNS0644: Could not open message file.
ERROR: nvsecd: nvsecd: The server key could not be installed.
Terminated
nvsecd: Closing Security.
nvsecd: Saving audit info.
In cleanupOVwSec
nvsecd: Completed closing nvsecd security daemon.
-----------------
And when I ran the 'ovstart nvsecd' command, I got this message :
----------------------------
ovstart nvsecd
object manager name: nvsecd
behavior: OVs_WELL_BEHAVED
state: FAILED
PID: 22548
last message: nvsecd: The server key could not be installed.
Terminated
exit status: -
-----------------------------
Any help to get my NV started (without re-installing NV) will be
appreciated...
Warmest Regards,
Kendra
_________________________________________________________________________
NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l
|