Krydos

Your account was suspended for the following reason: Malware. 1 file(s). Trojan.PHP-43 FOUND That means that there are some malware files found on your account. For your safety and to protect your website from potential further corruption the account has been suspended. To find the infected files we recommend making a backup of your site, download the backup file to your computer, and scan the backup using a reputable virus and malware scanner. If you're having trouble locating the offending files please ask and we can provide more information. If you are you certain that it is a false-positive, we strongly encourage you to file a false positive form here: http://cgi.clamav.net/sendvirus.cgi Your account should be unsuspended now, but keep in mind that this is a temporary unsuspension. You have 24 hours starting at the time of this post to clean your account of any and all malicious files or your account will be resuspended.

Well you didn't tell us your Heliohost username, but if your hosting account username matches your forum account name you typed in http://NetOhms.com/ as your domain. However that domain isn't hosted with us because you haven't set your nameservers to ns1.heliohost.org and ns2.heliohost.org To do this you will need to talk to your registrar, the company you bought this domain from, or log into your account on their website. If your hosting username isn't ezero then you should let us know what username you used.

The system claims we're already using the latest version of postgresql even though there are obviously newer versions available. They must be too cutting edge for our current settings, and they're filtered out. Here are the available versions of pg: pg (0.14.1 ruby x86-mingw32, 0.14.0 ruby x86-mingw32, 0.13.2 ruby x86-mingw32, 0.13.1 ruby x86-mingw32, 0.13.0 ruby x86-mingw32, 0.12.2 ruby x86-mingw32, 0.12.1, 0.12.0 ruby x86-mingw32, 0.11.0 ruby x86-mingw32 x86-mswin32, 0.10.1, 0.10.0, 0.9.0 ruby x86-mingw32 x86-mswin32, 0.8.0 ruby x86-mswin32-60, 0.7.9.2008.10.13, 0.7.9.2008.10.05, 0.7.9.2008.08.17, 0.7.9.2008.03.18, 0.7.9.2008.02.05, 0.7.9.2008.01.28) Starting at the newest and working backwards the first one that doesn't claim postgresql is too old is pg-0.13.1 which is now installed. You should be able to see it in your cPanel under installed Gems.

Deployed. http://infopar.heliohost.org/webCat/

Before you waste a lot of time here setting things up I have to ask, "Have you read the Terms of Service?" http://wiki.helionet.org/Terms Especially this line:

The guide for moving your account between servers http://wiki.helionet.org/Moving_your_account recommends waiting 48 hours between when you submit your original account to be deleted before trying to create the new account. This is because account deletions aren't instantaneous; they can take anywhere from 5 seconds to 48 hours to be fully deleted depending on server load and how many tasks are ahead of your deletion. I have manually verified that your account is fully deleted as of the time of this post, so go ahead and try creating your new account whenever you want. Here is a tool to help you know when sign ups are going to be available on Stevie again http://krydos.tk/sign-up.php Let is know if you're still having issues creating your account.

How long did you wait between deleting your Johnny account and signing up on Stevie?

Perhaps if you explain the situation a little more we can make an exception in the system to allow you and these other people to all have accounts without fear of being suspended. Is this place that you all logged in from a school, a private residence, a workplace, an internet cafe? How do you know these other people? Are they your family members, coworkers, fellow students, random strangers that you've never met before? To me all of the accounts even look exactly the same to me with slight variations of colours and topics so unless you can explain further I am leaning towards agreeing with the automatic system that it is all one person with 9 accounts. Anyways, the account panela has been unsuspended, and the other eight will remain suspended for now pending further explanation.

Your account password has been reset, tested, and emailed to your contact email address. Keep in mind that both the password and your username are case sensitive and must be typed exactly as they appear in the email. Let us know if you are still unable to log into your account.

Your account has been manually unsuspended. If you still see the suspended page then you should try clearing your browsers cache.

Your account is showing up as clean now. Thank you for taking care of this.

