Unknown errors in logs
I was viewing my logs randomly and I noticed some strange errors that don't relate much to anything my bot does. Are these errors from railway and should I be worried?
13 Replies
Project ID:
N/AN/A
Wait why did I say N/A
4d567c55-5247-4e54-8899-ae3cd121045f
Crap
Here's a screenshot:
theses are from your app, railway itself does not log anything in the deployment logs
I see. I've never seen errors like these before so it's incredibly strange to me. From what I can see the process ran out of memory. I'll investigate more to make sure it isn't a memory leak
you can always check the metrics tab of the service
Right, I did.
Out of nowhere the memory just blasted to 5 gb. I checked the debug logs my bot has and for whatever reason an evaluation occurred that was evaluating something as stressful as
for (;;) {}. This wasn't done through a command because there are no logs of eval being ran.
Overall an extremely weird situation but I'll enable further debugging and possibly find out the issue. What makes it weirder is the fact that the bot hadn't received any commands for 10 minutes before this happened and logged to never receive any even after the jump
Thanks for the help anywaythat is indeed very weird
The good thing is that it lasted for about a minute and no more. It would've been bad if it lasted more because it would've increased my monthly cost by quite a bit, Not to mention that I wouldn't have known anything had I not checked the console
you can always set a spend limit
I did that the second I signed up for the platform, no worries
I figured out what the issue was. My own system to prevent failures backfired on me. I tried to evaluate something about 7 days prior and it failed bc I pushed a change to GitHub which made the bot auto deploy. The failure was stored in the db and the bot executed it itself after the check I do every 7 days for failed commands, causing the load to spike up because it was a really stressful evaluation of the database... I should probably add an exception for commands like eval when it comes to failures :/
interesting
Not my wisest moment, It could've caused a lot of issues
It's meant to try and resolve issues with things like unbanning users once the duration expires (if it fails to initially) and some other infraction related things
Anyway, u can close this post now, it's all good