Bug #449
closedupdateAppionDB does not always work
0%
Description
found when checking emanjobgen.php. The database does not always get updated if you kill a job. There a script called updateAppionDB.py, which is run at the end of each job file, which sets the database to "D" for "done," "R," for "running," etc. If the job is killed from the terminal, for example, the database does not get updated.
Updated by Neil Voss about 14 years ago
- Status changed from New to Assigned
- Target version set to Appion/Leginon 2.0.0
The user should kill the job from the webpage. I am willing to put this bug in the won't fix category.
Updated by Amber Herold about 14 years ago
- Target version changed from Appion/Leginon 2.0.0 to Appion/Leginon 2.0.1
Updated by Neil Voss about 14 years ago
- Status changed from Assigned to In Test
- Assignee changed from Eric Hou to Dmitry Lyumkis
usr_object does not have permission to update the database change ALL your sinedon.cfg (home, guppy, garibaldi) to use ami_object
Updated by Amber Herold almost 14 years ago
- Target version deleted (
Appion/Leginon 2.0.1) - Affected Version set to Appion/Leginon 2.0.1
Updated by Dmitry Lyumkis almost 14 years ago
- Status changed from In Test to Merge
- Assignee changed from Dmitry Lyumkis to Amber Herold
i guess jobs should be killed from the webpage, and if the user wants to manually go in and kill it from the terminal, then that person is responsible for running their own updateAppionDB.py script to update the database. I put this into the Appion documentation (http://emg.nysbc.org/projects/appion/wiki/Common_Workflow).