Troubleshooting: qiime2 feature-classifier fit-classifier-naive-bayes

usegalaxy.eu support
, ,
2

Hello @ARW-UBT

You can always submit a bug report, and the server administrators do appreciate that! They review for server issues as the priority. If it is not clear that the error is technical, then it is unlikely that you’ll get a custom reply.

Instead, or in addition to, you can ask here and we’ll troubleshoot to get the error triaged to the right places. Knowing where in the chain the error is coming from can be quite complicated!

Your error appears to be from the job environment failing to build. The UseGalaxy.eu had a large update over the last several weeks specifically related to the protocol recipes for these job environments. Not the actual dependencies, more about how they are assembled at runtime. Capturing and reporting back what may still be unresolved is important and we can do that here! Example of similar tool error earlier today.

How you can help us to investigate:

  1. Share link to a small history with the error. If the inputs are intact, that helps! FAQ: Sharing your History
  2. Or, sometimes the job details page is enough. Make sure we can see the tool version, the paramaters used, expand inputs peek views, and all logs, including the command string and both stderr and stdout. FAQ: Troubleshooting errors

For this tool, the full tool name with the version is probably enough! I may be able to reproduce with the defaults and test data. My guess is that the Qimme2 docker itself is conflicting with some local settings on the server, or maybe the problem is happening for everyone due to a version update.

Does this look correct? I’ll start testing but please confirm.

  • qiime2 feature-classifier fit-classifier-naive-bayes Train the naive_bayes classifier (Galaxy Version 2026.1.0+q2galaxy.2026.1.0)

Then, if you want to explore a workaround, sometimes toggling into the prior tool version is enough (if this was due to an update). I haven’t tested this yet for this specific issue, and will, but you can also try since it might get you going sooner! Sometimes going back once is enough, sometimes more.

Thanks for reporting the issue and more soon! I’ll watch for your confirmation that I guessed the right tool/version combination. :slight_smile: