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

Container seems to have stalled. How to restart? #12

Closed
istrau2 opened this issue Apr 7, 2017 · 2 comments
Closed

Container seems to have stalled. How to restart? #12

istrau2 opened this issue Apr 7, 2017 · 2 comments

Comments

@istrau2
Copy link

istrau2 commented Apr 7, 2017

I have a running container with CATCHUP_COMPLETE=true. It seems to have caught up to "2016-05-22 16:20:32" and then stopped. By stopped, I mean that I see no new db entries getting added (to the core db's ledgerheaders table and to horizon db's history_ledgers table). I do however see the process listed when I do docker ps.

I guess I have two questions:

  1. What might have caused this?
  2. What are my options? Should I restart the container (and if so how can I tell it to just pick up where it left off).

Thanks in advance.

@istrau2
Copy link
Author

istrau2 commented Apr 7, 2017

hmm I think I ran into this bug: coreos/bugs#254

Could I just reboot the machine and restart the docker container?

@bartekn
Copy link
Contributor

bartekn commented Apr 8, 2017

Could I just reboot the machine and restart the docker container?

Yes. However if you're running the image in non-persistent mode you'll need to catchup again.

@bartekn bartekn closed this as completed Apr 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants