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
Unfortunately sometimes it will hang in the resolver and I think block db thus blocking further invocations. For some reason it will also eat 100% of cpu and hang like that forever.
Maybe host stats should include ip address to avoid using resolver for above operations (in addition to fixing whatever causes it to hang) ?
The text was updated successfully, but these errors were encountered:
I was attempting to periodically unlock old blocks and restore locks on startup using following crontab entries:
Unfortunately sometimes it will hang in the resolver and I think block db thus blocking further invocations. For some reason it will also eat 100% of cpu and hang like that forever.
Maybe host stats should include ip address to avoid using resolver for above operations (in addition to fixing whatever causes it to hang) ?
The text was updated successfully, but these errors were encountered: