georgelukas Posted April 24 Share Posted April 24 blocked again and blocked again and blocked again. Quote Link to comment Share on other sites More sharing options...
wolstech Posted April 24 Share Posted April 24 You didn't fix your load issue and got suspended yet again for it (previous suspensions on the 15th and 17th). It's unfair to the other 2000 users for your account to be slowing everything else down. We have a 3 strikes policy here for suspensions, and you just struck out. Your Plesk account cannot be unsuspended due to repeated failure to manage your load. You'll need to either buy a VPS (which will isolate your software on its own server so the load won't impact other users) or find a new host for this software. If you're interested in a VPS, you can purchase that here: https://heliohost.org/vps/ (it comes as an empty Linux box with root SSH access and you can install whatever you want provided it isn't illegal, including this telegram bot). Quote Link to comment Share on other sites More sharing options...
georgelukas Posted April 24 Author Share Posted April 24 I already did the reduction and modified the way of pulling the data into the database and I also made it so that it gets the data and does not need to load the server again.. I even set a timer to reduce orders, nothing more... Quote Link to comment Share on other sites More sharing options...
wolstech Posted April 24 Share Posted April 24 It clearly wasn't enough based on that chart above. Your app is still too heavy. In order for the software to not get you suspended, it can't use more than about ~50MB of RAM continuously, which is admittedly extremely difficult to achieve with a long running node process. (node-based websites and such are much easier to accomplish here because they can rely on Passenger to stop them when there's no traffic, but a telegram bot can't do this since it has to listen to its channel continuously). Most users here who are running these sorts of bots here have chosen alternatives like Python because it's more resource efficient and won't lead to suspensions like this. If you want, I'll unsuspend you one more time, but it comes on the condition that you either rebuild the bot in something else so it doesn't slow the server down, or that you use the account for something that is not related to said bot. A future suspension after that for node-related load would be a permanent ban from our service. Do you want me to do that? Quote Link to comment Share on other sites More sharing options...
georgelukas Posted April 25 Author Share Posted April 25 Do you have python support? because I couldn't do that Quote Link to comment Share on other sites More sharing options...
MoneyBroz Posted April 25 Share Posted April 25 3 hours ago, georgelukas said: Do you have python support? because I couldn't do that We support python 2.7, 3.6, and 3.10. there are several steps to take in order for python to work, you can find all of the details here: https://wiki.helionet.org/tutorials/python Quote Link to comment Share on other sites More sharing options...
georgelukas Posted April 25 Author Share Posted April 25 5 hours ago, MoneyBroz said: We support python 2.7, 3.6, and 3.10. there are several steps to take in order for python to work, you can find all of the details here: https://wiki.helionet.org/tutorials/python Can you unlock me to modify the code? Quote Link to comment Share on other sites More sharing options...
georgelukas Posted April 25 Author Share Posted April 25 16 hours ago, wolstech said: It clearly wasn't enough based on that chart above. Your app is still too heavy. In order for the software to not get you suspended, it can't use more than about ~50MB of RAM continuously, which is admittedly extremely difficult to achieve with a long running node process. (node-based websites and such are much easier to accomplish here because they can rely on Passenger to stop them when there's no traffic, but a telegram bot can't do this since it has to listen to its channel continuously). Most users here who are running these sorts of bots here have chosen alternatives like Python because it's more resource efficient and won't lead to suspensions like this. If you want, I'll unsuspend you one more time, but it comes on the condition that you either rebuild the bot in something else so it doesn't slow the server down, or that you use the account for something that is not related to said bot. A future suspension after that for node-related load would be a permanent ban from our service. Do you want me to do that? I redid all the code in Python and put limits so there wouldn't be any problems, can we release it to test again? Quote Link to comment Share on other sites More sharing options...
wolstech Posted April 25 Share Posted April 25 Node has been disabled and you've been unsuspended...again. It might take a few minutes to work. Please watch your load carefully at https://heliohost.org/dashboard/load when testing the python version of the bot. Quote Link to comment Share on other sites More sharing options...
georgelukas Posted April 25 Author Share Posted April 25 24 minutes ago, wolstech said: Node has been disabled and you've been unsuspended...again. It might take a few minutes to work. Please watch your load carefully at https://heliohost.org/dashboard/load when testing the python version of the bot. I did exactly as written in the tutorial and there is no cgi folder and after doing so I get the errorhttps://georgelukas.helioho.st/cgi-bin/tele.py Quote Link to comment Share on other sites More sharing options...
wolstech Posted April 25 Share Posted April 25 The shebang line was missing, line endings needed to be unix, and the permissions were wrong. The bot appears to be running now, but I suspect you may not have any way to stop it. You should set up a way to start and stop the process. I killed it for you. Our guide on Discord bots has an example in it of how to control long-running Python processes, the same methods should be applicable to any other long running Python scripts: https://wiki.helionet.org/tutorials/discord-bot Quote Link to comment Share on other sites More sharing options...
wolstech Posted April 26 Share Posted April 26 You're making progress. New code seems to be more efficient in that it isn't slamming the memory usage, but something happened to spike it. Do you know what might have happened around 0900 that caused the jump and pushed you over the limit? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.