wolstech

MySQL crashed while you were using it, which is why you started seeing those errors in the middle of your task. It's already escalated here: http://www.helionet.org/index/topic/26558-mysql-down/

It crashes due to the fact that it has over 11,000 users and countless more databases...all it takes is one abusive user or one corrupt database to crash it. Escalating...again.

You can convert the database to MyISAM as follows. This will also fix the #1874 (InnoDB read only) error: Make a copy of the .sql file you want to import.Search the copy of the .sql file for Engine=InnoDB and replace all instances with Engine=MyISAMCreate a new database.Import the edited copy of the .sql into the database using PhpMyAdmin to restore the content.We don't recommend using InnoDB on Stevie since the data gets lost or the server goes read-only quite regularly due to crashes.

What are you getting for output? An empty file? An error message?

I was unaware they were ever enabled on Johnny...we turned off a lot of the logging for performance reasons. I'll escalate this and see what Krydos says. He may have just forgotten.

Tommy is not yet released, and Johnny is crashed. You can only sign up on Stevie, which accepts only a few hundred registrations per day. You may need to sign up on our old website if you're having issues. The server monitor here shows when signups on Stevie are available: http://heliohost.grd.net.pl/monitor/

Seems to be working now.

It was down earlier but is currently working for me.

It takes 24-48 hours to start working after you add it. It shows queued until the server finishes setting it up.

Um...seems to still be down.

Looks like this crashed again... Escalating.

You need to configure the domain DNS at your registrar. In your registrar's control panel, create two NS records for that domain, pointed to ns1.heliohost.org and ns2.heliohost.org, remove all other records, then try again.

Squirrelmail should work. The database server is messed up on Stevie right now, and those issues with horde and round cube are caused by the softwares inability to use its database.

Just sign up on Stevie. If you need a domain removed, please let us know which domain it is and I will escalate for you. Your Johnny files and databases are available via FTP because Johnny crashed. The databases can be found in your home folder as .sql files.

Try another internet connection such as a cell phone on its data plan. It's possible that your ISP has cached the page. The site is working for me.

Please clear your cache.

You're suspended for multiple accounts. Users are limited to one account. The account emagrece has been unsuspended.

InnoDB went read-only again from the crash on Friday. Can this be fixed please?

This support request is being escalated to our root admin.

Since you're able to create and import the data for the database, the database and cP are now working fine. The "already exists" for a deleted DB is normal when you drop a corrupt InnoDB database. The corruption prevents it from dropping fully, and there is indeed no way to reuse the DB name unless a root admin manually clear out the damaged files that stored the database. I'm a bit confused: Is the error seen on your website showing the new or old database name? If it's the old database name, you likely missed a reference to the database name somewhere in your code. If it's the new one, you probably missed a password somewhere in your code.

Did you edit your website's code to use the new password you set? The password for the DB user matti76 should be your cPanel password, so changing the cPanel password will change the DB user's password too. Anything that uses that database user will need to be told what the new password is. If it still refuses to work after you've made sure the website code has the right password, make sure they match by changing the cPanel password again and checking the "Synchronize MySQL Password" checkbox to force the DB user's password to change. I don't recommend using your cPanel account as a database user for security reasons, but lets get it working first. #1874 is because InnoDB has gone read only again due to a crash yesterday morning. I'd advise not using InnoDB since many times when MySQL crashes, InnoDB data has a habit of getting lost. I recommend you convert the InnoDB database to MyISAM, which is much more fault-tolerant. We've never lost MyISAM data in our 10+ years of operation. We've lost all of our InnoDB data several times this year alone. You can convert the database to MyISAM as follows. This will also fix the #1874 error: Make a copy of the .sql fileSearch the copy of the .sql file for Engine=InnoDB and replace all instances with Engine=MyISAMCreate a new database.Import the edited copy of the .sql into the database using PhpMyAdmin to restore the content.

Try changing your cpanel password, then log out and in again. After that, try recreating the users again.

Phpmyadmin is no longer working, so there's no link to give. Escalating so krydos can check. Do note though that if your database used innodb, its currently unrecoverable.

Marko has it. Tommy is current unreleased, and as a result is invitation only right now. Also, for those who did get a Tommy invitation: if it was sent to an email address that currently is used by a Stevie account, you need to delete the Stevie account before the invitation will work.

Postgres does not crash as far as I'm aware. Not too many use it though.