# instaGRAAL on usegalaxy.eu finishes as “ok” but all outputs are 0 bytes **URL:** \ **Category:** usegalaxy.eu support\ **Tags:** assembly, server-open-issue, tool-help, instagraal\ **Created:** [May 18, 2026, 1:29pm UTC](https://help.galaxyproject.org/t/instagraal-on-usegalaxy-eu-finishes-as-ok-but-all-outputs-are-0-bytes/17733 "2026-05-18T13:29:03Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![alma.wis](https://avatars.discourse-cdn.com/v4/letter/a/898d66/32.png) [@alma.wis](https://help.galaxyproject.org/u/alma.wis)\ **Post date:** [May 18, 2026, 1:29pm UTC](https://help.galaxyproject.org/t/instagraal-on-usegalaxy-eu-finishes-as-ok-but-all-outputs-are-0-bytes/17733/1 "2026-05-18T13:29:03Z")
Hi! I am reporting a likely problem with the `instaGRAAL` tool on [usegalaxy.eu](http://usegalaxy.eu). I ran `instaGRAAL (0.1.6+galaxy0)` with these inputs: - `abs_fragments_contacts_weighted.txt` - `fragments_list.txt` - `info_contigs.txt` - reference genome FASTA The job ran for about 33 hours and Galaxy marked it as **ok** , but all 3 output datasets are **0 bytes** : - Genome sequence - Fragment information - Curated sequences In the Job Information page I see: - **Tool Exit Code = 1** - **Job State = ok** - Job message: This same behaviour happened in two independent histories with different datasets, so it seems systematic and not input-specific. The output dataset peeks do not contain real FASTA/tabular results, and the datasets remain at 0 bytes even after refresh. Could you please check whether the Galaxy wrapper is masking a real failure or failing to collect the expected output files? Thank you. ---
**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\ **Post date:** [May 18, 2026, 1:33pm UTC](https://help.galaxyproject.org/t/instagraal-on-usegalaxy-eu-finishes-as-ok-but-all-outputs-are-0-bytes/17733/2 "2026-05-18T13:33:47Z")
Welcome @alma.wis Hopefully we can help! I’m running a simple test on the server right now. Meanwhile, have you checked the full job logs? This is where to look → [FAQ: Troubleshooting errors](https://training.galaxyproject.org/training-material/faqs/galaxy/analysis_troubleshooting.html). I would also suggest that you send in a bug report from each error job (one dataset from each). You can include a link to this topic in the comments. The administrators of server screen these messages. You can copy paste the logs back here if you would like to! More soon as I run my test! 🙂 ---
**Author:** ![wm75](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/wm75/32/56_2.png) [@wm75](https://help.galaxyproject.org/u/wm75)\ **Post date:** [May 21, 2026, 7:02am UTC](https://help.galaxyproject.org/t/instagraal-on-usegalaxy-eu-finishes-as-ok-but-all-outputs-are-0-bytes/17733/3 "2026-05-21T07:02:32Z")
@alma.wis we are aware of this issue with the tool and a few of us have tried to fix it. Not 100% sure what the latest state is, but obviously things are still not working as they should. I’m sorry, but I don’t have a better anwer for you at the moment than that this tool is currently unusable and that you may check back here in a few weeks to see if things have changed. I’ll post here when that’s the case. ---
**Author:** ![wm75](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/wm75/32/56_2.png) [@wm75](https://help.galaxyproject.org/u/wm75)\ **Post date:** [May 21, 2026, 7:05am UTC](https://help.galaxyproject.org/t/instagraal-on-usegalaxy-eu-finishes-as-ok-but-all-outputs-are-0-bytes/17733/4 "2026-05-21T07:05:09Z")
@jennaj marked this as solved to have it show up on the tool interface. ---
**Author:** ![alma.wis](https://avatars.discourse-cdn.com/v4/letter/a/898d66/32.png) [@alma.wis](https://help.galaxyproject.org/u/alma.wis)\ **Post date:** [May 25, 2026, 11:36am UTC](https://help.galaxyproject.org/t/instagraal-on-usegalaxy-eu-finishes-as-ok-but-all-outputs-are-0-bytes/17733/5 "2026-05-25T11:36:47Z")
Hello, I am trying to run instaGRAAL on Galaxy, but the job fails during the PyCUDA/NVCC compilation step. The error is: nvcc fatal : Value ‘sm\_89’ is not defined for option ‘gpu-architecture’ The input files seem to be processed correctly because the pyramid is built before the crash. The failure happens only when PyCUDA tries to compile CUDA kernels. This suggests that the GPU has compute capability sm\_89, but the installed CUDA/NVCC version does not support it. Could you please update CUDA/NVCC, or route the instaGRAAL job to a GPU architecture supported by the current CUDA version? Thank you. ---
**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\ **Post date:** [May 26, 2026, 6:00pm UTC](https://help.galaxyproject.org/t/instagraal-on-usegalaxy-eu-finishes-as-ok-but-all-outputs-are-0-bytes/17733/6 "2026-05-26T18:00:05Z")
> [@wm75](#): > > I’m sorry, but I don’t have a better anwer for you at the moment than that this tool is currently unusable and that you may check back here in a few weeks to see if things have changed. I’ll post here when that’s the case. Hi @alma.wis Thanks for sharing the extra details! The EU team will see your message. They are aware of the issue and will try to resolve it soon! We only marked this as “resolved” to help others that run into the same issue to find the current status. I’ll mark this for an update in a few weeks, and please feel free to write back for an update if you don’t hear from us after the first week in June.