Re: [nv-l] Nvcorrd exits on signal 15

[James Shanks <jshanks@us.ibm.com>]

Well, signal 15 is SIGTERM, which is
what ovspmd would send
But the nvcorrd logs should tell you.
  When terminated by ovspmd a message to that effect is the line in
the current log.
 When nvcorrd is restarted, the
new current log is the .alog, which is opened afresh for writing, and the
last current log is copied to the .blog.  So if you haven't rolled
over to the blog yet, and you won't unless you are tracing or getting a
lot of errors, you should see it, and it would be time-stamped.

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

"Barr, Scott" <Scott_Barr@csgsystems.com>
Sent by: owner-nv-l@lists.us.ibm.com

04/21/2004 09:31 AM

Please respond to
nv-l

To	<nv-l@lists.us.ibm.com>
cc
Subject	[nv-l] Nvcorrd exits on signal 15

NetView v7.1.4
Solaris 2.8

Nvcorrd exiting on signal 15. Happened several times last night and now
it seems okay. Any suggestions on this? No core files. It is possible it
was being shut down via automation (ovstop).