|
|
Posted by Joshua Ruppert on 07/26/06 03:28
Chung Leong wrote:
> Joshua Ruppert wrote:
> > The root cause of the problems seems to be the response time of the DB
> > servers but I'm not certain. When the database servers became loaded,
> > the PHP processes seemed to hang while waiting for the database to
> > respond. Eventually this effected each of the PHP processes started by
> > FastCGI, completely taking down the site.
>
> Hmmm. What's the database server? Maybe a script has left a transaction
> open by accident?
There are four Microsoft SQL Server 2000 servers running behind a
single IIS page server.
As for an open transaction, that was my first thought too. I've
systematically check for and clean up open transactions before each use
and then at the end of each script. I did that because it was easy to
do a global search and replace on the open transaction statements.
> > The only way I found to restart the PHP processes is to reboot the
> > machine, because task manager did let me kill the processes that were
> > started by FastCGI.
>
> Sort off topic, but I think you'll find the kill util in the Windows
> Resource Kit quite handy for situations like that.
Thanks for the tip, though do you think FastCGI would respond properly
to a process being killed through the back door like that, and replace
it properly?
Navigation:
[Reply to this message]
|