Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*nvcorrd\s+exit\s+on\s+signal\s+No\.\s+9\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*nvcorrd\s+exit\s+on\s+signal\s+No\.\s+9\s*$/: 7 ]

Total 7 documents matching your query.

1. nvcorrd exit on signal No. 9 (score: 1): Author: Geoffrey Cheng <gcheng AT CA.IBM DOT COM>; Date: Fri, 9 Jul 1999 11:07:49 -0400; Hi, I've met a problem with nvcorrd, when doing a ovstart, nvcorrd started for a few seconds and then died silently, on signal no. 9. I've commented out all the rules in ESE.automation, but the probl; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-07/msg00113.html (11,462 bytes)
2. Re: nvcorrd exit on signal No. 9 (score: 1): Author: James Shanks <James_Shanks AT TIVOLI DOT COM>; Date: Fri, 9 Jul 1999 11:44:46 -0400; Hmmm. A signal 9 is just that. You can find out the meaning of any signal by doing "man signal". They are non-standard exits from UNIX. Signal 9 is the process being killed by the operating system or; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-07/msg00116.html (12,230 bytes)
3. Re: nvcorrd exit on signal No. 9 (score: 1): Author: Geoffrey Cheng <gcheng AT CA.IBM DOT COM>; Date: Fri, 9 Jul 1999 16:10:22 -0400; James, Yes, it's the only info. I've attached the ovstatus output as follows. Thanks. == ovstatus: sent STATUS request to ovspmd object manager name: OVsPMD behavior: OVs_PMD state: RUNNING PID: 1975; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-07/msg00126.html (17,886 bytes)
4. Re: nvcorrd exit on signal No. 9 (score: 1): Author: Karin Binder <karin.binder AT NWA DOT COM>; Date: Fri, 9 Jul 1999 15:29:34 -0500; Geoffrey, Don't know if this will help, but have you turned on nvcdebug and checked the nvcorrd logs? Karin -- follows. == == NetView signal by the reason. this out. NetView started for file. can see; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-07/msg00127.html (21,296 bytes)
5. Re: nvcorrd exit on signal No. 9 (score: 1): Author: Geoffrey Cheng <gcheng AT CA.IBM DOT COM>; Date: Fri, 9 Jul 1999 16:58:55 -0400; Thanks, Karin, yes, I tried. But since nvcorrd is not running, nvcdebug failed. Best Regards Geoffrey Cheng Please respond to karin.binder AT nwa DOT com Geoffrey, Don't know if this will help, but h; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-07/msg00130.html (21,558 bytes)
6. Re: nvcorrd exit on signal No. 9 (score: 1): Author: James Shanks <James_Shanks AT TIVOLI DOT COM>; Date: Fri, 9 Jul 1999 17:42:49 -0400; You're getting this on AIX? What level? and how long has NetView V5.1.1 been installed? Have you added the ulimit statements as described in the release notes? If it won't stay up long enough for nvc; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-07/msg00132.html (23,171 bytes)
7. Re: nvcorrd exit on signal No. 9 (score: 1): Author: James Shanks <James_Shanks AT TIVOLI DOT COM>; Date: Mon, 12 Jul 1999 08:16:56 -0400; It occurs to me that in addition to trying to set the AOTDEBUG flag, you might just want to try starting the daemon from the command line and see if any error messages accompany the failure. Just go; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-07/msg00151.html (23,810 bytes)

Current List: 1 - 7
Page: [1]