wolstech

Got 4 reds on the monitor and a pile of timeout alerts by email...

That domain is already configured as the main domain for that account. Is this the domain you want? It's showing queued, but they do take 24-48 hours to start working, so that's normal if you just changed it. Give it a day or so to finish setting up, then clear your cache. If it still doesn't work after that, let me know and we'll look into it further. EDIT: Byron beat me to it.

What account needs the domain changed?

Please clear your cache.

3 cron jobs. As you're aware, the limit is 2 per day. Unsuspended.

This support request is being escalated to our root admin.

Tommy is invitation only. Our public offering is currently only php 5.3.8. Please find an older version of your software.

I can't think of any time we lost files. InnoDB database tables are the most likely thing to get lost. InnoDB is horrible at fault-tolerance, its basically a 50/50 chance every time the database server shuts down improperly as to whether your InnoDB tables will still be there when it comes back.

Looks like the whole server crashed. I can't even think of the last time this happened. He sees load spikes and SQL issues rather regularly due to overloading, but it looks like this time the whole server fell over under the load.

Looks like he crashed...even the NS is down. Escalating. For the interested (maybe Krydos will better understand what I saw): Right before the crash I was on SSH editing some code of mine since I updated my main software today. I noticed HTTP slow then start timing out while testing. Top showed PostgreSQL and recquota (linux disk quota service) beating on the CPU (both pegging it). I left the SSH open with top running, and 10-15 minutes later the session died abruptly. Haven't reached Stevie since.

Stevie is suffering from some type of excessive load or abuse at the moment. cPanel has been down for over an hour: http://heliohost.grd.net.pl/monitor/ My attempts at logging in give me a network error. And for what its worth, MySQL appears to have crashed for the third time today as well...

i hope too, and soon coz' im gonna be in big trouble! Y_Y admin its not yet solved, a few minutes ago yes i can access again my database, but now its offline again Looks like it's fixed again. Why would we ban you? Thanks for letting us know it was broken

Unmarked as solved seeing the email link doesn't work for you.

MySQL crashed again...second (third?) time in 3 weeks Escalating.

Indeed it did. Escalating.

There are no plans to update Stevie since many users on Stevie require php 5.3. Also, php 7 is not backwards compatible with 5.x, so upgrading would break a lot of people's websites. Tommy, while currently invitation only, will let users pick from php 5.4 - 5.6 or php 7 when he is released.

This support request is being escalated to our root admin. @Krydos: You opened the UDP port, he wants the TCP one added as well.

This support request is being escalated to our root admin.

What account are you trying to validate? If you're signing up, do you already have an account?

It's not as common as it sounds, but it has happened once or twice this year. If you want to convert it, the safest way is export the database to a .sql file, replace all the Engine=InnoDB with Engine=MyISAM in the .sql file, then create a new database and import the edited file. After that, just point PhpBB to the new database, test, and drop the old one. Many people report newer PhpBB having trouble on MyISAM though, so if it acts strange, you may need to find other forum software or just make frequent backups (which we recommend anyway!) so you can restore it if InnoDB decides to go belly up.

Johnny crashed due to file system damage that is beyond repair. You need to download your files via FTP, and move to Stevie. Databases can be found as .sql files in your home directory. Please note that all InnoDB database data is unrecoverable, so databases using InnoDB will appear as empty files. See http://www.helionet.org/index/topic/25786-johnny-backups/

You were suspended for causing significant high load. I'll escalate this so we can see if Krydos knows what file caused it. Once we know the cause and you're ready to fix it, we can see about unsuspending it so you can make the changes needed to correct this.

Try disabling the encryption: File->Site Manager, pick the Tommy connection, change the encryption to "Only use plain FTP (insecure)" and try again. For me it seems to be 50/50 on whether TLS will work on any given session with Tommy. On Stevie I've never had an issue...

The database size just counts toward your account's disk space quota I believe. The only other limit we have on it is overuse/abuse of CPU time. Running complex or badly written queries that monopolize the server (or crash it...) can get you suspended for high load. Pretty much all common software doesn't have any issues with the load though. Finally, I recommend staying away from the innodb storage engine in MySQL if you're on Stevie, it is subject to going read only or just losing your data without notice if the database server crashes (can happen due to abuse on occasion).

Take a look at this topic: http://www.helionet.org/index/topic/26236-tutorial-setting-up-tk-domain-alias-to-your-hostnameheliohostorg/