[Solved] Tommy unreachable (500 errors)

[DennisF95]

typo in Topic: Tommy unreachable

 

Since I registred, I often have problems reching cPanel, phpMyAdmin, my Site and so on.

It's not occasional, but a dozen times every day. Is this a normal thing, I just have to deal with ?

 

phpMyAdmin error:

Internal Server Error

500

Error ID d8768521b945

 

cpsrvd Server at tommy.heliohost.org

 

 

My Site

 

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

Edited December 4, 2019 by DennisF95

[Sn1F3rt]

You're not the only one reporting this. There have been a dozen such reports already by people on and off Discord, and I myself noted this an hour ago. Sometimes Tommy is stable but of late, his load pushes upto even some 50 or so, with the normal being around 7.

 

I've reported this to Krydos, and I'm sure he'll look into this, when he's online this morning.

[wolstech]

As sohamb03 said, the load keeps spiking and generating 500 errors. It's not even just cPanel that's breaking, the actual websites are going down as well. I'm getting tons of uptime robot emails every day, nearly all for 500 errors on Tommy.

 

It might just be high load due to abuse (DoS wouldn't surprise me considering I banned several phishing sites on Tommy yesterday), but if not, I'm wondering if Tommy is reaching (or over) capacity. You can see the load spikes: http://heliohost.grd.net.pl/monitor/

[Krydos]

The problem was a combination of some high memory usage abuse, and abusing tomcat which also results in high memory usage.

[DennisF95]

It's happening again like last Saturday

I'm really annoyed by those who abuse it. Makes Tommy almost unuseable

[Krydos]

I'm working on making Tommy more stable. It's a balancing act because we want to allow as many accounts as we can, while still keeping performance reasonable.

[wolstech]

Perhaps make Tommy donation-only for a while? That'd cut down on new account load without sacrificing users who already use our other servers and want to move for better performance.

 

Some other ideas:

• Make domains take up to an hour to activate. It's not instant, but still better than Ricky and Johnny at up to two hours.
• Reduce the number of Java slots Tommy has.
  • Speaking of Java, with Sparkie around, have we considered building a Java-only server? That'd stop Java load from impact normal PHP users while still letting us offer it. Also, several users have wanted more than one Java app deployed. Perhaps we could offer 1 app for free, and $1/month per app afterwards?
• Turn off metrics processing for some or all of the metrics apps.
• (Very extreme solution...) Swap Johnny and Tommy (i.e. put Tommy on Sparkie and Johnny on Eddie).

[Krydos]

The problem is really just tomcat. My guess is someone's deployed .war is going haywire. Tommy v2 currently has about half the number of java enabled accounts, and yet tomcat is using like 300% more memory than Tommy v1 was using. I'm in the process of writing some tools to monitor java memory usage, and we might be requiring some java users to switch to a VPS if they want to continue hosting their servlet.