wolstech

Yes there is. The server you're on has failed. https://www.helionet.org/index/topic/32759-johnny-backups/

See https://www.helionet.org/index/topic/32442-suspended-ecsa/

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!)

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.

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.

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.

Actually No they won't. They just pile up in the queue. Also, Johnny is closed, only tommy and Ricky are opening at midnight.

Unblocked. It was for failed SFTP logins, so check the password in your ftp client.

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.

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

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.

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.

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/

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...

Glad to hear. Let us know if you need anything else.

This happens every once in a while. Krydos will renew it at some point. Right now we're more concerned with getting Johnny up and running again though, so I'm not sure how fast this will get fixed.

Yes, Johnny is currently down because he keeps crashing. We're working to figure out what is causing this, but as of now, we don't know when he'll be up and stable. He's been up and down a lot over the past 24 hours. http://heliohost.grd.net.pl/monitor/

InnoDB is almost certainly toast. It has a habit of not surviving a single improper reboot let alone multiple. What we do seem to know (or at least behaves like it) is that MySQL is why it's crashing. We can run Johnny as long as MySQL is stopped. We start it, and soon after, MySQL starts beating on the disks. While the disks are being kept busy by MySQL, other things spawn tasks which get allocated memory then just sit there blocked, waiting for the disk that rarely becomes free. Those tasks then pile up since they're completing too slowly or not at all. The server eventually runs out of memory, which just causes it to try to find more disk time to swap out the stalled tasks and make room for new ones, all of which are also waiting for the disk. It then just snowballs until it can no longer find any resources at all due to the massive backlog, at which point it just hangs. What I don't know is why MySQL is using the disk this much...is this normal and perhaps something else finally changed to make the server no longer able to handle the use? Is this a result of damage from an unrelated crash?

Yes.

The server you're on is down. http://heliohost.grd.net.pl/monitor/ We're in the process of identifying why the server keeps crashing...

Johnny is down, so this error is normal. http://heliohost.grd.net.pl/monitor/ We are in the process of identifying why he keeps crashing.

This appears to be a server malfunction of some kind. It says active on my end even though it's clearly not... Your account has been unsuspended.

That account does not exist.

This was sent yesterday...did you not receive it?

It looks like it may have crashed again at this point...http://heliohost.grd.net.pl/monitor/ It turned solid red for the second time and is once again unresponsive...