Jump to content

wolstech

Chief Risk Officer
  • Posts

    18,473
  • Joined

  • Last visited

  • Days Won

    715

Everything posted by wolstech

  1. The Access Denied errors seen on websites are fixable by deleting and recreating the database user. Be sure to reassign it to the database after deleting and recreating it. PhpMyAdmin and your cPanel MySQL account are still broken though (sometimes changing your password will fix these, but it did not when I tried it).
  2. The Access Denied is fixable by deleting and recreating the database user. Be sure to reassign it to the database after deleting and recreating it.
  3. These seem to be fixable by deleting and recreating the database user. Be sure to reassign it to the database after deleting and recreating it.
  4. It was indeed dead database users. I deleted mine and recreated them and they work. Still doesn't explain PHPMyAdmin though...
  5. Doesn't seem to be up. All my sites are still showing the access denied error and I can't even get into phpmyadmin. InnoDB was turned off a week or so ago, before this issue happened. InnoDB tables all show as "in use" now, and imports will fail with "unknown engine" as opposed to ghost tables.
  6. Give it 24 hours then clear your cache. If it's still suspended after that, please let us know.
  7. It appears to be a botched update, though at least one other user reported speaking to Krydos on IRC and who said he was unaware anything was updated (confused there, he's the only one who does this stuff). I've yet to hear anything official on this...nothing has been said to staff either. :-\
  8. There's a lot of users on Stevie with this issue. I'm affected too There's been no information on this issue, even internally to the mods. I'm hoping it gets fixed soon. Moving to customer service.
  9. You're on Stevie. Many if not all people on Stevie can't use their databases right now because MySQL is completely broken. Instead, you'll see a "can't connect" or "access denied" message. There is no fix but to wait until we hear from Krydos about this.
  10. You're not alone. A large number of people on Stevie can't access their databases right now. The database server on Stevie appears to be broken.
  11. Many people on Stevie are affected. The database server appears to be broken. It's up but returning access denied errors for the accounts.
  12. Agreed. I suspect this is part of an effort to do to Stevie what we did to Johnny a few months back. Similar upgrades were performed, and we fixed the busted InnoDB support while at it. I just wish there had been notice...I published a software update on Saturday, and many sites are rejecting my software submissions because the forwarding links I use to track statistics return errors instead of 301 redirects right now.
  13. cPanel definitely got upgraded. PHPMyAdmin was displaying a "This functionality is currently unavailable because a cPanel/WHM upgrade is in progress" message last night when I tried to log in. PhpPgAdmin was doing the same thing. cPanel went from 11.3x.x to 11.42.1, and I think MySQL went from 5.1.68 to 5.1.73 (though this may have happened earlier). If Krydos didn't know about it, then I'm confused. Nothing has been announced either publicly or to mods/admins, and only Krydos does major updates.
  14. Nobodies does. Everyone on Stevie is affected. Not sure when it'll be fixed, but it was likely related to what looks to have been a cpanel update yesterday.
  15. The database server is down entirely. Phpmyadmin is giving a message saying cpanel is being updated, which is odd.
  16. The database server is just broken right now. Your account is not suspended.
  17. MySQL is down right now. I tried to get into phpmyadmin too, but got a message saying cpanel was being updated.
  18. It's likely related to the MySQL damage and repairs on Stevie. As of Friday, my external hosts also don't show up (granted I just have a % there), and also all of my innodb tables are showing as "in use" in phpmyadmin and are not usable. I can't check now, but I'll assume this is still the case. The fix is to wait.
  19. Indeed suspended for cron, you had 6 jobs. As you're probably aware, the limit is 2 per day. You've been unsuspended.
  20. wolstech

    Password Reset

    You were suspended for spam. Your request over in the Suspended forum has been escalated: http://www.helionet.org/index/topic/21724-suspended-fldstn/
  21. You were suspended for spam. Escalating.
  22. I just used it 20 minutes ago. It does take a minute or two to open sometimes, but I've never had it error out. Try another PC and network connection. It's possible your ISP or PC is to blame.
  23. I'll split this off and escalate it for you. It's likely related to our phishing issue.
  24. You can't. Our system does in fact prevent users from registering with a number as the first character (though numbers can be used in subsequent characters). Someone else tried this a while back. We have over 20000 accounts, not a single one starts with a number.
  25. That explains it. My post was wrong in that case since I'd assumed you'd already changed that password. Marked solved
×
×
  • Create New...