Nice job of troubleshooting! Let's find out where the problem is. At
this point, it is generally quickest when I look at the actual data.
you working on the public Main instance at http://usegalaxy.org?
not, are you able to duplicate the issue there, using a small test set
of your data (please test, as this is also informative for
Once the error is on Main, either share a history link with me or
one of the failed runs as a bug report. In the email/bug report
comments, note the meablast error and your account email if different
from this email. I'll look at everything, but also want to focus on
most current troubleshooting run.
ex: #4 query .fasta + #5 custom .fasta => #7 megablast error
Datasets that are /_not permenently deleted_/ are best, as is
the complete analysis in the same history (e.g. original upload
any grooming or other manipulations, etc.). Sometimes there are
secondary issues (related or not) - I'll give feedback about those -
if there is a software or config problem, more info can only help.
Launch a re-run if you need to, for datasets key to the error that are
purged already, so I can see the exact UI parameters as displayed in
tool forms (to compare versus the command-lines executed). You don't
need to wait for these to complete before sharing.
How to share/submit bugs reports (just do one, your choice):
If the problem is not reproducible on Main, and you are using a local,
cloud, or other public Galaxy instance, write back on list, and we can
work from there.
I'll watch for your reply. Avoid posting share links to the public
or 'publishing' (just 'share'), to keep data private.
ps. Anyone else experience problems, the same guidelines apply. If
sharing a history, please start a galaxy-user thread first, then share
(this is when emailing team members direct with problems is best), it
help us with tracking. Bug reports from errors on Main can be sent in
directly from the history/dataset. I haven't posted the current
best-practice guidelines for error reporting yet this year to this
so took the opportunity to put this in our mail archives for
searches/reference. Please excuse the length.