Tony

We will be updating the Mercury server kernel to the latest version on Monday October 6th at 10:00am EST. We estimate this will result in about 10 minutes of down time while the server reboots. Keeping kernels up to data is a necessary step in order to stay on top of performance improvements as well as have the latest security fixes. Date: 10/06/2008 Start time (EST): 10:00am End time (EST): 10:30am Duration: 30 minutes Estimated Down Time: 10 minutes

We will be updating the Mars server kernel to the latest version on Monday October 6th at 9:30am EST. We estimate this will result in about 10 minutes of down time while the server reboots. Keeping kernels up to data is a necessary step in order to stay on top of performance improvements as well as have the latest security fixes. Date: 10/06/2008 Start time (EST): 9:30am End time (EST): 10:00am Duration: 30 minutes Estimated Down Time: 10 minutes

There is really no way this thing is going to ever be server friendly. Every time you check if a url still works it's intensive. You run it on 1000 topics a day that's quite a bit. This only gets worse as you add more topics. So just to make things clear the intensiveness is the portion where you need to see if the url is still working. fopen, curl doesn't matter. They're all costly when you go outside onto the internet.

There is no simple fix to a system like this. Lets say you have 10,000 threads each with just 1 outside link to be checked. That turns into 10,000 outgoing requests. So doing it daily that is 10,000 requests via curl each day. It's pretty much a proxy which we do not allow due to the CPU and bandwidth they use. The script itself is pretty flawed. It just runs continually and it's way of reducing it's load is sleeping itself. This is not going to stop the fact the process is sitting there and still using CPU time and memory. An ideal system would be one that stores last checked thread and is ran every few minutes. This way it's not sleeping and it runs then is killed. That's a complete re-design of the system in order to make it more reasonable. It's one of those scripts where it's advantages do not outweigh it's disadvantages.

Just for future reference for anyone asking the same questions 1) Accounts are usually setup within a few hours 2) Shared hosting accounts must change their name servers to ns1.hawkhost.com and ns2.hawkhost.com 3) It's not down just our operators are unavailable.

Extra FTP accounts require @domain.com. Your original cpanel account work with just the username.

Right now it's 1.6. But we try to run the newest stable version at all times. So if you need stability and don't want things breaking out of nowhere it's best to upload your own. The use of our include is great when you're just using it for development.

The server has Zend framework installed at /usr/local/lib/php/Zend I'm not sure what server you're on so I cannot check it's setup to see if that's the case. I checked one machine and it had the feed portion installed.

Sounds like some sort of issue with your jailed shell as a command like mkdir should work. I would advise you make a ticket and provide the login details to your account so we can confirm and figure out why it's not letting you even create a directory.

We send you an email with this information. If you have not received this your email provider may have flagged it as spam. You'll need to make a ticket and possibly verify who you are then we can send an account information email to an alternate address.

This format should work: 01234567891 If all else fails you could just put this in then make a ticket by emailing sales to explain the situation.

On the login screen are you providing your valid login information then it is hanging? Without more information I would advise you try using http://yourdomain.com/cpanel and seeing if you can login then. If you are still unable to login then please make a ticket and we'll look into it.

It may be our firewall blocking the connection. Can you open up a ticket and provide the IP you're connecting to and we'll take a look.

They will most likely give you trouble about it due to the fact you did not pay for the domain specifically. So you may be out of luck with regards to being able to transfer the domain away from them. Most places should be giving you a way to control your domain, but if they're not that is an instant red flag of a potential lock in where if you attempt to move hosting they keep your domain. If they refuse to give you access you could try going above them as they're most likely not an accredited domain registrar. Which means they are paying someone else for the right to sell domains. So you contact who they're purchasing the domains from and they may just give you access to the domain.

The simplest solution is to have the public_html be something like main.whateverdomain.com or something that is not the actual site maybe yourname.oneofourdomain.com. Then make an add-on domain point to the folder which is the actual domain. You'd need to make a ticket to set this up as you'd need a primary domain change.

Sounds like an issue you'd need us to solve. Looks like you have made a ticket about it so we'll resolve it there. As far as some suggestions for anyone in the future. It's always a good idea to logout and log back into cPanel some times the skin gets messed up. Other than that not much I can suggest as I do not know the cause of the problem at this point in time.

There is nothing you can really do wrong. If it's not working it may be an issue with cPanel. I would make a ticket outlining the user you're trying to attach and to what database so that we can take a look.

All our servers have at least 100mbit which is about 12.5Mbytes/sec. We do not limit the speed of sites. The limiting factor for users is latency and actual speed of their connection. So more users on is not going to make things suddenly slower unless you were maxing out 100mbit which you probably can't do when people are browsing a forum.

Best to make a ticket about this. I cannot really say why you cannot connect without more information. Usually it's firewalls so you can use ipaddress/cpanel for the url instead and it'll use a proxy if you cannot connect.

If you are on a shared web hosting account you will need to make a ticket requesting us to make the change for you.

For questions like this it would be best to make a ticket. As for an answer to this well I frankly am not sure. We do not specifically set any limits but there can be limits on the other end which I imagine would come into play first. So sending a 50MB attachment would probably work although it would not be ideal for example.

They post on a ton of forums with various IP's and dozens of emails and such. Plus we cannot go banning free emails lots of people use them. This guy comes around every few months it's fine it's a quick ban anyways.

The domain transfer might be an issue as you need access to it at the odld registrar still in order to transfer it. I'd check a site like whois.sc to see if it's even active still. As far as the username we use the first 6-8 characters of the domain. We can change the username upon request however (preferably via ticket right after you make your order)

mod_rewrite is on all our servers.

I usually delete them before anyone replies to the thread. This guy has spammed here several times with various url's and he'll be back again.