Jump to content

wolstech

Chief Risk Officer
  • Posts

    18,381
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by wolstech

  1. It's CPU and memory, not space. Basically, your program was hogging the server resources which makes everyone else's site slow, so we suspended you so everyone else could use their accounts. You don't have any way of monitoring it actually. The normal causes of this are programs that either need too many resources or are just malfunctioning. If it happens again, let us know and we can tell you what file is to blame for the load.
  2. Change your cPanel password, then log out and in again. After that, delete the database user ovt00_mysql, then recreate it and reassign its permissions. Once you do that, check PhpMyAdmin to make sure your database contains all of its data.
  3. If there was an old one, it wouldn't let you create the new one (I actually had this issue happen...I tried to drop one and it wouldn't let me make a new DB with the same name, Krydos had to drop it for me to get it to fully drop). Silly question, but did you use the same password on the new user? If you just used the password generator button, you need to edit the software's config file to make the passwords match. Just for testing, try using your cPanel username and password as your database user. While not recommended from a security standpoint, it'll at least prove that the database itself is functional since that user always has access to all databases in your account.
  4. Did you assign that user to the database you created? Also, try using your cpanel account as the database user to see if it works.
  5. Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. If you still see the suspended page, please clear your cache.
  6. Dd you make sure to reassign the database user to the database? Also make sure the database user h the right password.
  7. The user must be deleted and recreated, not just get a password change. After you recreate it, make sure you assign it to the database again too.
  8. I've not had any issues installing something using InnoDB then converting it's DB afterwards. I'm sure applications that won't work like this do exist, but they seem to be rather rare. For most, it's more because many programs have install scripts are just coded to import tables that are defined using it...the tables themselves don't care what format they are in, and the program using them is usually none the wiser if you change the engine, provided the schema stays the same.
  9. Topics older than a certain date "fall off the bottom of the list" (they become hidden). You can still get to them by finding them through search though. Also, post counts don't update immediately, and in some forums, posts don't count at all, so your count may not always be a perfect reflection of your posts.
  10. Please change your cPanel password, then log out and in again. After that, check that PhpMyAdmin works and that all your databases and their tables (especially InnoDB tables) are present. After that, go through your database users, delete and recreate them. Use the same password as last time (check in your software's config file for it if you don't know it). Make sure to reassign the users to their databases as well.
  11. If the backup was created after the recent crash, the InnoDB tables in your database will be missing from your backup. A lot of them were lost in the recent crash (again). Not sure what the odds of us having a backup are, so I'll escalate this for you. Note though that we don't make backups for user data regularly, we may not have anything to restore. Routine backups of databases should be made through cPanel or PhpMyAdmin, and it is the user's responsibility to make them. Once you get this fixed, I would recommend converting the database tables to MyISAM so this won't happen again.
  12. The roundcube on cPanel is indeed broken. Escalating.
  13. Working for me now too. If you still see the error, please clear your cache.
  14. You need to use a backup from before the incident.
  15. wolstech

    This support request is being escalated to our root admin.
  16. wolstech

    You're blocked by the firewall. Escalating so you can be unblocked.
  17. wolstech

    Please check your email.
  18. InnoDB is broken again. You need to create a new database with a different name. Try restoring a backup into that database and see if it works.
  19. MySQL went corrupt. Change your cPanel password, then log out and in again. After that, delete the users for your databases, recreate them (use the same password as before, find it in your program's config file if you don't know it), and reassign them to your databases. Finally, go into PhpMyAdmin and verify that all of your databases have all their tables and that they're accessible (especially ones with an Engine of InnoDB)
  20. MySQL's user data went corrupt. Change your cPanel password, then log out and in again. After that, delete the users for your databases, recreate them (use the same password as before, find it in your program's config file if you don't know it), and reassign them to your databases. Finally, go into PhpMyAdmin and verify that all of your databases have all their tables and that they're accessible (especially ones with an Engine of InnoDB)
  21. MySQL's user data went corrupt. Change your cPanel password, then log out and in again. After that, delete the users for your databases, recreate them (use the same password as before, find it in your program's config file if you don't know it), and reassign them to your databases. Finally, go into PhpMyAdmin and verify that all of your databases have all their tables and that they're accessible (especially ones with an Engine of InnoDB)
  22. That version is only available on Johnny. I'm not sure if Stevie will ever be updated. He was supposed to be updated at one point, but then we decided to get a new server... We are planning to put (I think) 5.6 on the new server, but I don't know when that server will go live.
  23. wolstech

    What's your username? I can email a new password to the address on your account so you can log in.
  24. Delete the user mrres then recreate it. Make sure to use the same password as last time (find it in the config file for your software), and reassign it to the database.
  25. Change your cPanel password (make sure to check "Synchronize MySQL password"), then log out and in. Once you do that, check PHPMyAdmin to verify that your databases are there, have all their tables in them, and that you can view the data. You also need to delete and recreate all your users, then reassign them all again.
×
×
  • Create New...