Tony

It sounds like wp-cron is not being run at all. I assume you are receiving traffic to the web site? The fact you visiting pages makes me thinking wp-cron is not running though as stuff just starts showing up when you do. I'm not familiar if there is a setting that would make it not run unless an admin views it or what. I'd probably check the error_log file wherever the wordpress blog is installed as well for errors. You could also prove that it's the wp-cron.php not being run by adding a cron via curl in cPanel and seeing if it resolves the issue.

All the ones you reported were already banned. I just like pro active solutions over reactive ones so going to find a way to stop them. These days it isn't even bots it's real people doing it so the image verifications are not going to stop them.

I'm going to look into a vbulletin plugin to help deal with this or a configuration. We get a lot of bots coming to the forums need a way to make it at least require 5 posts or something to stop the spam. At the very least 5 posts before they can post a url so they're very easy to ban.

The exclamation point image near the top is the report button. Like on posts there is one on the bar there is one in PM's as well.

It would be no different than our shared accounts 99.9% uptime guarantee. We monitor the servers the same and such. All notices are posted as far as maintenance and upgrades and such. The hardware is identical as well 12GB ram 8 cpu cores and such.

It is $100

DOS attacks which are trying to flood out the web server connections our system will start filtering. This type of attack more sounds like they're trying to use up all the CPU by doing all kinds of searches which are different url's. So we'd see lots of usage coming from your site check the traffic see if we can do anything if it's from a few IP's or there is a specific pattern. If it's all over the place then we might just disable access to the site. Though with this type of attack I think you could mitigate it yourself as well by simply denying the IP's doing it. If they're not hitting the PHP pages anymore they're not causing any trouble.

We do payouts to Paypal after you reach the withdrawal amount. If it's a lower amount we can credit it to an account and it could be used to pay for a hosting package or pay for a current one.

Safe in what way exactly? We cannot just sort of out of the blue know it's happening because we'd start filtering legitimate traffic. This sounds like a GET flood of sort if it's one IP easy to stop multiple IP's more difficult have to parse the access logs for a list of IP's doing it. So to answer the question you're not safe in respect to us doing it pro actively all the time. The attack has to start for us to do anything.

Clustering support I doubt will be available any time soon. Their windows version has it where services can be spread amongst multiple servers but nothing for linux. Linux version was developed single server so most services cannot be separated (only dns and mysql). We do help resellers with this to a degree though. You can have multiple accounts and use the name servers for us. So you can operate like you have multiple servers. Of course you need to be able to afford multiple resellers for that to be possible.

I'm too tired I misread what you put I thought it was a single shared account with multiple add-on domains becoming a bunch of accounts on a reseller. Switching a bunch of shared accounts into a reseller is far easier since they are cPanel accounts already can just use transfer tools. So it is possible we do it just need to give us time as it would not be a priority issue. Also one other thing to keep in mind is you're probably across various servers right now. So switching to a reseller is a single point of failure. So that server is down all your accounts with us would be down.

With the reseller it'll allow you to do a separate cPanel account per site. The thing to keep in mind though you'll need to move add-on domains into these cPanel accounts. There is no tool available to do this and we try to avoid doing this because all paths and database names ect. change. So the person running the site is best to do it to avoid problems. No real learning curve though it's like having a bunch of cPanel accounts.

There is no way for you to see if you're hitting it through your cPanel. In shell it won't let you spawn processes and on the PHP side your site will probably slow down. So to answer the second question caching like wp-super-cache does reduce it since it stops serving the pages as PHP thus less PHP processes are required.

We typically have accounts setup pretty fast within an hour but some times there can be delays depending on the time of the order. So if you order 5 hours from now it might be a few hours before it's setup as it be setup around 9am our time (it's 1:30am here now)

At this time it's not possible to do this.

Datacenter Engineers have identified a hardware issue an aggregate switch which provides connectivity to our Titan. To prevent an unplanned outage resulting in significant downtime, Engineers will be replacing the upstream front end aggregate switch during a scheduled maintenance window. During this maintenance, accounts on the Titan server will not be reachable. While the maintenance window is set for 1 hour, we expect no longer than 15-20 minutes of downtime. Data Center Maintenance - FAS05.SR02.SEA01 [12/29/2009] Date: Tuesday, December 29, 2009 (12/29/2009) Start time (PST): 01:00 End time (PST): 02:00 Services affected: Public Network Location: SEA01 Duration: 1 hour

The rebuild has been completed.

The drive has been replaced as this point and is about 70% finished rebuilding.

This has been completed the machine now has an additional 6GB of memory for a total of 12GB.

This window has started the machine will be doing down in 2 minutes to add the additional 6GB of memory.

We have been notified by the raid card on the Marlin server that one of the drives has failed. As a result we will be replacing the today (December 19th) between 5:00PM and 8:00PM CST. This will be a non service impacting maintenance as the server has hot swap capability. Once the drive is replaced the server will have slightly higher i/o wait while the new drive is rebuilding. Date: 12/19/2009 Start time (CST): 5:00pm End time (CST): 8:00pm Duration: 3 Hours Estimated Down Time: None

We run 2.8.6 and no issues here. I imagine the issue is coming from a plugin you're running on all of them. I'd try disabling all plugins then see if the problem goes away.

December 19th between 9:00am PST and 12:00PM PST we will be upgrading the Titan servers memory. We will be adding an additional 6GB of memory to the server to bring it to a total of 12GB. The window is for three hours but we estimate that the machine will be down no longer than 30 minutes. The reason for this upgrade it to bring the memory specification to match that of all our other servers. This will add additional stability and performance to the server as it will have more ram to use for applications and for caching purposes. If you have any questions or concerns about this maintenance window do not hesitate to contact support. Date: 12/19/2009 Start time (CST): 9:00am End time (CST): 12:00pm Duration: 3 hours Estimated Down Time: 30 Minutes

Should not the sub domains are not referenced anywhere on the internet. You could always be safe and 301 redirect your domain so any outside url points to the newdomain2.com Correct they are different sites Should not unless the site is down for an extended period of time.

When I visit that page I get the web site for it. It probably be best to make a ticket and explain the issue better.