We've definitely seen this dispsub message pop up on Netview v5 machines
that are starting up oserv and some are sourcing the setup_env.sh but
none are starting the console. They're all installed with the nv
machine as the server and the machine itself the only managed node. We
did finally just move the dispsub registration file out of the
registration/C directory to stop it.
Cristina Zabeu wrote:
>
> Some more information about dispsub...
>
> This process is started as an OVw application - there is a registration
> file under /usr/OV/registration/C called "dispsub" that by default
> starts this application with OVw. You may disable it by taking away the
> "-Initial" flag from the line that defines the command to be executed.
> For example, make the line where the command is defined to look like:
>
> Action "start_dispsub" {
> Command -Shared "${dispsub:/usr/OV/bin/dispsub}";
> }
>
> It can be started through the "Administer->Start Application->dispsub"
> on the main menu bar.
>
> As far as what can be wrong with the function, as James already
> mentioned, somebody on TEC is trying to display the submap that has the
> node from where the event was originated. This specific error occurs
> when the ip address of the node does not locate the equivalent object on
> NetView or this same address corresponds to more than one object on
> NetView, or yet if there is a serious problem in your database where the
> ip address field can not be located.
>
> Hope this helps,
> Cristina Zabeu
> Tivoli Systems
|