11 months ago by
United States
Hi,
Exceeding quota memory (data storage) and exceeding tool memory or exceeding quota again during job execution (data processing) are two distinct items with different solutions.
For the quota issues, you might have leftover data from a prior analysis or the calculation might be off. Double check the actual usage by reviewing active/delete data vs permanently deleted data. Resolve by purging unneeded data (if needed) then reset the quota usage calculation by logging out then in again. How to is explained in this set of FAQs: https://galaxyproject.org/support/#account
For the tool issues, this error indicates that the job is creating more data that puts your account quota again, or the job is too large to run at Galaxy Main with the given inputs and tool settings, or there is a problem with the inputs themselves (format or content problems) triggering a cluster error. Double check inputs first as this can often lead to tool errors (https://galaxyproject.org/support/#getting-inputs-right) and review the other troubleshooting help here (https://galaxyproject.org/support/tool-error). Often small fixes will result in a successful job.
Please be aware that RNA STAR is known to use more memory resources during job execution than HISAT2. When a job is simply too large for STAR (inputs/settings are ok, there is room in your account for the results to publish back into a history), we often suggest using HISAT instead. If still too large to execute with HISAT, the other options explained in the tool-error FAQ above can be considered.
Should you get stuck and want a second opinion, a bug report from an error job can be sent in when working at Galaxy Main https://usegalaxy.org. How to is also in the tool-error FAQ above.
Galaxy RNA-seq tutorials: https://galaxyproject.org/learn/
Hope that helps! Jen, Galaxy team
