[Veritas-bu] ltid active, but vmoprcmd gives ltid not active URGENT
2005-07-26 04:41:30
Subject: |
[Veritas-bu] ltid active, but vmoprcmd gives ltid not active URGENT |
From: |
richard_hellier AT hotmail DOT com (Richard Hellier) |
Date: |
Tue, 26 Jul 2005 09:41:30 +0100 |
Michael,
A long shot perhaps but check for lock files left over from before
the reboot. The way it looks is as if ltid "partially" starts but cannot
continue until a lock file is removed (and so it doesn't "answer" to the
other N/B processes). Try using the "filemon" tool from www.sysinternals.com
to watch ltid opening/closing files.
I'm not familiar with the Windows version of N/B but on Unix you can
stop/start the ltid process at will (and so can give the extra "-v" argument
to make the logs more verbose).
Good Luck!
Richard.
-----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
ida3248b AT post.cybercity DOT dk
Sent: 26 July 2005 08:48
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] ltid active, but vmoprcmd gives ltid not active URGENT
Hello All
After a reboot of our windows 2003 Master/media I keep getting:
09:42:26.548 [3116.2960] <2> oprd: cannot get message queue, assume ltid not
active
in volmgr/debug/daemon log
In the taskmanager I can see a ltid.exe
Any ideas/suggestion will be greatly appreciated
Regards
Michael
--
Cybercity Webhosting (http://www.cybercity.dk)
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
|
|