OT: re: Netscape Enterprise Server 3.6

OFF TOPIC

Netscape Enterprise Server 3.6 is no logner a supported product. It hasn't been for almost 2 years now.

The memory leak is a well documented problem. It first reared it's ugly head in 3.4. An attempt was made to fix it in 3.5, which was much worse. 3.6 introduced dxwdog which is supposed to be a watchdog script that looks for this very problem. I suggest looking to that & tweaking.

As a web software developer and engineer, my professional advice to you is to move to a supported platform. Even a move to Apache at this time would be far better in terms of performance and stability. The costs associated with that are labor. There's no GUI to configure Apache unless you use something like Tk/Apache a.k.a. Mohawk.

I suggest this since you mentioned that you are only serving static pages for the most part. If you were using LiveWire I'd suggest looking at Resin.

I know that you're trying to solve what appears to be a simple problem. You are not the first one to attempt this.

Migrate/Update!!

Wait! This isn't a Parachute, this is a Backpack!

Comment on OT: re: Netscape Enterprise Server 3.6

Replies are listed 'Best First'.
Re: OT: re: Netscape Enterprise Server 3.6 by jlongino (Parson) on Aug 09, 2001 at 03:45 UTC
I appreciate your input and I'll certainly look into dxwdog like you suggested as it sounds promising. However, as to being "Off Topic", I thought that it was clearly stated that I was looking for a perl-based solution (a module perhaps) that would facilitate monitoring CPU utilization of a given process. Apparently it wasn't as clearly stated as I thought, for which I apologize. As for upgrading or migrating to Apache, I've already made both those recommendations but I'm not in a position to demand them.	[reply]
Re: Re: OT: re: Netscape Enterprise Server 3.6 by blakem (Monsignor) on Aug 09, 2001 at 09:48 UTC
I don't think gregor42 meant that your question was off topic... As I read it, the answer was marked as off-topic. (i.e. not really perl related) In the same spirit my answer below is probably off topic as well.... In my experience, scripts that automatically diagnose and "fix" a problem (ala bouncing your webserver) are more trouble than they are worth. I'd recommend running a full fledged monitoring program that alerts you whenever a problem occurs. I've had good success with Big Brother but am seriously considering switching over to netsaint. Both systems religiously monitor everything from memory usage, to internet connectivity, to database connectability (sp?). You can also write your own "plug-in" scripts to monitor anything you want. Some have even used this feature to send out stock market alerts, or keep an eye out for cheap airline tickets. While the last two uses are rather esoteric, having a monitoring system that is easily customizable, is crucial to running a high quality internet service. -Blake	[reply]