Cleaning up a Prosper Install

aeisn

New member
May 6, 2009
715
12
0
I would post this on the prosper202 forums but it seems like they are pretty much dead.

I have been getting database connection errors whenever I go over a few hundred clicks a day. When I first installed prosper I could do thousands of clicks a day without it breaking a sweat. I want to keep the current links I have set up intact, so a fresh install isn't going to work. What's the best way to go about this?
 


I would post this on the prosper202 forums but it seems like they are pretty much dead.

I have been getting database connection errors whenever I go over a few hundred clicks a day. When I first installed prosper I could do thousands of clicks a day without it breaking a sweat. I want to keep the current links I have set up intact, so a fresh install isn't going to work. What's the best way to go about this?

Sounds like you need to go table by table and import what you need into a fresh install. This could be dangerous without understanding the schema since it would be very easy to inadvertently create a bunch of orphan records.

Could it be you're on a shared server that is getting a little more crowded lately?
 
Sounds like you need to go table by table and import what you need into a fresh install. This could be dangerous without understanding the schema since it would be very easy to inadvertently create a bunch of orphan records.

Could it be you're on a shared server that is getting a little more crowded lately?

I'm on a VPS so it's not a problem with the shared server. I'm just going to do a fresh install, hopefully I won't have to keep doing it everytime I hit 200k clicks though.
 
I read elsewhere that some AMs install P202 in the subdomains of each major campaign they run so they can spread the risk around a bit:
P202.AcaiLander.com
P202.WhiteTeethLP.com
P202.datingsite.com

etc....
 
Thanks, I might do that in the future if this happens again.

Right now I'm having an issue with the fresh install. I get a 500 internal server for every single page. The logs say it's because public_html/index.php is writeable by group, even though the permissions are 644 and it isn't writeable by group. Anyone have experience with this?