wolstech
-
Posts
17,066 -
Joined
-
Last visited
-
Days Won
618
Everything posted by wolstech
-
Looks like Johnny crashed again: http://heliohost.grd.net.pl/monitor/
-
This is the same issue everyone else had. Change your cpanel password (be sure to select synchronize MySQL password), then log out and in again. After that, delete the database users and recreate them, then reassign them. You also should check in phpmyadmin to make sure the data is still there. If your databases used innodb, your data is likely gone. Looks like Johnny crashed again. http://heliohost.grd.net.pl/monitor/
-
Your can't upgrade it and there are no plans to upgrade on Stevie. I would normally recommend Johnny since he has 5.4, but seeing his hardware is failing, I do not suggest moving over there at this time. Look for an older version of your software.
-
Make a new topic for it since I have to escalate that. Also, Heliohost.org is back up now, but Johnny is not (yet). You can register on Stevie if you want, but wait on deleting your Johnny account until he comes up (see here: http://heliohost.grd.net.pl/monitor/) If you want, just let me know here once you have the Stevie account and I'll take care of the Johnny account for you.
-
Had it been paid for? If so, please post the transaction ID from the paypal payment so it can be added to your account.
-
Change your cPanel password (select "Synchronize MySQL Password"), then log out and in again.
-
@Marko30: The backup he just created cannot be used to fix his databases. The backup he just made will actually be missing his data...he just backed up the empty databases. The one he made now is only good for his restoring files and any databases that aren't damaged. It's better than nothing, but it's not a fix for his lost data. He needs a backup from before the data got lost (basically, he needs a backup made in the first week of June or before that). If he doesn't have that, the data is permanently lost.
-
You will need to ask for it to be assigned to your Stevie account.
-
250MB if I remember right...I do know they count towards your 500MB quota, so it's possible that you can just use as much as the space allows. The choice of engine doesn't matter. Pg and My both have the same limits in regards to (over)use and size. I'd actually go for Pg if I had the choice, seeing MySQL has been known to crash.
-
Johnny lives on the Charlie hardware which failed today. The server also hosts Cody, which runs our website. Normally we'd suggest deleting your account and signing up again, but you can't do either right now with our site and your existing server down. You can't log into your Johnny account, nor sign up on Stevie. The solution is currently to just...wait. I can't even do any admin stuff with that box down. The only people who can use their accounts right now are users who already have an account on Stevie.
-
If its empty, your data is lost. You would need to create a new database with a different name and restore a backup. I would also recommend converting your tables to MyISAM. Innodb is ridiculously unreliable.
-
It's a backup...there should be an archive to download containing the files. A backup will not fix your website unless it was made before the crash. If you don't have a backup from before the crash, you have to start over.
-
I usually use backups, then select the option for full backup.
-
Change your cPanel password, then log out and in again. Delete and recreate your database users, then reassign them to the databases. Be sure you use the same password for the users as before (check in the config file for the software that uses the user to find it). Also, check in PhpMyAdmin to make sure your data is still in the databases. Odds are they're empty...
-
[Solved] Wordpress Db Not Deleted But Client Denied By Server Config
wolstech replied to robev's topic in Customer Service
Glad to hear you got it working Feel free to let us know if you need anything else. -
Change your cpanel password then log out and in again,
-
You can back up your entire account in cpanel. There's an option for a full backup, which includes files, databases, and other data. You can also just make a home directory backup if you want just the files. Note that making a backup now will not allow you to restore the lost databases.
-
If you restore a backup and edit the config files, you won't need to, since the software will look in the new database, see the data it expects, and know it is already installed. If you don't have a backup, then yes.
-
The data got lost. Everyone who had InnoDB tables in their databases lost their data. Drop the database, then create a new database with a different name. Restore your backups into that database using PhpMyAdmin. Then assign the user you already recreated to the new database, and edit your software's config file to use the new database name.
-
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.
-
[Solved] Wordpress Db Not Deleted But Client Denied By Server Config
wolstech replied to robev's topic in Customer Service
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.