Jump to content

wolstech

Chief Risk Officer
  • Posts

    17,048
  • Joined

  • Last visited

  • Days Won

    617

Everything posted by wolstech

  1. The server crashed. See https://www.helionet.org/index/topic/32759-johnny-backups/
  2. There likely will be eventually, but not at this time. Usually we end up offering a tool that emails you a link to an account backup.
  3. The server died. See https://www.helionet.org/index/topic/32759-johnny-backups/
  4. wolstech

    Johnny Backups

    I'd give it at least a few weeks if we rebuild it (accounting for testing time, etc.), less if we somehow magically managed to fix the file system and retain the old Johnny. Account backups will likely be made available if we rebuild, but I don't know much as I'm not the one doing the repairs (Krydos is the expert on the linux servers).
  5. WAR deployment is done from cPanel on Tommy. Check under the Software section for the Java options.
  6. Paypal will do (https://www.heliohost.org/donate/). Post the transaction ID (and an email address to send the invite to if your paypal address is used by that Johnny account), and I'll get the invite sent so you can get back to work.
  7. Right now, nothing. The server died. See https://www.helionet.org/index/topic/32759-johnny-backups/ I'd say odds are good we'll end up making backups for people at a later date, considering Johnny won't stay running long enough for most to back up. On the bright side, we didn't lose the InnoDB data this time around. Johnny has always been known for his lack of stability due to the unlimited accounts we allowed, and unfortunately that poor stability and the related crashes have finally damaged the file system to the point where it won't stay running. It needs to be rebuilt. For reference, this is the third time Johnny has died. The prior two losses were back-to-back disk failures. In contrast, Stevie (Ricky) has died only once (also disks), and Tommy has never died (though we did have to discard his archives because a disk went bad). We operate at a rather significant loss most months as it is, so we can't afford to get more servers, which is why we have to hold fundraisers for things like the NAS and overwork the servers we have to offer what we do. If you want, you can sign up on Ricky or Tommy when they open (be sure to use a different domain/email/username since they're still attached to the Johnny account for the time being). Tommy has the newest and most stable hardware, but is also very difficult to get an account on because everyone wants to use him. You can donate $1 to get an account easily if you want, and it'd be especially appreciated right now since Johnny is what brings us much of our ad revenue, but it's not required as a few accounts are offered for free at midnight.
  8. Your account cannot be unarchived at this time because Johnny crashed. https://www.helionet.org/index/topic/32759-johnny-backups/ (You won't be able to make a backup since the account is archived, though it may be possible for me to send you the archive itself, which is identical to a full backup, I'll look into whether this can be retrieved since it's actually stored on Cody, or if you wish, you can donate and I'll restore your archived account on Tommy instead).
  9. @subodhc: Make the backup when it's up. Johnny comes up for a few hours here and there, so you can make a backup if you catch him while he's online. http://heliohost.grd.net.pl/monitor/ @mover: No data loss (yet anyway). We even managed to get innodb to back up...
  10. Yes there is. The server you're on has failed. https://www.helionet.org/index/topic/32759-johnny-backups/
  11. See https://www.helionet.org/index/topic/32442-suspended-ecsa/
  12. It turns out all these issues are because Johnny is broken. https://www.helionet.org/index/topic/32759-johnny-backups/ "Invalid login" is normal when the server is down. Make a backup as soon as you can (whenever Johnny is up next), then move to Ricky or Tommy. (For what it's worth, both servers by design are much better in performance, stability, and features, so you're going to have a much better time over there!)
  13. I was able to move the account yamutha to Tommy during the brief Johnny uptime today. You may need to flush your DNS and clear your cache to see your site.
  14. Tomcat probably stopped for some reason. It does do that sometimes, and generally restarts on its own if it does. If I had to guess, it happened during that brief red block right after midnight UTC: http://heliohost.grd.net.pl/monitor/ I had a few emails this morning about Tommy being down for ~10m last night.
  15. That's what Krydos is going to do for you When an account sees severe load like this, we like to make sure you to know how to fix it before we unsuspend it...otherwise it'll just cause load again.
  16. Actually No they won't. They just pile up in the queue. Also, Johnny is closed, only tommy and Ricky are opening at midnight.
  17. Unblocked. It was for failed SFTP logins, so check the password in your ftp client.
  18. It's not just MySQL, the regular Johnny file system is corrupt too. Last I heard backups were being made prior to attempting a fix.
  19. That account cannot be unarchived at this time because it belongs to a server that has crashed. We'll unarchive it for you once the server is fixed. Please see here for more information about the crash: https://www.helionet.org/index/topic/32744-2018-05-01/?view=getnewpost
  20. We are unable to transfer accounts that are currently on Johnny because Johnny is down. Would you like a new account instead? If not, you'll need to wait until Johnny is fixed for your account to be moved.
  21. That account cannot be unarchived at this time because it belongs to a server that has crashed. We'll unarchive it for you once the server is fixed.
  22. You're suspended for inactivity, but you won't be able to renew until the server is fixed since it's currently down. See here for the server issues: https://www.helionet.org/index/topic/32744-2018-05-01/?view=getnewpost Once it's up again, you can renew your account at https://heliohost.org/renew/
  23. This is actually one option we're looking at doing to fix it, though we'd just move /var/mysql as opposed to the entirety of /var...
×
×
  • Create New...