William Scott Jordan schrieb:
Hey all!
I've had a few times recently where AOLserver has crashed under high
loads. Each time, I see a line in the logs that looks something like
unable to alloc 4895393 bytes.
What was the size of AOLserver before the crash (most likely around 2GB)?
What is
Hey all!
I've had a few times recently where AOLserver has crashed under high
loads. Each time, I see a line in the logs that looks something like
unable to alloc 4895393 bytes.
Any guesses on what's causing this?
-William
--
AOLserver - http://www.aolserver.com/
To Remove yourself from
On 7/1/09 12:54 PM, William Scott Jordan wrote:
I've had a few times recently where AOLserver has crashed under high
loads. Each time, I see a line in the logs that looks something like
unable to alloc 4895393 bytes.
Any guesses on what's causing this?
Got Tcl code that invokes [exec]
Verschickt: Mi., 29. Okt. 2008, 12:26
Thema: Re: [AOLSERVER] AOLserver Crash!
Hello,
From my experience, I think the problem may be related with the 64 bits.
I've servers with AOLServer 32 bits, and AOLServer 64 bits, and I have
seen 64 bits growing faster in memory (and even
Rami Jadaa wrote:
So any idea what could be there in nsmysql that would crash AOLserver?
Are you using the latest nsmysql (CVS HEAD)?
Can you get a core dump from the crash and a gdb backtrace?
--
Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/
Panoptic Computer Network
documentation, the current release is v45_r0 , I
think. .
good luck,
Bjoern
-Ursprüngliche Mitteilung-
Von: Juan José del Río [EMAIL PROTECTED]
An: AOLSERVER@LISTSERV.AOL.COM
Verschickt: Mi., 29. Okt. 2008, 12:26
Thema: Re: [AOLSERVER] AOLserver Crash!
Hello,
From my
Hi Scott,
Thanks for your reply.
I don't think that I can send the log as it will be so big , as AOlserver
initiates and load a lot of ACS code...
And for the checksum, we did the following:
Using pound, we shifted the load going to this webserver to another server
on another machine where it
It appears that you have the same problem in all of your servers; the
goal is to find out what part of the code is failing and under what
conditions. Three things stand out: failed servers are under a heavier
load than those that don't exhibit the failure; the failure happens
shortly after
Hello,
From my experience, I think the problem may be related with the 64 bits.
I've servers with AOLServer 32 bits, and AOLServer 64 bits, and I have
seen 64 bits growing faster in memory (and even not decreasing through
time), until it takes a considerable amount of memory (then I have to
Hi Juan,
That's a good point. I noticed Rami was hosting on 64 bit AMD systems
and it is possible that if he were running on a 32 bit architecture
the problems he's experiencing might not surface. This could mean a
problem with Tcl on 64 bit or something specific to AOLserver. I
suspect
Rami,
it looks to me as if the problem is due to a c-extension you are using
and happens after a thread exit. When a thread exists, it frees among
other things the associated tcl interpreter. At this time, all c
extensions have to unload cleanly as well. Note that ns_eval creates
and destroys as
Hello Everyone,
We are running multiple instances of AOLserver on different machines, and I
am enjoying the reload functionality to reload the proc libraries using
ns_eval source {fileName} in each one of them...
However, one of the AOLservers crashes after few minutes from the reload.
The
Rami,
Tcl is attempting to create a new hash table entry on a hash table
that was either never created or was created but has ceased to exist
-- most likely the pointer to that hash table is null or corrupted.
This could be something in AOLserver that uses the Tcl_Hash* API.
First steps:
On Sunday 21 January 2007 23:20, Brett Schwarz wrote:
That's funny actually...I just changed a bunch of these cases in a Tcl
extension I help maintain, just earlier today. I happened upon this post
that talks about it:
http://sourceforge.net/mailarchive/forum.php?thread_id=30611212forum_id=43
I have been getting some crashes in AOLserver (current cvs version).
AOLserver doesn't exit, but prints the following and stops responding:
'Tcl_SetBooleanObj called with shared object'
Here is a tcl page which exposes the behavior:
---
# Script to expose bug with ns_atclose/namespace
Okay, some more info on this.
ns_atclose has been changed in some strange ways.
First it now requires that you are in an open connection to invoke ns_atclose.
ns_atclose used to execute in scheduled procs, which makes sense so that you
can use one method to clean up stuff in case of errors.
I found the following change fixes the bug:
in nsd/tclresp.c, line 840:
static int
Result(Tcl_Interp *interp, int result)
{
/* Tcl_SetBooleanObj(Tcl_GetObjResult(interp), result == NS_OK ? 1 : 0); */
Tcl_SetObjResult(interp, Tcl_NewBooleanObj((result == NS_OK ? 1 : 0)));
return
of the aolserver code for these
occurances.
--brett
- Original Message
From: Tom Jackson [EMAIL PROTECTED]
To: AOLSERVER@LISTSERV.AOL.COM
Sent: Sunday, January 21, 2007 7:17:41 PM
Subject: Re: [AOLSERVER] AOLserver crash related to ns_atclose and namespace
commands
I found the following
18 matches
Mail list logo
