Error in pod5 data file ('filename' attribute not found)

Hello all, I have just installed galaxy 24.1 in my local machine. Basic setup has been done (just setting up the admin user, download some tools) and some simple analysis can be successfully conducted.

However, when I tried to run Dorado, it immediately stopped with error. The error log showed:

“File /home/mk1b/galaxy/tool-data/sift_db.loc specified by the ‘filename’ attribute not found”

The file “sift_db.loc” does not exist but sift_db.loc.sample is there. Shall I just delete the “.sample” and save another file?

In addition, if I try to run some tools that require / can utilize GPU resources, shall I install CUDA container toolkits (for docker and/or other)?

Thank you for your time
Cheers
KC

Run run.sh stop to stop the Galaxy service.
In the Linux system, execute the command: cp sift_db.loc.sample sift_db.loc
Then, edit the sift_db.loc file with vim and modify or add the entries you need.
Finally, restart the Galaxy service by running run.sh start.

1 Like

Many thanks Naibin, what would be the file “sift_db.loc” for ? Indeed, I have no idea what it is and how to modify it. would it be related to specific file loading / reading ? thank you.

Hi @polyukc

The problem with the loc file is probably spurious. It is much more likely that something else with your installation is going wrong.

This is just the first hit I got with a search about prior Q&A we’ve had about this (and mercurial update isn’t necessarily your problem but maybe still useful?) → Not able to install tools via tool shed · Issue #9235 · galaxyproject/galaxy · GitHub

So, my questions to get oriented would be

  1. Your release of Galaxy is 24.1 Releases — Galaxy Project 24.1.0.dev0 documentation
  2. What is your OS?
  3. Are you following these installation instructions? Galaxy Server administration / Tutorial List
  4. Are you installing tools from the Main tool shed? As an example, this is the tool you mentioned, and it was just updated, so you’ll want to use the updated version Galaxy | Tool Shed
  5. What is reported in your server logs?
  6. Is there anything special about your server?

Let’s continue from there, thanks! :slight_smile:

(All that said, yes, the advice from @Naibin_Duan is usually the way to go with a “missing loc” file – but in this case, that particular loc probably isn’t important. What it is for is described inside the file itself in the commented lines at the top, same as most loc files unless the tool README reports otherwise)