wolstech

I see now that you mentioned the backup was 1kb in size. It should be a lot larger...it probably didn't back up successfully. You'll probably need to just reinstall it and start over.

For me, the blog on your site redirects in an infinite loop. I would recommend dropping your database, recreating a new one with a different name and restoring your backup into that database. After that, assign the user to the database, and edit wp-config.php to use the new database.

@tj0001: Those SET messages are normal. They just set some database-wide attributes. Did you edit the wp-config.php to point to the new database? @efferod: Error 1146 is caused by reusing the same database name. Did you follow my procedure posted above? You must use a new database with a different name.

Doh! Forgot that part...yeah, you need to edit the WP Config to tell it the new name. Glad to hear you got it working though Let us know if you need anything else.

We mean adding the user back to the database. As for the backup not restoring, you cannot reuse the same database (or database name). Create a new database with a different name, then open it in phpmyadmin and restore the backup using phpmyadmin's import tab. After that assign the user to the database, and edit WP-Config to use the new database name.

Change your cpanel password, then log out and in again.

If you need fast and stable service, we recommend moving to Stevie. As for the login issues, both of you should try a different PC and a different internet connection (like a cell phone on its data plan, or a friend's house). I don't see either of you in the block list, so it's likely something on your end. Zyxel, please make a new topic for the email issue so that can be looked into.

Marko has it right, just be sure to log out and in again after doing that. It won't work until you do.

That account is not suspended.

Yes. Change cpanel password, log out and in, then delete database users and recreate them. After that, you need to check in phpmyadmin to see if all the data is there.

Unsuspended. Please remove the auto like bot, that's your cause. Auto like bots are actually the number one way people get suspended for high load (in fact, they are the entire reason we have a load limit!), and are also considered abuse. I can actually suspend you just for having that on your site but since you already got suspended, I'll give you time to remove it.

You have to use a different database name. Do this: Create a new database. Use any name you wish as long as it is not the same as the original database. Go into PHPMyAdmin and select the new database on the left side. Click Import up top, then import the SQL file. If it fails, upload the SQL file and PM me a link to it so I can see it. I'll edit it and send you a fixed one. If it succeeded, go back to cPanel and assign the user incog_wp109 to your new database. Grant it all rights when asked. Test.

Since you have a backup: Drop the database, create it again, reassign the user to it, then open the new database in PhpMyAdmin and import the backup. I'm assuming your "full backup" is the one cPanel makes. If you unzip the full backup, the databases are in a folder called mysql. Just import the .sql for the database being restored.

Did you drop the entire database and recreate it? You cannot reuse the damaged database, even if it appears empty. You must drop it in cPanel, make a new one, then open it in PhpMyAdmin and import the .sql file containing your backup. If it fails after doing that, let me know and I'll escalate it to see if Krydos can discard that for you.

It sounds like you got hit by this: http://www.helionet.org/index/topic/23764-stevie-innodb/ The data is likely lost. I lost 3 DBs myself. This is why we always recommend users make regular backups. The strange part is InnoDB data loss seems to be a common problem anywhere you go...another web host I deal with actually had InnoDB break for a chunk of users recently too...had to use a stale backup from December to fix it.

The databases themselves may or may not be there. Once you get into PhpMyAdmin, see if the tables are still in them. If they're not, you need to restore a backup. The database users will all need to be deleted and recreated as well.

My understanding is that Java is currently broken, so there isn't one. Krydos is working on fixing it. Once fixed, he'll put you and the other 50+ people who requested it on the wait list (he hasn't done the requests in over a month). We only have enough resources for ~50-100 users to have it right now, so someone new gets it when someone else loses it (due to suspension or inactivity).

Yeah, Stevie was acting up earlier. About 10 minutes after I posted, I got a flood of emails from my monitoring service saying it was going up and down repeatedly... Seems to be working now though.

@incog: Yep. Doesn't belong here. I'll move it for him though so he doesn't need to repost.

InnoDB tables were lost in the recent crash. The fix is to drop the database and restore your backups.

Empty response is when a server opens a connection then doesn't send anything to the client (in this, cloudflare). Odds are it was due to server load, especially if you are on Johnny. I see tons of ERR_EMPTY_RESPONSE in Chrome when trying to get pages to load from Johnny.

You have to change your account's main domain to a something.heliohost.org subdomain if you wish to do that. You can change the domain here: www.heliohost.org/home/support/scripts/domain The change takes about 24 hours to take effect once you do it.

The account uzair3 has been marked for deletion. When the deletion is complete, your old domain will show a queued page. You weren't able to delete it yourself because it was suspended for inactivity. Escalating so the theme can be changed to paper_lantern on account cwk.

Change your cPanel password, then log out and in again to fix PhpMyAdmin.

There is an advantage there, but it's far from mandatory in many cases. I have at least one application on my account that was adamant it needed InnoDB...it's been running on MyISAM for a year with zero issues. Full foreign key support/enforcement in the database is nice, but a decently-written program should be able to handle bad foreign keys without choking (granted it means the database isn't strictly valid...) All bets are off if Transactions are needed though...MyISAM doesn't understand them. If Inno didn't blow up as often as it does, I'd be more inclined to use it. The first crash here had me lose 2 months of data (had to restore a stale backup). Everything was converted to MyISAM then except some less-important applications. Those broke last week and ended up needing (recent 3-week-old) backups restored.