wolstech

PHP 5.6 and newer are currently unavailable on Tommy due to technical issues with the server. Also, mail services are currently down on Tommy regardless of software version. PHP 5.4 and 5.5 are working properly. PHP 7.2: https://krydos.heliohost.org/72/phpinfo.php (broken, 500 error) PHP 7.1: https://krydos.heliohost.org/71/phpinfo.php (broken, 500 error) PHP 7.0: https://krydos.heliohost.org/70/phpinfo.php (broken, 500 error) PHP 5.6: https://krydos.heliohost.org/56/phpinfo.php (broken, 500 error) PHP 5.5: https://krydos.heliohost.org/55/phpinfo.php (working) PHP 5.4: https://krydos.heliohost.org/54/phpinfo.php (working)

There's 2 solutions for this. Change the name servers entire for a few minutes to add the domain as an addon, then change them back after adding it and create an A record. You might need to use a different registrar if your current one can't do this for some reason. Note your domain will stop working for the duration of the change and setup. Or, use domain.com as your main domain and set an A record pointed to us instead. Note that in either configuration, the DNS, mail, and subdomains functionality won't work unless you create all the required dns records manually every time you do something. It might be easier to transfer the domain and use us for the DNS, and add the google records manually instead.

Unblocked. It should be effective within 10 minutes.

That domain is working properly for me. Is it still not working for you? (Ricky has been experiencing severe load and a lot of downtime today, so you probably tried in the middle of such an event). http://heliohost.grd.net.pl/monitor/

It depends. If it was a case where something like WP got malware, we make them remove the infected software and reinstall it to clean it up. If it was intentional spam (usually more of a Johnny issue...), yeah, banned.

Waiting for “exim” to start ……Job for exim.service failed because a configured resource limit was exceeded. See "systemctl status exim.service" and "journalctl -xe" for details. …Waiting for exim to shutdown ... not running. Job for exim.service failed because a configured resource limit was exceeded. See "systemctl status exim.service" and "journalctl -xe" for details. …Job for exim.service failed because a configured resource limit was exceeded. See "systemctl status exim.service" and "journalctl -xe" for details. …Job for exim.service failed because a configured resource limit was exceeded. See "systemctl status exim.service" and "journalctl -xe" for details. …Job for exim.service failed because a configured resource limit was exceeded. See "systemctl status exim.service" and "journalctl -xe" for details. …failed. Cpanel::Exception::Services::StartError Service Error (XID ykg3fs) The “exim” service failed to start. Startup Log Mar 19 20:38:43 tommy.heliohost.org systemd[1]: Failed to fork: Cannot allocate memory Mar 19 20:38:43 tommy.heliohost.org systemd[1]: exim.service failed to run 'start' task: Cannot allocate memory Mar 19 20:38:43 tommy.heliohost.org systemd[1]: Failed to start Exim is a Mail Transport Agent, which is the program that moves mail from one machine to another.. Mar 19 20:38:43 tommy.heliohost.org systemd[1]: exim.service failed. Mar 19 20:38:43 tommy.heliohost.org systemd[1]: Starting Exim is a Mail Transport Agent, which is the program that moves mail from one machine to another.... Mar 19 20:38:59 tommy.heliohost.org systemd[1]: Failed to fork: Cannot allocate memory Mar 19 20:38:59 tommy.heliohost.org systemd[1]: exim.service failed to run 'start' task: Cannot allocate memory Mar 19 20:38:59 tommy.heliohost.org systemd[1]: Failed to start Exim is a Mail Transport Agent, which is the program that moves mail from one machine to another.. Mar 19 20:38:59 tommy.heliohost.org systemd[1]: exim.service failed. Mar 19 20:38:59 tommy.heliohost.org systemd[1]: Starting Exim is a Mail Transport Agent, which is the program that moves mail from one machine to another.... exim has failed. Contact your system administrator if the service does not automagically recover. Swap's full. Odd it can't allocate memory though, there's only 70% usage on the actual RAM...

There is not. It's intentionally disabled due to a history of abuse (botnets and pirated/nulled software). Your only option would be to buy a VPS, where you can install anything you want: https://www.heliohost.org/vps/

It's probably a few things actually. Time of day is a big factor (the worst time for our servers is around 8PM EDT because we accept our day's worth of new account registrations during that time). I also banned a few accounts on johnny this morning that were probably contributing to load (they were running a spambot, those are notorious for causing load, ignoring the fact that sending spam is itself abuse).

675MB free as of this writing...http://heliohost.grd.net.pl/disk-space/

Unblocked.

This should be resolved for the time being. For the interested, the issue is the /var line under Tommy here: http://heliohost.grd.net.pl/disk-space/ When it hits 0, the server goes down because a lot of stuff doesn't like running out of space (PHP especially, can't save session data).

Done. Your account is now on Tommy. Thank you for the donation. If you see a queued page or 404 error, please clear your browser cache and flush your DNS resolver cache.

The username is actually naser01. Unarchiving...

Moving...

From what I can tell, your WordPress installation is either misconfigured, broken, or too bloated with extensions. The domain and server are working properly as evidenced by the phpinfo file I created: http://shgmta.ml/test.php For what it's worth, we highly recommend not using WP because it's poorly coded and laughably insecure. I'll let Krydos take a look at this and see what he thinks.

500 errors are not generally caused by these settings. The most common problem is file permissions needing to be changed. Start by verifying that all of your files are set to 644, and rename your .htaccess file to something else so it's ignored. Code errors can also cause this, but only if errors are turned off.

We don't allow users to change any of those settings to prevent abuse of resources. Krydos would have to change these for you. What PHP version needs the memory limit raised to 64M? Why? What PHP version needs the file upload limit raised to 128M? Why can't these files be uploaded via FTP instead? Also, we cap the timeouts at 30 seconds to prevent people from causing high load. It might be possible to have it raised to say, 60 seconds, but I can say for certain we would never raise it to 5 minutes. Honestly, if a script needs more than 30 seconds to produce a result, you should be rewriting or finding another script. If you really need the execution time limits, you would likely need to buy a VPS instead: https://heliohost.org/vps/ With a VPS, you have root access and can set whatever limits you please.

It's because the server is down because /var ran out of disk space. https://www.helionet.org/index/topic/34926-tommy-var-full/

Ironically, WP was actually the direct cause of at least one if not more than one of the /var issues. The downtime was basically a result of WP getting infected and sending spam (email lives on /var when it's waiting to be sent...in that case, the spam never sent because it was spam, so it sat and clogged up the space). We recommend not using WP if at all possible for this and many other reasons...

We'll move this for you as soon as we can I can't do it at the moment because we're working on getting a disk space issue fixed.

We're aware. The server is down because the disk is full. https://www.helionet.org/index/topic/34926-tommy-var-full/

Lets have Krydos look at this, but honestly, 200MB is ridiculously high...I don't think that's going to be approved. I'd suggest just uploading it via FTP instead.

Sure. We'll move you as soon as Tommy is fixed. He's currently down due to the disk being full. Please be aware also that since you have Java, you'll have to request it and wait again after the move. Moving servers unfortunately doesn't move your Java slot.

The server is currently down. See https://www.helionet.org/index/topic/34926-tommy-var-full/

That last few cases of this were caused by abuse, specifically infected Wordpress installations generating thousands of spam emails. Even though our system prevents them from sending, they still waste space... We ought to just make it larger though in my opinion. Even after cleaning it only has maybe 1GB free.