Suspended:petersen

[cornelio]

I tried to fix the code but I still can't. Please remove the suspension so I can backup important files and reset the account. I believe that some bug in the Laravel Toolkit is causing the memory consumption. I will try the project without Node to avoid this.

domain: cpetersenjr.com

server: tommy

[KazVee]

The account was suspended a 2nd time very quickly after the 1st unsuspension so this support request is being escalated to our root admins for their review. 

[cornelio]

Thanks for letting me know. I'm waiting.
If possible, disable the Laravel Toolkit (laravel installation) and any active Node.js services. I'm sure the problem is related to this since it was the most recent modification I made.

[cornelio]

On 5/3/2025 at 3:21 PM, KazVee said:

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.

Reading the Moderator's response, I believe I made the same mistake related to npm start command.

[Krydos]

Like I said on the news post 6% of your memory usage came from Laravel, and 94% of your memory usage came from Node.js. Laravel had nothing to do with your suspension.

You were unsuspended at 2025-05-07 13:14:31, and warned not to cause high load. Instead of reading our warning you just started a bunch of Node.js commands running again at 2025-05-07 14:39:28, and quickly went to 210 GB memory usage.

You can be unsuspended this time tomorrow when your load is back to zero. Hopefully the 24 hours will give you time to read and understand that you share this server with 929 other users, and it's not fair for you to hog all the system resources, cause downtime for other users, and cause other user's websites to load slowly.