Is vmd running in verbose mode? 
1. Check with ps -ef |grep vmd
If the vmd proccess is like vmd -v . If it is then goto step 2 else I'm
stumped...

2. In the /usr/openv/volmgr dir is there a debug log. I have seen that if
you start the vmd process in verbose mode with the the debug logs open
(check in Veritas Support for which these foldeers and logs are.) and then
delete them, when the day changes and on the attempt to create a new log,
the proccess cant find the directory it knew before. To solve this, stop
vmd, remove any verbose setting in vm.conf and restart Netbackup


JP



-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Li, Jackie
(Yanhui)
Sent: Wednesday, December 03, 2003 1:40 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] RE: vmd died everyday on linux around 00:00:00




I installed netbakcup 4.5 on Redhat Advanced server 2.1 and the vmd dies
everyday same time around 00:00:01 with following messages:

Dec  1 00:00:01 mar1 vmd[21376]: volume daemon terminating because it
received a signal (13) Dec  1 00:00:01 mar1 vmd[21376]: terminating - daemon
terminated (7)


Does anybody see this ?

Thanks
jackie

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu