nvstat
-cleanup (maybe /cleanup) will fix the dead port if nothing else works.
Unsupported but I Have used it on ovactiond.
The message means
that trapd could not get the UDP port for which he is configured, which is
usually 162, because someone else has it. Do you have something else
like midmand (MLM) also on the box? If so, he will grab port 162 when
trapd goes down. If not, then do a do a "ps -ef | grep trapd" and
see if there is an old copy of trapd still running, possibly with a parent of
1. If you find, one kill it (kill -9 <process_id).
If you cannot get that to work,
then I suggest you stop all the daemons and restart them with /etc/netnmrc or
else reboot. And finally, call
Support
James Shanks Level 3
Support for Tivoli NetView for UNIX and Windows Tivoli Software / IBM
Software Group
Abadir Hany-O10544
<o10544@motorola.com> Sent by: owner-nv-l@lists.us.ibm.com
03/01/2004 03:15 PM
|
To
| "'nv-l@lists.us.ibm.com'"
<nv-l@lists.us.ibm.com>
|
cc
|
|
Subject
| [nv-l] Error with
trapd |
|
Hello,
NV7.1.3 on AIX 4.3.1 Netmon went down and when I
tried to restart it, I found that trapd is down as shown below, any idea what
does that mean or how can I resolve that?
object manager name:
trapd behavior:
OVs_WELL_BEHAVED state:
NOT_RUNNING PID:
- last message: UDP socket is already in
use. exit status:
exit(1)
Regards! Hany
Abadir
|