wolstech

Have you dropped the database and recreated it? I've had this happen on my Stevie account, and just backing it up, dropping it, and recreating it in cPanel made it appear in PMA. If you create the DB in PMA, you won't see it in cPanel and can't assign users to it. Also, dropping databases created this way can be a challenge. A PC tool like MySQL workbench might work, or an admin can drop it for you.

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.

This support request is being escalated to our root admin.

That's odd...I'll escalate it. It should be out of queue by now.

You're probably suspended for something that's not inactivity. What is your account username and domain?

We don't generally make exceptions to this policy other than for those who need another account for something like Java (even then, it's 2 total, 1 per server, and you need permission from an admin). We can however let you back your data up and remove your domains so you can combine them into one account. If you want to do this, tell us which of the 4 you want to back up, and which one you want to keep. We'll unsuspend one at a time, then you make backups and remove your domains. When you're done, let us know and we'll resuspend it and move on to the next one. When it comes to how we tell, I can't go into detail, but I'll say that the server has software that can catch some for us, and they're usually pretty obvious if we look for them manually. As for not seeing a notice about this policy, it's hard to miss on the signup page in the red box: http://www.heliohost.org/home/create-johnny-account

If I remember right, someone else tried to install this a while back. For files, It's basically upload the files, and edit the Config file per the read me. The database needs to be created and imported using a PC program like pgadmin iii. Phppgadmin is broken on stevie, and we don't provide shell access.

InnoDB databases are not supported. Go here: http://www.helionet.org/index/topic/18875-stevie-mysql-common-questions-and-problems/ and follow the solution for error -2013 (use the last section of that solution, where it starts "If you have a backup that you want to restore...")

This support request is being escalated to our root admin.

I'm pretty sure this isn't as easy as you make it to be. I'll escalate this.

To move your account, you need to delete your account and sign up again on Stevie. You can delete your account here: http://www.heliohost.org/home/support/scripts/delete

Your Stevie account is now working at takay1.tk. If you still see the queued page, please clear your cache. You will need to add takay.tk as a parked domain and wait 24 hours for it to begin working. I will remove your Johnny account so you can add the domain to your Stevie account. Johnny's uptime is terrible in comparison to Stevie, so unless you need any of the special features on Johnny, Stevie is the best choice.

Johnny accounts take 4-7 days to become active. Also, you cannot have two accounts. I see you recently registered on Stevie with nearly identical information. Do you want me to delete the Johnny account so you can keep the Stevie one?

This support request is being escalated to our root admin.

We are indeed blacklisted by spamhaus and also CBL. CBL's website says it might be a botnet, so perhaps CryptPHP again? Krydos will need to fix this and get us unblocked again. http://mxtoolbox.com/SuperTool.aspx?action=blacklist%3aJohnny.heliohost.org&run=toolpage

It's likely flagging the hidden iframe on that page...its nothing to worry about. Even AVG's own site says the cpanel URL is safe.

/tmp and /usr are hard disk partitions that are rather large. /tmp never fills up unless someone abuses it (known to happen on occasion). /usr is irrelevant here. Your issue is because /tmp is full again. An admin needs to empty it and suspend somebody.

We usually say we're working on it, but It's been broken for a year. Seeing that even we don't know when it'll be fixed (Krydos is the only one who could fix it), and my understanding is that the damage was quite severe, I suspect the answer is "we're not".

I have no idea, but if you want, try registering your subdomain again. If you get an email with an error message after you register, post a new topic with the message and we can fix it.

Even though it should have been deleted long ago, an account for coldwin somehow still exists (last login is March of last year). The domain looks like perfectworld.tk. It's been unsuspended.

We don't keep backups Yeah, the deletion script isn't exactly thorough when it comes to DNS. It's generally caused by the server experiencing high load when the account is deleted, although there's definitely the possibility of bugs in the script's DNS zone cleanup. I do know that Krydos has cleaned up old orphaned DNS on occasion, so I suspect your account will be one of those that gets cleaned up whenever he does that again.

We don't generally upgrade this stuff for stability reasons. We only upgrade to whatever version comes with cPanel, so whenever that gets upgraded (rarely), this gets upgraded. I tell you this every single time. An interesting fact: I help people who use other hosts, both free and paid, and our software on Johnny is actually *newer* than what many of those are running. What's running on Stevie is what I find with most companies (though some still use PHP 5.2...) We understand that you want it, but you're just one of over 1500 users, and we're not going to make major server-wide (and likely account-breaking) changes for one person. It'll likely be upgraded whenever cPanel gets upgraded, probably not sooner.

ENGINE=InnoDB Change the engine to MyISAM and it'll work. We do not support InnoDB due to server damage last year.

I see a directory listing. Please clear your cache.

I'm seeing this: The MySQL server on Stevie is down...give it some time and it'll restart itself. It crashes quite a bit from InnoDB-related damage. Also, I can't look at the source of a .php file since it gets processed. Make a copy and change the file extension to .txt if you want us to see the source.