Krydos

Cpu usage = Unlimited on all three servers. If your account starts to cause significant performance degradation or downtime for the other accounts due to overusing the cpu it will be suspended to keep the other accounts online. Memory usage = Unlimited on all three servers. If your account starts to cause significant performance degradation or downtime for the other accounts due to overusing memory it will be suspended to keep the other accounts online. Bandwidth = Unlimited on all three servers. We have multiple accounts that regularly transfer around 100 GB per week each. You probably don't need to worry about bandwidth. Download/Upload speed = I tested it on all three servers, and the lowest I got was 9 MB/s, the highest I got was 31.6 MB/s. It will depend a lot on server load and how much bandwidth other accounts are using. The answer to this question is always Tommy. However free daily signups on Tommy generally fill in 5-10 seconds. So your best bet if you want a Tommy account is to make a donation of $1.00 USD or more to get an invite. Ricky is next best, and Johnny is out worst, slowest, and lowest uptime server. The only reason I can think of where you wouldn't pick Tommy is if you wanted to use Django or Flask with python 2.7 instead of python 3.6. There are very few people which that applies to though.

Create the log file manually, and then make sure the file is writable by other. 777 is a little bit of overkill, but it'll get the job done. If you want the application to be able to create the file itself you'll need to set the permissions on the directory the log is going to be written in to 777 or so. Obviously you can't change the permissions on /home/cridus10/, but you could create a directory like /home/cridus10/javalogs/ and give tomcat the permissions to write to that directory.

Opened.

Nope, I just deleted it as soon as I found the problem, and suspended your account that caused the issue. Off the top of my head I sort of recall it being roughly 50 files totaling a little over a gigabyte of space.

To be completely honest, there are literally gigabytes of logs and they are all a jumble of like 40 different deployed .wars and most of the lines in the log files don't even state which .war they originated from, etc. etc. You're much better off writing your own log files to your own home directory or testing this on your home pc because there's not a lot I can do for you even if I wanted to. That said I found one severe error that MAY belong to your application. I don't even know for sure. I PM'd it to you even though there is a chance it may be private information from someone else's .war. In the future if you can be a little more specific or give me some string to search for maybe.

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

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

Is it working now?

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

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

I'm not sure what you mean by java8. Tommy runs Tomcat 9.0 on Java 1.8. Johnny runs Tomcat 8.5 on Java 1.8. Eventually Johnny will be upgraded to Tomcat 9.0 as well though. EDIT: It looks like you probably mean Java 1.8 not Tomcat 8.0 like I was thinking https://www.quora.com/Do-Java-1-8-and-Java-8-refer-to-the-same-thing

Unblocked. It was because you tried to log in to cpanel with the wrong username and/or password too many times. If you login at https://www.heliohost.org/login/ this won't happen again.

Chart has been installed on Tommy's perl.

It looks like it's working again now. Having one nameserver down generally isn't going to affect the uptime of anyone's website, as long as at least one nameserver is up. The reason for two or more nameservers is to have 100% uptime of a least one of them being up. Having a nameserver down just means that the working nameserver is going to have to work twice as hard to answer all the requests. One of the nameservers going down won't make your site redirect to an old server, unless there is some caching issue going on and you just recently changed to our nameservers. The old wrong cached value should expire on it's own within a day or so. Usually less.

Closing due to inactivity.

Unarchived. Your username had to be changed to nazabal2.

Do you mean Tk::Chart (1.22)

Deployed.

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

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

Yes, reply to this post when you're certain the issue is fixed and I will remove the block preventing your account from deploying a .war. Once the block is removed you'll be able to use the java page in cpanel to deploy as usual.

Please clear your cache.

For the past month or so your .war has been crashing Tomcat on Tommy for everyone. You've caused a very considerable amount of downtime for everyone who uses java on Tommy. The first few times I just assumed was a fluke, and then I upgraded Tomcat to version 9.0 hoping it would solve the issue. After it continued crashing for something like the 10th time I actually put in the effort to troubleshoot the problem. What would happen is after a day or two of running without a restart Tomcat would just randomly go completely unresponsive. It wouldn't even shut down cleanly using bin/shutdown.sh. So I'd have to send it a signal 9 and restart it. The log files complained about running out of memory, but after some research I found that it was more likely it was running out of available threads. I doubled the number of available threads to Tomcat, and it seemed to help. It would take roughly twice as long for Tomcat to crash, but it was still crashing. Then I went through the very tedious task of analyzing the stack trace for thousands of active threads on Tomcat that had been running for over a day, but hadn't crashed entirely yet. What I found was that your .war is creating thousands of threads named pool-512-thread2, etc. and when the system reaches its maximum it shuts down. Just to be absolutely sure it was you causing the issue I undeployed your .war and Tomcat has been running for quite a while now, and the thread count is about 60 rather than several thousand. Please test your .war thoroughly on your home computer to make sure you have fixed the thread bug, and when you're confident you have it fixed let us know and I'll remove the block that prevents your .war from being deployed.

As long as the scripts don't cause a lot of load they should be fine. If you read the link that you posted there is actually 3 scripts. One to start the script that you access with a browser, one to end the script that you access with a browser, and a loop script that you don't access in a browser. If you run the loop.py directly you'll get a 500 error when you browser closes, times out, or the http process kills it, etc. Also I don't see a shebang on your script that you posted. Did you just omit that?

As long as everything goes well it should be installed tomorrow https://www.helionet.org/index/topic/34716-tommy-django-upgrade/