Kb207
Emulab FAQ: Testbed Operations: How do I deal with an experiment left in the "swapping" state?
Emulab FAQ: Testbed Operations: How do I deal with an experiment left in the "swapping" state?
> the one experiment I created after munging the database, > which did get swapped in, but got caught when boss hung, > was left in the "swapping" state
Things are setup so that after editing the following DB state, you can then rerun the swapout:
update experiments set expt_locked=NULL, state='active', canceled=0 where pid='PID' and eid='EID';
Change PID and EID of course. Then do a swapout again ...