Hi Nate,
I'm running
changeset: 12641:cab3db6e1d59
and I can see the same behaviour. The blast job is not listed under jobs
in the admin section and I can't kill it, also not via deleting the dataset.
Anything I can do to track that down?
In my case it's a large blast job with splitting
Hi Björn,
Does stopping other, non-split jobs work correctly for you?
--nate
On Wed, Feb 26, 2014 at 7:30 AM, Björn Grüning bjoern.gruen...@gmail.comwrote:
Hi Nate,
I'm running
changeset: 12641:cab3db6e1d59
and I can see the same behaviour. The blast job is not listed under jobs
in
Hi all,
There was a regression introduced in the most recent stable release that
was preventing jobs from being stopped, fixed here:
https://bitbucket.org/galaxy/galaxy-central/commits/1298d3f6aca59825d0eb3d32afd5686c4b1b9294?at=stable
You can pull from the stable branch of galaxy-central to
Hi,
I have one running at the moment, that job is also not listed in the
jobs monitor under the admin-panel.
Cheers,
Bjoern
On Tue, Feb 18, 2014 at 2:20 PM, Federico Zambelli
federico.zambe...@unimi.it wrote:
Hi,
something strange happens with Cufflinks in our Galaxy server. When a user
Hi,
I can also see that behaviour under SGE long running jobs, like blast+.
Screenshot attached.
Cheers,
Bjoern
On Tue, Feb 18, 2014 at 2:20 PM, Federico Zambelli
federico.zambe...@unimi.it wrote:
Hi,
something strange happens with Cufflinks in our Galaxy server. When a user
deletes a
Hi,
something strange happens with Cufflinks in our Galaxy server. When a
user deletes a running Cufflinks job in fact the associated Cufflinks
process(es) are not terminated. Apart from unneccessary CPU usage, this
prevents other jobs from starting if the max jobs limit has been already
On Tue, Feb 18, 2014 at 2:20 PM, Federico Zambelli
federico.zambe...@unimi.it wrote:
Hi,
something strange happens with Cufflinks in our Galaxy server. When a user
deletes a running Cufflinks job in fact the associated Cufflinks process(es)
are not terminated. Apart from unneccessary CPU
Hi Peter,
it runs on a single server since this Galaxy instance is for internal
use of our lab only.
Aborting other long running tools like tophat and bowtie works just as
expected. I have also noticed that at least a couple of times not only
the cufflinks process(es) were not terminated
