Closed ihodes closed 7 years ago
It looks like a setup problem; like Ketrew cannot talk to Coclobas?
I don't think it's setup; it worked for a few days, then stopped working. Restarting the docker image/relaunching Ketrew et al got it working it.
On Sat, Jan 14, 2017 at 3:13 PM, Sebastien Mondet notifications@github.com wrote:
It looks like a setup problem; like Ketrew cannot talk to Coclobas?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/hammerlab/ketrew/issues/509#issuecomment-272649809, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKPe6km8eR9Sr9hlaS7_ottD88vUsscks5rSSxPgaJpZM4LjtBT .
Did you just restart or the Sqlite DBs got deleted?
it can also be the coclobas container running out disk space or alike.
Just a restart; I don't think I'm running out of disk space (unless Docker has a smaller pool?)
This could be a coclobas bug (but not Ketrew's; it just could not talk to coclobas and reported all the info it had, thanks Unix…); closing for now unless we have more data on how this can be reproduced.
What info would be helpful to gather next time this occurs?
@ihodes
http://<coclobas-host:port>/status
returns something (with curl
for example)
looking at the status, I get