wolstech

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/

Accounts on Johnny can take several days sometimes before they come out of queue. Wait another 48 hours. If it's still not working by that time, post back and an admin will take a look at it.

It is a bit odd that your account is still queued after 5 days...created on 3/10. I've seen Johnny accounts take 3 days before, but not this long. I'll move this to customer service so an admin will be more likely to see it.

Years...that account is long gone. Go ahead and just create a new hosting account. You should be able to use the same username as before since it's not taken by anybody as far as I can see. Stevie signups open at midnight Pacific time every day and usually last several hours before they fill up. As for helionet still working, the hosting accounts and forum accounts are separate. Forum accounts never expire and are never deleted unless you ask to have it deleted.

I'm not finding anything under that username or domain. When you say "a long time", do you mean several months or more? If so, it might have been deleted for inactivity. Also, that domain's NS records appear to be pointing to a different host. You would need to check with them as to why that domain doesn't work, or point the domain here.

It's still broken. Haven't heard anything on how the repair is progressing either.

This support request is being escalated to our root admin.

You were indeed suspended for high load...you've been suspended for this 3 other times it appears over the course of 2 months. Are you running any sort of heavy applications on your account (proxies and WordPress with a lot of plugins are two of the more common load causers)? If you want, I can escalate this and an admin might be able to tell you what file is causing the load. Also, we normally only unsuspend users twice for the same reason. Consider this your final chance, since every time your account causes high load, it impacts the thousands of other users on Stevie. Your account has been unsuspended.

Your post was probably merged with the Stevie SQL issues topic (I don't agree with this for exactly this reason, but others keep doing it for cleanliness...you're not the first person I've heard from about topics disappearing, others have PM'd me). anyway, I hear ya on running a site with these issues. I have a pile of stuff on Stevie that is impacted as well. Haven't heard anything as to the progress of the repairs. In fact, I've noticed less admins around than normal too (I assume they're busy fixing this issue, they did say it was time consuming to repair).