# Munge Errors submitting job on SGE gridengine Galaxy 18.09

**URL:** <https://help.galaxyproject.org/t/munge-errors-submitting-job-on-sge-gridengine-galaxy-18-09/655>\
**Category:** Uncategorized\
**Tags:** devops-administration, cluster\
**Created:** [February 20, 2019, 4:41pm UTC](https://help.galaxyproject.org/t/munge-errors-submitting-job-on-sge-gridengine-galaxy-18-09/655 "2019-02-20T16:41:49Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![bring52405](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/bring52405/32/269_2.png) [@bring52405](https://help.galaxyproject.org/u/bring52405)\
**Post date:** [February 21, 2019, 2:07pm UTC](https://help.galaxyproject.org/t/munge-errors-submitting-job-on-sge-gridengine-galaxy-18-09/655/3 "2019-02-21T14:07:27Z")

</div>

I agree. I wrote a single thread and a thread-pool Python script outside of galaxy to test. I posted those results in [drmaa library threads and munge: Invalid Credential Format](https://help.galaxyproject.org/t/drmaa-library-threads-and-munge-invalid-credential-format/617) . Single-thread submission works.

My skill-set falls short on digging into the code and creating a wrapper to lock the submission on Galaxy. I thought about spinning up PULSAR and using that to submit the job to the SGE Cluster as a means to bypass the drmaa job runner. Could that act as a work-around?

---

_[View the full topic](https://help.galaxyproject.org/t/munge-errors-submitting-job-on-sge-gridengine-galaxy-18-09/655)._