-
Notifications
You must be signed in to change notification settings - Fork 23
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
[docker] client dies after a while #196
Comments
Then I do a docker-compose restart and
|
Looks like it’s an issue with the storage system. I’m guessing that the loop-hole I used was patched up. I’ll try to find a workaround. |
ooo storage to save state on slack itself? Can the bot send a message to itself and edit that message as needed? |
Lol this is exactly what it does: https://github.com/kesne/jeopardy-bot/blob/master/src/CleverPersistence.ts |
@fwenzel I updated some of the error handling and added logging around persistence. Can you try the latest code or container and see if it resolves the issue? I also just booted a long-running container to see if I can reproduce it. |
ah good call; I'll update the container (what's the docker-compose command for that 🤔) and see. It just died again, oddly, one of the people in the room says |
I'm not sure about the command, maybe re-pull the image or something? Compose might want you to run rebuild too. The image is a lot smaller now, as an added benefit. |
|
persistence and restore after restart seems to work mostly? |
Okay a little more info when this happens, the bot is not dead nor disconnected. In the channel, someone says "new game" and the logs show: but nothing further happens, no more logs and no output in the channel. The logs then continue periodically as expected:
|
Seems like the service dies on occasion and needs to be restarted.
The end of docker logs:
The text was updated successfully, but these errors were encountered: