Forum .LRN Q&A: Problem critical with aolserver

Posted by Dario Roig on 10/10/05 08:10 PM

Hi!

We have problems with aolserver, the server crash when the process nsd arrive about 2.5GB of memory.

The log of aolserver "error.log" show this message:
"unable to alloc 2100767 bytes"

The parameters more importants of aolserver are:
"config.tcl"
#----------------------------
# Global server parameters
#----------------------------
ns_param maxkeepalive 0

#modules loaded
ns_param nssock ${bindir}/nssock.so
ns_param nslog ${bindir}/nslog.so
ns_param nssha1 ${bindir}/nssha1.so
ns_param nscache ${bindir}/nscache.so
ns_param nsopenssl ${bindir}/nsopenssl.so
# LDAP authentication
ns_param nsldap ${bindir}/nsldap.so
ns_param nsdb ${bindir}/nsdb.so

#Thread library (nsthread) parameters
ns_section ns/threads
ns_param mutexmeter true
ns_param stacksize [expr 256 * 2048]

# Server parameters
ns_section ns/server/${server}
ns_param directoryfile $directoryfile
ns_param pageroot $pageroot
ns_param maxdropped 0
ns_param connsperthread 0
ns_param minthreads 30
ns_param maxthreads 100
ns_param maxconnections 150
ns_param threadtimeout 7200

The system is composed by two PC:

WEB SERVER
Hw:
AMD Opteron 2p
4GB RAM

Sw:
Linux Debian 2.6.3-1-k7-smp #1 SMP i686 GNU/Linux
Aolserver 4.0.10
TCL 8.4.11
.LRN 2.1

DB SERVER
Hw:
AMD Opteron 4P
12GB RAM
Sw:
Linux Debian 2.6.9 #3 SMP x86_64 GNU/Linux
Postgres 7.4.8

Thanks by read this message
----------------------
University of Valencia

2: Re: Problem critical with aolserver (response to 1)

Posted by Rocael Hernández Rizzardini on 10/11/05 12:24 AM

Hello Dario,
we have experimented the same error. It is supposed to be a problem introduced at tcl 8.4.7 and fixed in 8.4.11. Are you sure you're running tcl 8.4.11?, if you do a:
info patchlevel
in the openacs shell you'll see what version are you running.

Anyway, is your system using the whole 4GB of ram when it crash?

Also, be sure to upgrade your drivers: openssl & oracle to the latest version, since there are known memory leaks on them.

I think will be best if you post this at the aolserver list.

3: Re: Problem critical with aolserver (response to 1)

Posted by Alfred Essa on 10/11/05 03:04 AM

Dario, Are you still having problems?

4: Re: Problem critical with aolserver (response to 1)

Posted by Dario Roig on 10/11/05 03:11 PM

Thank you for your quick answer!

I'm sure we are tcl.8.4.11, the last version nspostgres-4.0 and OpenSSL 0.9.8 05 Jul 2005.

We have sent un mail to listserv.aol.com, Dossy Shiobara recommends us put "maxkeepalive 0" but the problem not resolve
http://www.mail-archive.com/aolserver@listserv.aol.com/msg09377.html

We this afternoon Aolserver is compiled for 64 bits
in one 64 bits platform.

Thanks.

5: Re: Problem critical with aolserver (response to 1)

Posted by Rocael Hernández Rizzardini on 10/12/05 06:40 PM

Dario,
please keep us posted through this thread about your progress on this issue.

6: Re: Problem critical with aolserver (response to 1)

Posted by Andrew Grumet on 10/14/05 04:33 AM

If all else fails, you might benefit from restarting the server at regular intervals, ideally when traffic is at it lowest (e.g. overnight).

7: Re: Problem critical with aolserver (response to 1)

Posted by Dario Roig on 10/24/05 09:48 AM

Hi!

The problem with the limit memory of process nsd is solved in the O.S. 64 bits.

$ uname -a
Linux borrador 2.6.8-11-amd64-k8-smp #1 SMP Wed Jun 1 00:01:27 CEST 2005 x86_64 GNU/Linux

Bye.

8: Re: Problem critical with aolserver (response to 1)

Posted by Dario Roig on 10/24/05 09:56 AM

New values in the config.tcl:

#----------------------------
# Global server parameters
#----------------------------
ns_param maxkeepalive 0

#Thread library (nsthread) parameters
ns_section ns/threads
ns_param mutexmeter true
ns_param stacksize [expr 512 * 2048]

# Server parameters
ns_section ns/server/${server}
ns_param directoryfile $directoryfile
ns_param pageroot $pageroot
ns_param maxdropped 0
ns_param connsperthread 0
ns_param minthreads 35
ns_param maxthreads 40
ns_param maxconnections 100
ns_param threadtimeout 3600