Tilo,
Try loading the daemon through command line without the ovstart (like
./nvlockd) just to see the error messages. May be there is a library
missing or something. In any case, you should have more information to
solve the problem.
HTH
Mario Behring
Tivoli Consultant
IBM Brazil
+55 11 8125-5598
+55 19 2104-3006
mariob@br.ibm.com
mariobehring@yahoo.com
--- tilo.strauch@rzleipzig.de wrote:
>
>
>
>
> Hi list,
>
> after update NV 7.1.3 to 7.1.4 all works fine. An ovstatus command shows
> that nvlockd and C5d are not running. I'd try to added those deamons
> whith
> ovaddobj but nothing helps.
>
>
> ovstart
> object manager name: nvlockd
> behavior: OVs_WELL_BEHAVED
> state: FAILED
> PID: 17802
> last message: Initialization failed
> exit status: -
>
> object manager name: nvlockd
> behavior: OVs_WELL_BEHAVED
> state: DONE
> PID: 17802
> last message: Initialization failed
> exit status: -
>
> object manager name: C5d
> behavior: OVs_WELL_BEHAVED
> state: NOT_RUNNING
> PID: 22962
> last message:
> exit status: exit(0)
>
> Regards
>
> Tilo Strauch
> ------------------------------------------------------------------------
> Netzwerkmanagement
> ------------------------------------------------------------------------
> Deutsche Rentenversicherung
> Rechenzentrum Leipzig e.V.
> Tel.: +49 0341 9170-220
> Fax: +49 0341 9110-806
> ------------------------------------------------------------------------
> mailto:tilo.strauch@rzleipzig.de
>
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
http://hotjobs.sweepstakes.yahoo.com/careermakeover
|