Dear Peter,
up to our galaxy admin, we make use of the Data Manager, so this seems not to
be the issue here?:
[cid:image001.jpg@01D41868.AAB17910]
Mit freundlichen Grüßen
Matthias Enders
---
GERMAN SEED ALLIAN
Hi All - Just a quick ask - anyone have anything BAD to say about running
Galaxy on a CENTOS 7.4/Scientific Linux with AMD EPYC chipset?
Its a bit new ... but looks good on paper and we would like to grow the Galaxy
environment here.
Thanks
Gerhard
Stellenbosch IT
[http://cdn.sun.ac.za/1
Thanks for getting back to us - this was actually my guess from the
original email - that it was not a blastn error message, but a Galaxy
message before ever calling BLAST.
My guess is you are seeing this issue, or something like it, with
having to restart Galaxy to reload the *.loc files?
https:
Dear all,
finally a restart of the container solved the issue with the database/blast.
Regarding the problem with the command line:
For other tools, the command line showed up, but not for blastn, as the wrapper
encountered the error before creating the command line (this is my
interpretation).
There is a setting to enable showing the command line string
and full paths on disk via the "i" icon from a history entry, see
https://docs.galaxyproject.org/en/master/admin/options.html#expose-dataset-path
# This option allows users to see the full path of datasets via the
# "View Details" optio
Hi all,
I have a galaxy instance running 18.05 version. I recently installed
'suite_samtools_1_2' (revision: 5b673ccc8747). When I used 'Mpileup' tool, I
ran into the below error, and the jobs fail.
Error message from UI:
This job was killed when Galaxy was restarted. Please retry the job.
Hi Matthias
If for whatever reasons the "i" (view details) icon doesn't work for
you, you can use the Galaxy Report Webapp (for docker installations see:
https://github.com/bgruening/docker-galaxy-stable#Galaxy-Report-Webapp )
as an alternative.
You can find your (failed) job via "Jobs in e
