Flush should just clear the template cache. This is often a sign of a permissions issue. In particular, can Apache write to the assets folder?
If you're getting 500 errors you should also be getting useful messages logged by Apache. Could you post the relevant errors? On Aug 18, 11:34 pm, Pete Graham <[email protected]> wrote: > Hi everybody, > > I have a live SilverStripe site that I'm experiencing major problems > with. After the site has been running for a while it starts spawning > multiple httpd processes, some taking up huge percentages of the CPU > (these can be seen using top). The site progressively become more and > more unresponsive returning 500 errors for requests. > > At first I thought this was most likely to be an server > misconfiguration, but the apache setup seems fine. Strangely I've > noticed that running ?flush=1 on the site gets rid off the spawned > httpd processes and the servers response time returns to expected > levels. > > Does anyone have suggestions about what exactly is happening here? > This suggests to me that something is going wrong with the > Silverstripe caching process. Does flush=1 clear just the cached php > files or does it perform other tasks also? > > The site has low to medium traffic and is on fairly hefty dedicated > server so should be able to handle the load easily. > > Any assistance would be greatly appreciated. > Pete -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
