[Solved] Second unsuspension

[gantelya111]

im quite surprised and im looking for the reason why my site using so much memory while it node.js were disabled, when i checked how much memory used it was quite late to do something so can im please being unsuspended?

[gantelya111]

when i checked last time everything was ok, and memory usage was low

[KazVee]

Same as yesterday, your account was suspended for High Server Usage due to using 200.14 GB memory when the daily limit is 200 GB.

One account causing heavy load on the server impacts performance for the hundreds of other accounts on the same server. Since this is the 2nd suspension in 2 days and I don't see any changes to the load being used since the last time your account was unsuspended, I'll escalate this thread to the root admins.

In the meantime, please provide clear steps explaining what you will do to immediately reduce the load your account is causing, to help the root admins make a decision about an unsuspension. Many thanks.

[gantelya111]

first I'll wait a day to knock down the limit completely, then I've already updated the code to reduce the load and added debugs, so I'll check if it helped and if the load continues I'll just disable the site and move to another programming language to see if it helps. I apologize for causing so much troubles. The question is why my code continued to load the server with node.js disabled

[gantelya111]

or change the payment plan for a higher limit

Edited 13 hours ago by gantelya111

[y-river]

I was also surprised that my Node.js project also ran for a short period of time, but the memory was about to reach the upper limit, which forced me to terminate my project early. There was obviously a problem with the memory and CPU usage.

[KazVee]

8 minutes ago, y-river said:

I was also surprised that my Node.js project also ran for a short period of time, but the memory was about to reach the upper limit, which forced me to terminate my project early. There was obviously a problem with the memory and CPU usage.

Node is one of the top reasons for users to get their accounts suspended. Please check out our Node.js guidance page for ways to keep the load low. 
If you have a support request, please make sure you create a new thread for yourself and let us know what the issue is. All staff are volunteers who help in their free time and it can be confusing for us to troubleshoot issues for 2 different users in the same thread. 🙂

[KazVee]

4 hours ago, gantelya111 said:

first I'll wait a day to knock down the limit completely, then I've already updated the code to reduce the load and added debugs, so I'll check if it helped and if the load continues I'll just disable the site and move to another programming language to see if it helps. I apologize for causing so much troubles. The question is why my code continued to load the server with node.js disabled

We looked into this further and found that the command `npm run start` was run: 

| sum(mem) | sum(cpu) | process                                         |
+----------+----------+-------------------------------------------------+
|    24064 |     0.00 | /usr/bin/hostnamectl --transient                |
|  1602836 |     2.30 | Passenger NodeApp: /home/gantelya111.helioho.st |
| 36087868 |     0.90 | npm run start:bootstrap                         |
| 45013376 |     1.60 | node --max-old-space-size=460 bootstrap-node.js |
| 56514848 |     2.70 | npm run start                                   |
| 70923448 |     4.30 | node bootstrap-node.js                          |

The `npm run start` command is not part of the Node guidance page I'd sent you after the 1st unsuspension, so it may be that you did not read the guide. The Node.js Wiki page offers steps to ensure that your Node apps run on Passenger, which is a service on Plesk that helps to reduce Node's memory usage.

Running commands that never exit (like `npm run start`) use a LOT more memory. If you need to continue using this command, and so much memory, we'd recommend you upgrade your account to the Morty server. Please make sure to review the Moving Your Account page for more details on the process, and make sure to backup your account before any account move. Once you're ready to move your account, you can begin the automated process from the Dashboard page for account moves. 

In the meantime, your account has been unsuspended. If you decide to keep your account on the Tommy server, we would strongly recommend checking the Node guidance page linked above, and making sure your app uses Passenger.

Please fix the issue quickly since without any code changes, another suspension is likely. Please also be aware of the Three-Strike Policy section of our Suspension Policy.

[gantelya111]

Thanks