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

Closing since this was being handled over in email support which is now working again. https://helionet.org/index/topic/67209-hh546672-is-there-an-alternate-way-to-pay-mortys-19-fee/

Our email support has been down since the 30th. If you haven't seen the news, our management/name servers (which host DNS alongside our account management system, forum, email support system, and our website) failed on April 30th. Long story short, one of the two suddenly skyrocketed in load and became inoperable, so we shut it down only for the other one to do the same hours later. With no prior history of this issue, it was kind of unexpected... The management infrastructure ran an old version of cPanel DNS-only under a well-past-EOL operating system. Those servers were that "we'll get to it later" project we all tend to have, and have been sitting ducks for quite a while now. Something finally shot the ducks. While we are working on recovery, we are still currently unable to process account moves, domains deletions, or email support requests. Your request has not been forgotten and will be processed when services are restored.

Missing DNS zone fixed. It may take a few minutes to be available everywhere.

An attempt to recreate the DNS zone failed. ERROR 3: Cody zone file is corrupt. Escalating. EDIT: Just realized I forgot the second : in the IPv6 for this one...probably the issue. Now how do I fix that?

Missing DNS zone fixed. It may take a few minutes before its available everywhere.

Missing DNS zone fixed. It may take a little while before everyone can reach the site again.

DNS for zone thedannified.helioho.st is not missing. We are currently unable to delete domains due to the recent DNS server failure. Work on restoring that functionality is ongoing.

Escalating to Krydos for reconsideration since you no longer live in Iran. It's possible that proof of non-Iranian residency may be required (e.g. German residency papers, non-Iranian passport, etc.) to be unsuspended.

Due to US Federal Regulations, HelioHost is unable to do business with users who reside in or are affiliated with the country of Iran.

Fixed missing DNS zone. It may take a few minutes to resolve and up to 4 hours for everyone to see it.

Fixed DNS zone. It may take a few minutes to start resolving, and up to 4 hours for everyone to be able to reach it.

You re suspended for excessive cpu load caused by overuse of scheduled tasks. I have disabled all scheduled tasks that run more frequently that once a day and unsuspended you. Please reduce the frequency on your scheduled tasks. Unsuspended. It can take up to two hours for your domains to function...

Missing DNS zone fixed. It may take a little while before the changes propagate.

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.