Re: ovwdb daemon


Your subject says "ovwdb" but your posting makes no mention of it.

In your posting, all the daemons you mention require ovtopmd to be running as a
pre-cursor to themselves.  So what does ovstatus ovtopmd say was the last error
message from ovtopmd?  If it is an exit 255, then the problem is most likely
that the Tivoli environment is not being sourced before the daemons are being
started.  ovtopmd requires the Tivoli libraries in his path.

How is NetView started at reboot in your environment?


James Shanks
Tivoli (NetView for UNIX) L3 Support



Fabiana Schurhaus <fabiana AT TELESC.COM DOT BR> on 06/21/99 04:55:07 PM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
      <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  ovwdb daemon




Hi,
     when i reboot the netview machine ( netview 5.1.1 with TIPN installed, Sun
2.51)  some daemons don't start:

     - ovtopmd, netmon, ems_sieve_agent, ems_log_agent, nvcold, snmpCollect  are
with state:  UNSTARTABLE

     - netmon - state:  NOT_RUNNING and exit status  exited on signal 9

               I don't know what can happening, because if restart the database
the daemons start until reboot the machine.


  ____________________________________________
   Fabiana Schurhaus
   TELESC - Telecomunica

ções de Santa Catarina S/A
   Tele Centro Sul
   Florianópolis - SC < http://www.telesc.com.br >
   E-mail: fabiana AT telesc.com DOT br
   Voice : 55-48-231-2812       FAX : 55-48-231-2611
   ___________________________________________