# Killing jobs or dead processes after a database crash on galaxy

**URL:** <https://help.galaxyproject.org/t/killing-jobs-or-dead-processes-after-a-database-crash-on-galaxy/1360>\
**Category:** Uncategorized\
**Tags:** devops-administration, galaxy-local, devops-gxadmin\
**Created:** [May 22, 2019, 8:44pm UTC](https://help.galaxyproject.org/t/killing-jobs-or-dead-processes-after-a-database-crash-on-galaxy/1360 "2019-05-22T20:44:42Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Slugger70](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/slugger70/32/58_2.png) [@Slugger70](https://help.galaxyproject.org/u/Slugger70)\
**Post date:** [May 22, 2019, 10:16pm UTC](https://help.galaxyproject.org/t/killing-jobs-or-dead-processes-after-a-database-crash-on-galaxy/1360/3 "2019-05-22T22:16:09Z")

</div>

Hi @glam02,

There is a really neat Galaxy Admin utility called **gxadmin** which can help you out. It contains a bunch of querys and scripts that can look at jobs, fail jobs manually etc.

You can get it from: [https://github.com/usegalaxy-eu/gxadmin](https://github.com/usegalaxy-eu/gxadmin)

The particular query you want to run is: `gxadmin mutate fail-job <job_id>` where `<job_id>` is the job number of the stalled jobs in your database.

There is a little bit of setup required, mostly so that gxadmin knows how to talk to your database.

I hope this helps.

Simon.

---

_[View the full topic](https://help.galaxyproject.org/t/killing-jobs-or-dead-processes-after-a-database-crash-on-galaxy/1360)._