Job failure with “sqlite3.OperationalError: unable to open database file” on usegalaxy.org


1 Like

Hi @Pelumioladipo,

It looks like an issue with the ORG server. Thank you for reporting it.

Hi @jennaj, hi @nekrut1,

It looks like a major issue on the ORG server. I cannot import a tiny file from Australia to the ORG: got the same error as the user.

Kind regards,
Igor

1 Like

Hi @nate,
It looks like the ORG server does not accept new files. Upload jobs fail. It looks like a major issue.
Kind regards,
Igor

1 Like

Hi @Pelumioladipo and @igor

Thanks for the report of the issue and for the ping! There was a short window yesterday at UseGalaxy.org that had issues (setting metadata, not getting the file itself) but things should have improved after and are Ok right now.

For any datasets still in that state, you can try using the pencil icon to re-detect the datatype. Or you can newly load the data again from the source, and delete/purge the red datasets.

Just as a note given some of the file types I see: When loading data, it is usually a good idea to allow Galaxy to “guess” the datatype instead of setting it directly yourself. This avoid issues with the file type formats and compression state conflicts. Fastq and bam data should always work well this way with the guess. If not, it means the data might have a problem before loading. → Getting Data into Galaxy

Please let me know if there are still issues! Thanks! :slight_smile: