Krydos

Are these core dumps still appearing? If so what is the latest date of one being created?

You have to realize that there are two types of load that we monitor: Sustained load (which is what you seem to be describing) and spike load (which is what you were suspended for.) Sustained load is where a site has thousands of visitors per hour and each visitor increases the load they put on the server by a small amount and over time that account ends up being the highest load on the server. You did not get suspended for that. Spike load is where one account causes a lot of load for a brief period of time. Their overall sustained load might be very small, but if that one user single handedly causes the server's load to spike above reasonable levels it still causes downtime and slow response times for all of the thousands of other users. Certain types of scripts tend to cause high spikes of load than others. Any script that uses curl or another function and connects to another server, web proxies, file transfer scripts, scripts that download torrents to the server, etc. The file that caused the spike in load that got your account suspended both times now is: /home1/toast/public_html/toast/index.php Which, unsurprisingly, is a webproxy. First of all webproxies aren't illegal on Heliohost. What is illegal is causing downtime or slow response time for other users. Stevie, as our stable server, is set a little more sensitive on these types of automated suspensions so that we can maintain a high level of service to our users that need reliable uptime, fast response times, and a stable server. Here are some options that you can consider: Stop hosting a webproxy because there are literally millions of free ones available elsewhere on the internet anyways. Only use your proxy when the overall server load is low because it will reduce your chances of being suspended. Use your webproxy whenever you want, and stop caring whether you get suspended for causing too much load with it. Transfer your account to Johnny where your chance of being suspended for high load is much much lower.

Please post the following information: Your cPanel username Your main domain The server that you are on

Does it work now? Please let us know if you receive the signup emails to your hotmail account if it does work.

It looks like your DNS entries dropped out of the system for some reason. I have recreated your DNS records and it should start working again within 24 hours. Let us know if you still can't access your site after 24 hours have passed.

Your account had the third highest cpu usage for today, and second highest memory usage. Yesterday you were second highest cpu usage, and highest memory usage. The day before that you were sixth highest cpu usage, and second highest memory usage. I would recommend looking into ways to reduce your memory usage because that's likely what is getting you suspended. Perhaps something like this can help you http://community.mybb.com/thread-109342.html

Dedicated IP granted.

Yes, you can restore everything on your new account. Like I said in my previous post you have to extract the full backup and find the .sql dumps etc, and then create the new database and import the data, etc. Your home directory is a little easier. You can just upload the compressed home directory file and extract it on the server. If you had any subdomains, addon domains, or parked domains you will need to use the corresponding links in cPanel to recreate them how you had them before. It's not like you just upload the full backup and click a single link and it all restores. You have to do some work to put everything the way it was before.

If windows live is having you set txt records and stuff to verify that you control the domain are you sure the data is the same from years ago? My guess is that windows will generate new codes for you to use. Once you have verified the codes you can post them on this thread. You can create all the record types yourself through cPanel except for the SRV type. I'll do that for you once you have verified and posted the required information.

It wasn't that long ago that there wasn't any way at all for users to deploy war files. Scripts like this have to be tested thoroughly before they can be allowed to run fully automated. You have to remember that you're not the only user on the server, and if the deployment of your war causes high load or crashes the server it doesn't just effect you, but the thousands of other users too. Obviously the plan is to allow users to deploy their own wars eventually, but since only a couple of users have even wanted to deploy wars we are still developing the process for deployment.

Successfully installed KiokuDB-0.56

The changes I made here http://www.helionet.org/index/topic/18019-script-times-out-is-it-possible-to-allow-it-to-run-longer/ will probably help you too.

Alright, is your script working better now?

I have made some changes to the server configuration that should help fix this issue, but it will take some time to become active. I'll post back on this thread once the changes go live.

People have reported that hotmail deletes our emails completely and doesn't even put them in the spam box. That's why that warning is there. Personally I signed up with a hotmail address to create my heliohost account and all the emails go straight to my inbox. Your mileage may vary. You can always change your email address later after you create your account if you're not receiving anything.

