(Illustration by Gaich Muramatsu)
On Thu, Mar 08, 2001 at 12:28:20PM +0000, Froody Dude wrote: > I recieved a whole load of messages in the logs and have searched for > references but have not been able to resolv the problem. > > Errors in log on SCM > > 11:50:16 ViceResolve:Couldnt lock volume 7f000005 at all accessible > servers > 11:51:39 CheckRetCodes: server nonscm-ip-address returned error 22 > > Errors in log on NONSCM > > 12:00:48 GetVolObj: VGetVolume(7f000005) error 103 > 12:00:48 GrabFsObj, GetVolObj error Volume not online > 12:00:48 RS_LockAndFetch: Couldnt translate Vid for (0x7f000005.0x1.0x1) It looks like NONSCM doesn't know that it is hosting that volume. Check whether the /vice/db/VRDB and VLDB files have been correctly propagated by the updateclnt/updatesrv daemons, i.e. timestamps, size and md5 checksums should be identical. If not, restart the update daemons on both SCM and NONSCM servers, /etc/rc.d/init.d/update.init restart JanReceived on 2001-03-08 13:21:59