Krydos

Just post here, or create a new topic if you're curious how your load stands after you've made some changes.

Here is your load and memory usage for the past week as a rank of all accounts on your server. The smaller the number the higher the load, and the more likely you are to get suspended. * means negligible cpu or memory usage. date cpu mem 2015-02-03 2 8 (suspended for about 40% of the day) 2015-02-02 6 10 2015-02-01 10 19 2015-01-31 * * 2015-01-30 * * 2015-01-29 * * 2015-01-28 * 35 According to the logs /home/epicaleb/public_html/hostedapp/SocialNotify/feedFetcher.php might be causing most of your load.

Thanks for noticing this and letting me know about it. Whenever I write a script that has as much power as suspending an account automatically I test it very thoroughly. This cron script I actually started writing in March 2013. After almost a year of using it manually, and verifying the results to be legitimate I automated it on January 18th 2014. Still I continued to manually check the accounts it was suspending from time to time, and it has never once bugged out or done anything unexpected. Until yesterday. My profuse apologies to the 51 accounts that were suspended for overuse of cron between 4:09 am, and 4:28 am. I suspect at least a few of them did actually exceed the limit of two, but just to be safe I have already unsuspended them all. I have already fixed the automatic cron suspension script, and this shouldn't happen again. Obviously after almost two years of thorough testing it was a bit of a fluke for this to happen.

I don't see an account with that username or that domain on any of the servers. When you create a hosting account on Heliohost you should get two emails. The first just lets you know that your account has been added to the creation queue, and then the second lets you know the outcome of the creation attempt. If there is a problem creating your account the second email will contain an error message. Did you get either email? If so what is the error, or does the second email say the account was created successfully? Either way I would recommend creating your account again by visiting http://www.heliohost.org/home/signup

Does it work now?

/tmp cleaned and the abusive account suspended.

Here is the report we received regarding your account: We have received a complaint about your account. Please investigate and fix within 24 hours. Hurricane Electric Abuse Department support@he.net From scomp@aol.net Sat Dec 13 14:39:01 2014 Return-Path: <scomp@aol.net> X-Original-To: report@abuse.he.net Delivered-To: report@abuse.he.net Received: from smr-m2.mx.aol.com (smr-m2.mx.aol.com [64.12.232.218]) by abuse.he.net (Postfix) with ESMTPS id 1F1EB540302 for <report@abuse.he.net>; Sat, 13 Dec 2014 14:39:01 -0800 (PST) Received: from scmp-m004.mail.aol.com (scmp-m004.mail.aol.com [172.29.110.247]) by smr-m2.mx.aol.com (AOL Mail Bouncer) with ESMTP id 7EE97380006C8 for <report@abuse.he.net>; Sat, 13 Dec 2014 17:39:00 -0500 (EST) Received: from scomp@aol.net by scmp-m004.mail.aol.com; Sat, 13 Dec 2014 17:38:55 EST To: report@abuse.he.net From: scomp@aol.net Date: Sat, 13 Dec 2014 17:38:55 EST Subject: Email Feedback Report for IP 65.19.143.2 MIME-Version: 1.0 Content-Type: multipart/report; report-type=feedback-report; boundary="boundary-1138-29572-2659438-25559" X-AOL-INRLY: stevie.heliohost.org [65.19.143.2] scmp-m004 X-Loop: scomp --boundary-1138-29572-2659438-25559 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit This is an email abuse report for an email message with the message-id of E1XzvHW-0003hq-TD@stevie.heliohost.org received from IP address 65.19.143.2 on Sat, 13 Dec 2014 17:35:11 -0500 (EST) For information, please review the top portion of the following page: http://postmaster.aol.com/Postmaster.FeedbackLoop.php For information about AOL E-mail guidelines, please see http://postmaster.aol.com/Postmaster.Guidelines.php If you would like to cancel or change the configuration for your FBL please use the tool located at: http://postmaster.aol.com/SupportRequest.FBL.php --boundary-1138-29572-2659438-25559 Content-Disposition: inline Content-Type: message/feedback-report Feedback-Type: abuse User-Agent: AOL SComp Version: 0.1 Received-Date: Sat, 13 Dec 2014 17:35:11 -0500 (EST) Source-IP: 65.19.143.2 Reported-Domain: stevie.heliohost.org Redacted-Address: redacted Redacted-Address: redacted@ --boundary-1138-29572-2659438-25559 Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <nick@wacc.heliohost.org> Received: from stevie.heliohost.org (stevie.heliohost.org [65.19.143.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mtaig-mad06.mx.aol.com (Internet Inbound) with ESMTPS id 26984700000A6 for <redacted@aol.com>; Sat, 13 Dec 2014 17:35:11 -0500 (EST) Received: from redacted by stevie.heliohost.org with local (Exim 4.80) (envelope-from <nick@wacc.heliohost.org>) id 1XzvHW-0003hq-TD for redacted@aol.com; Sat, 13 Dec 2014 14:35:01 -0800 To: redacted@aol.com Subject: deleteMe has created an account at wacc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes Content-Transfer-Encoding: 8Bit X-Mailer: Drupal From: nick@wacc.heliohost.org Message-Id: <E1XzvHW-0003hq-TD@stevie.heliohost.org> Date: Sat, 13 Dec 2014 14:34:57 -0800 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - stevie.heliohost.org X-AntiAbuse: Original Domain - aol.com X-AntiAbuse: Originator/Caller UID/GID - [40256 32003] / [47 12] X-AntiAbuse: Sender Address Domain - wacc.heliohost.org X-Get-Message-Sender-Via: stevie.heliohost.org: authenticated_id: redacted/from_h X-Source: /usr/bin/php X-Source-Args: /usr/bin/php /home/redacted/public_html/index.php X-Source-Dir: wacc.heliohost.org:/public_html x-aol-global-disposition: G Authentication-Results: mx.aol.com; spf=none (aol.com: the domain wacc.heliohost.org appears to have no SPF Record.) smtp.mailfrom=wacc.heliohost.org; x-aol-sid: 3039ac1addc6548cbf1e1ede X-AOL-IP: 65.19.143.2 X-AOL-SPF: domain : wacc.heliohost.org SPF : none You need to activate her! Follow this link, http://wacc.heliohost.org/admin/people , and unblock. --boundary-1138-29572-2659438-25559-- I can understand why it got reported as spam. "activate her" sounds like a phrase that would be used in a spam email. As a word of warning, I would be really careful sending emails to anyone that actually still uses @aol.com address because either AOL is really crazy about spam or their users report everything they receive as spam. Either way we get a lot of reports from them. Your account has been unsuspended. Please be more careful to not send emails that could be confused for spam.

