[AOLSERVER] More with the Chinese translations...
The Java solution is working, but it's kind of slow. I thought I'd give a try to what several of you suggested, namely using Tcl to do the conversion instead. Of course I've run into problems here too... nothing could be easy about this! :) To recap, I'm currently using a translator written in Java, from mandarintools.com. My servlet requests a page from the Traditional Chinese site, setting the charset to UTF-8. It then uses the converter to translate it from UTF-8 to UTF-8S, which is a version of Simplified Chinese that's apparently somewhat obscure, but gives the right results. It is then written out to the client with the charset once again set to UTF-8. All of my attempts to recreate this in Tcl have resulted in garbage. I started out assuming that my incoming data from ns_httpget will be in UTF-8, since the Traditional site is using it and Tcl strings default to that encoding. So I tried set page_body [ns_httpget http://big5.hrichina.org;] set translated_page_body [encoding convertto gb2312 $page_body] ns_write $translated_page_body The outgoing charset is also set to UTF-8, via the old Arsdigita ReturnHeaders proc. But this results in garbage. After messing with this for a while I decided to make sure I could read the page in and spit it back out without error. Nope. encoding system told me that the system encoding is iso8859-1, which seems correct. I've tried all combinations of converting from this, or not, and converting to utf-8, or not, and get garbage no matter what. I've also tried using encoding system to set Tcl's encoding to utf-8, but still no joy. Any suggestions? thanks, janine -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] More with the Chinese translations...
That was what I thought when I first started this, that that would
never work, but so many people have told me since then to try this
that I figured I was wrong. Now I'm not sure what to think!
janine
On Jun 25, 2009, at 5:53 PM, Stephen Deasey wrote:
On Fri, Jun 26, 2009 at 12:04 AM, Janine Siskjan...@furfly.net
wrote:
set translated_page_body [encoding convertto gb2312 $page_body]
This isn't going to work. It's not the encoding of the characters you
need to change but the characters themselves.
You want to do the equivalent of this:
% string map {h H w W} hello world
Hello World
Where 'h' and 'H' are similar, but distinct, letters and the encoding
hasn't changed (happens to be utf8 in my terminal, could be ascii
etc.).
In fact, looking at the source code for the software at
mandarintools.com that's all they're doing. It's a poor quality
conversion, according to what I've read, but if it's sufficient well
hey!
The file hcutf8.txt in the .zip source bundle contains a mapping of
simplififed to traditional characters. The first character on each
line (that is not a comment) is the simplified character, followed by
one or more traditional candidate characters.
You could create a Tcl list in the format string-map is expecting,
with each of the traditional characters followed by the simplified
character. Without using a proxy setup, simply map the
utf8-traditional response body into utf8-simplified and send directly
to the browser.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to lists...@listserv.aol.com
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the
Subject: field of your email blank.
---
Janine Sisk
President/CEO of furfly, LLC
503-693-6407
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
lists...@listserv.aol.com with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject:
field of your email blank.
Re: [AOLSERVER] Diagnosing an AOLserver performance problem
I think you are right, Gustaf - I've given my client a choice of which way to go from here, one of which is to start fixing the code. janine On May 14, 2009, at 12:22 AM, Gustaf Neumann wrote: Janine Sisk wrote: Unfortunately I have no idea; they process their own stats and so far have not shared (I have asked but they keep forgetting). ... With just those changes I'm still seeing the nsd process consume 50% + of the CPU from time to time but it looks like it's happening for a shorter period of time most of the time, so that is at least an improvement. From my experience, you can obtain much more improvement by looking for bottlenecks in the application than by tuning a few parameter in the aolserver configuration. So far, i did not see any case of slow behavior like you are describing attributable to aolserver. Your problem is most likely more an application performance problem than a aolserver performance problem. If you have an application running since several years, it is not unlikely that some tables have grown quite large, such that missing indices and sequentual scans might have become a problem over the years. Furthermore, many OpenACS user don't care much about the performance of scheduled jobs, but these can lead exactly to the behavior you are observing. I would recommend to monitor the behavior more closely, by using e.g. the xotcl request monitor and the aolserver statistics http://aolserver.cvs.sourceforge.net/viewvc/aolserver/aolserver/examples/config/stats.tcl?view=markup Since you seem to run quite an old version of OpenACS: Another option, i would consider is to upgrade OpenACS. We fixed many performance problems over the last years in the base framework. -gustaf neumann -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. --- Janine Sisk President/CEO of furfly, LLC 503-693-6407 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Diagnosing an AOLserver performance problem
Are you referring to Rob Mayoff's threadpool code from 2004? Does it still work in 4.5.1? I'm trying to avoid modifying the code as much as possible; I may get to that point, but I'm trying to exhaust my tuning options first. I have a feeling that once I crack open the cover I'm going to be stuck in buggy quicksand and I'd rather not go there if I don't have to, despite how financially rewarding it would be. :) janine On May 12, 2009, at 3:34 PM, Tom Jackson wrote: On Tue, 2009-05-12 at 22:23 +0200, Gustaf Neumann wrote: Janine Sisk schrieb: When I first started working on this problem, the settings were ns_param maxconnections 5 ns_param maxthreads 5 ns_param minthreads 5 maxconnections of 5 is for most applications to small. The term maxconnections is misleading since it does not mean maximum number of incoming connections, but is a counter per thread, when it will shut down. With the value above, every thread will exit and be recreated after 5 requests. If the application is well written, no garbage should be left after the request, therefore the value can be set to e.g. 1000. This sounds like great general advice. If I had to boil down a few rules, I would say at bare minimum: maxconnections 5 * maxthreads. But 10 to 20 times would be much better. Also, unless you have a memory leaking application, start with a minimum of 100 for maxconnections. You should also be using threadpools. If you don't, then every request gets dumped into a default threadpool that is shared by all virtual servers. What this means is that it is possible for multiple interps to exist in each thread, up to one for each virtual server. At a bare minimum, each virtual server should have its own default threadpool which matches every request to that vs. So the problem with one nsd-process-wide threadpool is the memory footprint of each thread will be at least the sum of each vs interp. Maybe I should point out that one advantage of threads is to reduce the memory footprint by specializing the interp code. If you setup a number of threadpools, you can partition your requests into static and dynamic (at the very least). A few threads can handle many static requests. You should also partition your requests by need run tcl code/filters. Do you want to require filter processing for css and basic image files? Personally I would use a different port for pure static content. I have used publicfile: http://cr.yp.to/publicfile.html but I have heard that AOLserver is pretty fast at static file handling (I'm trying to catch up). tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. --- Janine Sisk President/CEO of furfly, LLC 503-693-6407 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Error after AOLserver upgrade
Thanks Gustaf, that fixed it.
janine
On May 11, 2009, at 9:59 AM, Gustaf Neumann wrote:
Dear Janine,
please check:
http://www.openacs.org/forums/message-view?message_id=488620
The problem was fixed in OpenACS more than 2 years ago.
http://fisheye.openacs.org/browse/OpenACS/openacs-4/packages/acs-tcl/tcl/form-processing-procs.tcl?r1=1.55r2=1.56
Hope this helps,
-gustaf neumann
Janine Sisk schrieb:
Apologies in advance for posting with no research... was just
checking email before running out the door and found an error
report from the client I upgraded over the weekend. When I get
back I will employ The Google and look at the code and all that,
but I wanted to toss this out to see if anyone knew the answer.
This is in the proprietary CMS code that I didn't write, so it's
possible they are doing something that no-one has run into before.
bad variable name af_to_sql(form_name__publish_date): upvar won't
create a scalar variable that looks like an array element
while executing
global $name
(procedure ad_form line 308)
invoked from within
ad_form -extend -name form_name -form {
big snip
---
Janine Sisk
President/CEO of furfly, LLC
503-693-6407
-- AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to lists...@listserv.aol.com
with the body of SIGNOFF AOLSERVER in the email message. You
can leave the Subject: field of your email blank.
--
Univ.Prof. Dr. Gustaf Neumann
Institute of Information Systems and New Media
WU Vienna
Augasse 2-6, A-1090 Vienna, AUSTRIA
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to lists...@listserv.aol.com
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the
Subject: field of your email blank.
---
Janine Sisk
President/CEO of furfly, LLC
503-693-6407
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
lists...@listserv.aol.com with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject:
field of your email blank.
Re: [AOLSERVER] Diagnosing an AOLserver performance problem
/share/share1
ns_param uri /*
# all WebDAV options
ns_param options OPTIONS COPY GET PUT MOVE DELETE HEAD MKCOL POST
PROPFIND PROPPATCH LOCK UNLOCK
#ns_section ns/server/${server}/tdav/share/share2
#ns_param uri /share2/path/*
# read-only WebDAV options
#ns_param options OPTIONS COPY GET HEAD MKCOL POST PROPFIND PROPPATCH
ns_log notice nsd.tcl: finished reading config file.
-gustaf neumann
Janine Sisk schrieb:
Ok... I just upgraded all of the sites on this system.
Things look a bit better, but I still occasionally see an nsd pop
up to 50%+ for a few seconds. It doesn't seem to last as long, but
that may just be because it's Sunday (and Mother's Day in the US),
so traffic is always going to be a bit lighter.
Is there anything else I can try?
janine
On May 10, 2009, at 4:54 AM, Gustaf Neumann wrote:
Janine,
my recommendation is to give aolserver 4.5.1 a try. We had a
similar observation
especially when many connection threads are configured. Depending on
your query-patterns, it might easily happen with earlier versions
that more or less all connection threads will be refreshed
(restarted) at the same time. The more threads are defined the
worse it will become. Aolserver 4.5.1 addresses this problem by
providing a randomization spread.
best regards
-gustaf neumann
Janine Sisk schrieb:
I host a couple of sites based on an old version of OpenACS with
a proprietary (and fairly primitive) CMS. I didn't write any of
it, and up to now have not had to look at things very closely.
But a combination of increased traffic and more stuff running on
the system has made performance problems that were there all
along rear some really ugly heads, and I need to figure out
what's going on.
From watching the output of top I can see that both Postgres and
AOLserver are doing their share of CPU hogging. I've just turned
on log_min_duration_statement in Postgres, to see where it's
spending most of its time. I'm less sure of what to do for
AOLserver. I've increased maxconnections and maxthreads and that
seemed to help a little, but not enough. It has been a long time
since I last needed to tune AOLserver and I'm a bit at a loss.
Any suggestions on where to start? I'd love to know what it's
doing when it suddenly jumps up to using 86% of the cpu, then
drops back to almost nothing again.
BTW, this is AOLserver 4.0.10, with this patch applied:
http://sourceforge.net/tracker/index.php?func=detailgroup_id=3152atid=103152aid=1615787
(it didn't seem to help) I can try upgrading if necessary but
nothing I've read has made me think that 4.5 will give me any
better performance, so for the moment I'm erring on the side of
changing as little as possible.
thanks,
janine
---
Janine Sisk
President/CEO of furfly, LLC
503-693-6407
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to lists...@listserv.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 lists...@listserv.aol.com
with the
body of SIGNOFF AOLSERVER in the email message. You can leave
the Subject: field of your email blank.
---
Janine Sisk
President/CEO of furfly, LLC
503-693-6407
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to lists...@listserv.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 lists...@listserv.aol.com
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the
Subject: field of your email blank.
---
Janine Sisk
President/CEO of furfly, LLC
503-693-6407
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
lists...@listserv.aol.com with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject:
field of your email blank.
Re: [AOLSERVER] Diagnosing an AOLserver performance problem
On May 12, 2009, at 1:23 PM, Gustaf Neumann wrote: Janine Sisk schrieb: When I first started working on this problem, the settings were ns_param maxconnections 5 ns_param maxthreads 5 ns_param minthreads 5 maxconnections of 5 is for most applications to small. The term maxconnections is misleading since it does not mean maximum number of incoming connections, but is a counter per thread, when it will shut down. With the value above, every thread will exit and be recreated after 5 requests. If the application is well written, no garbage should be left after the request, therefore the value can be set to e.g. 1000. Interesting - I did not know that. I don't have much faith in this application to be well written so I haven't made this change yet, but I will try it next. I changed minthreads to 0, which dramatically sped up server restart time, and increased connections/threads first to 50/10 and then 100/20. I didn't see much of an increase in the last change so I left it there. when start with minthreads 5 takes long, you seem to have quite a slow machine. Do you have some usage figures, how many concurrent users you have to serve? By concurrent, i mean running requests at the same time. Unfortunately I have no idea; they process their own stats and so far have not shared (I have asked but they keep forgetting). The system is not the best, but it shouldn't be this bad. I've watched the error log as the site comes up and there is a lot of added stuff going on in the CMS, looks like it's loading in something from the database. It shouldn't be this slow, but I'm leaving delving into the code as a last resort because it looks like quicksand. You can as well increase the threadtimeout to reduce the number of thread restarts ns_param threadtimeout 120 I commented out the maxopen/maxidle and dropped the connections to 20 each. I didn't notice the 300 - that was clearly out of whack. With just those changes I'm still seeing the nsd process consume 50%+ of the CPU from time to time but it looks like it's happening for a shorter period of time most of the time, so that is at least an improvement. Thanks! janine regarding the pools: I would recommend to comment out the maxidle and maxopen values (were needed for old aolserver versions) and - more important - to reduce the number of connections. When you have maxthreads at a low value (e.g. 20), you should not need more than e.g. 20 connections for the first two pools. ns_section ns/db/pool/pool1 ns_param maxidle10 ns_param maxopen10 ns_param connections300 ns_param verbose$debug maybe the 600+ connections you have makes things slower than needed. best regards -gustaf neumann -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. --- Janine Sisk President/CEO of furfly, LLC 503-693-6407 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
[AOLSERVER] Error after AOLserver upgrade
Apologies in advance for posting with no research... was just checking
email before running out the door and found an error report from the
client I upgraded over the weekend. When I get back I will employ The
Google and look at the code and all that, but I wanted to toss this
out to see if anyone knew the answer. This is in the proprietary CMS
code that I didn't write, so it's possible they are doing something
that no-one has run into before.
bad variable name af_to_sql(form_name__publish_date): upvar won't
create a scalar variable that looks like an array element
while executing
global $name
(procedure ad_form line 308)
invoked from within
ad_form -extend -name form_name -form {
big snip
---
Janine Sisk
President/CEO of furfly, LLC
503-693-6407
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
lists...@listserv.aol.com with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject:
field of your email blank.
Re: [AOLSERVER] Diagnosing an AOLserver performance problem
Ok... I just upgraded all of the sites on this system. Things look a bit better, but I still occasionally see an nsd pop up to 50%+ for a few seconds. It doesn't seem to last as long, but that may just be because it's Sunday (and Mother's Day in the US), so traffic is always going to be a bit lighter. Is there anything else I can try? janine On May 10, 2009, at 4:54 AM, Gustaf Neumann wrote: Janine, my recommendation is to give aolserver 4.5.1 a try. We had a similar observation especially when many connection threads are configured. Depending on your query-patterns, it might easily happen with earlier versions that more or less all connection threads will be refreshed (restarted) at the same time. The more threads are defined the worse it will become. Aolserver 4.5.1 addresses this problem by providing a randomization spread. best regards -gustaf neumann Janine Sisk schrieb: I host a couple of sites based on an old version of OpenACS with a proprietary (and fairly primitive) CMS. I didn't write any of it, and up to now have not had to look at things very closely. But a combination of increased traffic and more stuff running on the system has made performance problems that were there all along rear some really ugly heads, and I need to figure out what's going on. From watching the output of top I can see that both Postgres and AOLserver are doing their share of CPU hogging. I've just turned on log_min_duration_statement in Postgres, to see where it's spending most of its time. I'm less sure of what to do for AOLserver. I've increased maxconnections and maxthreads and that seemed to help a little, but not enough. It has been a long time since I last needed to tune AOLserver and I'm a bit at a loss. Any suggestions on where to start? I'd love to know what it's doing when it suddenly jumps up to using 86% of the cpu, then drops back to almost nothing again. BTW, this is AOLserver 4.0.10, with this patch applied: http://sourceforge.net/tracker/index.php?func=detailgroup_id=3152atid=103152aid=1615787 (it didn't seem to help) I can try upgrading if necessary but nothing I've read has made me think that 4.5 will give me any better performance, so for the moment I'm erring on the side of changing as little as possible. thanks, janine --- Janine Sisk President/CEO of furfly, LLC 503-693-6407 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.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 lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. --- Janine Sisk President/CEO of furfly, LLC 503-693-6407 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] More on caching content...
Trying again... anyone??? Bueller? :) I'm getting closer... CacheIgnoreCacheControl helped. There was actually one place in OpenACS that might have been adding the cache-control header (in acs-tcl/tcl/request-processor-procs.tcl) but I commented that out a long time ago and it didn't make any difference. Now, with the CacheIngoreCacheControl directive, the home page gets cached properly. This is progress!! However, dynamic URLs are still not being cached. For example, both of these URLs work: translator.com/gate/gb/traditional-site.com/public/index translator.com/gate/gb?url=traditional-site.com/public/index The former gets cached, the latter does not. The reason for this is that mod_cache doesn't cache URLs with query variables unless either they contain an Expires directive or you turn on CacheIgnoreQueryString. But the latter is rather destructive as it returns the same content for all pages - not what one wants. I went into the OpenACS request processor and added the expires header; you can see it if you telnet to the page, so I know it worked, but it's somehow not making it back to Apache (it's not in the cached headers, and dynamic URLs are still not being cached). Any ideas how a header could get lost between AOLserver and Apache? Oh, and before anyone suggests this I did try adding an expiration via mod_expires in Apache, but that had no effect either. I didn't really expect it to, since that's not the request being cached, but it was worth a try. Thanks for everyone's patience with this mostly-OT topic! janine PS Here's the relevant part of my httpd.conf file: # mod_cache/mod_mem_cache LoadModule cache_module modules/mod_cache.so LoadModule disk_cache_module modules/mod_disk_cache.so IfModule mod_cache.c CacheEnable disk / # seconds (86400 = 1 day) CacheDefaultExpire 86400 CacheIgnoreNoLastMod On CacheIgnoreCacheControl On # seconds (2678400 = 31 days) CacheMaxExpire 2678400 IfModule mod_mem_cache.c # KB #MCacheSize 524288 MCacheSize 262144 MCacheMaxObjectCount 1000 # bytes MCacheMinObjectSize 1 # bytes MCacheMaxObjectSize 524288 /IfModule IfModule mod_disk_cache.c CacheRoot /var/www/cache CacheDirLevels 1 CacheDirLength 4 CacheMaxFileSize 524288 CacheMinFileSize 1 /IfModule /IfModule #LoadModule headers_module modules/mod_headers.so #Header set Cache-Control max-age=999 #LoadModule expires_module modules/mod_expires.so #ExpiresActive On #ExpiresDefault M86400 LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so ProxyRequests Off Proxy * Order deny,allow Allow from all /Proxy #ProxyPassMatch /(.+) http://staging-big5.hrichina.org/$1 ProxyPassMatch /(.+) http://209.162.194.27:8081/$1 On Apr 13, 2009, at 12:47 PM, David Walker wrote: To aid your troubleshooting, I would recommend a grep or other full- text search of the code running on AOLServer to determine if there are any circumstances where it would generate a cache-control header. Your telnet test may not give you all of the data you desire without a full set of headers on the request side. The Tamper Data add-on for Firefox will allow you to observe the interaction (headers and all) between your browser and the web server. The CacheIgnoreCacheControl directive may allow you to force Apache to cache regardless of whether there is a cache-control directive. http://httpd.apache.org/docs/2.0/mod/mod_cache.html Janine Sisk wrote: This is only peripherally related to AOLserver, but there are so many helpful and knowledgeable people on this list, I'm hoping someone will recognize this. I'm still working on that Apache/Tomcat caching thing I wrote about a few days ago. The client is insisting on Apache and nothing but Apache, so I haven't investigated Squid, Varnish or anything else so far. I figured out how to use mod_cache to get Apache to cache the content, but it's kind of useless because there's a Cache- Control: max-age=0 header that causes it to request a new copy every time. The problem is, I can't figure out where it's coming from. I've eliminated Tomcat from the loop entirely, so the fault lies somewhere between AOLserver and Apache: - telnet to AOLserver directly - no cache-control at all GET /public/index HTTP/1.0 HTTP/1.0 200 OK Set-Cookie: ad_session_id=82810106%2c0%2c0+ %7b514+1239579021+56A366FC5E92AF28DB87E48214C6C4CE8C0581BB%7d; Path=/; Max-Age=1200 MIME-Version: 1.0 Date: Sun, 12 Apr 2009 23:10:21 GMT Server: AOLserver/4.0.10 Content-Type: text/html; charset=utf-8 Content-Length: 127358 Connection: close - have Apache send request to AOLserver via mod_proxy (ProxyPassMatch) - has Cache-Control with max-age=0 Last-Modified: Mon, 30 Mar 2009 11:26:14 GMT MIME-Version: 1.0 Date: Sun, 12 Apr 2009 23:03:02 GMT Server: AOLserver/4.0.10 Content-Type: image/gif Content-Length: 395
Re: [AOLSERVER] More on caching content...
This isn't the original code... this is a new servlet I wrote, which uses an open source translator written in Java. It may not be ideal (I am certainly not the world's best Java programmer) but the client (mostly Chinese-speaking) is happy with the output. The advantage is I control the source, but that is only helpful if I know what to change. :) janine On Apr 23, 2009, at 1:21 PM, Stephen Deasey wrote: On Thu, Apr 23, 2009 at 7:40 PM, Janine Sisk jan...@furfly.net wrote: Trying again... anyone??? Bueller? :) Is this tc2sc conversion software actually any good? I remember you were having the same problem 18 months ago, and you said that the company that wrote the software has gone out of business and you don't have the source code. The world expert on c2c conversion says that many such programs do only a simple 'level 1' conversion: http://www.cjk.org/cjk/c2c/c2cbasis.htm If that's the case for the program you're using, throw it away! You could perform an equally poor level 1 tc2sc conversion using Tcl's built-in charset api easily. Level 2 wouldn't be much harder. The advantage however would be that you would not have to wrestle with defunct java software and performance-sucking proxies. Maybe you could figure out how awesome the software is by feeding it some of the examples from the above web page and see how it measures up? -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. --- Janine Sisk President/CEO of furfly, LLC 503-693-6407 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] More on caching content...
On Apr 23, 2009, at 1:41 PM, David Walker wrote: Check the format of the Expires header. It must be in RFC 1123 date format, which, if I understand the documentation, looks like the line below. Expires: Thu, 01 Dec 1994 16:00:00 GMT It's being put in by AOLserver's ns_setexpires directive, so hopefully it's formatted properly. I can't check right at this moment but I know it looked more or less like that. Also, make sure you know how to clear the cache on Apache. I think rm -rf /var/www/cache/* will work. Clearing the cache as you troubleshoot will help you avoid having something cached blocking the caching of your new request. Yes, I have been doing that frequently. Also, try also sending a Last-Modified header or setting CacheIgnoreNoLastMod On I've already got that directive turned on. thanks, janine Janine Sisk wrote: Trying again... anyone??? Bueller? :) I'm getting closer... CacheIgnoreCacheControl helped. There was actually one place in OpenACS that might have been adding the cache-control header (in acs-tcl/tcl/request-processor- procs.tcl) but I commented that out a long time ago and it didn't make any difference. Now, with the CacheIngoreCacheControl directive, the home page gets cached properly. This is progress!! However, dynamic URLs are still not being cached. For example, both of these URLs work: translator.com/gate/gb/traditional-site.com/public/index translator.com/gate/gb?url=traditional-site.com/public/index The former gets cached, the latter does not. The reason for this is that mod_cache doesn't cache URLs with query variables unless either they contain an Expires directive or you turn on CacheIgnoreQueryString. But the latter is rather destructive as it returns the same content for all pages - not what one wants. I went into the OpenACS request processor and added the expires header; you can see it if you telnet to the page, so I know it worked, but it's somehow not making it back to Apache (it's not in the cached headers, and dynamic URLs are still not being cached). Any ideas how a header could get lost between AOLserver and Apache? Oh, and before anyone suggests this I did try adding an expiration via mod_expires in Apache, but that had no effect either. I didn't really expect it to, since that's not the request being cached, but it was worth a try. Thanks for everyone's patience with this mostly-OT topic! janine PS Here's the relevant part of my httpd.conf file: # mod_cache/mod_mem_cache LoadModule cache_module modules/mod_cache.so LoadModule disk_cache_module modules/mod_disk_cache.so IfModule mod_cache.c CacheEnable disk / # seconds (86400 = 1 day) CacheDefaultExpire 86400 CacheIgnoreNoLastMod On CacheIgnoreCacheControl On # seconds (2678400 = 31 days) CacheMaxExpire 2678400 IfModule mod_mem_cache.c # KB #MCacheSize 524288 MCacheSize 262144 MCacheMaxObjectCount 1000 # bytes MCacheMinObjectSize 1 # bytes MCacheMaxObjectSize 524288 /IfModule IfModule mod_disk_cache.c CacheRoot /var/www/cache CacheDirLevels 1 CacheDirLength 4 CacheMaxFileSize 524288 CacheMinFileSize 1 /IfModule /IfModule #LoadModule headers_module modules/mod_headers.so #Header set Cache-Control max-age=999 #LoadModule expires_module modules/mod_expires.so #ExpiresActive On #ExpiresDefault M86400 LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so ProxyRequests Off Proxy * Order deny,allow Allow from all /Proxy #ProxyPassMatch /(.+) http://staging-big5.hrichina.org/$1 ProxyPassMatch /(.+) http://209.162.194.27:8081/$1 On Apr 13, 2009, at 12:47 PM, David Walker wrote: To aid your troubleshooting, I would recommend a grep or other full-text search of the code running on AOLServer to determine if there are any circumstances where it would generate a cache- control header. Your telnet test may not give you all of the data you desire without a full set of headers on the request side. The Tamper Data add-on for Firefox will allow you to observe the interaction (headers and all) between your browser and the web server. The CacheIgnoreCacheControl directive may allow you to force Apache to cache regardless of whether there is a cache-control directive. http://httpd.apache.org/docs/2.0/mod/mod_cache.html Janine Sisk wrote: This is only peripherally related to AOLserver, but there are so many helpful and knowledgeable people on this list, I'm hoping someone will recognize this. I'm still working on that Apache/Tomcat caching thing I wrote about a few days ago. The client is insisting on Apache and nothing but Apache, so I haven't investigated Squid, Varnish or anything else so far. I figured out how to use mod_cache to get Apache to cache the content, but it's kind of useless because there's a Cache- Control: max-age=0 header that causes
Re: [AOLSERVER] More on caching content...
I'm getting closer... CacheIgnoreCacheControl helped. There was actually one place in OpenACS that might have been adding the cache-control header (in acs-tcl/tcl/request-processor-procs.tcl) but I commented that out a long time ago and it didn't make any difference. Now, with the CacheIngoreCacheControl directive, the home page gets cached properly. This is progress!! However, dynamic URLs are still not being cached. For example, both of these URLs work: translator.com/gate/gb/traditional-site.com/public/index translator.com/gate/gb?url=traditional-site.com/public/index The former gets cached, the latter does not. The reason for this is that mod_cache doesn't cache URLs with query variables unless either they contain an Expires directive or you turn on CacheIgnoreQueryString. But the latter is rather destructive as it returns the same content for all pages - not what one wants. I went into the OpenACS request processor and added the expires header; you can see it if you telnet to the page, so I know it worked, but it's somehow not making it back to Apache (it's not in the cached headers, and dynamic URLs are still not being cached). Any ideas how a header could get lost between AOLserver and Apache? Oh, and before anyone suggests this I did try adding an expiration via mod_expires in Apache, but that had no effect either. I didn't really expect it to, since that's not the request being cached, but it was worth a try. Thanks for everyone's patience with this mostly-OT topic! janine PS Here's the relevant part of my httpd.conf file: # mod_cache/mod_mem_cache LoadModule cache_module modules/mod_cache.so LoadModule disk_cache_module modules/mod_disk_cache.so IfModule mod_cache.c CacheEnable disk / # seconds (86400 = 1 day) CacheDefaultExpire 86400 CacheIgnoreNoLastMod On CacheIgnoreCacheControl On # seconds (2678400 = 31 days) CacheMaxExpire 2678400 IfModule mod_mem_cache.c # KB #MCacheSize 524288 MCacheSize 262144 MCacheMaxObjectCount 1000 # bytes MCacheMinObjectSize 1 # bytes MCacheMaxObjectSize 524288 /IfModule IfModule mod_disk_cache.c CacheRoot /var/www/cache CacheDirLevels 1 CacheDirLength 4 CacheMaxFileSize 524288 CacheMinFileSize 1 /IfModule /IfModule #LoadModule headers_module modules/mod_headers.so #Header set Cache-Control max-age=999 #LoadModule expires_module modules/mod_expires.so #ExpiresActive On #ExpiresDefault M86400 LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so ProxyRequests Off Proxy * Order deny,allow Allow from all /Proxy #ProxyPassMatch /(.+) http://staging-big5.hrichina.org/$1 ProxyPassMatch /(.+) http://209.162.194.27:8081/$1 On Apr 13, 2009, at 12:47 PM, David Walker wrote: To aid your troubleshooting, I would recommend a grep or other full- text search of the code running on AOLServer to determine if there are any circumstances where it would generate a cache-control header. Your telnet test may not give you all of the data you desire without a full set of headers on the request side. The Tamper Data add-on for Firefox will allow you to observe the interaction (headers and all) between your browser and the web server. The CacheIgnoreCacheControl directive may allow you to force Apache to cache regardless of whether there is a cache-control directive. http://httpd.apache.org/docs/2.0/mod/mod_cache.html Janine Sisk wrote: This is only peripherally related to AOLserver, but there are so many helpful and knowledgeable people on this list, I'm hoping someone will recognize this. I'm still working on that Apache/Tomcat caching thing I wrote about a few days ago. The client is insisting on Apache and nothing but Apache, so I haven't investigated Squid, Varnish or anything else so far. I figured out how to use mod_cache to get Apache to cache the content, but it's kind of useless because there's a Cache- Control: max-age=0 header that causes it to request a new copy every time. The problem is, I can't figure out where it's coming from. I've eliminated Tomcat from the loop entirely, so the fault lies somewhere between AOLserver and Apache: - telnet to AOLserver directly - no cache-control at all GET /public/index HTTP/1.0 HTTP/1.0 200 OK Set-Cookie: ad_session_id=82810106%2c0%2c0+ %7b514+1239579021+56A366FC5E92AF28DB87E48214C6C4CE8C0581BB%7d; Path=/; Max-Age=1200 MIME-Version: 1.0 Date: Sun, 12 Apr 2009 23:10:21 GMT Server: AOLserver/4.0.10 Content-Type: text/html; charset=utf-8 Content-Length: 127358 Connection: close - have Apache send request to AOLserver via mod_proxy (ProxyPassMatch) - has Cache-Control with max-age=0 Last-Modified: Mon, 30 Mar 2009 11:26:14 GMT MIME-Version: 1.0 Date: Sun, 12 Apr 2009 23:03:02 GMT Server: AOLserver/4.0.10 Content-Type: image/gif Content-Length: 395 User-Agent: Mozilla/5.0 (Macintosh; U
Re: [AOLSERVER] More on caching content...
Mark, thanks for the tip - it sounded logical but unfortunately doesn't seem to be the case. I didn't have any expire directives in the conf file but I added this anyway: ExpiresActive On ExpiresDefault M86400 and it doesn't seem to be making any difference. I tried commenting out the code for mod_headers and then the first Cache-Control line is missing, but the one with max-age=0 is still there. just for grins, I tried using telnet to request the URL instead of going to it in the browser. I then found the corresponding header in Apache's cache (this one is the actual HTML, the rest are all images), so it's more of an apples-to-apples comparison. Both are below. The interesting thing is that the cached header includes a lot more information, including the erroneous Cache-Control: max-age=0. Some of it comes from mod_proxy, specifically the X-Forwarded part. But there's nothing in the docs to suggest that mod_proxy does anything with Cache-Control... I've Googled quite a bit and have found other people with similar issues but all the ones I found went unanswered. Seems I've found a hard-to-solve problem. Lucky me. :) janine What Apache caches: http://pug.furfly.com:8080/public/index? MIME-Version: 1.0 Date: Mon, 13 Apr 2009 17:34:43 GMT Server: AOLserver/4.0.10 Content-Type: text/html; charset=utf-8 Content-Length: 127358 Set-Cookie: ad_session_id=82810314%2c0%2c0+ %7b504+1239645283+E08EA2C07D8750971544D8B6671200EAF699C98D%7d; Path=/; Max-Age=1200 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_6; en-us) AppleWebKit/525.27.1 (KHTML, like Gecko) Version/3.2.1 Safari/525.27.1 Cache-Control: max-age=0 Accept: text/xml,application/xml,application/xhtml+xml,text/ html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Language: en-us Accept-Encoding: gzip, deflate Cookie: __qca=482b4ca6-9b388-0907d-155ca; __utma=146890400.1264817709.1186083344.1190161690.1203300241.4; __utma =69865361.424306058273248.1238996261.1239575290.1239642259.7; __utmc=69865361; __utmz=69865361.1238996261.1.1.utmcsr=(direct)| utmccn=(direct)|utmcmd=(none); ad_session_id=82810314%2c0%2c0+ %7b875+1239644942+FC98624F29A05DF429C7EEDE1E3233089A2BF039%7d; JSESSIONID=1428D1022033F5CAB31B6FDA6F349021 Host: pug.furfly.com:8080 X-Forwarded-For: 173.50.249.21 X-Forwarded-Host: pug.furfly.com:8080 X-Forwarded-Server: pug.furfly.com What telnet receives: GET /public/index HTTP/1.0 HTTP/1.1 200 OK Date: Mon, 13 Apr 2009 17:36:00 GMT Server: Apache/2.2.11 (Unix) Set-Cookie: ad_session_id=82810314%2c0%2c0+ %7b504+1239645283+E08EA2C07D875097154 4D8B6671200EAF699C98D%7d; Path=/; Max-Age=1200 MIME-Version: 1.0 Content-Length: 127358 Age: 77 Connection: close Content-Type: text/html; charset=utf-8 On Apr 13, 2009, at 5:36 AM, Mark Aufflick wrote: Hi Janine, The key with Apache documentation is to know which module is going to do what you want. Once you've figured that out, the docs are quite clear (with the exception of mod_rewrite of course :) In this case I happen to know that the Cache-control header is generated by mod_expires, and you will find how to control it here: http://httpd.apache.org/docs/2.0/mod/mod_expires.html Your httpd config might have expiration set by default, or by file extension. Mark. On Mon, Apr 13, 2009 at 9:32 AM, Janine Sisk jan...@furfly.net wrote: This is only peripherally related to AOLserver, but there are so many helpful and knowledgeable people on this list, I'm hoping someone will recognize this. I'm still working on that Apache/Tomcat caching thing I wrote about a few days ago. The client is insisting on Apache and nothing but Apache, so I haven't investigated Squid, Varnish or anything else so far. I figured out how to use mod_cache to get Apache to cache the content, but it's kind of useless because there's a Cache-Control: max-age=0 header that causes it to request a new copy every time. The problem is, I can't figure out where it's coming from. I've eliminated Tomcat from the loop entirely, so the fault lies somewhere between AOLserver and Apache: - telnet to AOLserver directly - no cache-control at all GET /public/index HTTP/1.0 HTTP/1.0 200 OK Set-Cookie: ad_session_id=82810106%2c0%2c0+ %7b514+1239579021+56A366FC5E92AF28DB87E48214C6C4CE8C0581BB%7d; Path=/; Max-Age=1200 MIME-Version: 1.0 Date: Sun, 12 Apr 2009 23:10:21 GMT Server: AOLserver/4.0.10 Content-Type: text/html; charset=utf-8 Content-Length: 127358 Connection: close - have Apache send request to AOLserver via mod_proxy (ProxyPassMatch) - has Cache-Control with max-age=0 Last-Modified: Mon, 30 Mar 2009 11:26:14 GMT MIME-Version: 1.0 Date: Sun, 12 Apr 2009 23:03:02 GMT Server: AOLserver/4.0.10 Content-Type: image/gif Content-Length: 395 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_6; en-us) AppleWebKit/525.27.1 (KHTML, like Gecko) Version/3.2.1 Safari/ 525.27.1 Referer: http://pug.furfly.com:8080/public/index
[AOLSERVER] More on caching content...
This is only peripherally related to AOLserver, but there are so many helpful and knowledgeable people on this list, I'm hoping someone will recognize this. I'm still working on that Apache/Tomcat caching thing I wrote about a few days ago. The client is insisting on Apache and nothing but Apache, so I haven't investigated Squid, Varnish or anything else so far. I figured out how to use mod_cache to get Apache to cache the content, but it's kind of useless because there's a Cache-Control: max-age=0 header that causes it to request a new copy every time. The problem is, I can't figure out where it's coming from. I've eliminated Tomcat from the loop entirely, so the fault lies somewhere between AOLserver and Apache: - telnet to AOLserver directly - no cache-control at all GET /public/index HTTP/1.0 HTTP/1.0 200 OK Set-Cookie: ad_session_id=82810106%2c0%2c0+ %7b514+1239579021+56A366FC5E92AF28DB87E48214C6C4CE8C0581BB%7d; Path=/; Max-Age=1200 MIME-Version: 1.0 Date: Sun, 12 Apr 2009 23:10:21 GMT Server: AOLserver/4.0.10 Content-Type: text/html; charset=utf-8 Content-Length: 127358 Connection: close - have Apache send request to AOLserver via mod_proxy (ProxyPassMatch) - has Cache-Control with max-age=0 Last-Modified: Mon, 30 Mar 2009 11:26:14 GMT MIME-Version: 1.0 Date: Sun, 12 Apr 2009 23:03:02 GMT Server: AOLserver/4.0.10 Content-Type: image/gif Content-Length: 395 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_6; en-us) AppleWebKit/525.27.1 (KHTML, like Gecko) Version/3.2.1 Safari/525.27.1 Referer: http://pug.furfly.com:8080/public/index Cache-Control: max-age=0 Accept: */* Accept-Language: en-us Accept-Encoding: gzip, deflate - use mod_headers to add a Cache-Control header - now we have two: Last-Modified: Mon, 30 Mar 2009 11:26:14 GMT MIME-Version: 1.0 Date: Sun, 12 Apr 2009 23:15:04 GMT Server: AOLserver/4.0.10 Content-Type: image/gif Content-Length: 395 Cache-Control: max-age=999 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_6; en-us) AppleWebKit/525.27.1 (KHTML, like Gecko) Version/3.2.1 Safari/525.27.1 Referer: http://pug.furfly.com:8080/public/index Cache-Control: max-age=0 Accept: */* Accept-Language: en-us Accept-Encoding: gzip, deflate It appears that Apache is adding the rogue header, but I don't know how to tell it to stop! Any suggestions? janine --- Janine Sisk President/CEO of furfly, LLC 503-693-6407 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
[AOLSERVER] Caching questions
I have a really screwy setup and am looking for some advice. I have an AOLserver site running a not-very-recent version of OpenACS with a custom CMS I did not write. It serves up a site written entirely in Traditional Chinese. I also have a java servlet which takes a page from that site and translates it into Simplified Chinese. So URLs are like this: Traditional - http://big5.mysite.com/public/index Simplified - http://gb.mysite.com/gate/gb/big5.mysite.com/public/index The latter goes to a Tomcat site which requests the specified page from big5.mysite.com, translates it, and returns it. As you can imagine, this is not fast. I'm working on convincing the client that what we really need to do is make a static HTML version of the Simplified site, which gets updated when they update content, and serve that directly. Ultimately I'm pretty sure that's what we'll end up doing. But first I have a tech guy on their end who thinks caching is the way to go, and I need to try that before they'll let me implement my own solution. He thought I should just slap Apache in front of all this and use mod_cache, but that was a dead end. Since Apache doesn't actually serve any content in this scenario but merely hands off to Tomcat, there is nothing for it to cache. I've done some googling on Tomcat and caching but there don't seem to be any add-ons for it. They say it does some caching by default but I'm not seeing it, maybe because I'm not using any JSPs. This is my first foray into Java programming so it's all new to me. I know that some people use Squid as a caching proxy in front of AOLserver, but I'm not sure if that would solve my problem or not. Any suggestions out there? thanks, janine --- Janine Sisk President/CEO of furfly, LLC 503-693-6407 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
[AOLSERVER] Virtual hosting
Hi all, I'm considering moving from owning my own hardware to hosting everything with Amazon. It has many advantages, but one huge drawback - each virtual server can only have one external IP address. I've never tried to use AOLserver's virtual hosting; at one time it was said to be less than reliable, and I've never revisited it. We've always had enough IP addresses that every site could have one of their very own. But that's not going to be the case if I make this change; virtual servers aren't cheap enough that I can set one up for every site, they're still going to have to be roommates. So my question - what is the latest in virtual hosting? Can I actually run multiple sites off of one IP address these days? What about SSL? I'm still using version 4.0.10 - haven't had any need to upgrade. I can upgrade if necessary to deal with this, though I'd rather not introduce that variable at this particular point in time. Thanks in advance, janine --- Janine Sisk President/CEO of furfly, LLC 503-693-6407 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to lists...@listserv.aol.com with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] AOLserver Wiki is now mirrored at dev.aolserver.com
I agree. janine On Dec 13, 2007, at 7:38 AM, Juan José del Río [Simple Option] wrote: Hello everyone, I think dev.aolserver.com is a better place to find it, and people will feel it more like the official wiki, based on the url :) If it works fine, then I think it's a good change. Regards, Juan José - Juan José del Río| Comercio online / e-commerce +34 616 512 340 | [EMAIL PROTECTED] Simple Option S.L. Tel: +34 951 930 122 Fax: +34 952 792 455 http://www.simpleoption.com On Thu, 2007-12-13 at 09:36 -0500, Dossy Shiobara wrote: Everyone, I've mirrored a copy of the AOLserver Wiki onto dev.aolserver.com: http://dev.aolserver.com/ It's based on a backup of the wiki from about 30 minutes ago. I've tested it and everything still works except for a few extensions I've added, which I'm still troubleshooting. For now, the copy of the AOLserver Wiki up on dev.aolserver.com is in read-only mode to prevent folks from making changes there that will get clobbered by a future refresh. I'd like to make dev.aolserver.com the permanent home of the AOLserver Wiki, but I want to let it burn in for a bit, first. I'd like to make sure everything works, it performs well enough, etc. What do you think? -- Dossy -- 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. -- 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] unknown IP address in access log
I'm looking at nslog.c and I think this is probably the bit that's
responsible for my unknowns:
/*
* Append the peer address and auth user (if any).
* Watch for users comming from proxy servers.
*/
if (conn-headers (p = Ns_SetIGet(conn-headers, X-Forwarded-
For))) {
Ns_DStringAppend(ds, p);
} else {
Ns_DStringAppend(ds, Ns_ConnPeer(conn));
}
I've even found one today that has both my problem and the one Juan
reported:
66.102.186.10, unknown - - [29/Nov/2007:00:09:57 -0800] ...
What I don't know is, is there anything I can do to get a valid IP
address? I don't know how Ns_ConnPeer(conn) gets set - if the X-
Forwarded_For header is present but set to unknown (which is my
guess as to what's happening), can I revert to using Ns_ConnPeer
(conn) instead? Or am I just outta luck? It seems like there ought
to be a valid IP address somewhere, as the request isn't supposed to
be able to be delivered to the server without one.
The reason I care about this is that we've implemented IP-based site
subscriptions, and the folks coming in with unknown aren't able to
access the site. In this particular instance it's better to get the
IP of the proxy server than have it unavailable entirely.
janine
On Nov 14, 2007, at 5:25 PM, Tom Jackson wrote:
This looks like a reverse lookup, but very strange.
Janine's case is also weird. The access log is a small chunk of
code, so it
might be easy to figure it out.
Which versions of AOLserver are being used here?
tom jackson
On Wednesday 14 November 2007 16:18, Juan José del Río [Simple
Option] wrote:
That's very weird, Janine. Maybe some other knows what's going on.
In my case, I have a weird behaviour too...
213.99.4.203, 212.170.235.17 - - [14/nov/2007:19:32:31 +0100] GET /
HTTP/1.0 200 3295 Mozilla/5.0 (Windows; U; Windows
NT 5.0; es-ES; rv:1.8.1.9) Gecko/20071025 Firefox/2.0.0.4 0.077743
What about this? I don't know what's going on with the *TWO* IPs
Regards,
Juan José
-
Juan José del Río| Comercio online / e-commerce
+34 616 512 340 | [EMAIL PROTECTED]
Simple Option S.L.
Tel: +34 951 930 122
Fax: +34 952 792 455
http://www.simpleoption.com
On Wed, 2007-11-14 at 15:49 -0800, Janine Sisk wrote:
Does anyone know what causes the IP address to be reported as
unknown for a handful of acesses each day?
unknown - - [13/Nov/2007:12:32:06 -0800] GET / HTTP/1.0 200 17880
Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.9)
Gecko/20071025 Firefox/2.0.0.9
janine
--
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.
--
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.
--
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.
--
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] unknown IP address in access log
I am using 4.0.10. thanks, janine On Nov 14, 2007, at 5:25 PM, Tom Jackson wrote: This looks like a reverse lookup, but very strange. Janine's case is also weird. The access log is a small chunk of code, so it might be easy to figure it out. Which versions of AOLserver are being used here? tom jackson On Wednesday 14 November 2007 16:18, Juan José del Río [Simple Option] wrote: That's very weird, Janine. Maybe some other knows what's going on. In my case, I have a weird behaviour too... 213.99.4.203, 212.170.235.17 - - [14/nov/2007:19:32:31 +0100] GET / HTTP/1.0 200 3295 Mozilla/5.0 (Windows; U; Windows NT 5.0; es-ES; rv:1.8.1.9) Gecko/20071025 Firefox/2.0.0.4 0.077743 What about this? I don't know what's going on with the *TWO* IPs Regards, Juan José - Juan José del Río| Comercio online / e-commerce +34 616 512 340 | [EMAIL PROTECTED] Simple Option S.L. Tel: +34 951 930 122 Fax: +34 952 792 455 http://www.simpleoption.com On Wed, 2007-11-14 at 15:49 -0800, Janine Sisk wrote: Does anyone know what causes the IP address to be reported as unknown for a handful of acesses each day? unknown - - [13/Nov/2007:12:32:06 -0800] GET / HTTP/1.0 200 17880 Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.9) Gecko/20071025 Firefox/2.0.0.9 janine -- 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. -- 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. -- 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. -- 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.
[AOLSERVER] unknown IP address in access log
Does anyone know what causes the IP address to be reported as unknown for a handful of acesses each day? unknown - - [13/Nov/2007:12:32:06 -0800] GET / HTTP/1.0 200 17880 Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.9) Gecko/20071025 Firefox/2.0.0.9 janine -- 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] Working with Chinese characters in Tcl/AOLserver
I think I will just go with moving the thing to Tomcat; it looks like that's going to be easier than rewriting the mapping process in Tcl. Thanks for the input, everyone! janine On Sep 5, 2007, at 6:42 PM, Tom Jackson wrote: On Wednesday 05 September 2007 17:53, Dave Bauer wrote: Might work, might not. You could write a few tests by comparing output from tjhe Java to your new maintainable map. This assumes there is a one-to-one mapping. I have no idea, I am not familiar with Chinese. There are several steps, but processing is char-by-char. You have to know how to read a char. With UTF-16, this is easy. UTF-8 is harder to read. Once you have a char, you need a method to map it to the new character set. Handling errors is another story. Also, if you are reading a channel, you can fconfigure as binary. If you don't do this, then Tcl will probably convert it to UTF-8. Use your char reader on a binary channel unless Tcl can do the conversion all by itself. Don't expect too much, I have yet to find a browser which reads UTF-8 100% correct. see: http://rmadilo.com/files/utf-8/UTF-8-test.txt 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. -- 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.
[AOLSERVER] Working with Chinese characters in Tcl/AOLserver
This may be more of a Tcl question than an AOLserver one, but I'm guessing that people on this list are more likely to have run into it. So here goes. I'm working with strings encoded in big5 and gb2312 (traditional and simplified Chinese, respectively). I'm exec'ing out to an Java program that translates from one to the other. I have found that the only way to get my data to the program intact, and get the response back intact, is to store the data in intermediate files with the fconfigure command to set the encoding. Anything else ends up mangling the data. I can't, for example, grab the return value of the command directly from the exec; if I do, it's mangled. I have to have the java program write it to a file, and then read it with the encoding set, in order to get the data intact. As you can imagine, having to write two files per page request isn't exactly ideal, even with caching. So has anyone else done this and found a way to do it? thanks, janine -- 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] Working with Chinese characters in Tcl/AOLserver
This is still not working out very well... let me explain more about what I'm doing, and maybe it will ring a bell for someone. I'm working with a site that stores it's content in big5, and is run through a conversion program to create a gb2312 version for those who prefer the simplified characters. I know these are the charsets being used; I've seen the config files for the converter. Unfortunately the converter was written by a Chinese company with no English info available, does not appear in Google, and is no longer supported even by the original authors. So basically I have to write my own program to do what it does, without any info on how it does what it does. I'm currently working with a snippet of text from the site, but the eventual idea is to have the converter run under a separate web server and have it grab the page from the big5 site, convert it, and send it out to the browser. This is how the existing translator works, as far as I can tell. Regardless of whether I'm reading the snippet from a text file or getting an entire page via ns_http; I have to set the encoding to utf-8 in order to get the data properly. It does not display properly if I call it big5. This is odd, but not terribly so; the database and source AOLserver are both configured to use utf-8, so this is at least consistent. The only conversion that works with the java program is to go utf-8 to utf-8s, which it calls simplified utf-8. Google tells me that this is a bastardized format of sorts, proposed by Oracle and not widely accepted. Unfortunately it is, so far, the only one that works. Data comes in as utf-8, gets converted to utf-8s, and goes out through AOLserver configured to use utf-8. All is well. The problem is, Tcl doesn't support utf-8s, and as far as I can tell there is no other format that will work. This will leave me stuck with the java program, and I have serious concerns about the performance of any sort of exec, let alone one that involves writing files. Any suggestions? thanks, janine On Sep 5, 2007, at 6:08 AM, Dossy Shiobara wrote: On 2007.09.05, Janine Sisk [EMAIL PROTECTED] wrote: I'm working with strings encoded in big5 and gb2312 (traditional and simplified Chinese, respectively). I'm exec'ing out to an Java program that translates from one to the other. [...] Is that Java program doing anything else to the data? If you're just using Java to transcode Tcl strings, you're really hurting yourself for no reason: set big5string [encoding convertto big5 $gb2312string] set gb2312string [encoding convertto gb2312 $big5string] Tcl's encoding support is probably one of its strenghts as a scripting language. I can't, for example, grab the return value of the command directly from the exec; if I do, it's mangled. I don't think you can tell [exec] what encoding the I/O will be. Perhaps you could/should see if there's a TIP for [exec -encoding $name $command] already ... -- 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. -- 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] Working with Chinese characters in Tcl/AOLserver
I'm not using Oracle, but Postgres. The database is in UTF-8 format, so that should be what I'm getting out of it. I'm not getting the data directly from the database anyway, but via ns_http. I have no idea how UTF-8S is getting in to the mix other than it's the only format I can find to convert to that works. Bas is probably right, I should just do this in pure java. My main concern is that I'm doing something wrong that's making this harder than it needs to be. Using the encoding command would be so simple... I already saw that message, thanks, and have followed it as much as possible. janine On Sep 5, 2007, at 4:17 PM, Dossy Shiobara wrote: On 2007.09.05, Janine Sisk [EMAIL PROTECTED] wrote: The only conversion that works with the java program is to go utf-8 to utf-8s, which it calls simplified utf-8. Google tells me that this is a bastardized format of sorts, proposed by Oracle and not widely accepted. http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ appunicode.htm | Oracle's AL32UTF8 character set supports 1-byte, 2-byte, 3-byte, | and 4-byte values. Oracle's UTF8 character set supports 1-byte, | 2-byte, and 3-byte values, but not 4-byte values. Are you using Oracle with NLS_LANG set to AL32UTF8, or just UTF8? I spotted this OpenACS forum message, if you see what to check and/or change: http://openacs.org/forums/message-view?message_id=198856 The problem is, Tcl doesn't support utf-8s, and as far as I can tell there is no other format that will work. If you tell Oracle you want AL32UTF8, then you'll get UTF-8 as Tcl expects (and can handle). -- 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. -- 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] Problem starting aolserver
Some other process is already listening on that IP address on port 80. Usually the culprit is Apache, however in this case when I go to http://64.58.34.71 I get the AOLserver 4.5 welcome page, so it looks like you might just be trying to run a second instance of the nsd you just installed. When things like this happen to me I usually shut everything down (killall nsd works well if you don't have other sites on the system that need to stay running) and start it up fresh. janine On Feb 12, 2007, at 11:19 AM, Thorpe Mayes wrote: When trying to start a newly installed version of aolserver, I get this error: Error: nssock: failed to listen on 64.58.34.71:80: Permission denied What folder/file does not have the correct permissions? Here is what I am using to start the server: /usr/local/aolserver/bin/nsd -ft ./nsd.tcl -u something -g something Thank you. Thorpe -- 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. -- 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] SSL read error: bad write retry
I see that error in my logs all the time, but was not aware it was one the users were seeing. We haven't had any complaints about it. I don't know what causes it; since it has been going on for years with no complaints it never really made it on my radar screen. nsopenssl puts out a bunch of apparently victimless errors like this. janine On Jan 25, 2007, at 2:52 PM, Alex Kroman wrote: Hi all, Every day about 1% of connections to my website result in the following error: Error: nsopenssl: SSL write error: bad write retry I can reproduce the error by repeatedly submiting a form. Eventually one of those submits will fail and give the generic Internet Explorer connection error and append the bad write retry message to the log. Has anyone run into this problem? I am using the stock Debian versions of AOLServer 4.0.10 and nsopenssl 3.0beta22. Here are some settings from my configuration file: ns_param maxinput [expr 1024 * 1024 * 100] ns_param recvwait [expr 20 * 60] ns_param socktimeout 240 Thanks, Alex -- 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. -- 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 3.x not running scheduled procs anymore
The problem was that the very large value we all use for MaxOpen and MaxIdle on the database pools causes an integer overflow (I think) in the time calculation. You need to set them to a smaller value, or set them to zero; that is supposed to have the same effect (keep them open indefinitely) and it seems to be working ok on the one site I had to do this on. janine On Oct 18, 2006, at 7:38 PM, Mark Aufflick wrote: I remember some time ago (maybe last year) people complaining that their aolserver 3.x servers stopped running scheduled procs. My sole remaining 3.x site didn't exhibit the problem and I didn't pay too much attention. A few weeks ago, however, my (still sole remaining) aolserver 3 site stopped running scheduled procs! Can anyone remember if anyone found the root cause of this? Mark. -- Mark Aufflick e: [EMAIL PROTECTED] w: mark.aufflick.com p: +61 438 700 647 f: +61 2 9436 4737 -- 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. -- 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] nsopenssl
On Sep 20, 2006, at 2:30 PM, Dossy Shiobara wrote: So: what are you (plural -- all of you) still waiting for to be done in nsopenssl? I'm not waiting for anything; it works fine for me, except for the already-mentioned overly verbose logging. janine -- 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's documentation woes and its future
On Sep 5, 2006, at 7:50 AM, Rick Gutleber wrote: If AOL wants to sever its ties with AOLServer (and it looks like it does) I am most curious about this statement. Does AOL truly want to move away from using AOLserver internally (which would seem to be the case if they want to sever ties with it), and if so, what are they going to be replacing it with? janine -- 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's documentation woes and its future
Well... yes, all our customers who are technically savvy enough to understand know that we use AOLserver. Unfortunately, the fact that OpenACS requires AOLserver is a hindrance in the sales cycle, and there have been repeated requests from many people over the years for OpenACS to run under Apache (which is never going to happen). Part of the problem is the association with AOL - rightly or wrongly, that inspires a fight or flight response in many of the IT people we talk to. But the biggest issue is that it's different, and Enterprise customers generally don't want to take on a new web server for their admins to have to learn and support. As far as the community goes... I have been using AOLserver since early 1999; that's 7.5 years. During that time, I have maybe looked at the source a dozen times, if that, and usually I don't find what I'm looking for. It's an application that requires specialized domain knowledge to understand, written in a language I haven't worked in professionally for almost 20 years. It's not where I can spend my time most effectively. I think there are relatively few people out there who really *want* to dive into the internals of a web server, and most of them are working on Apache. So the participating community does not have a huge pool of people to draw on. Even writing documentation would be a big investment of time for me, because in order to document something one has to really understand what it does, and right now the only way to do that is to read the source. Maybe it makes me a bad person, but I just don't have that much time to invest in this. I think we have a bit of a catch-22 situation here. There are only a handful of people who are knowledgeable enough about AOLserver to help those who are having trouble. Those people are overloaded and are not able to provide the hand-holding needed by users who don't know how to use debugging tools and fix their own problems. So people either stop using AOLserver, or they learn to put up with or work around problems they aren't able to fix on their own. And so the community stays small, and enthusiasm for participating is dampened. There were a lot more attempts at community participation years ago, but they were mostly rebuffed. Patches being rejected for no good reason used to be a fairly frequent topic on this list. That also set a tone of people not wasting their time contributing which probably persists to this day even though the person responsible is long gone. Unfortunately, it is much easier to describe the problem than it is to find solutions. About the best suggestion I can think of is that you may get more participation if you realize that although most of us are developers, very few of us are AOLserver developers. It's not enough to throw open the gates and invite us to participate. There has to be some way for those who are so inclined to gain the basic knowledge needed to be useful, and right now that's just not there. My $0.02, janine On Sep 1, 2006, at 11:10 AM, Dossy Shiobara wrote: I'd like to share with the community a comment made by someone at AOL: || My problems with AOLserver are: || || 1) The lack of documentation, which is annoying, but could be fixed. || || 2) The tiny userbase, which [AOL] simply can't fix. Not unless AOL || puts 10 times more support into the product than they ever have in || the past and that's not gonna happen. I know that the sad state of the documentation has been a big problem for a long time. I'd really like to hear suggestions from everyone as to how we might go about solving it. Does it all have to be written by one or two people? Can the work be distributed? Where do we start? Should we take the old documentation and just freshen it up? Do we need to start with a new draft Table of Contents and start over? What is keeping folks from contributing (time, expertise, money, something else)? What format do folks want: dead tree books, online e-books, both, something else entirely? With respect to the size of the community, what can we do to grow it? We definitely need more evangelism: marketing, communication with the press, white papers, etc. Do folks in the AOLserver community attend trade shows and conferences? Which ones? Do you tell folks about AOLserver? Why or why not? If you have a commercial product built on top of AOLserver, do your customers know this? Do you mention the existence of this community to them? If not, why not? I realize there are folks located all around the world, but if I organized it, would folks be willing to travel for an AOLserver Conference? Where would people want to attend it (excluding obvious destinations like Hawaii and on a cruise ship that may be slightly out of our reach right now, :-)? Would anyone be willing to volunteer to help organize it? Even if we can't achieve it, I'd like everyone to
Re: [AOLSERVER] A wolf in sheep's clothing: AOLserver behind Apache (was Re: AOLserver's documentation woes and its future)
On Sep 1, 2006, at 1:41 PM, Dossy Shiobara wrote: I find this kind of funny since organizations are willing to support Tomcat, or WebSphere, etc. I didn't say it was logical! :) It's conceivable that you could run Apache as the web server (handling HTTP requests) sitting in front of AOLserver as the application server. We all understand why this is largely unnecessary, but presumably it would get you past the auto-immune reaction of your customers. Unfortunately that doesn't help. If the client wants to host it themselves, then having AOLserver in there anywhere is a problem. This can actually be beneficial for us; our hosting business thrives mainly because people don't want to deal with it themselves or can't get their IT depts to touch it. But for those whose policies dictate that they must host in-house, it's often the kiss of death. janine -- 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] Is tcl exec _really_ bad with threads
On Aug 30, 2006, at 8:56 AM, Nathan Folkman wrote: What is it you are trying to exec? From OpenACS we mostly just exec Imagemagick. I can't think of anything else. janine -- 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] Is tcl exec _really_ bad with threads
On Aug 30, 2006, at 10:32 AM, Nathan Folkman wrote: So the easy way to do this would be to exec from the nsproxy. Better option might be to wrap the C API, although I'm not entirely sure whether or not Imagemagick is truly thread-safe. Even if it is not, you'd probably still see better performance using the wrapped C API from the nsproxy. Is this concern something new for 4.5? Because OpenACS has been exec'ing Imagemagik, sqlplus and plsql for years now with no apparent problems. Have we just been really lucky? janine -- 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] Fedora 5 and aolserver 4.5.0
I have a system running Fedora Core 4. I was able to build 4.0.10 on this system but it did not run properly, as I have described in a previous message. I just tried 4.5.0 on this system and it builds and runs fine, or so it appears. I only tried it with the sample config file it came with, but that seemed to work ok. So there's another data point - apparently FC4 is ok, but FC5 is not. Unfortunately I don't have any FC5 systems available to test with at the moment. janine On Jul 11, 2006, at 12:37 PM, Jon Griffin wrote: I could never make 4.0.10 work with FC5 even with a local version of tcl. multiple definition of `_init' shows up no matter what I do. I am now trying to compile 4.5 and the following error is thrown. nsdb nssock nslog nsperm nscgi nscp make: execvp: ./util/nsmakeall.tcl: Permission denied make: *** [build] Error 127 Any ideas? It appears that Fedora and AOL don't like each other. All my other boxes are gentoo and I have no problems. -- 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. -- 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.
[AOLSERVER] Trouble running AOLserver 4.0.10 (with possible solution)
I just lost an unbelievable amount of time to this problem; maybe this will help save someone else some time. I went to install .LRN on a new system and I just could not get it to work. No matter what I did, when I tried to load the site I got a blank page. No errors, and not even an entry in the access log. I went round, and round, and round, checking and double-checking. Everything seemed to be set up correctly. I finally started stripping down the setup to a minimal number of pieces. I found that if I got rid of .LRN entirely and had a simple index.html, it would load correctly. An index.tcl, however, caused a received fatal signal 11 error and restarted AOLserver. Google lead me to this thread: http://openacs.org/forums/message- view?message_id=318659 Which suggested that downgrading glibc from 2.3.5-4 to 2.3.2 had fixed this problem for someone else. I checked the system and saw that I had version 2.3.6-3, so I grabbed a copy of AOLserver from another system which has 2.3.4-2.19. Sure enough, these binaries run just fine, and I was able to complete my .LRN install without further incident. Of course there are other differences between the two systems so I can't say for sure that the glibc version is at fault, but the pattern fits - version 2.3.4 is ok, but 2.3.5 and above are not. janine -- 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] Something wrong after 2006-05-12 21:25 (was Re: Weird memory leak problem in AOLserver 3.4.2/3.x)
On May 19, 2006, at 1:04 PM, 'Jesus' Jeff Rogers wrote: The only bug is that Ns_CondTimedWait doesn't do any wraparound on the time parameter. All the same, I've been enjoying telling people that I hit my first y2038 bug. So are you saying you've fixed it, or just that you've narrowed it down to this? If you've fixed it, do tell! :) janine -- 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] Something wrong after 2006-05-12 21:25 (was Re: Weird memory leak problem in AOLserver 3.4.2/3.x)
1) ns_info patchlevel
3.3 apparently didn't have patchlevel, as that gave me an error. The
output of ns_version is 3.3.1+ad13
2) uname -a
Linux x.furfly.com 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:54:53 EST
2006 i686 i686 i386 GNU/Linux
3) glibc version
$ rpm -qa | grep glibc
glibc-kernheaders-2.4-9.1.98.EL
glibc-common-2.3.4-2.19
glibc-devel-2.3.4-2.19
glibc-2.3.4-2.19
glibc-headers-2.3.4-2.19
On May 17, 2006, at 1:34 PM, Dossy Shiobara wrote:
On 2006.05.17, Zachary Shaw [EMAIL PROTECTED] wrote:
We're experiancing a similar issue at Brandeis University, but we get
no error, our scheduled procs just hang. [...] we're running
aolserver
3.3.1 ad13 [...] if I set the system date to may 12th or earilier all
the procs will run. otherwise they run for a little then stop.
looking at the straces the difference appears to be in how the
nanosleep is set for the pids.
before may 13th nanosleep was in the form
[pid 614] nanosleep({0, 34478}, unfinished ...
after the 12th there were nanosleeps in the form
[pid 614] nanosleep({9, 934211000}, unfinished ...
Dave Siktberg seems to have narrowed it down to 2006-05-12 21:25.
What's interesting is I'm running AOLserver 4.0.10 on x86/Linux
2.6.15.6
with glibc6 2.3.5 with no OpenACS and all my scheduled procs are
firing
just fine.
Can we get everyone who's experiencing this problem to provide a few
things:
1) ns_info patchlevel
2) uname -a
3) glibc version
I'm betting this is an older Linux or LinuxThreads or glibc
problem. I
could be wrong, of course, but gathering this info will help to figure
it out.
-- 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.
--
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] Something wrong after 2006-05-12 21:25 (was Re: Weird memory leak problem in AOLserver 3.4.2/3.x)
My info patchlevel is also 8.3.2. janine On May 17, 2006, at 2:12 PM, Titi Ala'ilima wrote: We just decided to move everything left on 3.3ad13 to 4.0, but to help those who need it: Can we get everyone who's experiencing this problem to provide a few things: 1) ns_info patchlevel I think you mean info patchlevel I've got 8.3.2 2) uname -a Linux servername 2.4.21-4.EL #1 Fri Oct 3 18:13:58 EDT 2003 i686 i686 i386 GNU/Linux 3) glibc version glibc-2.3.2-95.3 -- 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. -- 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] Something wrong after 2006-05-12 21:25 (was Re: Weird memory leak problem in AOLserver 3.4.2/3.x)
On May 17, 2006, at 2:35 PM, Dossy Shiobara wrote: On 2006.05.17, Titi Ala'ilima [EMAIL PROTECTED] wrote: Janine, could you give us your info patchlevel too? Same with everyone else who is seing this problem and is reporting information. 8.3.2 also. janine -- 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] Weird memory leak problem in AOLserver 3.4.2/3.x
In addition to the below, there are at least two of us over at openacs.org reporting that scheduled procs stopped firing over the weekend. I have one site left on 3.3+ad13 and the other guy says he has 3.2+ad12. This site hasn't been upgraded because the client didn't want to upgrade, so any pointers on fixing this would be greatly appreciated. janine On May 15, 2006, at 9:55 AM, Guan Yang wrote: I've experienced this problem over the weekend on half a dozen servers in three different locations: After starting up, AOLserver (mostly 3.4.2, also a 3.5.11) begins allocating a lot of virtual memory. When I follow the process in top, the virtual memory counter (but not real memory) rapidly increases over the course of 10 to 20 seconds, until it hits the limit of 3 GB virtual memory in user space on x86 Linux boxes. The process then crashes with this message: nsthread(3094) error: pthread_create failed in NsThreadCreate: Cannot allocate memory (The process is then restarted by supervise/svscan.) I couldn't find a fix for the problem and had to migrate to AOLserver 4.0.10 (we had already planned this for next month) immediately. But I find it a bit weird that practically every AOLserver 3 installation that I know of encounters this problem over the same weekend. Just bad luck? Date sensitive code? Guan -- 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. -- 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] Weird memory leak problem in AOLserver 3.4.2/3.x
By the way, one more thing: I have three sites running on this server - staging, live and an old keepalive instance. The live site is the only one exhibiting the scheduled proc problem; it's also the only one that gets any significant traffic. So I'm thinking it's some kind of overflow where it only causes problems when a busy site is using memory and ends up overwriting something. janine On May 16, 2006, at 12:10 AM, Janine Sisk wrote: In addition to the below, there are at least two of us over at openacs.org reporting that scheduled procs stopped firing over the weekend. I have one site left on 3.3+ad13 and the other guy says he has 3.2+ad12. This site hasn't been upgraded because the client didn't want to upgrade, so any pointers on fixing this would be greatly appreciated. janine On May 15, 2006, at 9:55 AM, Guan Yang wrote: I've experienced this problem over the weekend on half a dozen servers in three different locations: After starting up, AOLserver (mostly 3.4.2, also a 3.5.11) begins allocating a lot of virtual memory. When I follow the process in top, the virtual memory counter (but not real memory) rapidly increases over the course of 10 to 20 seconds, until it hits the limit of 3 GB virtual memory in user space on x86 Linux boxes. The process then crashes with this message: nsthread(3094) error: pthread_create failed in NsThreadCreate: Cannot allocate memory (The process is then restarted by supervise/svscan.) I couldn't find a fix for the problem and had to migrate to AOLserver 4.0.10 (we had already planned this for next month) immediately. But I find it a bit weird that practically every AOLserver 3 installation that I know of encounters this problem over the same weekend. Just bad luck? Date sensitive code? Guan -- 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. -- 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. -- 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] Weird memory leak problem in AOLserver 3.4.2/3.x
I realized after I sent this last night that the other two sites are probably still working because they haven't been restarted in quite a while. The live site gets restarted fairly frequently, so it started exhibiting the problem right away. janine On May 16, 2006, at 12:18 AM, Janine Sisk wrote: By the way, one more thing: I have three sites running on this server - staging, live and an old keepalive instance. The live site is the only one exhibiting the scheduled proc problem; it's also the only one that gets any significant traffic. So I'm thinking it's some kind of overflow where it only causes problems when a busy site is using memory and ends up overwriting something. janine On May 16, 2006, at 12:10 AM, Janine Sisk wrote: In addition to the below, there are at least two of us over at openacs.org reporting that scheduled procs stopped firing over the weekend. I have one site left on 3.3+ad13 and the other guy says he has 3.2+ad12. This site hasn't been upgraded because the client didn't want to upgrade, so any pointers on fixing this would be greatly appreciated. janine On May 15, 2006, at 9:55 AM, Guan Yang wrote: I've experienced this problem over the weekend on half a dozen servers in three different locations: After starting up, AOLserver (mostly 3.4.2, also a 3.5.11) begins allocating a lot of virtual memory. When I follow the process in top, the virtual memory counter (but not real memory) rapidly increases over the course of 10 to 20 seconds, until it hits the limit of 3 GB virtual memory in user space on x86 Linux boxes. The process then crashes with this message: nsthread(3094) error: pthread_create failed in NsThreadCreate: Cannot allocate memory (The process is then restarted by supervise/svscan.) I couldn't find a fix for the problem and had to migrate to AOLserver 4.0.10 (we had already planned this for next month) immediately. But I find it a bit weird that practically every AOLserver 3 installation that I know of encounters this problem over the same weekend. Just bad luck? Date sensitive code? Guan -- 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. -- 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. -- 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. -- 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] Weird memory leak problem in AOLserver 3.4.2/3.x
On May 16, 2006, at 8:04 AM, Nathan Folkman wrote: It's been a while, and I'm still on my first cup of coffee, but I think your biggest hurdle is probably going to be the loss of ns_share in favor of nsv. Also 4.x requires Tcl 8.x. Hope that helps! Ugh. You're absolutely right - this site is *full* of ns_shares. That's probably another reason why we decided not to tackle this a while back. I know the client didn't want to spend any time on the old site if it could possibly be avoided. janine -- 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] Retrieving oid from INSERT
The way we do this in OpenACS is to have a primary key in each table that is populated from a sequence. So in your code you get the next number from the sequence, do the insert (storing the number in the primary key column), and then you have that number already in your possession to use to reference the row. janine On Mar 28, 2006, at 11:58 AM, William Scott Jordan wrote: Hi all! Is there any way to get the oid or any other row identifier from a database insert with ns_db on Postgres? Say for example I have the following table: CREATE TABLE test ( test_column int ) ; And then I do an insert with aolserver, along the lines of: ns_db dml $db INSERT INTO test (test_column) SELECT COALESCE(MAX (test_column),0) + 1 FROM test Because I don't know the value of test_column that I just entered, I don't have any way to continue working with that entry. Is there some trick to getting either the entry's oid or the value of test_column back into the current TCL workspace? Any suggestions would be appreciated. -Scott -- 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. -- 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] Returning a 301 status to the client
Tom, The problem is that when ad_returnredirect is using ns_respond instead of ns_returnredirect, cookies don't work. When you try to log in, you just keep getting sent back to the login page. And if you try to put something in your cart, you get the message about cookies being disabled. Since the change doesn't affect the cookie's being set in the first place, my assumption is that it's not making it intact through the redirect. janine On Feb 17, 2006, at 10:24 PM, Tom Jackson wrote: Janine, But when I send the telnet request, with the Cookie: header, I get the same thing as when I use a browser. The target page test2.tcl doesn't include the Set-Cookie header in response. Is this what you want to happen or not? Here is what I think is happening: The client sends a request with a Cookie header (not Set-Cookie), so OACS knows who the user is. For some reason, this causes OACS to not include a Set-Cookie header for return to the client. I'm still not quite sure what the actual problem is that caused you to look into this, so maybe there is another issue besides this one. But the browser is working exactly like telnet if you include the Cookie header with the telnet request for test2.tcl. Nothing is wrong with the way the browser is working. But I think that OACS should probably be updating the cookie value so that the new expiration time will take effect. What code is deciding when to set the header? If OACS doesn't do this update, then eventually the 1200 seconds will expire and the browser will no longer send that cookie. At that point OACS will issue a new cookie and probably force the user to login again. Is that the behavior you are seeing? tom jackson On Friday 17 February 2006 18:30, Janine Sisk wrote: I may have started you on the proverbial wild goose chase with this cookie stuff, so let's start over. There are two main differences between a page sent to the browser via ns_returnredirect vs one sent by ns_respond. ns_returnredirect puts together a small HTML page and sends it off to the browser with content type text/html, using the header data that's already in the conn data structure. ns_respond takes the set of headers passed to it, replaces the headers in conn with the ones that are passed in, and then sends the string off to the browser. So the two significant differences are the handling of the headers, and that ns_returnredirect sends a properly formed HTML page whereas my use of ns_respond sends only the word Redirect. My hunch is that the former is the problem. So could there be something about the way the -headers argument to ns_respond is handled that is somehow garbling the data? Could Tcl be doing something to it as it's being passed along? janine On Feb 17, 2006, at 6:03 PM, Tom Jackson wrote: Janine, Now I'm getting confused. If the browser or the telnet sends the cookie it just received, the outputheaders on test2.tcl don't include a set- cookie header. So it isn't in the outputheaders I guess. I just did this: [EMAIL PROTECTED]:/media/floppy telnet temp.nybooks.com 80 Trying 209.162.194.75... Connected to temp.nybooks.com. Escape character is '^]'. GET /test.tcl HTTP/1.0 Host: temp.nybooks.com HTTP/1.0 302 Found Host: temp.nybooks.com Set-Cookie: ad_session_id=8004%2c0+%7b663+1140228924 +1E0DA0457345E6F9CE3F6D34E60EA76197B8858D%7d; Path=/; Max-Age=1200 location: http://temp.nybooks.com/test2.tcl MIME-Version: 1.0 Date: Sat, 18 Feb 2006 01:55:24 GMT Server: AOLserver/4.0.10 Content-Type: text/plain; charset=iso-8859-1 Content-Length: 8 Connection: close RedirectConnection closed by foreign host. [EMAIL PROTECTED]:/media/floppy telnet temp.nybooks.com 80 Trying 209.162.194.75... Connected to temp.nybooks.com. Escape character is '^]'. GET /test2.tcl HTTP/1.0 Host: temp.nybooks.com Cookie: ad_session_id=8004%2c0+%7b663+1140228924 +1E0DA0457345E6F9CE3F6D34E60EA76197B8858D%7d; HTTP/1.0 200 OK MIME-Version: 1.0 Content-Type: text/html Server: AOLserver/4.0 ns_conn headers - size = 2br key = Host, value = temp.nybooks.combr key = Cookie, value = ad_session_id=8004%2c0+%7b663+1140228924 +1E0DA0457345E6F9CE3F6D34E60EA76197B8858D%7d;br p ad_conn headers - size = 2br key = Host, value = temp.nybooks.combr key = Cookie, value = ad_session_id=8004%2c0+%7b663+1140228924 +1E0DA0457345E6F9CE3F6D34E60EA76197B8858D%7d;br p ns_conn outputheaders - size = 1br key = Server, value = AOLserver/4.0br p ad_conn outputheaders - size = 1br key = Server, value = AOLserver/4.0br Connection closed by foreign host. My browser shows the same behavior as telnet. OACS isn't filling the outputheader with the set-cookie if the browser/client has a cookie. tom jackson On Friday 17 February 2006 17:35, Janine Sisk wrote: Well no, I'm not sure that it sends the Set-Cookie header on every request. But something about the change I made is causing OACS to act as though the browser has cookies turned off, so I kind of zeroed
Re: [AOLSERVER] Returning a 301 status to the client
It has to be related to changing from ns_returnredirect to ns_respond. Because the former works, and the latter doesn't, and nothing else is changing. I can flip between the two and make cookies work, or not work. There is something different about what ns_respond does, I just don't know what it is. janine On Feb 18, 2006, at 8:17 AM, Tom Jackson wrote: Janine, Okay, so the problem you are seeing must be somewhere else, because when I visit test.tcl with a firefox browser, I get redirected to test2.tcl and I have a cookie set and it sends the cookie back to the server, which is read by test2.tcl. The type of cookie is a session cookie, which will expire in 1200 sec. The only thing that looks weird to me is that I would think that OACS should send a similar cookie which also expires in 1200 sec so that a user who is grabbing a page ever 20 minutes stays logged in. Right now it looks like that doesn't happen. Maybe the redirect is to a different domain that isn't covered by the cookie? Or the cookie is set in https as secure, but the user is redirected to http? But I don't see the issue from what you have presented so far. I will say that this reminds me of http://www.washingtonpost.com/ , which for whatever reason doesn't accept cookies from my konqurer browser. Does exactly what you describe here. So you might at the very least test in another browser from a separate code base than whatever you use, which you probably have already done. tom jackson On Saturday 18 February 2006 00:08, Janine Sisk wrote: Tom, The problem is that when ad_returnredirect is using ns_respond instead of ns_returnredirect, cookies don't work. When you try to log in, you just keep getting sent back to the login page. And if you try to put something in your cart, you get the message about cookies being disabled. Since the change doesn't affect the cookie's being set in the first place, my assumption is that it's not making it intact through the redirect. -- 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. -- 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.
[AOLSERVER] Returning a 301 status to the client
This should be simple, but it's turning out not to be. First I used this code, which I got from a post at openacs.org (and the poster got it from the AOLserver docs for ns_respond): set headers [ns_set new myheaders] ns_set put $headers location $url ns_respond -status $return_code -type text/plain -string Redirect - headers $headers This worked as far as the redirect and status code are concerned, but cookies were no longer functioning. I noticed that ad_set_cookie (an openacs proc) adds a key called Set- Cookie to the ns_conn outputheaders set, so I tried this, hoping to capture all possible relevant values: set headers [ad_conn headers] set outputheaders [ad_conn outputheaders] set allheaders [ns_set merge $headers $outputheaders] ns_set idelkey $allheaders location ns_set put $allheaders location $url ns_respond -status $return_code -type text/plain -string Redirect - headers $allheaders No improvement; cookies still don't work. BTW, I tried it with both ns_conn and ad_conn but they both give the exact same output, so same end result. Any suggestions on what I might be doing wrong here? I know that the best way to fix this would be to create an ns_returnmoved function in AOLserver, but I was trying to avoid having any of our clients using a customized version. Thanks for any suggestions, janine -- 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] Returning a 301 status to the client
If I telnet in and do GET / I just get the HTML for the page, like you would expect: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN http://www.w3.org/TR/html4/loose.dtd; html head and so forth. If I request the page that does the redirect I get GET test.tcl RedirectConnection closed by foreign host. However if I request test.tcl in the browser I do get properly redirected to test2.tcl. I am not very well versed in telnet commands, so if there's something else I can do to get more info, please let me know. Yes, I have printed out the contents of outputheaders and the Set- Cookie is there, but it doesn't make it through the redirect. janine On Feb 17, 2006, at 2:48 PM, Tom Jackson wrote: Janine, If you telnet into the page, what do you get sent back? I'm not sure where in here you add the Set-Cookie header? Do you know that it is in the output headers at the time you grab a copy of the set? tom jackson On Friday 17 February 2006 14:10, Janine Sisk wrote: This should be simple, but it's turning out not to be. First I used this code, which I got from a post at openacs.org (and the poster got it from the AOLserver docs for ns_respond): set headers [ns_set new myheaders] ns_set put $headers location $url ns_respond -status $return_code -type text/plain -string Redirect - headers $headers This worked as far as the redirect and status code are concerned, but cookies were no longer functioning. I noticed that ad_set_cookie (an openacs proc) adds a key called Set- Cookie to the ns_conn outputheaders set, so I tried this, hoping to capture all possible relevant values: set headers [ad_conn headers] set outputheaders [ad_conn outputheaders] set allheaders [ns_set merge $headers $outputheaders] ns_set idelkey $allheaders location ns_set put $allheaders location $url ns_respond -status $return_code -type text/plain -string Redirect - headers $allheaders No improvement; cookies still don't work. BTW, I tried it with both ns_conn and ad_conn but they both give the exact same output, so same end result. Any suggestions on what I might be doing wrong here? I know that the best way to fix this would be to create an ns_returnmoved function in AOLserver, but I was trying to avoid having any of our clients using a customized version. Thanks for any suggestions, janine -- 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. -- 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. -- 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] Returning a 301 status to the client
OK, so here we go. test.tcl contains a single line, a call to ad_returnredirect, which has been modified to use ns_respond instead of ns_returnredirect. GET /test.tcl HTTP/1.0 HTTP/1.0 302 Found Set-Cookie: ad_session_id=80111002%2c0+%7b542+1140224229 +57E9A3EA3E33AB40F47F8EA71184A3D012E347ED%7d; Path=/; Max-Age=1200 location: http://temp.nybooks.com/test2.tcl MIME-Version: 1.0 Date: Sat, 18 Feb 2006 00:37:09 GMT Server: AOLserver/4.0.10 Content-Type: text/plain; charset=iso-8859-1 Content-Length: 8 Connection: close RedirectConnection closed by foreign host. And if I request test2.tcl directly, I get GET /test2.tcl HTTP/1.0 HTTP/1.0 200 OK MIME-Version: 1.0 Content-Type: text/html Set-Cookie: ad_session_id=80111202%2c0+%7b453+1140224589 +962CB2C08C8F3888B4A1FF91770F02814E70BB45%7d; Path=/; Max-Age=1200 Server: AOLserver/4.0 ns_conn headers - size = 0br p ad_conn headers - size = 0br p ns_conn outputheaders - size = 2br key = Set-Cookie, value = ad_session_id=80111202%2c0+%7b453+1140224589 +962CB2C08C8F3888B4A1FF91770F02814E70BB45%7d; Path=/; Max-Age=1200br key = Server, value = AOLserver/4.0br p ad_conn outputheaders - size = 2br key = Set-Cookie, value = ad_session_id=80111202%2c0+%7b453+1140224589 +962CB2C08C8F3888B4A1FF91770F02814E70BB45%7d; Path=/; Max-Age=1200br key = Server, value = AOLserver/4.0br Connection closed by foreign host. So Set-Cookie is there. However, if I request test.tcl in the browser, I get redirected to test2.tcl which prints out the output of ad/ns_conn headers and ad/ ns_conn outputheaders, where there is nary a Set-Cookie in sight. Somehow it's getting lost along the way. I'm perplexed. janine On Feb 17, 2006, at 3:45 PM, Tom Jackson wrote: Janine, So the command sequence I use goes like this: $ telnet rmadilo.com 80 Trying 216.211.130.179... Connected to rmadilo.com. Escape character is '^]'. GET /mypage HTTP/1.0 Host: rmadilo.com HTTP/1.0 200 OK Set-Cookie: SessionID = 9A7EDDAAACCD226251DFC34240FA7A320FA7FE5C ; Max-Age = 911003711 ; Path=/ Set-Cookie2: SessionID = 9A7EDDAAACCD226251DFC34240FA7A320FA7FE5C ; Max-Age = 911003711 ; Path=/ ; Version = 1 Last-Modified: Mon, 09 May 2005 23:27:28 GMT MIME-Version: 1.0 Date: Sat, 18 Feb 2006 00:24:49 GMT Server: AOLserver/4.0.10 Content-Type: text/html; charset=iso-8859-1 Content-Length: 29 Connection: close a href=/files/Files/a It is only necessary to use the Host: header if you use virtual hosting. tom jackson On Friday 17 February 2006 15:12, Janine Sisk wrote: If I telnet in and do GET / I just get the HTML for the page, like you would expect: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN http://www.w3.org/TR/html4/loose.dtd; html head and so forth. If I request the page that does the redirect I get GET test.tcl RedirectConnection closed by foreign host. However if I request test.tcl in the browser I do get properly redirected to test2.tcl. I am not very well versed in telnet commands, so if there's something else I can do to get more info, please let me know. Yes, I have printed out the contents of outputheaders and the Set- Cookie is there, but it doesn't make it through the redirect. janine On Feb 17, 2006, at 2:48 PM, Tom Jackson wrote: Janine, If you telnet into the page, what do you get sent back? I'm not sure where in here you add the Set-Cookie header? Do you know that it is in the output headers at the time you grab a copy of the set? tom jackson On Friday 17 February 2006 14:10, Janine Sisk wrote: This should be simple, but it's turning out not to be. First I used this code, which I got from a post at openacs.org (and the poster got it from the AOLserver docs for ns_respond): set headers [ns_set new myheaders] ns_set put $headers location $url ns_respond -status $return_code -type text/plain -string Redirect - headers $headers This worked as far as the redirect and status code are concerned, but cookies were no longer functioning. I noticed that ad_set_cookie (an openacs proc) adds a key called Set- Cookie to the ns_conn outputheaders set, so I tried this, hoping to capture all possible relevant values: set headers [ad_conn headers] set outputheaders [ad_conn outputheaders] set allheaders [ns_set merge $headers $outputheaders] ns_set idelkey $allheaders location ns_set put $allheaders location $url ns_respond -status $return_code -type text/plain -string Redirect - headers $allheaders No improvement; cookies still don't work. BTW, I tried it with both ns_conn and ad_conn but they both give the exact same output, so same end result. Any suggestions on what I might be doing wrong here? I know that the best way to fix this would be to create an ns_returnmoved function in AOLserver, but I was trying to avoid having any of our clients using a customized version. Thanks for any suggestions, janine -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email
Re: [AOLSERVER] Returning a 301 status to the client
Well no, I'm not sure that it sends the Set-Cookie header on every request. But something about the change I made is causing OACS to act as though the browser has cookies turned off, so I kind of zeroed in on that. If there are other things that could cause that symptom I should look at those too, I just didn't know what they might be. janine On Feb 17, 2006, at 5:24 PM, Tom Jackson wrote: Janine, I would try the second request via telnet, but send the cookie value you received on the first request. Are you sure that OACS sends the Set- Cookie header on every request? Maybe it doesn't do it since the cookie is already there? tom jackson GET /test.tcl HTTP/1.0 Host: temp.nybooks.com Cookie: ad_session_id=80111002%2c0+%7b542+1140224229 +57E9A3EA3E33AB40F47F8EA71184A3D012E347ED%7d; On Friday 17 February 2006 16:44, Janine Sisk wrote: OK, so here we go. test.tcl contains a single line, a call to ad_returnredirect, which has been modified to use ns_respond instead of ns_returnredirect. GET /test.tcl HTTP/1.0 HTTP/1.0 302 Found Set-Cookie: ad_session_id=80111002%2c0+%7b542+1140224229 +57E9A3EA3E33AB40F47F8EA71184A3D012E347ED%7d; Path=/; Max-Age=1200 location: http://temp.nybooks.com/test2.tcl MIME-Version: 1.0 Date: Sat, 18 Feb 2006 00:37:09 GMT Server: AOLserver/4.0.10 Content-Type: text/plain; charset=iso-8859-1 Content-Length: 8 Connection: close RedirectConnection closed by foreign host. And if I request test2.tcl directly, I get GET /test2.tcl HTTP/1.0 HTTP/1.0 200 OK MIME-Version: 1.0 Content-Type: text/html Set-Cookie: ad_session_id=80111202%2c0+%7b453+1140224589 +962CB2C08C8F3888B4A1FF91770F02814E70BB45%7d; Path=/; Max-Age=1200 Server: AOLserver/4.0 ns_conn headers - size = 0br p ad_conn headers - size = 0br p ns_conn outputheaders - size = 2br key = Set-Cookie, value = ad_session_id=80111202%2c0+%7b453 +1140224589 +962CB2C08C8F3888B4A1FF91770F02814E70BB45%7d; Path=/; Max- Age=1200br key = Server, value = AOLserver/4.0br p ad_conn outputheaders - size = 2br key = Set-Cookie, value = ad_session_id=80111202%2c0+%7b453 +1140224589 +962CB2C08C8F3888B4A1FF91770F02814E70BB45%7d; Path=/; Max- Age=1200br key = Server, value = AOLserver/4.0br Connection closed by foreign host. So Set-Cookie is there. However, if I request test.tcl in the browser, I get redirected to test2.tcl which prints out the output of ad/ns_conn headers and ad/ ns_conn outputheaders, where there is nary a Set-Cookie in sight. Somehow it's getting lost along the way. I'm perplexed. janine On Feb 17, 2006, at 3:45 PM, Tom Jackson wrote: Janine, So the command sequence I use goes like this: $ telnet rmadilo.com 80 Trying 216.211.130.179... Connected to rmadilo.com. Escape character is '^]'. GET /mypage HTTP/1.0 Host: rmadilo.com HTTP/1.0 200 OK Set-Cookie: SessionID = 9A7EDDAAACCD226251DFC34240FA7A320FA7FE5C ; Max-Age = 911003711 ; Path=/ Set-Cookie2: SessionID = 9A7EDDAAACCD226251DFC34240FA7A320FA7FE5C ; Max-Age = 911003711 ; Path=/ ; Version = 1 Last-Modified: Mon, 09 May 2005 23:27:28 GMT MIME-Version: 1.0 Date: Sat, 18 Feb 2006 00:24:49 GMT Server: AOLserver/4.0.10 Content-Type: text/html; charset=iso-8859-1 Content-Length: 29 Connection: close a href=/files/Files/a It is only necessary to use the Host: header if you use virtual hosting. tom jackson On Friday 17 February 2006 15:12, Janine Sisk wrote: If I telnet in and do GET / I just get the HTML for the page, like you would expect: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN http://www.w3.org/TR/html4/loose.dtd; html head and so forth. If I request the page that does the redirect I get GET test.tcl RedirectConnection closed by foreign host. However if I request test.tcl in the browser I do get properly redirected to test2.tcl. I am not very well versed in telnet commands, so if there's something else I can do to get more info, please let me know. Yes, I have printed out the contents of outputheaders and the Set- Cookie is there, but it doesn't make it through the redirect. janine On Feb 17, 2006, at 2:48 PM, Tom Jackson wrote: Janine, If you telnet into the page, what do you get sent back? I'm not sure where in here you add the Set-Cookie header? Do you know that it is in the output headers at the time you grab a copy of the set? tom jackson On Friday 17 February 2006 14:10, Janine Sisk wrote: This should be simple, but it's turning out not to be. First I used this code, which I got from a post at openacs.org (and the poster got it from the AOLserver docs for ns_respond): set headers [ns_set new myheaders] ns_set put $headers location $url ns_respond -status $return_code -type text/plain -string Redirect - headers $headers This worked as far as the redirect and status code are concerned, but cookies were no longer functioning. I noticed that ad_set_cookie (an openacs proc) adds a key called Set- Cookie to the ns_conn outputheaders set, so I tried this, hoping to capture all possible
Re: [AOLSERVER] Returning a 301 status to the client
I may have started you on the proverbial wild goose chase with this cookie stuff, so let's start over. There are two main differences between a page sent to the browser via ns_returnredirect vs one sent by ns_respond. ns_returnredirect puts together a small HTML page and sends it off to the browser with content type text/html, using the header data that's already in the conn data structure. ns_respond takes the set of headers passed to it, replaces the headers in conn with the ones that are passed in, and then sends the string off to the browser. So the two significant differences are the handling of the headers, and that ns_returnredirect sends a properly formed HTML page whereas my use of ns_respond sends only the word Redirect. My hunch is that the former is the problem. So could there be something about the way the -headers argument to ns_respond is handled that is somehow garbling the data? Could Tcl be doing something to it as it's being passed along? janine On Feb 17, 2006, at 6:03 PM, Tom Jackson wrote: Janine, Now I'm getting confused. If the browser or the telnet sends the cookie it just received, the outputheaders on test2.tcl don't include a set- cookie header. So it isn't in the outputheaders I guess. I just did this: [EMAIL PROTECTED]:/media/floppy telnet temp.nybooks.com 80 Trying 209.162.194.75... Connected to temp.nybooks.com. Escape character is '^]'. GET /test.tcl HTTP/1.0 Host: temp.nybooks.com HTTP/1.0 302 Found Host: temp.nybooks.com Set-Cookie: ad_session_id=8004%2c0+%7b663+1140228924 +1E0DA0457345E6F9CE3F6D34E60EA76197B8858D%7d; Path=/; Max-Age=1200 location: http://temp.nybooks.com/test2.tcl MIME-Version: 1.0 Date: Sat, 18 Feb 2006 01:55:24 GMT Server: AOLserver/4.0.10 Content-Type: text/plain; charset=iso-8859-1 Content-Length: 8 Connection: close RedirectConnection closed by foreign host. [EMAIL PROTECTED]:/media/floppy telnet temp.nybooks.com 80 Trying 209.162.194.75... Connected to temp.nybooks.com. Escape character is '^]'. GET /test2.tcl HTTP/1.0 Host: temp.nybooks.com Cookie: ad_session_id=8004%2c0+%7b663+1140228924 +1E0DA0457345E6F9CE3F6D34E60EA76197B8858D%7d; HTTP/1.0 200 OK MIME-Version: 1.0 Content-Type: text/html Server: AOLserver/4.0 ns_conn headers - size = 2br key = Host, value = temp.nybooks.combr key = Cookie, value = ad_session_id=8004%2c0+%7b663+1140228924 +1E0DA0457345E6F9CE3F6D34E60EA76197B8858D%7d;br p ad_conn headers - size = 2br key = Host, value = temp.nybooks.combr key = Cookie, value = ad_session_id=8004%2c0+%7b663+1140228924 +1E0DA0457345E6F9CE3F6D34E60EA76197B8858D%7d;br p ns_conn outputheaders - size = 1br key = Server, value = AOLserver/4.0br p ad_conn outputheaders - size = 1br key = Server, value = AOLserver/4.0br Connection closed by foreign host. My browser shows the same behavior as telnet. OACS isn't filling the outputheader with the set-cookie if the browser/client has a cookie. tom jackson On Friday 17 February 2006 17:35, Janine Sisk wrote: Well no, I'm not sure that it sends the Set-Cookie header on every request. But something about the change I made is causing OACS to act as though the browser has cookies turned off, so I kind of zeroed in on that. If there are other things that could cause that symptom I should look at those too, I just didn't know what they might be. janine On Feb 17, 2006, at 5:24 PM, Tom Jackson wrote: Janine, I would try the second request via telnet, but send the cookie value you received on the first request. Are you sure that OACS sends the Set- Cookie header on every request? Maybe it doesn't do it since the cookie is already there? tom jackson GET /test.tcl HTTP/1.0 Host: temp.nybooks.com Cookie: ad_session_id=80111002%2c0+%7b542+1140224229 +57E9A3EA3E33AB40F47F8EA71184A3D012E347ED%7d; On Friday 17 February 2006 16:44, Janine Sisk wrote: OK, so here we go. test.tcl contains a single line, a call to ad_returnredirect, which has been modified to use ns_respond instead of ns_returnredirect. GET /test.tcl HTTP/1.0 HTTP/1.0 302 Found Set-Cookie: ad_session_id=80111002%2c0+%7b542+1140224229 +57E9A3EA3E33AB40F47F8EA71184A3D012E347ED%7d; Path=/; Max-Age=1200 location: http://temp.nybooks.com/test2.tcl MIME-Version: 1.0 Date: Sat, 18 Feb 2006 00:37:09 GMT Server: AOLserver/4.0.10 Content-Type: text/plain; charset=iso-8859-1 Content-Length: 8 Connection: close RedirectConnection closed by foreign host. And if I request test2.tcl directly, I get GET /test2.tcl HTTP/1.0 HTTP/1.0 200 OK MIME-Version: 1.0 Content-Type: text/html Set-Cookie: ad_session_id=80111202%2c0+%7b453+1140224589 +962CB2C08C8F3888B4A1FF91770F02814E70BB45%7d; Path=/; Max-Age=1200 Server: AOLserver/4.0 ns_conn headers - size = 0br p ad_conn headers - size = 0br p ns_conn outputheaders - size = 2br key = Set-Cookie, value = ad_session_id=80111202%2c0+%7b453 +1140224589 +962CB2C08C8F3888B4A1FF91770F02814E70BB45%7d; Path=/; Max- Age=1200br key = Server, value
Re: [AOLSERVER] PostgreSQL near-lockups
On Jan 17, 2006, at 11:40 PM, Bas Scheffers wrote: On 18 Jan 2006, at 04:15, Janine Sisk wrote: The thing I don't understand is why this happens to some sites, while others can be restarted with -t all day long and they will never hang. It seems to hint at there being something wrong with the few sites afflicted by this, doesn't it? These sites aren't running one of those older 4.x versions that don't actually stop when told to. (ie: requiring a second ctrl-c when running in the foreground) No, at least one of my sites that does it is running OpenACS 3.x. janine -- 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] PostgreSQL near-lockups
On Jan 17, 2006, at 5:51 PM, Tom Jackson wrote: If you want a slightly different alternative, try -t, wait a few seconds for most everything to stop, then do a -k, but this behavior has been around for a long time, mostly because people use -t. The thing I don't understand is why this happens to some sites, while others can be restarted with -t all day long and they will never hang. It seems to hint at there being something wrong with the few sites afflicted by this, doesn't it? janine -- 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] PostgreSQL near-lockups
We have found that some sites, when restarted with svc -t, go into a funky half-shut-down state and stay there. I don't know why, and it seems to be very consistently some sites (all using PG) and not others. For those sites we use svc -k, in other words send the kill signal instead of the terminate signal. If you have things set up properly it doesn't really matter, the site should come back up either way. I don't know if this is your problem or not, but it's worth a try. janine On Jan 16, 2006, at 5:18 PM, Dave Siktberg wrote: Janine Sisk recently wrote that she restarts her AOLservers every night to help prevent lockups. I'd like to do that, but often when I do a restart I get several postgresql threads that chew up nearly all the cpu cycles for 30 minutes or more and effectively block access to my site. It appears to be a shorter wait if I do a restart each day, but I'm loathe to risk making the site unavailable for a long time even in the wee hours. Any idea what could cause this? How to fix it? A year ago I did not observe this behavior. Dave Siktberg -- 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. -- 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 bug
On Jan 12, 2006, at 11:34 AM, Jeff Rogers wrote: I found a bug in aolserver 4.0.10 (and previous 4.x versions, not sure about earlier) that causes the server to lock up. I'm fairly certain I understand the cause, and my fix appears to work although I'm not sure it is the best approach. FWIW, we see this happening on all our busy sites. Whether the cause is the same I don't know, but the symptoms are identical. We do nightly restarts, which helps reduce the incidence, but it is still not uncommon to have sites get restarted because they were non- responsive and yet the system load was nearly 0. janine -- 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 not responding or hanging
All of our busier AOLserver-based sites hang like this periodically, but that's maybe once or twice a month. Five times a day sounds a bit extreme. You might need to increase your number of connections, or maybe your stack size (though running out of stack tends to cause crashes rather than hangs). However, as far as I can tell nothing you do will eliminate this completely. It has been happening to us for years, though different versions of all the various pieces of software we use. It's pretty tough to track down the cause since once it happens nsd is totally unresponsive and doesn't give any clues as to what happened. It seems to happen more often on busier sites, and I know of some sites that have a daily restart process to keep the hangs at bay. Sorry to not be more encouraging, janine On Sep 30, 2005, at 3:17 PM, Nathaniel Haggard wrote: AOLserver becomes unresponsive at least 5 times a day. Restarting the server fixes the problem, but since it won't crash inittab doesn't automatically restart it. I think it may be nsopenssl, the postgres driver, or evil adp code. Is there a known probelm with this combination of packages? nsopenssl-3.0beta26 tcl 8.4.11 aolserver 4.0.10 What could be causing this? Where should I start troubleshooting? Nate -- 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. -- 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 not responding or hanging
I don't have a copy of that handy - does it use ns_server? If so, that command (which used to be useful in tracking these things down) now randomly causes nsd to crash. I forget the reason; I think it's due to an architectural change in 4.x.janineOn Oct 3, 2005, at 10:57 AM, Nathaniel Haggard wrote:And running nstelemetry.adp causes it to stop responding as well. NateOn 9/30/05, Nathaniel Haggard [EMAIL PROTECTED] wrote: AOLserver becomes unresponsive at least 5 times a day. Restarting the server fixes the problem, but since it won't crash inittab doesn't automatically restart it. I think it may be nsopenssl, the postgres driver, or evil adp code. Is there a known probelm with this combination of packages? nsopenssl-3.0beta26 tcl 8.4.11 aolserver 4.0.10 What could be causing this? Where should I start troubleshooting? Nate -- 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. -- 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 not responding or hanging
It is Linux. Unfortunately, it's always the production instances that hang, and I can't leave them that way while I poke around. Especially since it seems to be load related and so usually happens at the busiest times of the day. I don't really know how to use gdb; if there is something quick I can do that can be examined offline, let me know and I will try it. janine On Oct 3, 2005, at 11:15 AM, Dossy Shiobara wrote: On 2005.10.03, Janine Sisk [EMAIL PROTECTED] wrote: It's pretty tough to track down the cause since once it happens nsd is totally unresponsive and doesn't give any clues as to what happened. If you're running on Solaris, you might want to capture the pstack output of the process. On Linux, you could attach with gdb and try to get a backtrace. -- 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. -- 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.
[AOLSERVER] Server not stopping, revisited
Ok, sorry for the break - I had to go off and work on something else, but I'm back now. To recap: I have a site that has a lot of scheduled procs that run frequently, so there is one going off every few seconds. Under AOLserver 4.0.1, I had no problems restarting this site, but under 4.0.10 it stops accepting connections but keeps on running the scheduled procs. From the error logs: 4.0.1: [08/Jul/2005:20:00:57][30673.3073912960][-main-] Notice: nsmain: AOLserver/4.0 stopping [08/Jul/2005:20:00:57][30673.3073912960][-main-] Notice: serv: stopping server: live-gmt [08/Jul/2005:20:00:57][30673.3073912960][-main-] Notice: serv: connection threads stopped [08/Jul/2005:20:00:57][30673.3073912960][-main-] Notice: driver: shutdown complete [08/Jul/2005:20:00:57][30673.3073912960][-main-] Notice: sched: shutdown pending [08/Jul/2005:20:00:57][30673.3063348144][-sched-] Notice: sched: shutdown started [08/Jul/2005:20:00:57][30673.3063348144][-sched-] Notice: sched: waiting for event threads... [08/Jul/2005:20:00:57][30673.3045063600][-sched:idle1-] Notice: exiting [08/Jul/2005:20:00:57][30673.3050306480][-sched:idle2-] Notice: exiting [08/Jul/2005:20:00:57][30673.3048209328][-sched:idle0-] Notice: exiting [08/Jul/2005:20:00:59][30673.3063348144][-sched-] Notice: sched: shutdown complete [08/Jul/2005:20:00:59][30673.3063348144][-shutdown-] Notice: nslog: closing '/export/logs/live/live-gmt.log' [08/Jul/2005:20:00:59][30673.3073912960][-main-] Notice: nsmain: AOLserver/4.0 exiting 4.0.10: [18/Jul/2005:16:35:50][11681.3086617504][-main-] Notice: nsmain: AOLserver/4.0.10 stopping [18/Jul/2005:16:35:50][11681.3086617504][-main-] Notice: driver: triggering shutdown [18/Jul/2005:16:35:50][11681.3086617504][-main-] Notice: serv: stopping server: live-gmt [18/Jul/2005:16:35:51][11681.3086617504][-main-] Notice: serv: connection threads stopped and then it goes on allowing new scheduled procs to start up and run, so it never goes any further with it's shutdown. It appears it will stay in this state forever, though I've never left it longer than about 5 minutes. When we discussed this before Dossy suggested modifying background threads to detect that the server is shutting down. That's not the problem, though; as far as I know we don't have any particularly long-running processes. The problem is that the scheduler is letting new ones start up. Any suggestions on how to debug/fix this? thanks, janine -- 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] access log getting wiped
On Jul 21, 2005, at 3:49 AM, Mark Aufflick wrote: That's interesting to note about the rollfmt/maxbackup thing - it answers Janine's point about eventually losing log data with maxbackup. It does, though I'm not sure I'd want to rely on it - it sounds like something that someone could eventually decide is a bug and needs fixing. IMHO it would be better to have a magic value to use for maxbackup that explicitly means there is no max. janine -- 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] charset problem update
On Jul 20, 2005, at 2:04 AM, Andrew Piskorski wrote: You should run csscan on that database to get an idea of the extent of your character set problems. I'm doing this now, against the original database, to hopefully give me an idea of which tables need to be updated with the data I converted yesterday. I'm wondering, though... in it's intended use of running this tool before starting out, what does it tell you besides sorry, you're screwed? I haven't found any documentation suggesting you can actually fix the problem data in any way. Is there something one could actually do if they did run this before converting, other than know how big a mess they were going to end up with? janine -- 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.
[AOLSERVER] charset problem update
Below is the update I just sent to the Oracle list, in case it sparks any ideas here. I have no objection to UTF-8 except that converting to it is problematic, according to Ask Tom, because everything takes up more space and things can overflow their storage (something else Oracle should handle, but presumably does not). So for the moment I'll settle for any character set that works, and worry about the Euro later. :) janine Thanks to everyone who e-mailed me with suggestions and info from metalink and other sources. It was all good stuff, but ultimately not the right stuff. I tried various scenarios: - export from old database with NLS_LANG set to US7ASCII, import to new database with NLS_LANG set to USASCII, let imp do the conversion - export from old database with NLS_LANG set to WE8ISO8859P1, import to new database with NLS_LANG set to WE8ISO8859P1, let exp do the conversion but nothing worked. I ultimately found a white paper from Oracle (this is the HTML version of their PDF, from google): http://66.102.7.104/search?q=cache:1shB3SfIDNkJ:www.oracle.com/ technology/tech/globalization/pdf/ TWP_Character_Set_Migration_Best_Practices_10gR2.pdf+oracle+export+us7as cii++8-bithl=enstart=1client=firefox-a which talks about what a big job this is. As far as I can tell, the problem is that Oracle lets you store 8-bit characters with a 7-bit character setting, but when you do any sort of conversion it forgets about that and drops the 8th bit. I then tried a different approach. I set up a second database on the 8i system, still in US7ASCII. I loaded my data into it, and verified that this time it loaded and displayed correctly. Then I tried changing the character set of the database. I thought this might perhaps use different conversion code and maybe it was done correctly, but no joy here either. I first tried WE8ISO8859P1, then I tried WE8MSWIN1252, which is specifically for those funky characters from MS Word, and I even tried UTF8. The first two gave the same result as my imp/exp trials, which is corruption of all the 8-bit characters, and the last corrupted the data completely so all I got was a row of question marks and nothing readable at all. And yes, I was creating the database over from scratch in US7ASCII and reloading the data each time (it's been a long night :) I need to read that conversion doc from Oracle in more detail, but what I got from skimming over it was basically that one should use tools to remove problem data before doing the conversion. In this case it would be the same data that's getting corrupted. I'm not getting the impression that this data can be saved One thing just occurred to me. If I set up a second database on the 9i system in US7ASCII and loaded the dump from the 8i system, and connected to it from our application with NLS_LANG set to US7ASCII, I would probably get good data. The problem here is that I have no way to set up a connection to the target database at the same time with a different NLS_LANG value; they will both use the same environment variable and I know of no way to override it.. Drat, I thought I was on to something for a second there! :) If I'm missing, overlooking or otherwise misunderstanding something, please let me know. At this point the alternatives are looking a bit bleak. janine -- 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] charset problem update
On Jul 20, 2005, at 2:48 AM, Carsten Clasohm wrote: and search for A Horror Story About Oracle and Charsets. Wow. Yes, that's the scenario exactly. And I'm actually somewhat proud to say that I followed almost exactly the same path as Branimir - I had a lot of respect for him back in the aD days. In fact, I actually looked at the dump file early on hoping to find a US7ASCII somewhere that I could change, but it wasn't that simple. Of course not, this is Oracle! :) Despite the title, recovering your data is actually pretty easy - I have never had to edit a binary file, but how bad can it be? (note to self - make copy first :) Thanks, Carsten, looks like you may have just saved the rest of my week. I'll be back after I've tried it to report results. janine -- 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.
[AOLSERVER] Charset problem update
Still plugging away at this, without much progress so far. Branimir's directions say to edit four different spots in the dump file. The Metalink note only mentions the first. I did the first two from Branimir's list; the other two were in the middle of user data so that seemed like a bad idea. imp gives the imp-ression (groan :) that it's working: import done in WE8ISO8859P1 character set and AL16UTF16 NCHAR character set export server uses US7ASCII NCHAR character set (possible ncharset conversion) (remember we don't care about NCHAR) but the end result is unchanged - two question marks, sometimes upside down, where the 8-bit characters are. I thought that perhaps WE8ISO8859P1 does not contain the characters in question, so I went back to the 8i system and created a database in UTF-8. Again, the load appears to work: import done in UTF8 character set and US7ASCII NCHAR character set but this time I got a B followed by a little square, wherever there were question marks before. I can think of a few more things to try- try importing into AL32UTF8 under 9i, or importing under US7ASCII under 9i and then seeing if I can convert that up to something useful with ALTER DATABASE. Perhaps 8i has some bugs in this area that are fixed under 9i.Or maybe I can connect to the US7ASCII database from the WE8ISO8859P1 one and pull in data without the clobbering conversion. Stephen's search/replace idea would be my last resort, because it's easy to corrupt dump files that way, but I may yet have to do it. And no matter which one of these works (I sure hope one of them does), I'll still have to merge the clean data into the currently corrupted but live databases. It's going to be a looong week. It's (past) time for lunch, so I thought I'd send out an update for those of you following the saga. ;) janine -- 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] charset problem update
On Jul 20, 2005, at 2:47 PM, Carsten Clasohm wrote: Janine Sisk wrote: I have never had to edit a binary file, but how bad can it be? (note to self - make copy first :) Below is a little C program I wrote the last time I had to fix a dump file. Run it with Thanks, Carsten. I tried it, just in case my editing was bad, but got the same results as before (that is, the evil question marks). Before anyone asks, I have tried loading this dump into an 8i US7ASCII database and the data was good, so the bits are there. I think my next task is going to be to do the same under 9i, just to make sure there's no issue with that. janine -- 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.
[AOLSERVER] Charset success (I think)
Well, after all that, here's what finally seems to have worked: create a database under 9i in US7ASCII, load the data as such, and then use ALTER DATABASE to convert to WE8ISO8859P1. My test page finally does not have question marks where they shouldn't be. Of course, I'm not done yet. I now have a 3 day old copy of the site in one database and a live copy in the other. But they are both in the same charset and that's a start. Now I have to figure out how I'm going to stitch the two together. I also need to decide if I want to tempt fate and go to UTF-8 now, or do that at a later date when there isn't quite so much interest in getting this fixed yesterday. It appears that the problem that Branimir, Carsten and I encountered was an 8i bug, as I did this exact same procedure under 8i last night and it didn't work. Thanks to all for your help and encouragement! If anything else interesting happens with this I will post again. janine -- 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.
[AOLSERVER] Charset problem
Hi all, I've just made a mess for myself and I'm hoping someone will know how to fix it. It's really more of an Oracle problem and the message below is a modified version of one i just sent to an Oracle list, but I thought perhaps someone here would have already struggled with it. I took a site that was running under 8.7.1.4 and moved it to 9.2.0.4 (both on RedHat Linux) using exp/imp. I didn't specify a character set in either case. The data has accented characters and they have been working fine in 8.1..7.4. Now, it seems that the default setting of NLS_CHARACTERSET in 8.1.7.4 was US7ASCII and in 9.2.0.4 it's WE8ISO8859P1. Everything I've read about this conversion says that since it's going from 7 bit to 8 bit there shouldn't be any data problems. Well, hah! :) We didn't spot any at first, but now that the client is looking closely he's finding pages all over the place that have ?? where accented characters should be. The problem was even worse at first; some characters displayed ok until you edited the page via the web browser, and then they turned into ?? as well. I was able to fix that, as far as I can tell, by setting NLS_CHARACTERSET to WE8ISO8859P1 in the environment of the user running the site. It has not, unfortunately, helped us with the rest of the mess. AOLserver is configured to use iso-8859-1 for it's charset and has been all along. The only thing that has changed here is the Oracle version and it's charset. I have this in the ns/parameters section: ns_param HackContentType1 ns_param DefaultCharset iso-8859-1 ns_param HttpOpenCharsetiso-8859-1 ns_param OutputCharset iso-8859-1 ns_param URLCharset iso-8859-1 Going back and reimporting the data is a last resort, as we'd either lose or recreate user data that has been entered since the site was moved on Sunday night. Is there anything else I can do to fix this? In short, heeelp! :) thanks, janine -- 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] Charset problem
On Jul 19, 2005, at 2:42 PM, Dossy Shiobara wrote: If you had accented characters (octets with the 8th bit set to 1) stored in the database under 8.1.7.4, then there is NO way the character set of the database was US7ASCII. If it was, then when the data was stored it would have been transcoded to ?'s. Yes way! :) I've verified it myself. Plus someone sent me this snippet from Metalink, which was posted by Oracle Support in response to someone with a similar problem: It is possible that conversion occured, depending on your data. US7ASCII is a 7-bit character set and it was only supported to use 7-bit characters, however, if 8-bit characters were entered into the database they would be stored (a common example would be the use of accent marks). This would cause conversion as defined by the NLS_LANG parameter. To avoid this, you need to set the NLS_LANG parameter to the target database value of: AMERICAN_AMERICA.WE8ISO8859P1 before starting EXP/IMP. So that's the step I skipped. It makes no sense to me - since imp reports that it is using WE8ISO8859P1 and there will be possible data conversion I would think that it would have worked, but apparently not. You will need to re-exp the data setting NLS_CHARSET to WE8ISO8859P1 before doing the exp. Then, imp it back in. I have now been told every possible variation on what to set NLS_LANG to for each step. :) I haven't figured out which of the variations actually works. janine -- 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] Server not stopping properly
On Jul 18, 2005, at 5:35 PM, Dossy Shiobara wrote: If you look in your server logs from when it was running 4.0.1, at shutdown you probably saw an fatal error being logged. If so, I suspect you were taking advantage of SF Bug #1029918: Nope, actually not: [08/Jul/2005:20:00:57][30673.3073912960][-main-] Notice: nsmain: AOLserver/4.0 stopping [08/Jul/2005:20:00:57][30673.3073912960][-main-] Notice: serv: stopping server: live-gmt [08/Jul/2005:20:00:57][30673.3073912960][-main-] Notice: serv: connection threads stopped [08/Jul/2005:20:00:57][30673.3073912960][-main-] Notice: driver: shutdown complete [08/Jul/2005:20:00:57][30673.3073912960][-main-] Notice: sched: shutdown pending [08/Jul/2005:20:00:57][30673.3063348144][-sched-] Notice: sched: shutdown started [08/Jul/2005:20:00:57][30673.3063348144][-sched-] Notice: sched: waiting for event threads... [08/Jul/2005:20:00:57][30673.3045063600][-sched:idle1-] Notice: exiting [08/Jul/2005:20:00:57][30673.3050306480][-sched:idle2-] Notice: exiting [08/Jul/2005:20:00:57][30673.3048209328][-sched:idle0-] Notice: exiting [08/Jul/2005:20:00:59][30673.3063348144][-sched-] Notice: sched: shutdown complete [08/Jul/2005:20:00:59][30673.3063348144][-shutdown-] Notice: nslog: closing '/export/logs/live/live-gmt.log' [08/Jul/2005:20:00:59][30673.3073912960][-main-] Notice: nsmain: AOLserver/4.0 exiting So, now your server really will wait until the shutdown timeout (default 20 seconds) before giving up and tearing down the server. It's staying in this state for a lot longer than 20 seconds. I can't let it go for a long time since it's a production site but I think it would hang there forever. I've filed RFE #1029889 that will introduce [ns_info shutdownpending] so that Tcl scripts, such as scheduled procs and other background threads can detect that the server is shutting down, and exit/clean up as appropriate. Of course, this means that those background threads will need to be modified to periodically test [ns_info shutdownpending] and if it returns true, to exit gracefully. Wouldn't it make sense for the scheduler to stop starting up new proc runs once it knows the server is shutting down? It's not like these are long running things; they are starting up very frequently because they only run for a few seconds and then finish. So it wouldn't be a big issue if the ones that were running when the server was shut down were allowed to finish; the problem is that the scheduler is keeping on going, running more of them, seemingly forever. thanks, janine -- 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] Problem building 4.0.10 on FC4
Thanks, Jim. Does that include both problems, or just the first one? I'm still stuck on the second problem, so any hints would be greatly appreciated! janine On Jun 27, 2005, at 5:28 AM, Jim Davidson wrote: Odd -- I caught this error just last night and fixed. I'll checkin later today or tomorrow. I think it's a more strict warning for gcc4.0 -- the code has technically worked for years :) -jim On Jun 26, 2005, at 8:46 PM, Janine Sisk wrote: I started out with this error: conn.c: In function ‘NsTclConnObjCmd’: conn.c:843: error: invalid lvalue in assignment Line 843 looks like this: connPtr = (Conn *) conn = itPtr-conn; The gcc version here is # gcc --version gcc (GCC) 4.0.0 20050519 (Red Hat 4.0.0-8) The exact same tarball was compiled a few weeks ago on an RHEL 4 system with no problems. The gcc version there is: # gcc --version gcc (GCC) 3.4.3 20050227 (Red Hat 3.4.3-22.1) As a test, I just went back to the RHEL system and touched conn.c. I got a warning instead of an error. conn.c: In function `NsTclConnObjCmd': conn.c:843: warning: use of cast expressions as lvalues is deprecated I checked the version in CVS and this line has not been changed. My C skills are a tad rusty but I went in and changed it to this, and it compiled under FC4: // connPtr = (Conn *) conn = itPtr-conn; conn = itPtr-conn; connPtr = (Conn *) conn; Is this valid? I thought I had saved the day, but I ended up stuck on this: libnsd.so: undefined reference to `pthread_kill_other_threads_np' That's in nsd/unix.c, in FatalSignalHandler: #ifdef __linux /* * LinuxThreads thread manager needs to kill all child threads * on fatal signals, else they get left behind as dead threads. * As of glibc 2.3 with NPTL, this should be a no-op. */ pthread_kill_other_threads_np(); #endif This system has glibc 2.3.5,, but I don't know if I have NPTL or not. The system on which this builds just fine has glibc 2.3.4. Suggestions? thanks, janine -- 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. -- 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. -- 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] Problem building 4.0.10 on FC4
Thanks, guys - I have a successful build now. If you don't hear from me again on this then it actually works, too. :) janine On Jun 27, 2005, at 10:58 AM, Dossy Shiobara wrote: On 2005.06.27, Jim Davidson [EMAIL PROTECTED] wrote: Ah -- sorry -- didn't read that far. As for the second error, the problem is the _np in pthread_kill_other_threads_np which means non-portable. It's an old API in LinuxThreads to kill all threads in the process-based threads which pre-date modern Linux kernels. The fix is to simply remove the code and expect folks are running a modern Linux where kill/exit/etc. actually work, always. This should be the case today. ... except for the large installed base of Redhat Linux AS 2.1, which is still LinuxThreads. I'd love to push forward and declare those systems unsupported, but, the largest user of AOLserver would be left in the dark. :-) -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.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. -- 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.
[AOLSERVER] Problem building 4.0.10 on FC4
I started out with this error: conn.c: In function ‘NsTclConnObjCmd’: conn.c:843: error: invalid lvalue in assignment Line 843 looks like this: connPtr = (Conn *) conn = itPtr-conn; The gcc version here is # gcc --version gcc (GCC) 4.0.0 20050519 (Red Hat 4.0.0-8) The exact same tarball was compiled a few weeks ago on an RHEL 4 system with no problems. The gcc version there is: # gcc --version gcc (GCC) 3.4.3 20050227 (Red Hat 3.4.3-22.1) As a test, I just went back to the RHEL system and touched conn.c. I got a warning instead of an error. conn.c: In function `NsTclConnObjCmd': conn.c:843: warning: use of cast expressions as lvalues is deprecated I checked the version in CVS and this line has not been changed. My C skills are a tad rusty but I went in and changed it to this, and it compiled under FC4: // connPtr = (Conn *) conn = itPtr-conn; conn = itPtr-conn; connPtr = (Conn *) conn; Is this valid? I thought I had saved the day, but I ended up stuck on this: libnsd.so: undefined reference to `pthread_kill_other_threads_np' That's in nsd/unix.c, in FatalSignalHandler: #ifdef __linux /* * LinuxThreads thread manager needs to kill all child threads * on fatal signals, else they get left behind as dead threads. * As of glibc 2.3 with NPTL, this should be a no-op. */ pthread_kill_other_threads_np(); #endif This system has glibc 2.3.5,, but I don't know if I have NPTL or not. The system on which this builds just fine has glibc 2.3.4. Suggestions? thanks, janine -- 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] proc getting scheduled more than once
On Jun 14, 2005, at 4:22 PM, Dossy Shiobara wrote:
Janine said that she is not using virtual servers. However, the
behavior she's describing *only* makes sense if she were.
I'm not. Certainly not intentionally, anyway.
Janine, could you do a quick test:
snip
Do you get one log entry, or more than one?
I did this, and got only one entry. So then I took a config file from
one of the sites that did this, hacked it up slightly to get it to use
the same locations for logs, etc as the sample, and tried that. This
time I got two entries. That's a surprising number since it's not
equal to maxthreads like it was before, but it's still more than
one
Ok, this is really weird. I took my config file and started removing
things from it until it worked. The line that causes the second load
of test.tcl is:
ns_param dbname(test) test
This has been in my config files forever; once upon a time it was used
by a backup script, but that script isn't even installed on this
system. It's in the ns/servers section. What makes no sense, of
course, is why this would affect anything. there doesn't seem to be
any code referencing anything called dbname:
[EMAIL PROTECTED] aolserver]# cd /usr/local/src/aol*
[EMAIL PROTECTED] aolserver-4.0.10]# find . -type f -exec fgrep -l dbname {}
\;
[EMAIL PROTECTED] aolserver-4.0.10]# cd /usr/local/aolserver
[EMAIL PROTECTED] aolserver]# find . -type f -exec fgrep -l dbname {} \;
./test.tcl
(test.tcl is my config file, so that's ok)
It's late and I'm tired, so I'm not going to do any more with this
tonight. Tomorrow I will try this with a real site and verify that
it's still that line that causes the problem.
janine
--
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] proc getting scheduled more than once
On Jun 15, 2005, at 7:50 AM, Dossy Shiobara wrote: Any ns_param in the ns/servers section defines a new virtual server. In this case, you defined a virtual server whose name is dbname(test) and its description is test. Whoa. that's slightly unexpected. :) I haven't used virtual servers in eons, so had no idea how they are even set up anymore. Of course, I don't know why you only saw a change in startup behavior moving from 4.0.8 to 4.0.10 ... but perhaps there was a bug that was fixed somewhere between the two versions. Must have been, because this sure isn't new. In fact, many of my config files have two ns_params at the start of ns/servers, like this: ns_paramstaging-foo staging-site ns_paramlive-foolive site And then everything else in that section has a someparam(staging-foo) version and a someparam(live-foo) version. The server value would be set on the nsd command line with -s and would choose which of these sets of values was actually used. It was just a shortcut way of having only one config file per client. That stopped working a long time ago; there was a patch for it in the 3.x days, but when we moved to 4.x we had to split the config files into two. A lot of them still have the extra stuff in them for the other server, though, which up to now was just ignored by nsd (as far as we could tell, anyway). I was planning on doing some config file cleanup anyway... looks like I had better move that closer to the top of the todo list! janine -- 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] proc getting scheduled more than once
On Jun 15, 2005, at 7:39 AM, Tom Jackson wrote: I'm just wondering if the above param line used to be something like: set dbname(test) test ?? There is actually a set and an ns_param for dbname. As I recall, you had to use ns_param if you wanted to access the value from outside of the config file. In this case it was for a Tcl script that did database backups, and there were times when the database name didn't match the server name so this was how we made the database name available to that script. The set value was available internally and the ns_param value was available externally. At least that is how I remember it - this was all written years ago now. janine -- 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] proc getting scheduled more than once
On Jun 14, 2005, at 1:12 AM, Tom Jackson wrote: The question is what in Janine's code is calling the same thing N times. This is the bug. I don't think it's in my code. To make sure it's clear, here's the scenario: On 4.0.8 (and many versions previous) I put the script roll-logs.tcl, which was reproduced in it's entirety in my first post, in /usr/local/aolserver/modules/tcl. It was sourced only once. My evidence is that my ns_log was run only once despite the ns_share thing clearly not working. In 4.0.10, when I put it in /usr/local/aolserver/modules/tcl it gets sourced N times, where N is the number of threads. This is evident in both the ns_log notices in the error log and the actual rolling of the logs happening multiple times. When I moved it to the site's private Tcl library, it went back to being sourced only once. I did not modify the script at all. As far as I know, the only code that sources files in either location is within AOLserver. I'm not doing anything with them explicitly. janine -- 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.
[AOLSERVER] proc getting scheduled more than once
I just upgraded several sites from AOLserver 4.0.8 to 4.0.10. I added
the following script to /usr/local/aolserver/modules/tcl/roll-logs.tcl,
as I always do:
# from Michael Cleverly:
#
http://www.opennsd.org/bboard/q-and-a-fetch-msg.tcl?
msg_id=5ntopic_id=1t
opic=OpenNSD
proc roll_logs {} {
set server_name [ns_info server]
set yesterday [ns_fmttime [expr [ns_time] - 86400] %Y-%m-%d]
set access_file_name [ns_config ns/server/${server_name}/module/nslog
File]
# access log
ns_accesslog roll $access_file_name.$yesterday
# server log
ns_logroll
}
ns_share -init {set schedule_roll 0} schedule_roll
if {!$schedule_roll} {
ns_schedule_daily 0 0 roll_logs
ns_log Notice roll_logs for [ns_info server] has been scheduled at
12:00 am.
}
Up to now, the ns_share has kept the proc from being scheduled more
than once. Now, however, with 4.0.10 it seems to be happening in each
thread. So with maxthreads set to 5, the script gets scheduled five
times.
I know that this is old code and that ns_share was deprecated a long
time ago. Can someone clue me in on what the modern way to schedule
this only once would be?
thanks,
janine
--
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] proc getting scheduled more than once
On Jun 13, 2005, at 5:14 PM, Tom Jackson wrote: I don't see how any of this works the way you described it, and even if it did, you shouldn't need a shared var to run a proc once daily, otherwise we need to change the proc name to ns_schedule_run_once_per_thread_daily. Maybe so, but it was SOP (standard operating procedure) way back in the ancient ACS days. There are many examples of it in the older code - try tcl/notification-defs.tcl from OpenACS 3.2.5, as the first example I came up with. The idea, as I understood it, was that your script was going to be loaded by each thread, so the way to make sure that something got executed only once was to set a flag that it had already happened. It used to work fine, but something seems to have changed recently so that the ns_share'd variable isn't visible from the other threads. I'm not calling it a bug, since no-one cares about ns_share anymore, just something I need to work around. The way to replace ns_share is to use nsv: Thanks! janine -- 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] proc getting scheduled more than once
Sorry Dossy, forgot to hit reply all so you get three copies. On Jun 13, 2005, at 5:35 PM, Dossy Shiobara wrote: Strangely, this smells like a config issue -- either an error in your config, or a change to AOLserver that could be breaking backward compatibility. I'm hoping it's the former and not the latter ... :-) Could be, but the config files were copied across and changed as little as possible. We did revamp our directory structure while we were at it, though, so I could have messed something up. What is your private and shared Tcl libraries configured to? Do you have virtual servers configured, or is it a single server? The private Tcl library is /export/sites/sitename/staging/tcl Which is where the bootstrapping code for OpenACS lives. I don't seem to have anything set for shared Tcl library, and I can't remember ever having it set. SIngle server - we gave up on virtual servers many moons ago. janine -- 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] proc getting scheduled more than once
On Jun 13, 2005, at 5:59 PM, Dossy Shiobara wrote: On 2005.06.13, Janine Sisk [EMAIL PROTECTED] wrote: Could be, but the config files were copied across and changed as little as possible. We did revamp our directory structure while we were at it, though, so I could have messed something up. It's the first thing I'd check. I don't see anything amiss, unfortunately. When you say it's scheduled N times where N == maxthreads, are you saying this because you see it listed that many times in [ns_info scheduled] output? The proc has an ns_log statement when it gets scheduled and I'm going by how many times I see it in the log. Once for a 4.0.8 installation, N times for 4.0.10 (per restart). Are you using Zoran's ttrace extension? Nope. janine -- 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] proc getting scheduled more than once
On Jun 13, 2005, at 7:45 PM, Dossy Shiobara wrote: Am I missing something, or where do you ever set schedule_roll to something other than 0? Good point. It worked, so I never noticed that (I didn't write this, I borrowed it). Still, this Tcl shouldn't get sourced in more than once at server start-up anyway. It shouldn't be getting executed once per thread and/or interp init. Unless, in some other .tcl file, you have something that goes and iterates over all the files in your Tcl libraries and does some [source]'ing of files on interp init or somesuch. I don't. no. In case this detail has gotten lost, this was being placed in /usr/local/aolserver/modules/tcl. I have been doing this for years, and it has always worked before (where worked is defined as being sourced only once). I subsequently moved it into my private Tcl library and it's only being sourced once there, so I have a workaround but as far as I can tell this is new behavior in 4.0.10. janine -- 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] Help in upgrading to 3.5
On May 24, 2005, at 6:41 PM, Dossy Shiobara wrote: Perhaps someone could coax Zoran into providing a patch for the Tcl Bug #1178445 which fixed the memory leak in question: Zoran, pretty please? :) This would really help me, as I'm setting up new production servers this week and I really don't want to use almost 8.4.10, but I don't want a memory leak either. thanks, janine -- 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] Leaky AS/Tcl memory allocator -- Tcl 8.4.7 the culprit
The system I'm having the most leak problems on is already using 8.4.6,
unfortunately. But I'd like to try your test code anyway and see what
happens. Where do I get this Threads extension?
janine
On Apr 6, 2005, at 6:20 PM, Dossy Shiobara wrote:
On 2005.04.06, Dossy Shiobara [EMAIL PROTECTED] wrote:
OK, time to binary search to figure out what Tcl version introduced
this
leak. :-)
OK, looks like Tcl 8.4.7 introduced the leak. Here's my test run
against Tcl 8.4.6:
$ LD_LIBRARY_PATH=`pwd` ./tclsh
% info patchlevel
8.4.6
% lappend auto_path /usr/lib/tcl8.4; package require Thread
2.6.1
% exec ps -p [pid] -o pid,vsz,rss,args
PID VSZ RSS COMMAND
8317 12704 1996 ./tclsh
% for {set i 0} {$i 1000} {incr i} {
thread::join [thread::create -joinable {}]
}
% exec ps -p [pid] -o pid,vsz,rss,args
PID VSZ RSS COMMAND
8317 21192 2272 ./tclsh
Same test against Tcl 8.4.7:
$ LD_LIBRARY_PATH=`pwd` ./tclsh
% info patchlevel
8.4.7
% lappend auto_path /usr/lib/tcl8.4; package require Thread
2.6.1
% exec ps -p [pid] -o pid,vsz,rss,args
PID VSZ RSS COMMAND
9358 12692 2000 ./tclsh
% for {set i 0} {$i 1000} {incr i} {
thread::join [thread::create -joinable {}]
}
% exec ps -p [pid] -o pid,vsz,rss,args
PID VSZ RSS COMMAND
9358 48272 29432 ./tclsh
If anyone wants to review the changes to Tcl between 8.4.6 and 8.4.7,
you can produce the diff like this:
$ cvs -z6 -d :pserver:[EMAIL PROTECTED]:/cvsroot/tcl rdiff
-rcore-8-4-6 -rcore-8-4-7 tcl tcl-846-847.diff
In the meantime, everyone who is seeing unexplained nsd memory growth
if
you're running Tcl = 8.4.7, please roll back to Tcl 8.4.6 and see if
that makes the problem go away. (Andrew? Janine? etc.)
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.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.
--
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] More on memory leak
Dossy, I just wanted to let you (and everyone else) know that I haven't given up on this, I've just been very busy moving and am just now getting back into getting some work done. I'll be back as soon as I have some more useful info. janine On Jan 31, 2005, at 3:46 PM, Dossy Shiobara wrote: On 2005.01.31, Janine Sisk [EMAIL PROTECTED] wrote: Well, here's what I tried, using version 2.2 of valgrind: valgrind --tool=memcheck --leak-check=yes --show-reachable=yes --num-callers=8 --log-file=/tmp/staging -v /export/aolserver4/bin/nsd-oracle -ft /export/aolserver4/staging.tcl -b 209.202.133.58:80,209.202.133.58:443 -u nsadmin -d --trace-children=no|yes Valgrind-ise child processes? [no] Try adding --trace-children=yes. All I get is the messages from a few exiting threads, which say that there were no malloc'd blocks, and then nothing. I've tried requesting pages but nothing more happens. It's like it's not following along to the child processes that are actually running. What OS and libc are you using? If it's Linux, is it NPTL or LinuxThreads? $ getconf GNU_LIBPTHREAD_VERSION NPTL 0.60 -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.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. -- 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] nsopenssl howto
On Feb 22, 2005, at 8:31 AM, Trenton Cameron wrote: http://openacs.org/doc/openacs-5-1/install-nsopenssl.html is a pretty good tutorial on howto install nsopenssl on aolserver That's good for installation, but not so much for configuration. However, if you download the OpenACS tarball and grab the config file (etc/config.tcl, IIRC) it has a section in it for nsopenssl that will show you one way it can be done (I'm sure there are others). janine -- 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] More on memory leak
On Jan 28, 2005, at 3:52 PM, Nathan Folkman wrote: As promised, below is slightly cleaner version (still needs more work) that ties in some of the information from ns_info threads. Hopefully this will help a little. Ok, I've posted this at http://www.furfly.net/janine/memory-pools.html (replaces the old one). I can see what you did (split up the data by thread) and it makes sense, but I still don't really know what to make of these numbers, or how I can get from here to figuring out what's consuming all the memory. A couple of days ago I tried to run nsd with valgrind, but it didn't seem to work. The only output I got was from a few threads that had exited during startup; it seemed like valgrind wasn't able to handle the child processes spawned by the initial thread. I think they must have changed valgrind recently, because the version I have (freshly downloaded) requires the --tool parameter, which Dossy didn't use when he posted his valgrind runs a week or so ago. Thanks for your help, Nathan! janine -- 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] More on memory leak
On Jan 31, 2005, at 2:13 PM, Nathan Folkman wrote: At this point it seems like your efforts might be better spent working with Dossy to get one of the profiling tools to work correctly with AOLserver. Well, here's what I tried, using version 2.2 of valgrind: valgrind --tool=memcheck --leak-check=yes --show-reachable=yes --num-callers=8 --log-file=/tmp/staging -v /export/aolserver4/bin/nsd-oracle -ft /export/aolserver4/staging.tcl -b 209.202.133.58:80,209.202.133.58:443 -u nsadmin -d All I get is the messages from a few exiting threads, which say that there were no malloc'd blocks, and then nothing. I've tried requesting pages but nothing more happens. It's like it's not following along to the child processes that are actually running. Suggestions? janine -- 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] More on memory leak
On Jan 24, 2005, at 8:55 PM, Nathan Folkman wrote: Below is a quick and dirty page you can use to print out some info from the Zippy memory allocator. Not pretty, but might help you gain some insight into what is going on. Pay close attention to the total stats at the end of the page. By design the memory allocator is somewhat of a memory hog (note the high overhead), however, you'll notice the lock contention is nearly non-existent. In practice memory is cheap and lock contention is to be avoided at all costs! Hope this helps! Thanks, Nathan! I've run this, but I'm not sure how to interpret the output. The full page is at http://www.furfly.net/janine/memory-pools.html The total stats you mentioned are: Bytes Requested:17754181 Bytes Free: 1980544 Bytes Allocated:28301396 Bytes Wasted: 10547215 Byte Overhead: 59.41% Mutex Locks:10660 Mutex Lock Waits: 0 Lock Wait Ratio:0.00% Gets/Puts: 1722429 Lock Avoidance: 99.38% The Bytes Wasted seems pretty high, but without knowing why or how they are considered wasted it's hard to know what to think about that. Does this suggest anything to you? It seems like it would be useful to be able to look at Tcl's data structures and see how much memory is allocated to NSVs, etc, but I don't know how to do that, if it's even possible. thanks, janine -- 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] Grr! Stupid mistake when doing previous mem. leak tests.
On Jan 16, 2005, at 1:31 PM, Andrew Piskorski wrote: Since Janine is running AOLserver 3.3 (presumably 3.3+ad13 or the like), it is about 99.9% certain that she is running Tcl 8.3.2 with Right. Janine, one obvious thing to try is, for your AOLserver 4.x, upgrade from Tcl 8.4.6 to the latest stable version, which I think is currently 8.4.9. I doubt that will make any difference to the problem, but you never know; also it's at least unlikely to hurt, and is probably worth doing anyway. Ok, I can try that. I need to relink AOLserver also when I do that, right? janine -- 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] Grr! Stupid mistake when doing previous mem. leak tests.
On Jan 16, 2005, at 10:01 AM, Dossy Shiobara wrote:
Yow! That's frightening. In the code you're running, does it test
anywhere for if {[ns_info version] = 4.0} { ... } or something and
behave differently on 4.0.x than it did on 3.x?
Nope. I know it doesn't; I'm the only programmer and when we upgraded
to 4.x I didn't change anything special like that.
You're running the same code on the same machine with the same config
and the only variable you changed is the AOLserver version? Same
version of Tcl?
The config files are different because I switched to the OpenACS config
format. I will try using the exact same file when I can get back to
experimenting, but I don't expect it to make a difference. In the
important respects they are pretty much the same as far as I know.
OK, I'd like to know if running your htdig over and over for, say, an
hour straight, if the nsd ever reaches a stable memory size for
either AOLserver version.
Ok.
janine
--
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] Grr! Stupid mistake when doing previous mem. leak tests.
On Jan 15, 2005, at 11:22 AM, Dossy Shiobara wrote: If there's zero memory growth after reaching a stable size in 3.x, but no such stable size is ever reached in 4.0.x, that might be helpful. That'd likely indicate a leak in AOLserver itself that was introduced in 4.0.x. I can't answer that yet, but I did run some tests. I restarted the site, checked the size, then ran htdig three times in quick succession and checked again. In 3.3 we gained 8.8 MB, which was 24% of the original size. In 4.0.8 we gained 301.8 MB, 110% of the original size. However, much of the gain was in the first run, and subsequent runs only added about 500 KB each. That's not enough to explain the growth I've been seeing; running once per hour over a week, it would have to add about 10 MB each run. I will try to rig up some multi-day tests, but I can't do it immediately; I have other work I need to do for this client that requires the staging site. Once that's done, then I can experiment a bit. If you can identify what URL or URLs, when requested, cause the growth in 4.0.x, that would be extremely helpful. Well, I certainly know that requesting an article does it; I haven't branched out to try others yet. Also, what version of Tcl are you running? 8.4.6. janine -- 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] Grr! Stupid mistake when doing previous mem. leak tests.
On Jan 14, 2005, at 10:16 PM, Dossy Shiobara wrote: SO, this begs the question: The people who are reporting memory leaks, do you have connsperthread set to anything in your config files? Nope, not me. I will do some comparison testing between 3.3 and 4.0.8, if that will be useful information. Other than that, I've never tried to debug a memory leak like this so any info on how to do so will be helpful. I don't have access to Purify. The site is running on RHES 3, if that makes a difference. thanks, janine -- 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] memory leak in 4.0.9?
On Jan 14, 2005, at 3:04 AM, Dan Chak wrote: So, are there any known leaks in 4.0.x? I've been wondering this myself. I've been experimenting with using htdig to search a client site, and I have it digging the staging site once an hour. It only grabs 500 articles, and it's the same ones each time. There's very little other traffic on the staging site. Each time the dig runs, the size of the nsd process grows a bit; when it was last started up a week ago it was using 53 MB and now it's using 1.77 GB (that's assuming that the numbers ps gives me are in KB, which I've been told they are). This doesn't seem right to me, but I don't have any tools to diagnose it further. The site is running AOLserver 4.0.8. janine -- 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] memory leak in 4.0.9?
On Jan 14, 2005, at 10:38 AM, Dossy Shiobara wrote: Using PostgreSQL? Could there be a memory leak in the nspostgres driver? I'd defer to the OpenACS folks to say whether there are any known memory leaks in any of the OpenACS Tcl code. Nope, using Oracle. I'm not aware of any leaks, and I never noticed this when I was using nsd 3.3 and the same version of the Oracle driver. These other sites run in separate nsd's though, right? Right. janine -- 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] nsopenssl errors
FWIW, I saw those messages too, when I was using nsopenssl2.1, and I see similar ones using AOLserver 4 and the latest nsopenssl. The only difference is that I've never had a user complaint related to them, so I was assuming that they were victimless crimes. Perhaps that is not the case, though we usually do hear pretty quickly if something's not working right from the user's perspective. janine On Oct 25, 2004, at 5:05 PM, Dossy Shiobara wrote: On 2004.10.25, Steve [EMAIL PROTECTED] wrote: They seem to cause a variety of errors in different browsers. I've been on the receiving end of one of these and in Mozilla it gave a popup message: Are you able to reproduce this error on demand? Or is it completely random? Unfortunately the logs are going to quickly for me to determine which error gave the message. The site is getting to be very busy in the run up to halloween so I wondered if it was related to the load apart from these errors the system doesn't seem to have any problems and the response is good. What do you mean by going too quickly? Aren't you logging to disk? Can't you just roll the log and then inspect it at your leisure? I'd be grateful is someone could shed some light on these errors or point me at a way to diagnose the problem without adversely effecting the site. How large is the nsd process memory footprint? What modules are you loading? Did you upgrade anything at ALL lately? What OS is this on? Is it a single front-end host or a farm of them? If it's a farm, is it behind a load balancer, if so what make/model? Is your upstream bandwidth provider having routing issues? What kind of uplink exists on the host (10mbit, 100mbit, half or full duplex, configured or auto-negotiate)? What make/model switch is/are the hosts connected to? Are the switches configured or auto-negotiate? Is there any other traffic on your network segment or is it just these front-end webservers? Is there a RDBMS involved, and is it running on its own dedicated host? On the same network segment? Do you serve static assets from these front-end hosts, or are you using a dedicated server for them and/or a CDN? This is just a short list of questions to get a better picture of what you're running, what your network architecture looks like and some things I've personally seen before that could possibly be responsible for the badness you're seeing. Lets eliminate the low-hanging fruit first ... -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.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. -- 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] 4.0.8
Sorry about the late response... On Oct 13, 2004, at 9:27 AM, Andrew Grumet wrote: Janine and Bruno, are you guys running nsopenssl? Yes, I am. As far as I know it's the latest. I think the trick here is trying to figure out where the memory is going. Jeff D. threw me some introspection code that reports nsv usage and other stuff, but I didn't see any smoking guns. Andy P. suggested purify. Maybe I'll take a look at that. Any luck? janine -- 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] Progress report
On Aug 18, 2004, at 9:47 AM, Dossy Shiobara wrote: What class of hardware are these sites running on? maxthreads=10 is pretty low, IMHO. Running one site on a 1.2 GHz P3 running Linux, I'd comfortably set minthreads=maxthreads=30. BTW, what's the guidelines on setting maxconnections? Should it be the same as max and min threads? thanks, janine -- 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] Support for non-HTTP protocols
On Tuesday 17 August 2004 11:51 am, Dossy Shiobara wrote: Janine has offered to help, but cannot provide access to her production environments where the problem is occurring. Actually I can, but what I can't do is put AOLserver 4 + nsopenssl beta 21 back into production. Right now I am running 3.3+ad13 all around, with one of the staging sites on 3.5.11 to see if it will work ok. I don't think being able to log into this box now is going to help you much with the nsopenssl problem. I'll post an update later on the random hang problem I've been having with my current setup, the one that prompted my attempt to upgrade in the first place. janine -- 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] Problems with older nsd3.3 site
On Aug 12, 2004, at 11:11 AM, Andrew Piskorski wrote: Hm, I dunno. Are the AOLserver thread settings ok? I had maxthreads set to 10, but wasn't setting minthreads or threadtimeout so I set those to 10 and 3500, respectively. We'll see what happens. What do you use for maxconnections? I have it specified in both config files as maxconnection (singular) so that's probably being ignored and using the default, which I think is 100. That seems reasonable but I've never really known how to set these things, plus this is based on a very old config file and the recommendations have probably changed. But maybe you can figure out what's happening on the Tcl level without ever using gdb. E.g., take a look at the nstelemetry ADP nstelemetry.adp (on SourceForge), it is pretty simple. You could run those Tcl commands periodically and ns_log the results. If you could log that stuff during a pause it might tell you something useful. Hmm, not a bad idea. I've sort of ignored that script because I can't run it once the server is wedged, but you're right that I could have the server run them. There's nothing obvious in the logs; no error messages and it seems to stop in random places, not like it's at the same query every time or anything. Besides which there isn't any unusual load on the system, which I would expect to see if a monster query was tying up Oracle. janine -- 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.
