wolstech

It takes 5 to 6 months based on current estimates. We only add java to people's accounts when it is removed from other accounts due to suspension or inactivity.

Unfortunately, few if anybody here knows ASP.NET/Mono, so I can't help with this exact issue. What I can say though is that the most common cause of problems with ASP.NET applications though is incorrect target platform. Heliohost only supports .NET 3.5. If you build applications targeted for .NET 4 and newer, they will not work properly.

I see this: http://imgur.com/nNz1K7T Try another browser (or computer). If no change, try a different internet connection. It may be your network or ISP caching the queued page.

If you SELECT from the tables, it works fine. If you UPDATE/INSERT/DELETE data in such a table, it fails with "Got -1 from storage engine" but generally won't crash. Creating/altering/dropping the tables themselves (or databases containing them) seems to frequently cause a crash.

That domain is working fine. Please clear your cache.

It's because status data for Johnny isn't available. Johnny's load shows as white "no data" on that monitor. The load graphics we use also say "down" at the moment.

As you found in the wiki, it's disabled. If you want stats of some sort, you need to find web statistics software and install that to do it, or use one of the many free website analytical services out there.

Username or password is incorrect. I'd start by making sure the user exists and is assigned to the database in cpanel.

We don't specifically prohibit them. However, if you allow public uploads, you are responsible for what people upload and you only get 500MB of space, so a lot of things won't fit. Also, if any of the files are infected, you might get suspended for malware when the AV scan runs.

I'm not seeing any account with that username. Did you receive a second email saying the creation failed?

Did you create the subdomain? They need to be created in cpanel and take 24 hours to start working once you do. Subdomains for accounts on Johnny may take longer. Also, you used commas between the 1 and channel. Those should be periods, like http://1.channel.heliohost.org

You're welcome.

Try it now.

Ns2 is down and hasn't worked in months...Does your registrar requires two working nameservers?

We don't offer that for security reasons. It would affect every one of the 1000+ users on the server. What specific reason makes you think this is necessary?

You're on Johnny. Accounts on Johnny can take up to 5 days to come out of the queue. Just give it some more time. If it still isn't working on Friday, let us know and we'll look into it further.

You were suspended for running 3 cron jobs. The limit is 2 executions per day. Your account has been unsuspended.

Any unsuspension beyond 3 for the same reason is up to us, but we're usually pretty flexible as long as you're actually working on fixing the software issues that cause it. We have the limit because some users will just ask to be unsuspended over and over without fixing the problems. High load affects every account on your server (in this case Stevie), so letting people continuously do it over and over would just lead to performance issues and downtime. If you get suspended again before the admin posts the file causing this, we can unsuspend you again once the information is posted. It's not a hassle to unsuspend an account (it takes 30 seconds or so). As for recovering the content of an account that's suspended permanently, our official policy is that we don't make/keep/provide backups, so what you're doing is the best course of action...make plenty of backups on your own.

We don't monitor bandwidth. You were suspended for excess resource usage (RAM and/or CPU) last time. Your suspension this time is for the same thing. Your account has been unsuspended. Do be aware that a third suspension for this reason will be permanent. This support request is being escalated to our root admin. He may be able to provide you with the name of the file that caused the load.

If it keeps asking, it's generally because the username or password is incorrect. Usernames must be in lower case, and passwords are case sensitive. Your username is mellokc. Try resetting your password. If it doesn't reset, let us know and we can reset it manually and email it to you.

Those apparently didn't spew deprecated warnings in 5.3 for some reason. Those functions are the exact reason why my software doesn't work in anything newer. I get tons of warnings about the MySQL commands. The commands are scattered throughout every one of the hundred or so files that make the system up. My software is all custom and I don't have time to rewrite it using mysqli (which has no benefit aside from new php version support anyway when you develop procedurally as I do...)

This support request is being escalated to our root admin. The admin needs to run that command for you to unblock you.

Theres not too many hosts that support php newer than 5.3. This'll change with time, but right now we only support 5.3, as do many others. The reason many places aren't upgrading quickly is because the newer php versions are not completely backwards compatible like the previous ones were. If we upgraded, many users would be left with broken software. For instance, the software I use won't run on 5.5 at all, and works but spews tons of deprecated errors on 5.4.

There is no solution beyond waiting for the repair to be finished. @yashrs: There seems to be something going on in the past day or so. My site crashed 14 times yesterday in comparison to the ~3/day it's been experiencing. It died on me several times last night while trying to do some work.

See http://www.helionet.org/index/topic/18875-stevie-mysql-common-questions-and-problems/ First one in the list. The 500 error is likely just whatever software you use choking on a crashed database server. It goes away because cP restarts MySQL after a few minutes when its down.