My webware servers were dying, too, without a mention of it in the
error logs, and only when I wasn't watching. It turned out that I had
a stack size limit, too, of 24K and my server was slowly growing in
size (I have a bug somewhere that I haven't found yet). And, if my
pages ever raised an exception when it was over the limit, I would get
a segmentation fault because webware would try to do its pretty
traceback page, but the gc module (garbage collection) would just die
with an Out of Memory error. I was finally able to catch the server
doing it and see the traceback and also using gdb was able to see that
the gc module caused the seg fault.
--Tracy
On Saturday, January 25, 2003, at 06:29 PM, Ben Logan wrote:
> Thanks to everyone for your responses. I do have cron access on the
> server, so I'll give that method a shot. I hadn't considered that
> appserver might be dying because they've limited my cpu time, so I ran
> 'ulimit -a' on the server, and my cpu time is unlimited. However, the
> stack size is limited to 8192Kb. I wouldn't have thought that I would
> be using that much stack with my application, but maybe that's the
> problem.
>
> Thanks again,
> Ben
>
> --
> Ben Logan
> Google Answers Researcher
> answers.google.com
> When you're searching for information, Google Answers.
>
> Nothing motivates a man more than to see his boss put in an honest
> day's work.
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Webware-discuss mailing list
> Webware-discuss@...
> https://lists.sourceforge.net/lists/listinfo/webware-discuss
>
|