Conference smurf::buildhelp

1964.0. "ODE commands taking too long (forever?)" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Tue Nov 28 1995 12:08

Date Of Receipt: 	28-NOV-1995 08:10:53.57
From: 	SMURF::QUARRY::lueck "Greg Lueck Development Environment  28-Nov-1995 0808"
To: 	odehelp@DEC:.zko.quarry
CC: 	lueck@DEC:.zko.quarry
Subj: 	ODE commands taking too long (forever?)

I'm noticing that some ODE commands are taking a very long time to
complete this morning.  This bcs command, for instance, has been hung
for several minutes now:

gurgi 5% bcs -o -u -debug command.h
>> DEBUG INFO in current_sb:
>> Found sb name in environment.  Name is: atombox2.
>> DEBUG INFO in current_sb:
>> sb name is in rc file.  Name is: atombox2.
>> DEBUG INFO in current_sb:
>> Found base dir in rcfile. Dir is: /home/lueck/sandboxes.
>> DEBUG INFO in current_sb:
>> Using default sandbox rc file: /home/lueck/sandboxes/atombox2/rc_files/local.
>> DEBUG INFO in current_sb:
>> sb name is in rc file.  Name is: atombox2.
>> DEBUG INFO in current_sb:
>> Found base dir in rcfile. Dir is: /home/lueck/sandboxes.
>> DEBUG INFO in current_sb:
>> Using default sandbox rc file: /home/lueck/sandboxes/atombox2/rc_files/local.
>> DEBUG INFO in current_set:
>> found default set, Greg_Lueck_atombox2, in sb rcfile.
>> DEBUG INFO in current_sb:
>> sb name is in rc file.  Name is: atombox2.
>> DEBUG INFO in current_sb:
>> Found base dir in rcfile. Dir is: /home/lueck/sandboxes.
>> DEBUG INFO in current_sb:
>> Using default sandbox rc file: /home/lueck/sandboxes/atombox2/rc_files/local.
>> DEBUG INFO in current_set:
>> matched set, Greg_Lueck_atombox2, and setdir, ., in sb rcfile.
[ SET: Greg_Lueck_atombox2 ]
Waiting for sandbox lock (with lockf())


It took between 30 seconds and 1 minute before any of the debug info
was printed.  Now, it's been waiting on the "sandbox lock" for several
minutes.  Other commands, like "bdiff" seem to be taking longer than usual
too.

I tried exitting an re-entering my workon, but that didn't help.  Is there
something that I can do to fix this?  Is there a problem with some ODE server?

-- Greg