[phenixbb] Recovering Autobuild from tty disconnect
Thomas C. Terwilliger
terwilliger at lanl.gov
Fri Aug 26 16:55:06 PDT 2011
If you run from the GUI and choose to run "detached" I would think that
should do the job....(You may have to specify "edit parameters and run/
run detached to get this option).
For AutoBuild, no there is no way to restart the job. However you might
just look through the log file, pick out the best model so far, and
restart with that one.
All the best,
>> Our job submission node disconnects 'idle' after 4 hours of inactivity. As
>> most grid / autobuild jobs take about that long I end being disconnected
>> while the grid jobs complete.
>>  Screen is not an option since access to the job submission node is via
>> a load balancer and none of the job submission nodes allow access unless
>> you're coming from the load balancer . i.e. there's no way to get to
>> original machine where your screen has been started
>>  all processes are sent SIGKILL during this automatic logout preventing
>> the use of nohup.. will background=True work?
>>  In the meantime, is it possible to resurrect the current autobuild?
>> I've got FINISHED in all the autobuild's submitted to the grid, but
>> everytime I try to combine_only=True run=my_run_number, I start from the
>> beginning (with submitting the autobuild jobs to the cluster) even when
>> I've moved the best of each build into MULTIPLE_MODELS.
>> Francis E. Reyes M.Sc.
>> 215 UCB
>> University of Colorado at Boulder
>> phenixbb mailing list
>> phenixbb at phenix-online.org
More information about the phenixbb