wolstech

You caused severe high load. I'm going to have this looked into a bit more before we unsuspend it because we'd rather you know exactly what needs to be fixed beforehand. Otherwise you'll just cause a bunch of load and Johnny downtime.

InnoDB is currently unavailable on Johnny due to being damaged. We currently don't have an estimate for when it will be fixed because we're providing our users time to back up their databases while it's in read only mode. The repairs will likely result in some or all of the InnoDB tables being lost. If you really need InnoDB, you'll need to move to Ricky or Tommy. We recommend against using InnoDB if you can avoid it though, it's prone to going corrupt when you do so much as look at it wrong. MyISAM on the other hand takes abuse all day long and keeps chugging away. If you do decide to use InnoDB, be sure to make frequent backups.

Done. You should now be able to log in and your website should start working again within the next 12 hours.

Unarchiving...

Unarchiving...

Your message body was discarded during delivery. Please be aware that our system cannot accept emails containing attachments or images of any kind. What account needs to be unarchived?

That sounds like the software may be too heavy to run here... Let's see what Krydos says.

This is limited to prevent the server from becoming overloaded. A well-written script shouldn't have any issues with the limits we have set. What are you trying to do, and is your script closing your SQL connections when you're done with them?

This is intentionally disabled due to a history of abuse (botnets and copyright infringement).

We're not familiar with that site. You'd need to ask its owner.

You got blocked again. Unblocked. This is likely going to keep happening while we have the firewall configured this way. I'd suggest just trying again later once the traffic from the DoS dies down a bit.

Looking at the firewall IP blocklist explains it...this was a DoS attack.

This one wasn't anything you did, you just happened to connect during an ongoing DoS attack and got stuck in the firewall. Unblocked.

That account cannot be restored because it was deleted for disk space. An invitation has been sent to the email address on file for that account so you can create a new one. We apologize for any inconvenience this may cause.

Deployed. Please note that it may take up to 12 hours for the 404 error to go away.

Looks like load causing apache to die based on the monitor. There's only 4 accounts suspended on Tommy. One account suspended on Tommy is for load (mrj's account, he posted earlier). The others are banned for malware, child porn, and phishing.

That would be this forum. It serves as our support system as well as a place for our users to communicate and knowledge with each other.

It got suspended for high load again. Let's see if Krydos can identify what's causing it for you.

It's sporadic, but yes there does seem to be an issue with tommy's Apache service at the moment. You can see here: http://heliohost.grd.net.pl/monitor/ The issue is being looked into.

That's typically how it gets taken out of read only. The thing is, in our experience, when we do that, MySQL either won't start anymore, or just corrupts everything. In the past, we had to discard the innodb data to get it working again.

You can't. Johnny only supports 5.6. Ricky and tommy offer multiple versions of php. Ricky offers free accounts at midnight UTC every day if you want to move servers. Tommy requires a donation. http://wiki.helionet.org/Moving_your_account

That's why. We have tomcat 7 on Johnny, so that app won't run. You'll need to rebuild it for tomcat 7 if you want to run it on Johnny.

Deployed. http://bfpsw.heliohost.org/JAW/

Deployment did not succeed (hung while starting). Moving so Krydos can take a look at it...

Your message is blank and the IP you posted from is not blocked.