Account suspended due to Load

[slashbit]

Hi , looks like my account was suspended. 

I am trying to understand what caused it, so I can take action.  I am not able to access https://heliohost.org/dashboard/storage/

Could you please help?

 

Thanks 

Edited Monday at 09:21 PM by slashbit

[wolstech]

It's because you're not suspended for storage. All suspensions except for storage overuse (which is self-correctable by buying space) will lock you out entirely because they require contacting support to resolve.

Your suspension is specifically for excessive CPU use due to running scheduled tasks too frequently. I've disabled all scheduled tasks that run more frequently than once a day, and unsuspended you. Please reduce the frequency and number of jobs on your account. If you need to be able to run jobs more frequently, we recommend moving to Morty (where you will be charged fees for the extra resources instead of being suspended).

Unsuspended. It may take up to 2 hours for your domains to work again.

[slashbit]

Thanks, I have enabled some scheduled tasks. I will monitor the Memory and CPU in the next a few days.
The tasks only run for a few seconds every 2 minutes. So far the resources use is not significant. But I will see what may consume more and if there spikes. Before I move to Morty, i would like to understand what might be causing it.
Thanks

[wolstech]

The code itself isn't the cause of your load, it's systemd. Whenever a process is running under a user account (CGI execution, scheduled tasks, sftp, etc.), systemd causes load for that account. That load counts even though the script itself uses next to nothing. The load from systemd is basically directly correlated to the amount of time you have processes running. The more stuff you run (or leave running), the higher it gets.

You can even get suspended for load by connecting to sftp and leaving the open connection idle.

Looking at what's running, the Python apps and the PHP called via scheduled tasks are likely what's causing systemd to be running for your account.

Your load by process:

14.71 GB	0		(sd-pam)
12.37 GB	5.45 k	/usr/lib/systemd/systemd --user
6.99 GB		34.7	/opt/plesk/php/5.6/bin/php -f httpdocs/airspace_around_me/web/api/ogn_bridge_control.php
5.46 GB		212		python3 -u ogn_bridge.py
4.73 GB		26		/opt/plesk/php/5.6/bin/php -f httpdocs/airspace_around_me/web/api/collector_control.php
3.07 GB		137.4	python3 -u collector_hosted.py
1.37 GB		41.5	/opt/plesk/php/8.3/bin/php-cgi -c /home/system/ogn.helioho.st/etc/php.ini
45.33 MB	0.4		/opt/plesk/php/8.5/bin/php -f httpdocs/airspace_around_me/web/api/notam_control.php
45.20 MB	0.2		/opt/plesk/php/8.4/bin/php -f httpdocs/ogn_tools/scheduled_daily_postprocessing.php
41.24 MB	2.1		python3 -u notam_collector.py
18.11 MB	0.3		python3 Scripts/puretrack_labelsConverter_json_to_db.py

 

[slashbit]

That's helpful, thanks. I identified some PHP task, that shouldn't be left running. They are run once per day in the morning like notam_control.php and notam_collector.py.
Perhaps not closed properly. I will correct that .

Thanks