Comment by 😎 flipperzero
Re: "@flipperzero The hashnix.club misfin server is down, looks…"
@cipres do I add this under the [service.main] section, or under the others entitled [service.main.ratelimit.anonymous] or [service.main.ratelimit.verified]? In fact, until you had made mention, I hadn't ever noticed this file or that there were these other fields. Would any info within those fields help you better? This is what they print.
Let me know at your soonest convenience, thanks much and always.
Apr 30 · 7 days ago
12 Later Comments ↓
🚀 cipres [OP] · May 01 at 10:14:
@flipperzero Add them at the top of the config file (outside of the service section). Your rate limit config has the default values, that's fine then. Then you can restart the daemon and we should get more logs.
😎 flipperzero · May 02 at 01:15:
@cipres I sent you an email now, at your proton address, hopefully it shows it sent from my hashnix email host. Let me know if this helps, and if the message gets to you.
🚀 cipres [OP] · May 02 at 15:57:
@flipperzero I can't access the log file's URL you sent me (not found error).
😎 flipperzero · May 02 at 16:14:
apologies, there was a typo, try it now
🚀 cipres [OP] · May 02 at 16:51:
@flipperzero Got the log, very helpful. I'll fix what's generating these traceback errors but that's not what would cause a crash. Did a crash occur in the time window covered by this log (for any of those 5 srv restarts) ?
😎 flipperzero · May 02 at 16:56:
@cipres those restarts were when crashes occured or at least before hand of, and from up to that point after the end of April to May 1st there have been no restarts and still the misfin page stays stuck loading as these messages continue to occur.
🚀 cipres [OP] · May 02 at 17:37:
@flipperzero Enough memory and disk space available on your server ? This is really puzzling.
🚀 cipres [OP] · May 02 at 17:49:
@flipperzero I was able to reproduce the issue, will push a fix hopefully today, otherwise tomorrow. Thanks again !
😎 flipperzero · May 02 at 18:43:
@cipres 8gb RAM, 8 cores that max at 2.8 - 3ghz
** edit - apologies, just seen you found the fix. Can’t wait for the update!
🚀 cipres [OP] · May 02 at 19:32:
@flipperzero New release is out. It changes the default worker threads configuration. Not sure 100% this will fix it. Do an update and restart the service, and then i'll do a stress test on the server.
😎 flipperzero · May 02 at 19:44:
@cipres uppdated and running now
🚀 cipres [OP] · May 02 at 19:51:
@flipperzero Ok. The frontend seems to respond faster than before. Let's wait and see, there's a small chance that it's fixed now but i wouldn't bet too much on it.
Original Post
@flipperzero The hashnix.club misfin server is down, looks like it has been down for a couple of days.