Douglas, by any chance have you noticed events which read something like
"netmon-related application reached maximum number of outstanding
events, disconnecting from trapd"? If so, it may be that ovactiond is
simply not able to keep up with the volume of traps being received. It
might help to configure ovactiond to wait 0 seconds for command
completion or there may be some other configuration changes which would
help if this is the case.
Blaine Owens
bowens@eastman.com
> -----Original Message-----
> From: Douglas Staub [SMTP:Douglas_Staub@keybank.com]
> Sent: Tuesday, September 08, 1998 8:12 AM
> To: NV-L@UCSBVM.ucsb.edu
> Subject: ovactiond and trapd losing contact
>
> Hi all:
>
> I have been experiencing consistent problems with the ovactiond daemon
> losing contact with the trapd daemon. Has anyone experienced the same
> problem? We are using NetView 4.1 on AIX 4.2.1 and will be upgrading
> to
> 5.1 by end of year. We also rely on the rulesets for processing many
> events. Here is the output from doing an ovstatus for ovactiond:
>
> object manager name: ovactiond
> behavior: OVs_WELL_BEHAVED
> state: NOT_RUNNING
> PID: 541382
> last message: ovactiond lost contact with trapd.
> exit status: exit(1)
>
> /usr/OV/bin/ovstart fixes it, but not permanently. Any ideas??
>
> Any help would be greatly appreciated. Thanks in advance!
>
> Sincerely,
> Doug Staub
> Key Services Corporation
> (216) 689-0632
|