wolstech

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.

All available files and data can be downloaded via FTP. Your databases will be found as .sql files in your home folder.

This appears to be fixed.

I've been here 5 years, and Stevie MySQL has always crashed a lot. I think it's load-related, but Krydos would know for sure exactly why it crashes.

MySQL died again... Escalating.

Typically, they fill up as a result of broken code that never exits (php), due to email clients that check too frequently (imap), or similar reasons. Logging into cpanel causes a 500 error due to processes, though that one should clear on its own when you log off. I've never had to ask for a process kill at any point. There is no away to see or do it yourself.

The SQL error is likely something wrong with the syntax of whatever statement would normally generate the data for that field. Seeing that no specific error number or message is shown, there's no way to tell what happened from that picture. Also, do you have a license for IPB? I looked at your site, and it appears to be pirated/nulled, which violates our TOS. If you don't have a license, please delete the entire IPB install or you will be suspended for copyright infringement. I'll go ahead and mark this answered since the software in question has been removed.

Domain changed. Please give it 24-48 hours to update and start working.

That's what this tutorial explains...how to park a .tk domain. Alias is just the paper_lantern theme's name for a parked domain.

I don't see an SQL error, I see a general 500 error. Whatever code feeds the genre section is outputting a 500 error.