Error showing things still building, but nothing running

[ihodes]

looking at the status, I get

non-fatal error "Client.IO: Unix.Unix_error(Unix.ECONNREFUSED, "connect", "")" (check-running)

[smondet]

It looks like a setup problem; like Ketrew cannot talk to Coclobas?

[ihodes]

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 ***@***.***> 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 <#509 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKPe6km8eR9Sr9hlaS7_ottD88vUsscks5rSSxPgaJpZM4LjtBT> .

[smondet]

Did you just restart or the Sqlite DBs got deleted?

it can also be the coclobas container running out disk space or alike.

[ihodes]

Just a restart; I don't think I'm running out of disk space (unless Docker has a smaller pool?)

[smondet]

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.

[ihodes]

What info would be helpful to gather next time this occurs?

[smondet]

@ihodes

• the Coclobas logs,
• the status of the container
• whether http://<coclobas-host:port>/status returns something (with curl for example)