Hi all,

It would be best to consider history importing/exporting as an incomplete/beta 
feature. 

There are two specific enhancements needed: (a) corner cases and general error 
handling when importing/exporting histories are not currently supported, which 
is why some histories work fine and other fail silently and (b) the UI should 
be improved so that importing does not silently fail. 

If you want to look at the error(s) preventing import, you'll need to inspect 
the database using this SQL query on your Galaxy database:

select id, history_id, stderr, stdout from job where tool_id = 
'__IMPORT_HISTORY__';

the stderr column is most likely to have the issue. 

Feel free to create a Trello card for the two enhancements noted above or 
particular issues that you run into when importing/exporting. As always, bug 
fixes and/or enhancements via pull requests are most welcome.

Thanks,
J.

On Dec 18, 2013, at 9:30 AM, "Lukasse, Pieter" <pieter.luka...@wur.nl> wrote:

> Hi Jeremy, Anna,
>  
> I’m having a similar problem here as well. I would like to get a history from 
> one Galaxy server to another and I followed the export and import steps. I 
> even did a wget at the destination Galaxy server to check whether it could 
> download the tar.gz file and this worked. When using the web UI I also get 
> this message on my log showing it is actually doing something when I trigger 
> the import:
>  
>  
> 10.85.13.89 - - [18/Dec/2013:15:10:48 +0200] "POST /history/import_archive 
> HTTP/1.1" 200 - "http://dev1.ab.wurnet.nl:8088/history/import_archive"; 
> "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) 
> Chrome/31.0.1650.63 Safari/537.36"
> galaxy.jobs DEBUG 2013-12-18 15:10:48,391 (3201) Working directory for job 
> is: /home/lukas007/galaxy-dist/database/job_working_directory/003/3201
> galaxy.jobs.handler DEBUG 2013-12-18 15:10:48,404 (3201) Dispatching to local 
> runner
> galaxy.jobs DEBUG 2013-12-18 15:10:48,478 (3201) Persisting job destination 
> (destination id: local:///)
> galaxy.jobs.handler INFO 2013-12-18 15:10:48,514 (3201) Job dispatched
> galaxy.jobs.runners.local DEBUG 2013-12-18 15:10:48,742 (3201) executing: 
> export GALAXY_SLOTS="1"; python 
> /home/lukas007/galaxy-dist/lib/galaxy/tools/imp_exp/unpack_tar_gz_archive.pyhttp://galaxy.wur.nl/galaxy_production/history/export_archive?id=b1f249e032330dc4
>  /home/lukas007/galaxy-dist/database/tmp/tmpPGL6le --url
> galaxy.jobs DEBUG 2013-12-18 15:10:48,786 (3201) Persisting job destination 
> (destination id: local:///)
> galaxy.jobs.runners.local DEBUG 2013-12-18 15:10:48,875 execution finished: 
> export GALAXY_SLOTS="1"; python 
> /home/lukas007/galaxy-dist/lib/galaxy/tools/imp_exp/unpack_tar_gz_archive.pyhttp://galaxy.wur.nl/galaxy_production/history/export_archive?id=b1f249e032330dc4
>  /home/lukas007/galaxy-dist/database/tmp/tmpPGL6le --url
> galaxy.jobs DEBUG 2013-12-18 15:10:49,040 job 3201 ended
> galaxy.datatypes.metadata DEBUG 2013-12-18 15:10:49,040 Cleaning up external 
> metadata files
>  
>  
> However, nothing is visible in my histories list. What could be wrong? I also 
> don’t see any error messages in the log above.
>  
> Thanks and regards,
>  
>  
> Pieter.
>  
>  
> From: galaxy-dev-boun...@lists.bx.psu.edu 
> [mailto:galaxy-dev-boun...@lists.bx.psu.edu] On Behalf Of Jeremy Goecks
> Sent: dinsdag 11 juni 2013 19:06
> To: Edlund, Anna
> Cc: galaxy-...@bx.psu.edu; Nicola Segata
> Subject: Re: [galaxy-dev] problems with exporting or importing data
>  
> Anna,
>  
> Try following these steps:
>  
> (1) Make your history accessible (Share or Publish --> Make History 
> Accessible by Link).
> (2) Export your history again; make sure to wait until you can use the URL to 
> download a .gz file of your history.
> (3) Try importing it via URL to the Huttenhower Lab Galaxy.
>  
> Let us know if you have any problems.
>  
> Best,
> J.
>  
> On Jun 10, 2013, at 11:45 AM, Edlund, Anna wrote:
> 
> 
> Hi.
>  
> I have uploaded fasta files on the main galaxy server through my FileZilla 
> program.  In want to transfer them to the Galaxy at the Huttenhower Lab (see 
> http://huttenhower.org/galaxy/root) page and to do that  go to history list 
> when I am logged in at both locations and I select ‘Import a History from an 
> archive’.  I paste the url address from the main galaxy server (where my 
> archive is located) and select submit.  Then I waited for 2 days and nothing 
> was transferred?  I am clearly doing something wrong and would really like 
> you input asap.
>  
> Thank you very much!!
>  
> Best regards,
>  
> Anna Edlund
>  
> My user name is aedl...@jcvi.org
>  
>  
> ___________________________________________________________
> Please keep all replies on the list by using "reply all"
> in your mail client.  To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
>  http://lists.bx.psu.edu/
> 
> To search Galaxy mailing lists use the unified search at:
>  http://galaxyproject.org/search/mailinglists/
>  

___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/

Reply via email to