Skip to content
This repository has been archived by the owner on Jan 24, 2018. It is now read-only.

ga4gh-example-data/registry.db is malformed #1638

Open
zhangb1 opened this issue Sep 18, 2017 · 5 comments
Open

ga4gh-example-data/registry.db is malformed #1638

zhangb1 opened this issue Sep 18, 2017 · 5 comments

Comments

@zhangb1
Copy link

zhangb1 commented Sep 18, 2017

Hi ,

When I ran the the command ga4gh_server , it came out the error

Database file 'ga4gh-example-data/registry.db' is malformed.
@kozbo
Copy link
Contributor

kozbo commented Sep 18, 2017

I need more information to help you. Are you trying to run the demo?

That error generally means that the registry.db is out of sync with the version expected by the server. The usual process to fix this problem is to delete the db and build a new one.

@zhangb1
Copy link
Author

zhangb1 commented Sep 18, 2017

@kozbo Thank you for your replay.

Yes, I want to run the demo. but seems the example file registry.db for downloading is malformed.

Do you have the new example for the test run?

@rdeborja
Copy link

rdeborja commented Sep 25, 2017

@zhangb1 we ran into the same issue and rebuilt the database using the ga4gh_repo command (http://ga4gh-server.readthedocs.io/en/stable/datarepo.html).

@jonejkim
Copy link

jonejkim commented Oct 2, 2017

We have encountered the same malformed database problem few weeks ago, but we could no longer replicate that problem today when ga4gh-server is built and ran on from the dockerfile in this repository.

However it is still possible to replicate the problem if we were run the server based on instructions in http://ga4gh-server.readthedocs.io/en/latest/demo.html , and the example data linked (https://github.com/ga4gh/ga4gh-server/releases/download/data/ga4gh-example-data_4.6.tar) there.

@hannah413
Copy link

I am also getting this error while working through the demo.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants