Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mtbrowse.xml code is not working in Galaxy v20.01 #1

Closed
rakesh4osdd opened this issue Mar 4, 2020 · 2 comments
Closed

mtbrowse.xml code is not working in Galaxy v20.01 #1

rakesh4osdd opened this issue Mar 4, 2020 · 2 comments

Comments

@rakesh4osdd
Copy link
Owner

@rakesh4osdd rakesh4osdd commented Mar 4, 2020

The new Galaxy v20.01 is working fine with Get Data for UCSC Table browser (UCSC Main on Human: knownGene (chrM:235-16,571)).
But when I have migrated mtbrowse.xml tool from Galaxy v15.10 to Galaxy v20.01, then it is not working and showing the following the issue in Galaxy v20.01:-

At local instance link
http://172.16.1.44:8080/tool_runner/data_source_redirect?tool_id=mtbrowsedata

The error is
"The remote data source application may be off line, please try again later. Error: <urlopen error [Errno -2] Name or service not known>"

How can we resolve this issue?

@rakesh4osdd
Copy link
Owner Author

@rakesh4osdd rakesh4osdd commented Mar 20, 2020

Still error exists as given below while import data from mtbrowse webserver
http://ab-openlab.csir.res.in/cgi-bin/gb2/gbrowse/mitolink

"The remote data source application may be off line, please try again later. Error: [Errno 104] Connection reset by peer"

Loading

@rakesh4osdd
Copy link
Owner Author

@rakesh4osdd rakesh4osdd commented May 9, 2020

I found this code working when I used in online WAN IP address. Until the code run from LAN IP address, it does't work.

I don't know the exact reason for it but I think it is due the architecture of the communication channel between GBrowse and Galaxy which uses both online presence to work together.

Loading

@rakesh4osdd rakesh4osdd closed this May 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant