Question: Jobs ending with error "Unable to finish job" having details "TypeError: object of type 'NoneType' has no len()" -- RESOLVED, please rerun
gravatar for francesca.cortini
9 weeks ago by
francesca.cortini10 wrote:


I have problems with Map with BWA-MEM tool, I launch my Galaxy workflow but, two days ago it doesn't work at Map-BWA MEM step

error bwa bwa-mem galaxy • 377 views
ADD COMMENTlink modified 9 weeks ago by Jennifer Hillman Jackson25k • written 9 weeks ago by francesca.cortini10

Update 9-25-2018 10:30am EST

I found your bug report. This is a temporary cluster issue that we are working to resolve.

The current workaround is to directly set the cluster where the job is executed to be the Galaxy Cluster using the Job Resources Parameter near the end of the tool form. FAQ:

For anyone else running into this problem, the error reported is in web interface will be:

Unable to finish job

With the full error Job Traceback reporting:

Traceback (most recent call last):
  File "/cvmfs/", line 514, in finish_job
  File "/cvmfs/", line 1445, in finish
    job.set_streams(job.stdout, job.stderr)
  File "/cvmfs/", line 227, in set_streams
    if (len(stdout) > galaxy.util.DATABASE_MAX_STRING_SIZE):
TypeError: object of type 'NoneType' has no len()

Thanks for reporting the problem and we will close out this post once resolved.

Jen, Galaxy team

ADD REPLYlink modified 9 weeks ago • written 9 weeks ago by Jennifer Hillman Jackson25k
gravatar for Jennifer Hillman Jackson
9 weeks ago by
United States
Jennifer Hillman Jackson25k wrote:

Update 9-25-2018 4pm EST

This issue is now fixed.

These jobs can be run without setting the Job Resources parameter (Galaxy chooses the cluster with available resources) or you can target one of the other clusters. Each cluster has a different profile (memory/walltime) -- Details:

Avoid the development clusters or errors may come up unexpectedly. We really do use these for testing and no bug reports need to be sent in for odd job results when using them.

Note: There was another issue that triggered certain jobs to fail for not finding built-in indexes. This was also corrected and the specific error message can vary by tool. And there is one more issue that related to data input types that has been fixed but not applied to the server yet. This error message can also vary by the tool and does not impact all runs -- so try rerunning a few times to achieve a successful result (FastQC was one of the impacted tools).

Main point: If you had any odd job failures over the last few days, please rerun now. If the job fails, it can be sent in as a bug report or you can double check your inputs using the FAQ help here first:

Thanks to all for reporting the problems and for your patience while we corrected the problem.

Jen & the Galaxy team

ADD COMMENTlink written 9 weeks ago by Jennifer Hillman Jackson25k
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 172 users visited in the last hour