There is three steps to setting up a database and user to go with it. Create the database. Create the database user. Grant the user access to the database. It sounds like you did 1 and 2, but not 3. Visit http://johnny.heliohost.org:2082/frontend/x3/sql/index.html#mysqlusers and try adding user to database.

That IP address is actually still in use by the account jlbrec which is inactive, but has not yet been deleted from our systems. If you would like to reactivate the account and regain access to your dedicated IP you may use this link http://www.heliohost.org/home/support/scripts/renew Sorry for the change in policy, but I no longer check my PMs unless someone specifically mentions that they sent me one on these forums. We find it's best to provide support in a publicly visible way so future users who might have a similar issue can find answers without even having to create a new thread in most cases. Also keep in mind that each user is only allowed to have one account so once you reactivate your old account and have two active accounts there is the possibility that your accounts could be suspended. The solution is to backup and delete everything from your current account and move it to your old account with the dedicated IP. Once you have everything backed up from your new account you may use http://www.heliohost.org/home/support/scripts/delete to delete any active accounts in excess of one that you may have.

Deployed. http://lani1234.heliohost.org/CandC

Just keep in mind that full backups cannot be restored automatically. You have to extract them on your home computer and find all the data you need to restore them on your new account. Sometimes this is a bit confusing for users, but if you post here on the forums we can help you with that too. Admins don't delete your account for you, because you can do it yourself. Once you're sure you have everything backed up and downloaded just visit http://www.heliohost.org/home/support/scripts/delete to add your account to the deletion queue.

Yeah, occasionally this core.##### problem surfaces. While we're looking into how to prevent the core files from being created in the first place it might help you to fix the errors that cause the core files in the first place. All of the core files I found on your account were for the same error: Core was generated by `/usr/bin/php /home/robev/public_html/blog/wp-cron.php'. Program terminated with signal 24, CPU time limit exceeded. This means that wp-cron.php script is running for too long and being killed by the system. If you can find a way to prevent that script from running for so long, or disable it completely it would prevent those core files from being created. Since your account was capped out at 500 MB, I deleted three core files for you and you're currently at 304 MB.

catalina.2013-12-22.log:INFO: The start() method was called on component [standardEngine[Catalina].StandardHost[localhost].StandardContext[/lani1234_TestingWarFileOnHelioNEW2]] after start() had already been called. The second call will be ignored. catalina.out:INFO: The start() method was called on component [standardEngine[Catalina].StandardHost[localhost].StandardContext[/lani1234_TestingWarFileOnHelioNEW2]] after start() had already been called. The second call will be ignored. catalina.out:com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: User lani1234_lani already has more than 'max_user_connections' active connections and a whole bunch of these catalina.out:SEVERE: The web application [/lani1234_TestingHelioWarWithDB] appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it. This is very likely to create a memory leak.

Deployed. http://lani1234.heliohost.org/CandC

Try going to http://stevie.heliohost.org:2082/frontend/x3/sql/index.html and deleting the MySQL user for that database. Then recreate that user, give them access to the database, and update your script to reflect the new password for the user. Let us know if you're still having trouble connecting to MySQL after you've done that.

The brute force protection system detected you attempting to log in with the wrong password many times and decided that you were trying to guess the password. Make sure you don't continue trying to log in with the wrong password over and over. I have cleared the blocks on your account and you should be able to log in now. Let us know if you're still having issues logging into your account.

That's kind of weird. Here is what cPanel is seeing: Name Servers ns1.mydomain.com 66.96.142.148 ns2.mydomain.com 65.254.254.172 and some whois tools see that too http://who.is/whois/marionfamily.org I would contact domain.com support (or whoever you registered this domain with) and ask them why the nameservers are showing one thing in some places, and another in other places. It might just be a DNS caching issue, like some DNS is still showing the old data, and some are showing the new, in which case waiting some more might help. You've already waited quite a while though so I don't understand why any old entries would still exist anywhere. Perhaps your registrar has some strange settings or they can help you sort this out.