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

Consider regularly restarting main program via the supervisor #14

Closed
HouzuoGuo opened this issue Nov 23, 2017 · 1 comment
Closed

Consider regularly restarting main program via the supervisor #14

HouzuoGuo opened this issue Nov 23, 2017 · 1 comment
Assignees

Comments

@HouzuoGuo
Copy link
Owner

Due to rather hideous issues deep inside laitos or one of the popular cloud platforms, laitos DNS and sock daemon appears to grow "tired" after unpredictable amount of uptime, generally between 2-7 days.

Symptom being that both daemons begin to perform very slowly at around the same time, yet none of the daemon reports rate limit being exceeded. One very rare case even caused laitos to crash - and subsequently supervisor did its proper job to relaunch laitos. Unfortunately the program log was lost before it could be inspected.

So while this issue demands more investigation, implement a temporary measure in supervisor that relaunches laitos regularly, interval of which is defined by user in configuration.

@HouzuoGuo HouzuoGuo self-assigned this Nov 23, 2017
@HouzuoGuo
Copy link
Owner Author

well, this is a bad idea

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

No branches or pull requests

1 participant