Conference smurf::buildhelp

2054.0. "ODE problem with guru mount on host alpha" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Tue Jan 16 1996 22:37

Date Of Receipt: 	16-JAN-1996 18:04:40.95
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  16-Jan-1996 1802"
To: 	aardvark@coltrane.wdec.locus.com
CC: 	strasen@DEC:.zko.flume, odehelp@DEC:.zko.flume, unifix::cchapman
Subj: 	ODE problem with guru mount on host alpha

Warren,

I have talked with guru's sysadmin, Kurt Strasen (cc'd) and he has told
me they have been having nfs locking problems on guru for several days
now, observed within dxmail.

Kurt has been working to try to resolve the problem, but he has not yet
done so; he's involved the support organization and has filed a QAR;
he's about to reboot guru now to see if that helps to reset things.

This problem would definitely cause the kind of behavior you're seeing,
as ODE requires nfs locking to be working on both the client and the
server if your sandbox is mounted via nfs.

My home directory is on flume, and by logging in to guru with my home
directory and a test sandbox nfs mounted there, I was able to exactly
reproduce the problems you've reported, using your nfs-mounted
directory from guru on alpha.  (When I use my home directory from flume
on alpha it works just fine, as locking is working fine on alpha and flume.)

If you do all your work locally on guru, then the locking is no longer
required.  Is there any reason you need to do your workon on alpha?
You should be able to complete all your work using host 'guru'.  At
least you can bco/bci/bsubmit from there; if you require additional
services on alpha for building or testing you can rlogin there for
those services, but I would like to know if there's a reason you can't
do everything locally on guru.

The lock that ODE takes out is on the file <sandbox>/src/.BCSlock - 
when you retry this from guru, you may get the following error:
>       Waiting for sandbox lock (with lockf())
If you do, all you need to do is to remove the .BCSlock file and 
then new locks will be taken out on a new .BCSlock file that ODE will
create.  (When Kurt reboots guru this lock will probably be cleared so
it may not be an issue, but it may be useful another time.)

I've copied Carole Chapman since she contacted me to find out the
status on this.

I believe that you should be all set if you can do all your work
locally on host guru.

-josh



------- Forwarded Message

Date: Mon, 15 Jan 1996 11:47:09 -0800
From: aardvark@coltrane.wdec.locus.com (Warren Usui)
To: jmf@locusfilter.zk3.dec.com
Subject: Re:  Information about the ODE problem.

> 	Please send the results of the bco command using these switches:
	
> % bco -verbose -debug -odedebug csv find.c

>> DEBUG INFO in current_sb:
>> Found sb name in environment.  Name is: find32c.
>> DEBUG INFO in current_sb:
>> sb name is in rc file.  Name is: find32c.
>> DEBUG INFO in current_sb:
>> Found base dir in rcfile. Dir is: /home/usui/sb.
>> DEBUG INFO in current_sb:
>> Using default sandbox rc file: /home/usui/sb/find32c/rc_files/local.
>> DEBUG INFO in current_sb:
>> sb name is in rc file.  Name is: find32c.
>> DEBUG INFO in current_sb:
>> Found base dir in rcfile. Dir is: /home/usui/sb.
>> DEBUG INFO in current_sb:
>> Using default sandbox rc file: /home/usui/sb/find32c/rc_files/local.
>> DEBUG INFO in current_set:
>> found default set, Warren_Usui_find32c, in sb rcfile.
>> DEBUG INFO in current_sb:
>> sb name is in rc file.  Name is: find32c.
>> DEBUG INFO in current_sb:
>> Found base dir in rcfile. Dir is: /home/usui/sb.
>> DEBUG INFO in current_sb:
>> Using default sandbox rc file: /home/usui/sb/find32c/rc_files/local.
>> DEBUG INFO in current_set:
>> matched set, Warren_Usui_find32c, and setdir, ., in sb rcfile.
[ SET: Warren_Usui_find32c ]

At this point it hangs forever. 
      


------- End of Forwarded Message