Question: Orphan dataset after Exporting history to file
0
gravatar for e.rempel
21 months ago by
e.rempel • 30
Germany
e.rempel • 30 wrote:

Dear all,

we are running a local Galaxy (an older release) instance and encounter the following issue. After exporting history to file there is an "orphan" dataset left (in galaxy/database/files/...). It looks like it doesn`t belong to any history, thus the cleanup scripts cannot delete it. Of course, we can delete it manually via "rm", but it is usually not at all recommended.

Is there a recommended procedure to deal with it? I assume the most promising way would be to update our instance, but I would like to know whether someone already encountered this issue and solved it.

Best,

Eugen

history export • 498 views
ADD COMMENT • link • modified 20 months ago • written 21 months ago by e.rempel • 30
1
gravatar for e.rempel
20 months ago by
e.rempel • 30
Germany
e.rempel • 30 wrote:

There is a simple solution to this problem (pointed out by Bjoern Gruening, thanks!): pgcleanup.py - A script for cleaning up datasets in Galaxy efficiently, by bypassing the Galaxy model and operating directly on the database (https://github.com/galaxyproject/galaxy/blob/dev/scripts/cleanup_datasets/pgcleanup.py).

ADD COMMENT • link written 20 months ago by e.rempel • 30
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 176 users visited in the last hour