Re: [cobalt-developers] Re: Good 'ol CASPENG?

[Skyhound Internet <tom@xxxxxxxxxxxxxxxxxxxx>]

Everything that Chris said is exactly what was happening to me with one 
exception.

I checked the GUI and the ASP setting "Use administrative server" was
OFF. I never even tried to check it from command line since I saw caspeng
was running.  Doh!

So, after trial and error I found out that when it's OFF, and I called
up a web page that had .asp in it, caspeng would run and go to 100% CPU.
I turned on the Administrative Server and did the same experiment,
caspeng started up and used about 0.8 of CPU.

So, I have no idea how or why ASP shut itself off, or why if it's off
it should even do this, but the problem is temporarily solved.

It may have been a fluke, since this didn't work with Chris, but right
now I'm keeping my fingers crossed, something I am forced to do often
with a Cobalt.

Tom Hanberg
Skyhound Internet
Long Beach, CA

-------Original Message-------

From: cobalt-developers@xxxxxxxxxxxxxxx
Date: Wednesday, September 03, 2003 7:08:48 AM
To: cobalt-developers@xxxxxxxxxxxxxxx
Subject: [cobalt-developers] Re: Good 'ol CASPENG?

I have seen caspeng go weird. Everything is running along fine, and
then something happens. From that point on, ASP does not work. Hitting
a simple page (that worked fine before) no longer works; one caspeng
process will be running at 100% CPU and no ASP pages come up. If you
kill the one CPU hog process, you'll get:

HTTP Error 507

507 Unexpected

The Web server encountered an unexpected error while communicating
with the ASP service.

Please contact the server's administrator if this problem persists.

from the web server. Restarting the ASP service, or even ASP & Apache,
does not help (even for the first hit on a simple site). Sometimes it
will just start working again on its own.

While I was typing this, one of our 550s (the one that sees this often),
just went through a period with this problem. ASP had not been working
since late last night, and one caspeng process was running at 100% CPU.
Multiple attempts at restarting it did not help, but then one more try,
and voila, it is now working.

There is definately a problem there somewhere, but I sure as hell won't
pay Sun $95 just to report their bug to them (already tried that for one
bug and they just told us there wasn't a problem - I guess we just have
to reboot some of our servers on a regular basis for no reason).
--
Chris Adams <cmadams@xxxxxxxxxx>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.