We had problems with that combination of apache/mod_perl, on solaris 8 as well. We switched to mod_perl 1.25 and that fixed our problems. Since then we have also moved to newer versions of apache. I would build a newer version of apache/mod_perl on one of the systems and then leave the configuration the same. (Assuming you can do that, some work environments are locked down to older versions of software.)
It would be interesting to see what "truss" reported when you hit the server when it was not responding. ----- Original Message ----- From: "Tom Servo" <[EMAIL PROTECTED]> To: "Marc Slagle" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, April 18, 2002 2:14 PM Subject: Re: Solaris 8 lockups > Nevermind about mod_perl version number, looks like we're running 1.24 > > ------------ > Brian Nilsen > [EMAIL PROTECTED] > > On Thu, 18 Apr 2002, Marc Slagle wrote: > > > What version apache/mod_perl are you running? Also, were these intel > > solaris 7 servers or sparc? > > > > > > > We've recently started trying to migrate a number of Solaris 7 machines to > > > Solaris 8, and everything seemed fine for a while. > > > > > > We have each box running its own static, dynamic (mod_perl) and ssl > > > servers, and everything runs fine for 3-7 hours after starting the server. > > > Eventually, however, the mod_perl children just stop responding. If you > > > try to telnet into the port, the connection just hangs why trying to > > > connect...we don't get a refused connection, and it doesn't let you > > > connect to the point where you can issue an HTTP request. It just seems > > > to stop responding and get stuck. > > > > > > Has anyone else run into any of these problems? So far we've had nothing > > > like this happen with Solaris 7 and with Linux, but I can't even think > > > where to start looking on Solaris 8. > > > > > > As a side note, this happened both on boxes that had been upgraded from 7 > > > to 8, as well as boxes that had fresh 8 installs. > > > > > > > > > > > >
