New Topics

Server: Johnny (johnny.heliohost.org) Path: /devashraf/waken.helioho.st/jpnew/ Directory permissions are 775 recursively Error: Could not create directory: Received error SSH_FX_FAILURE with description 'Failure' Cannot mkdir or write files, even though 775 is set Request: Please check if ACLs are restricting write access, or if there's a chroot security policy blocking writes to this directory. Note: Even file manager uplaods failes with the error below: No upload response Some files were not uploaded due to an error. The remaining files will not be uploaded.

I plan to keep it around for a moment albeit not yet purchased (I registered that from NameCheap back when I had the free 1-year thing from my Github Student Pack). I only need the other disabled domains to be removed, for now. Thanks for asking, Krydos! It seems everything is already in place for my account now. Thanks for all the help I got from everyone! ☺️

Database: dipeshshrestha_lrmDatabase Username: dipeshshrestha_dipeshshrestha

This support request is being escalated to our root admins who can fix the DNS issue for you.

Thank you for your support. I understand—you have been so much help to me. I’m a PhD geophysics hobbyist, and I can’t blame the US. I’m very anti-Iran too, haha. Either way, God bless you guys, and thank you for your unwavering support. Maybe once I actually get out of this hellhole and immigrate for good, I’ll come back if you’ll have me. Thanks again,

DNS recreated.

It looks like you decided to upgrade your storage space, and your account is working again. Marking this one as solved. Let us know if you need help with anything else.

I've now removed the butangfindr domain from your account as requested.

As it's been over a week, I will go ahead and mark this request as [Solved] so it's clear to all unpaid volunteer staff which user requests are still pending. If you decide to proceed with the account reset, please let us know in a new support request thread that you want the addon domain to be your new main domain, and that you're ready for the required account reset to accomplish this. Thanks!

DNS recreated.

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/

root@control [~]# dig +short A @ns1.heliohost.org affittimastrogiuseppe.helioho.st 64.62.151.106 root@control [~]# dig +short A @ns2.heliohost.org affittimastrogiuseppe.helioho.st 64.62.151.106 root@control [~]# dig +short AAAA @ns1.heliohost.org affittimastrogiuseppe.helioho.st 2001:470:1:1ee::2009 root@control [~]# dig +short AAAA @ns2.heliohost.org affittimastrogiuseppe.helioho.st 2001:470:1:1ee::2009 Should be good to go now.

Thank you so much for the rapid assistance.

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

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

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...

DNS recreated.

DNS recreated.

DNS recreated.

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

First of all, sorry for the long downtime on our main website. Over the past few years our main database has just been getting slower and slower. It was last rebuilt in 2017 so it was well overdue for an upgrade. A few days ago the main database was so slow that we decided to take it offline, and rebuild it with a modern operating system and up-to-date software. We expected the downtime to last a few hours, but then during the upgrade everything fell apart. While Cody was down, his twin brother Brody got so sad he died too. This happens sometimes with twins because they can't live without each other, which is cute but also very tragic. So then, with both a dead Cody and a dead Brody, we had no nameservers, no main database, no website, no forum, no wiki, etc etc etc. But here at HelioHost we never give up. No matter how many servers explode, or how many evil for-profit corporations try to destroy us we will never give up. It took a few days, but our main website is back online, both of our nameservers are back online, our forum is working again, and a lot of the stuff going on behind the scenes are working again too. That said, there is still plenty of stuff that isn't working yet. The main issue seems to be that during the upgrade of the nameservers a lot of DNS zones got lost, so some websites are offline. If your domain gives a DNS error when you try to visit it in a browser let us know and we can take a look. It usually only takes a few seconds to recreate the DNS for you. We're still working on getting everything functional again, but we're making progress. Thanks for everyone's patience during this crazy rebuild.

Thank You!! Working again!