Something wrong after 2006-05-12 21:25 (was Re: Weird "memory leak" problem in AOLserver 3.4.2/3.x

It seems, as if all problems are in tcl 8.3.*.
it should be possible to compile aolserver 3.* with e.g. tcl
8.4.13. 
Seems worth a try.

-gustaf

Dave Siktberg schrieb:
> SERVER #1 exhibiting the problem
>
> % info patchlevel
> 8.3.3
>
> $ rpm -qa | grep glibc
> glibc-2.2.4-13
> glibc-common-2.2.4-13
> glibc-devel-2.2.4-13
>
> $ uname -a
> Linux opus 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT 2001 i686
unknown
>
> ns_info version: 3.3.1+ad13 
>
>
> --
> AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email
to <listservlistserv.aol.com> with the
> body of "SIGNOFF AOLSERVER" in the email
message. You can leave the Subject: field of your email
blank.
>   


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
<listservlistserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email
message. You can leave the Subject: field of your email
blank.

Quoting Gustaf Neumann <neumannWU-WIEN.AC.AT>:
> It seems, as if all problems are in tcl 8.3.*.
> it should be possible to compile aolserver 3.* with
e.g. tcl 8.4.13. 

But just a data point from the "not happening
here" side. I have
AOLserver 3.3.1+ad13 servers that are all running fine -
both the ones
that have been long running and those that get HUPed every
morning. 

info patchlevel 8.3.2

AOLserver/3.3.1+ad13 

Code is mostly based on ACS 3.4.10

Linux 2.4.20-29.7.progeny.9bigmem #1 SMP Fri Jan 7 18:08:47
EST 2005
i686 unknown (RedHat 7.3)

$ rpm -qa | grep glibc
compat-glibc-6.2-2.1.3.2
glibc-2.2.5-44.progeny.1
glibc-kernheaders-2.4-7.16
glibc-common-2.2.5-44.progeny.1
glibc-devel-2.2.5-44.progeny.1

My guess was that there was something about the length or
content of
the scheduled procs list, but the server that was just
running a
single file worth of scheduled procs (or rather not running
it)
demolished that theory. 

-- 
Cynthia Kiser
cnkcaltech.edu


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
<listservlistserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email
message. You can leave the Subject: field of your email
blank.

Cynthia Kiser wrote:
> Quoting Gustaf Neumann <neumannWU-WIEN.AC.AT>:
>   
>> It seems, as if all problems are in tcl 8.3.*.
>>     
> But just a data point from the "not happening
here" side. I have
>
> info patchlevel 8.3.2
>   
FWIW, on my boxes where aolserver appears to function
correctly, the tcl 
in the aolserver lib is 8.3:

/usr/local/aolserver/lib/tcl8.3/

On one box I have tcl 8.3.3 installed generally, and on
another 8.4.9 
(as revealed by checking [info patchlevel] from tclsh). But
I presume 
that in both cases, aolserver is still using the tcl in its
lib 
directory, correct? Since [ns_info patchlevel] isn't
implemented in 
3.3.1+ad13, is there some way to tell for sure which tcl
aolserver is using?

Anyway, if it is the case that aolserver is using its own
version of 
tcl, then the "tcl 8.3.x is the problem" theory
wouldn't appear to stand.


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
<listservlistserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email
message. You can leave the Subject: field of your email
blank.

On Thu, May 18, 2006 at 10:03:59AM -0700, Stan Kaufman
wrote:

> On one box I have tcl 8.3.3 installed generally, and on
another 8.4.9 
> (as revealed by checking [info patchlevel] from tclsh).
But I presume 
> that in both cases, aolserver is still using the tcl in
its lib 
> directory, correct? Since [ns_info patchlevel] isn't
implemented in 
> 3.3.1+ad13, is there some way to tell for sure which
tcl aolserver is using?

If all you want to know is the Tcl version AOLserver is
using, it's
trivially easy, just use the Tcl "info
patchlevel" command from inside
AOLserver.

> Anyway, if it is the case that aolserver is using its
own version of 
> tcl, then the "tcl 8.3.x is the problem"
theory wouldn't appear to stand.

All versions of AOLserver 3.3 REQUIRED and shipped with
their own
special version of Tcl 8.3.x.  So unless you took very
special steps
to make it do so, it's very unlikely that your AOLserver is
using any
other version of Tcl.  I tried once to make AOLserver
3.3+ad13 use a
newer version of Tcl - I failed, and I never heard of anyone
else
doing it either.

-- 
Andrew Piskorski <atppiskorski.com>
http://www.piskorski.com/


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
<listservlistserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email
message. You can leave the Subject: field of your email
blank.

>>
> FWIW, on my boxes where aolserver appears to function
correctly,  
> the tcl in the aolserver lib is 8.3:
>

I have a what seems reliable test see if aolserver is
working properly.

copy off your .ini file
modify any Library entries and point them to a new location.
in the new location put a .tcl file that schedules a number
of  
ns_logs some with threading  (I suggest having the procs run
ever  
second or 2 or 3).
also kill any lines that have an auxconfigdir

bring up the new server using your new .ini file

if the logs stop getting written to you know you have a
problem.

----
Zach Shaw
Web Developer, Library and Technology Services
Brandeis University
zshawbrandeis.edu
781-736-4206


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
<listservlistserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email
message. You can leave the Subject: field of your email
blank.

Andrew Piskorski wrote:
> If all you want to know is the Tcl version AOLserver is
using, it's
> trivially easy, just use the Tcl "info
patchlevel" command from inside
> AOLserver.
Right; duh. Thanks. So, the version of tcl my 3.3.1+ad13
sites are using 
is 8.3.2, and they appear to reboot without the VM and
scheduled proc 
problems. FWIW.


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
<listservlistserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email
message. You can leave the Subject: field of your email
blank.

> All versions of AOLserver 3.3 REQUIRED and shipped with
their own
> special version of Tcl 8.3.x.  So unless you took very
special steps
> to make it do so, it's very unlikely that your
AOLserver is using any
> other version of Tcl.  I tried once to make AOLserver
3.3+ad13 use a
> newer version of Tcl - I failed, and I never heard of
anyone else
> doing it either.

I did some googling and it appears you're right.  People
did get 8.4
working with AOLserver 3.4, but not 3.3 ...


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
<listservlistserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email
message. You can leave the Subject: field of your email
blank.