Phishing accounts cannot be deleted because the data in the account can be used to prosecute the offenders.

Thanks for removing the offending file.

What is the addon domain that you're trying to add? atmforex.what? I can't really add it for you if I have no idea what to add.

We are aware of an issue on the Johnny server causing slow connections or disconnections. The problem will be fixed as soon as possible. We will provide updates as soon as they are available.

Dedicated IP granted.

It looks like java was last installed on your account on August 13th. You didn't use your java a single time, nor did anyone access any jsp pages or servlets on your account over the next month, therefore java was automatically removed on September 13th to make room for people who actually use it. Sorry, but it isn't really fair for all of the people waiting in the queue to be unable to use java when someone who does have java enabled isn't even using it. Unfortunately just having java installed on your account uses up system resources (whether you're actually using it or not) and prevents others from being able to even have it installed. TLDR: Use it, or lose it.

Yesterday your account used 122% more memory than the second highest memory usage account, and was fifth highest cpu usage. The day before that your account used 203% more memory than the second highest, and 112% more cpu load than the second highest. The day before that your account used 198% more memory than the second highest, and 140% more cpu load than the second highest. I could go on and on like this. Basically every day your account is the highest load on the server. Sure, Byron, if you want to unsuspend his account you can, or maybe just make a full backup for him. It's up to you. I don't have any issues with you being the nice guy, but my job is to keep the servers running as well as I can for the other thousands of users and there is no doubt in my mind that the Stevie is much better off without his massive amounts of load and overuse of memory.

At this point cloudflare dns is not available for any domain.heliohost.org type domain, but if you have a .tk, .com, .org, .net, etc. type domain you can use cloudflare instead of the default heliohost dns servers.

Java is not currently installed on the account softlab. You can request java for your account by making a post following the instructions located at http://www.helionet.org/index/forum/74-java-requests/

Stevie is no longer listed in any spam lists that I can find.

Well, as the suspension note said your account was suspended for filling 44% of the /tmp partition. When one user overuses this partition it means that other users and other system services are unable to use this partition because it is full. To prevent an account from continuing to cause a disruption to all the other users on the server the problematic account is suspended until the owner of the account is ready to fix the problem. If the owner of the account fails to fix the problem the account will probably just end up getting suspended again for the same thing. One suggestion on how to fix this issue would be to use a tmp directory in your own account's space such as /home/stamp/tmp instead of the system wide shared /tmp directory. This way if your scripts run wild and fill up all available space only your account will be affected, and you won't end up getting suspended.

Yeah, I've been struggling with a mental block of how to fix the uptime with the Heliohost nameservers for a long time. Many thanks to Ashoat took a look with fresh eyes and fresh error logs that were being emailed to him that I didn't have access to. In simple terms it was the monitoring process that is responsible for keeping the nameservers online that ironically was causing the nameservers to be offline so often. It's like saying you need to go down if you want to go up, or turn left to go right. It just didn't occur to me because it was such an illogical solution. Anyways, ns1.heliohost.org should once again have nearly 100% uptime, and ns2.heliohost.org should have better than 0% uptime as it has for the last several months. This should solve your issues of setting your nameservers on your registrar. Let us know if you need any further help.

First of all sorry for not getting back to you sooner. As wolstech said I usually try to check in on the forums at least every other day, but I've been very busy. As wolstech said that account cannot be unsuspended, and we cannot provide a backup of any of the data on the account because of illegal activity. I have queued the account for deletion and you should be able to recreate your account using your .com domain shortly. It does look like your wordpress site was hacked and that's why you were permanently suspended. It is each users responsibility to maintain the security of your website, and if you use weak passwords or vulnerable software this can happen sometimes. In the future I recommend being a little more vigilant about your security.

Dedicated IP granted. My apologies for the delay.

If you would like to use a different version of Phpmyadmin than what is default in cPanel it is possible for users to install a different version on their account.

/var on Stevie currently has about 2.0 GB of free space, and /var on Johnny currently has about 6.8 GB free. Email on both servers is working for me. Marking solved. Let us know if you're having any other issues.

Standard policy is to suspend all accounts until he chooses one that he wants to keep.

Ok, no problem.