[wp-hackers] Problems ?

[Jason Hoffman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mar 6, 2005, at 2:57 PM, Podz wrote:

> A couple of days ago, Shadow got dropped by Lunarpages
> http://shadows.os42.com/2005/03/04/you-never-know-what-is-around-that- 
> next-corner/
>
> Today, two more users with issues:
> http://wordpress.org/support/topic.php?id=26372
>
> Another user saying their site is slow:
> http://wordpress.org/support/topic.php?id=26396
> and there are a few more:
> http://wordpress.org/support/search.php?q=slow
>
> Does this need some good looking at ?
> The problem from a support pov is that we can't really do a whole lot,  
> so the posts sit around gathering only attention, not solutions and if  
> this is potentially a problem.....

I have a number of people that have come to TextDrive after getting the  
boot from lunarpages and a couple others, and they are all Wordpress  
users. Then when they came here there were some initial issues, and  
what they always involved was corruption of the comments table after a  
particularly bad onslaught (these people found relief behind  
mod_security and some other stuff). The other problem they had where  
post tables that had to be repaired.

So this problem of load shows up with WP when tables go bad AND they  
are running under php-cgi (notice that the data in all those support  
forms are /usr/bin/php ...). Once they had been here a few weeks and we  
were running regular repairs on their tables, it seems to even  
themselves out

The other thing to note is that of the dozen people I've seen have this  
happen to them (WP user > load bad > gets boot from lunarpages or  
similar crap host > we see that their post table needs to be regularly  
repaired) all them them were posting over xml-rpc with external  
editors. I would see some post and then the table would go bad, so  
code-wise that might be somewhere to look if there's any indication  
that it's a potential wordpress issue.

- - Jason

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBQiuUx1UyB+ajXkCLEQLrWACgqvCMNaxzMAbUL4cwXnZnWsZGCTAAn1LB
RqQjRIXLOPtCMJ4eX7v25g7d
=Z0Yr
-----END PGP SIGNATURE-----