Jump to content

wolstech

Chief Risk Officer
 View Profile  See their activity

  • Posts

    17,332

  • Joined

  • Last visited

  • Days Won

    639

 Content Type 

Everything posted by wolstech

  1. wolstech
    That is indeed the issue I am speaking of. Also, your website is currently working fine. (I see this: http://imgur.com/FOZTxaC) And yes, being in cP a lot will do that to your site. A cache isn't a bad idea for now since the DB server is broken. We're hoping we'll get this fixed soon, but there is no timeline for repairs to be complete unfortunately.
  2. wolstech
    When importing in PhpMyAdmin, try not to use a zip file. Upload the .sql file by itself into an existing but empty database directly in PhpMyAdmin (not in cPanel). The error #2002 is an issue when dropping DBs sometimes. I had to convert three of mine, and one failed to drop with #2002. You probably have a half-dropped DB now...it shows in PhpMyAdmin, but not cPanel. Once the DB server issues are worked out, an admin can drop the unwanted database for you.
  3. wolstech
    Timeouts...that sounds like the firewall might have blocked you. Does it work if you use a different internet connection (e.g. neighbor's house, 3G, or local coffee shop)? You mentioned that you used FTP...overuse of FTP is the most common way to get blocked. An admin will need to check and can unblock you if needed. Also, just so you know, your account is still here, and is still showing the queued page. You'll need to wait a few more days (and get unblocked) before you'll actually be able to see your website.
  4. wolstech
    By the description of the problem, I'll guess you're on Stevie. PhpMyAdmin is always slow on Stevie. As for the #2002, the database server is broken on Stevie at the moment due to a crash 5 weeks ago. The repair is still in progress. You see that error if you try to use PMA while the mysql server isn't working (it goes up and down a lot due to the damage caused by the crash.) The 500 errors are likely high load or hitting your process limit, especially if they started appearing out of nowhere and go away on their own. Note that logging into cPanel on Stevie may cause a 500 error on your website. Also, please post your cpanel username (but not your password), your server, and your domain so we can look at the issue. There is no need to PM it someone. In fact, PMing it to someone makes it more difficult for us to help you, as more than one of us may take a look at the issue.
  5. wolstech
    Johnny has been slow to finish creating accounts lately. I've seen them take 5 or 6 days. Wait another 48 hours or so, then clear your cache.
  6. wolstech
    An admin will need to handle all of that. I can't even access your account's content.
  7. wolstech
    PHP appears to be working fine on Stevie (it is working for my account anyway.) Do you have a .htaccess file in either of those folders? If so, rename or delete it and try again.
  8. wolstech
    You weren't suspended for cron jobs (the system deletes them on its own if they're set to run too frequently). This time around it says it was for high server load. Using too many resources impacts the performance of all the other accounts on the server. Your account has been unsuspended.
  9. wolstech
    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.
  10. wolstech
    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.
  11. wolstech
    We don't even measure bandwidth here. As long as your account has enough free space, you should be fine.
  12. wolstech
    Im pretty sure the max number of connections is limited for the server, not your account. When the limit is reached, everything that tries to connect sees that error until something disconnects and makes room. I see it quite a bit too in my apps.
  13. wolstech
    You're now both inactive and suspended...it is kinda strange that it bothered to mark you inactive, but nonetheless. As for what happened, it sounds like what you said: you probably got hacked and turned into a zombie for spam/malware distribution. It happens to the best of us, although not usually to the extent that it happened here. If you used something like WordPress, odds are that was how you got attacked. CMSes and other widely used applications like forum software are prime targets for hackers, as are the extensions and themes for them. Updating whenever new versions come out is essential. Avoid themes and extensions from non-reputable sources. Also, you don't have backups, but if you did, I wouldn't recommend them anyway, since backups would contain whatever vulnerability was used to hack you. If you happen to create a new account in the future, just be sure this never happens again.
  14. wolstech
    Everything usually gets updated on Johnny first as a testing ground. Seeing that Johnny hasn't even been updated, a PHP upgrade is unlikely to happen anytime in the near future. It's also worth noting that PHP 5.4 is not exactly the most backwards compatible version out there (5.5 is even worse). I have an app that won't run on it for instance... As for mysql upgrades...no comment. The DB server issues are being worked on though. Some work done this morning to repair damaged databases has improved mysql's up-time, and work on the repair continues.
  15. wolstech
    Yep. That error is the database server being down. You dot mention what server you're on, but if its Stevie, the error is likely due to the broken MySQL server. Stevie's MySQL tends to give that error a lot ever since the crash.
  16. wolstech
    The admins have known about the database issues since 2/17 when it broke. There's no information on the status of repairs. It's been broken for a month though and the repair was expected to be time-consuming, so I wouldn't expect it to be repaired in the immediate future.
  17. wolstech
    Evrooije pretty much said it. Joomla cannot be installed on Stevie due to the database issues. You'll need to wait until they are fixed. It might be possible to modify the joomla installer to use myisam, but i'm not sure how one would go about this.
  18. wolstech
    That domain is working. Please clear your cache.
  19. wolstech
    Make a copy of your backup, open it in a text editor. Check the CREATE TABLE statements for "engine=InnoDB" and replace all "engine=InnoDB" with "engine=MyISAM". Save. Then, try importing the edited copy. The lost connection error with a restore is usually because your backup is trying to create InnoDB tables.
  20. wolstech
    The DB settings look fine. I'm out of ideas on it unfortunately. Perhaps someone else might know more about Joomla. I don't know much about it since I do not use it. The only thing I can suggest now is waiting until the DB server is fixed (might be a while, there's been little/no update on the repairs in a month), moving to Johnny (the DB server is working but high downtime due to load), or replacing Joomla with something else.
  21. wolstech
    It is showing as active in the system. If you can't log in, try resetting your password. If that doesn't work, let me know and I can reset it manually for you.
  22. wolstech
    This issue is part of the ongoing problems as well. I tried dropping one after I made a new one with MyISAM tables and did that too. It shouldn't be an issue other than being wasted space. You can't get rid of it, an admin needs to drop it for you. I think mysql is having issues dropping the databases since it goes down so much due to the problems. As for the error being the same...do the tables actually show as MyISAM now (I'd assume so, since I don't believe InnoDB tables can be created at the moment)? The error is caused by database issues, most likely an inability to reach the server. Check that the DB user/pass and DB name are right. The host should be localhost. If you want, post the configuration.php here and I'll look when I have time (censor the password please). Joomla's board has this topic about the error: http://forum.joomla.org/viewtopic.php?t=791765
  23. wolstech
    Export your entire database through phpmyadmin, then edit the exported dump (replace "Engine=InnoDB" with "Engine=MyISAM" in every place you find it). After that, create a new database and assign the user you currently use for the old database to it, then import the edited dump into the new database through phpmyadmin. Finally, edit the database configuration for your website to use the new database.
  24. wolstech
    That account is not suspended. However, the main domain is not pointing to our name servers. You need to change that domain's name servers to ns1.heliohost.org and ns2.heliohost.org if you want that domain to be hosted here.
  25. wolstech
    This is related to the SQL issues that Stevie has been having for the past month. That error is from the installer trying to create innodb tables. There's not much you can do about it except wait until it is fixed.
×
×
  • Create New...