In our case memory seems alright, and the webserver outputs HTML documents just nicely, as if nothing ever happened........ But if you look closer, there're 5 or more CSPnsd processes running at the same time and no response when a csp is requested!
Also, I heard the Linux cron hangs as well......could the two be related? "Nuno Canas" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I had similar behaviours, even cache consuming 98% of cpu because of > some "bug" or bad coded csp. > There are some processes known in unix as "runaways" that never stop and > keep consuming resources forever. > Depending in what size of shared memory segment you have it's easy to > get out of swap space (another good reason to stop reponding). > If it's CSPnsd YES, it's CSPgateway, if not, if it's cache process it > can be something derived from errors in code that generate a big > pipelining and freeze the machine. > Another interesting point is to check what's frozen: process (user), or > machine (system) and see if you kill the process the machine recovers or > not. > > Nuno > > Denver Braughler wrote: > > > Nuno Canas wrote: > > > >>You're saying it's CSPGateway, so is it CSPnsd daemon that is frozen !? > > > > > > When there are crashes, odd and apparently unrelated behaviors can arise. > > I had trouble with Studio and Terminal pursuant to a crash during a CSP. > > Terminal would appear fine, but freeze up on a HALT. >
