wolstech

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/

Your password won't reset because Johnny is down. We're working to get him running again, though we currently don't have an estimated time when he'll be up and stable again. Johnny has been up and down a lot over the past 24 hours as we try to troubleshoot what's causing him to crash. 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.

Your message's content was lost during delivery, likely because it contained images or attachments. Our system does not accept messages containing images or files.<br /><br />If you need to send an image or file, please provide a link instead of attaching it directly to the email.<br /><br />Please resend your request without images or attachments, or post on our forums for assistance.<br />

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

Johnny crashed earlier and is currently down from load caused by what appears to be a DoS attack. An "Invalid login" message is normal when the server you're on is down.

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

Odds are you just need to clear your cache, not that it'd do much good right now since the server you're on is down (again). The server you picked (Johnny) is the most unreliable and buggy server we have. It's meant for people to play around on, and as such is very unstable and slow. If you need a reliable, proper experience for a production website, we recommend getting a Ricky or Tommy account, both of which can be had for free at midnight UTC every day if you're lucky. We only allow a few new users per day on those servers to prevent them from becoming overloaded (the server you're on, Johnny, is a great example of what happens when we don't do this...). If you can't wait, you can also donate $1 or more and get an invitation for a Tommy account within 24 hours by email.

It looks like Johnny has hung or crashed. We're looking into it.

2FA was removed from deny on Tommy.

Yeah, 2017. Most don't realize that XP POSReady and XP Embedded are still supported until 2020. In fact, if you change a registry setting on a regular Windows xp computer, it will happily utilize the additional 6 years of security updates meant for posready.

They're not. We do install the Centos updates though. If we installed the cpanel uplates as they intended, this service wouldn't function. Cpanel is only meant to handle a few hundred accounts per server. We've customized it to the extent that got 10,000 accounts out of 10 year old hardware...(Johnny), and it's actually stable, provided someone is not abusing the service. Cpanel's own support has even recognized us as one of their most extreme use cases for what we've managed to do with it. Based on their design guidelines, we should have about 20 servers (they recommend about 400 accounts/server). We have 3.

WinXP is also surprisingly popular for embedded devices despite its age...things get installed and never replaced until failure. Vendors also love to crank out the same things year after year in that world despite being obsolete right off the line. Source: Helpe install some brand new control equipment running XP for my job two week ago. :-/ Manufactured December 2017...

Edit: I can't see it under "password & security" It has its own page under Security on the cpanel home page. It's right near the SSL options.

Our custom stuff modifies a bunch of cPanel files and scripts so releases of theirs that reinstall or updates most/all files in cpanel will break the service. Does the LTS version update/replace fewer files per release, or does it still do a mass file replacement every time, but make fewer changes/enhancements? If it only patches a few files here and there as opposed to basically reinstalling it during update, it may be something we could consider for future servers.

Were they Innodb tables? If so, innodb did go corrupt on Johnny again and lost all the data for a second time. You'll need to make a new database and restore a backup. We HIGHLY recommend not using innodb if you can avoid it. We've lost innodb data too many times to count, but have never lost Myisam data in our 10+ years in operation. If you really need innodb, I'd recommend moving to Tommy to reduce the risk of corruption caused by load/server crashes.

Suspended. Thank you for reporting this.

That requires cpanel 68, the newest version we run is 66, and that's on Ricky. Tommy has 64, and Johnny is even older (and can't be updated yet due to the RoR support). We rarely if ever update cpanel because all of our custom stuff breaks when we do. Upgrading cpanel is basically the second most involved thing we can do to just rebuilding the whole server.

Yep, Likebots/follower bots are against our TOS. That cannot be hosted here.

Done. You should now be able to log in and your website should start working within 2 hours.