I always find it interesting how people never try to fix whatever is causing their account to be suspended until they've used up all of their chances. The reason we give people three strikes is so that they can ask questions or make changes to their site to reduce load or fix whatever the problem is. Maybe I'm mistaken, and you're still not interested in fixing your website. Anyways, within a few seconds of looking at the logs I quickly realized why your simple "website with a form" keeps getting suspended. From midnight PST until the time of your suspension at 9:30am PST your account used almost 300% more system memory than the second highest memory usage account, and not only that but your account was the highest CPU usage over the same period. That kind of resources usage is not acceptable on a shared host. A link to your account backup has been emailed to your hosting account contact email address.

Just go to your request http://www.helionet.org/index/topic/14774-request-for-java-sumer03/ and click Follow in the top right. Then make sure your Helionet account settings are to email you when topics you follow receive replies.

Testing what?

First of all, your account is not queued. If you view http://sumer.heliohost.org/ you should see a directory listing of your public_html folder not the queued page. If you see the queued page try clearing your browser cache. If by "queued" you mean you're waiting in line for Java, then you just need to be patient. Java does not scale well on a shared host so the server can only handle having java enabled on a finite number of accounts at once. There is no set number of accounts that can have java at a time, but rather we have an automated system that monitors the system resources and only allows new accounts to receive java when memory usage and cpu usage, etc are low enough to add another account without crashing the server. That's actually part of the reason that the uptime on Johnny isn't as good as Stevie. If we were to raise the threshold and add java to more accounts then the uptime would plummet even further below the 90% or so that it's hovering at now. If we were to lower the threshold and allow less accounts to have java enabled at once then the uptime would surely raise to 95% or maybe even higher. I think the way we have it balanced now is a pretty decent balance of uptime while maximizing the number of people who can use java at once. The last person who had java installed made their request on January 23rd, and received it on February 11th. That's 20 days of waiting in line. You requested java on February 4th, and have been waiting 7 days, 23 hours, and 18 minutes. It's hard to make predictions of how long you will have to wait, because as long as people are still using java and their account is in good standing they can continue using java forever. Java will be enabled on your account as soon as possible, but there are 20 people ahead of you in line to receive java first. It wouldn't be fair to them to enable java on your account before them since they asked for it first and have been waiting patiently for it for longer than you. Hopefully, this helps you understand. If you have any other questions feel free to ask.

Ok, try it now. Actually using the telnet command on various ports is a great way to troubleshoot services. For instance if you're having trouble with httpd service you could telnet to port 80 to see the raw responses.

Your account is showing up as clean now. Thank you for taking care of this.

The system has automatic protections in place to prevent people from creating a second account when they already have one. Is there any reason you can't host this new site on your account?

Source: http://php.net/manual/en/function.imagegrabscreen.php

Does it work now? Yes.

/home1/hoorkeet/public_html/geonotes/moo/accordion.html /home1/hoorkeet/public_html/geonotes/moo/native.html /home1/hoorkeet/public_html/geonotes/moo/Request.JSON.html /home1/hoorkeet/public_html/geonotes/moo/Sortables.html

The problem was that public_html had been deleted. Once the directory was recreated the 404 error goes away. Also, it should be noted that public_html is automatically created once every 24 hours in the case of accidental deletion, so with time this issue would have fixed itself anyways.

Ok, your account has been whitelisted, so your IP address won't get blocked again for high FTP usage. You can continue your automatic movement detection uploads as they were before if you would like. The reason I asked the additional questions was to make sure you had a legitimate reason to be using FTP so much, which you definitely do. Our apologies for the service interruption you experienced, but there has been an increasing number of users complaining about being unable to connect to Stevie via FTP. In order to counter these errors and slow connections that many are experiencing we are attempting to deny access to the bots and hackers that are trying to gain illegal access to accounts hosted on our servers or just to cause us downtime for whatever reason, and unfortunately your account got caught up by our automated systems.

Hey, the good news is your account has been unsuspended for about 15 hours so far and it hasn't tried to send any emails yet. Perhaps the bot that was abusing vulnerabilities in your code can't find your site because the IP address changed. Now is your chance to get this fixed before they find your site again.

Well, nothing is permanent. You're welcome to delete your current account and recreate it on Stevie, but then it would be suspended with no chance of unsuspension. Even if you're throttled and no emails will leave the server your account attempting to send thousands of emails per hour still causes server load and makes other accounts legitimate emails slower. You've been suspended five times already in a relatively short time period; you should probably consider yourself lucky to have a sixth chance.