You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: