Marcelo,
This "sudden death" has already happened to me some times. That
happened to me when the Netview server was running out of swap
space.
So, check out the size of your swap space, and increase it if
necessary. If you are using AIX do the following:
- Open two shell windows
- on the first type netview
- on the second type "lsps -a" in a regular basis. Until the netview
goes down.
With this simple test you will be able to see if you are running out of
swap space.
Hope this helps,
Claudio Medeiros
Date sent: Thu, 10 Feb 2000 08:46:18 -0200
Send reply to: Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV-L@UCSBVM.UCSB.EDU>
From: Marcelo Pastre <mpastre@POWER.UFSCAR.BR>
Subject: Other Problem..
To: NV-L@UCSBVM.UCSB.EDU
> Hi folks...
> I have one more strange problem.
> I type netview and it start.
> But after a few minutes late (about 10 minutes), the NetView close itself.
> I did verify the logs file: trapd.log, ovactiond.log, snmpCol.log and
> nvcorrd.alog.
> Please, look this files:
>
> /usr/OV/log/trapd.log
> last line => T FATAL: Killing trapd on signal 33
>
> /usr/OV/log/ovactiond.log
> last line => 02/04/00 15:00:31 ovactiond lost contact with trapd.
>
> /usr/OV/log/snmpCol.log
> last line => Fri Feb 04 15:00:30 2000 : Signal #33 received, exiting.
>
> /usr/OV/log/nvcorrd.alog
> 2000/04/02 15:00:30 nl_nvcorrd.C[751] : Unable to start connection with
> trapd to receive SNMP traps
> 2000/04/02 15:00:31 nl_nvcorrd.C[760] : Error number from trapd is 63
> 2000/04/02 15:00:31 nl_nvcorrd.C[802] : exitting because connection for
> traps failed The connext(2) system call failed
>
> What's happening???
> Did it happen to someone before?
>
> Thanks very much,
> Marcelo.
>
Claudio Medeiros
cmedeiro@pobox.com
ICQ UIN: 26244020
|