wolstech

You weren't suspended for cron jobs (the system deletes them on its own if they're set to run too frequently). This time around it says it was for high server load. Using too many resources impacts the performance of all the other accounts on the server. Your account has been unsuspended.

Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. If you still see the suspended page, please clear your cache.

Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. If you still see the suspended page, please clear your cache.

We don't even measure bandwidth here. As long as your account has enough free space, you should be fine.

Im pretty sure the max number of connections is limited for the server, not your account. When the limit is reached, everything that tries to connect sees that error until something disconnects and makes room. I see it quite a bit too in my apps.

You're now both inactive and suspended...it is kinda strange that it bothered to mark you inactive, but nonetheless. As for what happened, it sounds like what you said: you probably got hacked and turned into a zombie for spam/malware distribution. It happens to the best of us, although not usually to the extent that it happened here. If you used something like WordPress, odds are that was how you got attacked. CMSes and other widely used applications like forum software are prime targets for hackers, as are the extensions and themes for them. Updating whenever new versions come out is essential. Avoid themes and extensions from non-reputable sources. Also, you don't have backups, but if you did, I wouldn't recommend them anyway, since backups would contain whatever vulnerability was used to hack you. If you happen to create a new account in the future, just be sure this never happens again.

Everything usually gets updated on Johnny first as a testing ground. Seeing that Johnny hasn't even been updated, a PHP upgrade is unlikely to happen anytime in the near future. It's also worth noting that PHP 5.4 is not exactly the most backwards compatible version out there (5.5 is even worse). I have an app that won't run on it for instance... As for mysql upgrades...no comment. The DB server issues are being worked on though. Some work done this morning to repair damaged databases has improved mysql's up-time, and work on the repair continues.

Yep. That error is the database server being down. You dot mention what server you're on, but if its Stevie, the error is likely due to the broken MySQL server. Stevie's MySQL tends to give that error a lot ever since the crash.

The admins have known about the database issues since 2/17 when it broke. There's no information on the status of repairs. It's been broken for a month though and the repair was expected to be time-consuming, so I wouldn't expect it to be repaired in the immediate future.

Evrooije pretty much said it. Joomla cannot be installed on Stevie due to the database issues. You'll need to wait until they are fixed. It might be possible to modify the joomla installer to use myisam, but i'm not sure how one would go about this.

That domain is working. Please clear your cache.

Make a copy of your backup, open it in a text editor. Check the CREATE TABLE statements for "engine=InnoDB" and replace all "engine=InnoDB" with "engine=MyISAM". Save. Then, try importing the edited copy. The lost connection error with a restore is usually because your backup is trying to create InnoDB tables.

The DB settings look fine. I'm out of ideas on it unfortunately. Perhaps someone else might know more about Joomla. I don't know much about it since I do not use it. The only thing I can suggest now is waiting until the DB server is fixed (might be a while, there's been little/no update on the repairs in a month), moving to Johnny (the DB server is working but high downtime due to load), or replacing Joomla with something else.

It is showing as active in the system. If you can't log in, try resetting your password. If that doesn't work, let me know and I can reset it manually for you.

This issue is part of the ongoing problems as well. I tried dropping one after I made a new one with MyISAM tables and did that too. It shouldn't be an issue other than being wasted space. You can't get rid of it, an admin needs to drop it for you. I think mysql is having issues dropping the databases since it goes down so much due to the problems. As for the error being the same...do the tables actually show as MyISAM now (I'd assume so, since I don't believe InnoDB tables can be created at the moment)? The error is caused by database issues, most likely an inability to reach the server. Check that the DB user/pass and DB name are right. The host should be localhost. If you want, post the configuration.php here and I'll look when I have time (censor the password please). Joomla's board has this topic about the error: http://forum.joomla.org/viewtopic.php?t=791765

Export your entire database through phpmyadmin, then edit the exported dump (replace "Engine=InnoDB" with "Engine=MyISAM" in every place you find it). After that, create a new database and assign the user you currently use for the old database to it, then import the edited dump into the new database through phpmyadmin. Finally, edit the database configuration for your website to use the new database.

That account is not suspended. However, the main domain is not pointing to our name servers. You need to change that domain's name servers to ns1.heliohost.org and ns2.heliohost.org if you want that domain to be hosted here.

This is related to the SQL issues that Stevie has been having for the past month. That error is from the installer trying to create innodb tables. There's not much you can do about it except wait until it is fixed.

Yep. That's the solution many of us are using to convert our tables. Good to hear it's working for you now

Yes it works. As for it's difference from parking a domain...there's no real benefit except for a few cases such as when you use registrars like registro.br that require you add the domain before you can set your nameservers. Most users can just park their domain and it will work fine.

That account cannot be unsuspended.

Chances are the first change did finish and start working, hence why it looks like that. You need to wait 24 hours after you make the changes before they start working. Check back tomorrow to see if your old heliohost.org domain works again. It is showing as queued, so it is in the process of being recreated...

Using that script changes your main domain...cts-enlinea.heliohost.org is down because you un-registered the heliohost.org subdomain when you changed your main domain to ctsinmobiliaria.com. To fix it, use that script again to change your main domain back to cts-enlinea.heliohost.org The "You can't park your main domain!" error is because of the same issue. You made that domain your main domain, so you cannot park it as well. Once you change your main domain back to cts-enlinea.heliohost.org, you will be able to park the new domain. Once you change the main domain back and park your new domain, wait 24 hours, and both domains should work. If you want to keep the new domain as your main domain, don't do anything (it is working). Do note, however, that you cannot have cts-enlinea.heliohost.org if you use your new domain as your main domain.

Do you know about a domain called vimvou.com.br?

InnoDB is broken on Stevie. Use MyISAM tables instead, or wait until the issue is fixed. You are one of many that is affected by this issue. See http://www.helionet.org/index/topic/18427-stevie-mysql-issues/