Re: [AOLSERVER] aolserver stalling on me
Hey Dossy and Andrew, thanks a lot for you advice. We changed some parameters in our config.tcl files and it *looks* like everything runs smoothly now. I really didn't want to switch from a debian package to a compiled version of aolserver... we thought we had to. This is what we changed: minthreads 5 maxthreads 20 threadtimeout 3600 20 db connections in main, 15 db connections in subquery and log Thanks again guys :-) David -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] aolserver stalling on me
On Tue, Jan 31, 2006 at 11:23:31AM +0100, David Kuczek wrote: thanks a lot for you advice. We changed some parameters in our config.tcl files and it *looks* like everything runs smoothly now. I really didn't want to switch from a debian package to a compiled version of aolserver... we thought we had to. Tsk, Debian aolserver is PERFECT. :-P -- Francesco P. Lovergine -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] aolserver stalling on me
On Monday 30 January 2006 09:28, David Kuczek wrote: Hi, I just moved an oldschool openacs 3.2.5 site from a compiled version of aolserver 3.oldschool to 4.0.10. I am running Debian 3.1 and used the debian package. I have three sites running on openacs 3.2.5 on that server and *only* one is stalling on me once a day while somebody requests a page. They all use the same installation of aolserver. The other two sites work flawlessly. I cannot see any regularity in aolserver's behavior besides it being *around* once a day :-( I checked the log file, the error file and they showed nothing extraordinary. I can even ping the site that stalled but I can't access it over a browser. Any advice? what happens when you telnet? Do you connect, or what? $ telnet example.com 80 Trying 127.0.0.1... Connected to example.com. Escape character is '^]'. (Then type in -- GET /test HTTP/1.0 Host: example.com Returns what, if anything... or stops where? tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] aolserver stalling on me
On 2006.01.30, David Kuczek [EMAIL PROTECTED] wrote: I just moved an oldschool openacs 3.2.5 site from a compiled version of aolserver 3.oldschool to 4.0.10. I am running Debian 3.1 and used the debian package. I have three sites running on openacs 3.2.5 on that server and *only* one is stalling on me once a day while somebody requests a page. They all use the same installation of aolserver. The other two sites work flawlessly. I cannot see any regularity in aolserver's behavior besides it being *around* once a day :-( I checked the log file, the error file and they showed nothing extraordinary. I can even ping the site that stalled but I can't access it over a browser. Any advice? Are you thread-maxing? Or, DB pool connection maxing? Do you have the control port (nscp) configured? Can you connect to the control port when the site becomes unresponsive? -- Dossy -- Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] aolserver stalling on me
Thanks for the quick replies :-)
#
Tom: we will try to telnet on the next stall!
#
Dossy:
Are you thread-maxing? Or, DB pool connection maxing?
I am not sure if I know what you exactly mean. I'll just copy here the
appropriate fragments of config.tcl. This is my 3.x config.tcl file
that I also use for my current 4.0.10 aolserver.
#
# Thread library (nsthread) parameters
#
ns_section ns/threads
ns_param mutexmeter true ;# measure lock contention
ns_param stacksize 50
#
# Server parameters
#
ns_section ns/server/${server}
ns_param directoryfile $directoryfile
ns_param pageroot $pageroot
ns_param maxconnections 20
ns_param maxdropped 0
ns_param maxthreads 5
ns_param minthreads 5
ns_param threadtimeout 120
ns_param globalstatsfalse;# Enable built-in statistics
ns_param urlstats false;# Enable URL statistics
ns_param maxurlstats1000 ;# Max number of URL's to do
stats on
#ns_param directoryadp$pageroot/dirlist.adp ;# Choose one or
the other
#ns_param directoryproc_ns_dirlist ;# ...but not both!
#ns_param directorylisting fancy ;# Can be simple or
fancy
#
# Socket driver module (HTTP) -- nssock
#
ns_section ns/server/${server}/module/nssock
ns_param timeout120
ns_param address$address
ns_param hostname $hostname
ns_section ns/db/pools
ns_param main Pool 1
ns_param subquery Pool 2
ns_param log Pool 3
ns_section ns/db/pool/main
ns_param maxidle10
ns_param maxopen10
ns_param connections5
ns_param verbose$debug
ns_param extendedtableinfo true
ns_param logsqlerrors $debug
ns_param driver postgres
#
# Modules to load
#
ns_section ns/server/${server}/modules
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 nsdb ${bindir}/nsdb.so
ns_param nscgi ${bindir}/nscgi.so
Do you have the
control port (nscp) configured? Can you connect to the control port
when the site becomes unresponsive?
We just installed nscp. We will check the control port next time when
it stops responding.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to [EMAIL PROTECTED]
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject:
field of your email blank.
Re: [AOLSERVER] aolserver stalling on me
On 2006.01.30, David Kuczek [EMAIL PROTECTED] wrote: Are you thread-maxing? Or, DB pool connection maxing? I am not sure if I know what you exactly mean. I'll just copy here the appropriate fragments of config.tcl. This is my 3.x config.tcl file that I also use for my current 4.0.10 aolserver. [...] ns_param maxconnections 20 ns_param maxdropped 0 ns_param maxthreads 5 ns_param minthreads 5 Oh, wow, ouch. If you have a long running request -- five of them -- at the same time ... subsequent requests will stall/hang until one of those requests completes. If you haven't already, I'd configure nslog's logreqtime on and look in your access log for any long-running requests. See: http://aolserver.com/sf/cvs/aolserver/nslog/nslog.html?rev=HEAD Are you sure this site will never see 5 simultaneous users at any given time? Hmm. -- Dossy -- Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] aolserver stalling on me
On Mon, Jan 30, 2006 at 08:51:47PM +0100, David Kuczek wrote:
ns_section ns/server/${server}
ns_param maxthreads 5
ns_param minthreads 5
ns_param threadtimeout 120
It is not the cause of your current problem, but a threadtimeout of
120 is very low. Unless you have very special and clear reasons for
choosing 120, try 3600 or even higher.
maxthreads of only 5 is quite low, suitable for a Dev server but NOT
for a busy Production server. This could EASILY be the cause of your
problem.
ns_section ns/db/pool/main
ns_param connections5
Only 5 db connections is also quite low, this could also easily be the
cause of your problem.
Most likely, your stalling is because either all 5 conn threads or
all 5 db connectiosn are tied up. Similar info is available lots of
places, e.g.:
http://openacs.org/forums/message-view?message_id=122020
http://openacs.org/forums/message-view?message_id=105902
http://openacs.org/forums/message-view?message_id=156801
--
Andrew Piskorski [EMAIL PROTECTED]
http://www.piskorski.com/
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to [EMAIL PROTECTED]
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject:
field of your email blank.
