[AOLSERVER] nsopenssl 3.0 beta 10
nsopenssl 3.0 beta 10 is available on http://scottg.net. Kick the tires. /s. -- 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] UTF8 filenames in AOLserver 4
I found out that the problem is not in the saving of the file, but in the return of the utf-8 file from the filesystem. I found out that using ns_returnfile [encoding convertto [encoding system] $filename] would allow aolserver to find the utf-8 filename from the filesystem and return the correct file. I discovered this by accident when I learned that aolserver by itself and OpenACS behaved differently. The filter on the GET method in OpenACS calls ns_returnfile. If it is called without the encoding command it fails in the same way as the standard AOLserver only GET behavior. I looked in fastpath.c, but I couldn't find out where i might need to look to see how it is working. Using Dossy's suggestion worked partially, but it actually stored incorrect bytes in the filename as far as I could tell. So I am trying to get consistent behavior from ns_returnfile and whatever the standard GET response is from AOLserver. Dave On Thu, Jan 01, 2004 at 08:46:25PM -0500, Dossy wrote: > On 2004.01.01, Dave Bauer <[EMAIL PROTECTED]> wrote: > > The code that creates the file looks like this: > > > > set fd [open $filename w+] > > ns_writecontent $fd > > > > The file in my filesystem ends up as "res-?" > > Try: > > set fd [open [encoding convertto utf-8 $filename] w+] > > -- 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. > -- Dave Bauer [EMAIL PROTECTED] http://www.thedesignexperience.org -- 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] UTF8 filenames in AOLserver 4
This is only a problem on AOLserver 4.0 (at least). It works on AOLserver3.3+ad13. This leads me to suspect that there might be a charset issue that is in 3.3+ad13 that isn't in 4.0. Dave On Thu, Jan 08, 2004 at 03:20:09PM -0500, Dave Bauer wrote: > I found out that the problem is not in the saving of the file, but in > the return of the utf-8 file from the filesystem. > > > I found out that using > > ns_returnfile [encoding convertto [encoding system] $filename] > > would allow aolserver to find the utf-8 filename from the filesystem and > return the correct file. > > I discovered this by accident when I learned that aolserver by itself > and OpenACS behaved differently. The filter on the GET method in OpenACS > calls ns_returnfile. If it is called without the encoding command it > fails in the same way as the standard AOLserver only GET behavior. > > I looked in fastpath.c, but I couldn't find out where i might need to > look to see how it is working. > > Using Dossy's suggestion worked partially, but it actually stored > incorrect bytes in the filename as far as I could tell. > > So I am trying to get consistent behavior from ns_returnfile and > whatever the standard GET response is from AOLserver. > > Dave > > On Thu, Jan 01, 2004 at 08:46:25PM -0500, Dossy wrote: > > On 2004.01.01, Dave Bauer <[EMAIL PROTECTED]> wrote: > > > The code that creates the file looks like this: > > > > > > set fd [open $filename w+] > > > ns_writecontent $fd > > > > > > The file in my filesystem ends up as "res-?" > > > > Try: > > > > set fd [open [encoding convertto utf-8 $filename] w+] > > > > -- 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. > > > > -- > Dave Bauer > [EMAIL PROTECTED] > http://www.thedesignexperience.org > > > -- > 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. > -- Dave Bauer [EMAIL PROTECTED] http://www.thedesignexperience.org -- 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] nsd and memory leaks
I was running nsd v.3.4.2 on a fairly active website (FreeBSD 4.x os) for a few weeks and had some trouble with the nsd process growing. I was restarting the process every few days as it grew to 40-60Mb. I posted a couple messages on this list about v4.0 and using port 80 as I was trying to run it, but decided it's probably not stable enough for a production server. I built v3.5.6 for the site with the latest tcl (8.4.5) and the PHP4.3.4 sapi module (but not running any php actively on the site). I'm running zero dynamic/database stuff at this point, but am running a couple small perl/C cgi things (form mailer and counter). Now, it appears that the 3.5.6 process still has a memory leak, as it has been steadily growing for about the last 24 hours. It's up to 21mb, which would be okay if it stops growing pretty soon. Anyone have any ideas on what causes or how to stop memory leaks in version 3.x? What size do your nsd processes typically run at after a few days? Maybe I'm just being paranoid and not letting it grow to where it needs to be (if it caches). I'm used to apache processes running at <20Mb. Thanks, -- Untied we stand, fettered we fall. -- 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] nsopenssl 3.0 beta 10 and OpenACS
Forgot to mention that you'll have to get around the fact that ServerPort is no longer a valid name in the config -- OpenACS will have an issue with that. Since you can now have multiple drivers per virtual server, and drivers for each virtual server, you'll have to figure out a way for OpenACS to determine which driver port number it really wants from the config file. Sorry... /s. -- 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] nsd and memory leaks
No, you're not being paranoid. Are you using nscgi and running CGI scripts? If so, then you're running into this problem (from the ChangeLog): 2003-04-04 Scott S. Goodwin <[EMAIL PROTECTED]> * nscgi/nscgi.c: (bug) Ns_DStringInit called in CgiExec was destroying the linked list used to maintain the list of dstrings in use by the module, resulting in a memory leak for every cgi script run. You can get AOLserver 3.5.9 or later (better yet, go grab the latest CVS copy on the v35bp branch), or go into nscgi.c and remove the line that reads: Ns_DStringInit(&dsPtr); from the CgiExec function, and recompile. /s. On Jan 8, 2004, at 4:57 PM, John Shafto wrote: I was running nsd v.3.4.2 on a fairly active website (FreeBSD 4.x os) for a few weeks and had some trouble with the nsd process growing. I was restarting the process every few days as it grew to 40-60Mb. I posted a couple messages on this list about v4.0 and using port 80 as I was trying to run it, but decided it's probably not stable enough for a production server. I built v3.5.6 for the site with the latest tcl (8.4.5) and the PHP4.3.4 sapi module (but not running any php actively on the site). I'm running zero dynamic/database stuff at this point, but am running a couple small perl/C cgi things (form mailer and counter). Now, it appears that the 3.5.6 process still has a memory leak, as it has been steadily growing for about the last 24 hours. It's up to 21mb, which would be okay if it stops growing pretty soon. Anyone have any ideas on what causes or how to stop memory leaks in version 3.x? What size do your nsd processes typically run at after a few days? Maybe I'm just being paranoid and not letting it grow to where it needs to be (if it caches). I'm used to apache processes running at <20Mb. Thanks, -- Untied we stand, fettered we fall. -- 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] nsd and memory leaks
Thanks Scott, Yes, I am running some small cgi stuff, so that is likely it. I didn't see a tarball for v3.5.9 on the sourceforge site, and not being much of a manual CVSer, not sure how I would checkout v35bp. Would it be: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/aolserver co aolserver_v35_bp ? -- Untied we stand, fettered we fall. - Original Message - From: "Scott Goodwin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 08, 2004 15:37 Subject: Re: [AOLSERVER] nsd and memory leaks No, you're not being paranoid. Are you using nscgi and running CGI scripts? If so, then you're running into this problem (from the ChangeLog): 2003-04-04 Scott S. Goodwin <[EMAIL PROTECTED]> * nscgi/nscgi.c: (bug) Ns_DStringInit called in CgiExec was destroying the linked list used to maintain the list of dstrings in use by the module, resulting in a memory leak for every cgi script run. You can get AOLserver 3.5.9 or later (better yet, go grab the latest CVS copy on the v35bp branch), or go into nscgi.c and remove the line that reads: Ns_DStringInit(&dsPtr); from the CgiExec function, and recompile. /s. -- 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] nsd and memory leaks
On 09/01/2004, at 10:16 AM, John Shafto wrote: I didn't see a tarball for v3.5.9 on the sourceforge site, and not being much of a manual CVSer, not sure how I would checkout v35bp. Would it be: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/aolserver co aolserver_v35_bp John, I think it's: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/aolserver co -r aolserver_v35_bp aolserver Matthew -- 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] nsd and memory leaks
Almost -- you need the -r flag to identify the branch: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/aolserver login cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/aolserver \ co -r aolserver_v35_bp aolserver /s. On Jan 8, 2004, at 6:16 PM, John Shafto wrote: Thanks Scott, Yes, I am running some small cgi stuff, so that is likely it. I didn't see a tarball for v3.5.9 on the sourceforge site, and not being much of a manual CVSer, not sure how I would checkout v35bp. Would it be: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/aolserver co aolserver_v35_bp ? -- Untied we stand, fettered we fall. - Original Message - From: "Scott Goodwin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 08, 2004 15:37 Subject: Re: [AOLSERVER] nsd and memory leaks No, you're not being paranoid. Are you using nscgi and running CGI scripts? If so, then you're running into this problem (from the ChangeLog): 2003-04-04 Scott S. Goodwin <[EMAIL PROTECTED]> * nscgi/nscgi.c: (bug) Ns_DStringInit called in CgiExec was destroying the linked list used to maintain the list of dstrings in use by the module, resulting in a memory leak for every cgi script run. You can get AOLserver 3.5.9 or later (better yet, go grab the latest CVS copy on the v35bp branch), or go into nscgi.c and remove the line that reads: Ns_DStringInit(&dsPtr); from the CgiExec function, and recompile. /s. -- 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] nsd and memory leaks
On 2004.01.08, John Shafto <[EMAIL PROTECTED]> wrote: > I was running nsd v.3.4.2 on a fairly active website > (FreeBSD 4.x os) for a few weeks and had some > trouble with the nsd process growing. I was restarting > the process every few days as it grew to 40-60Mb. 40-60MB is nothing. I'd worry if your nsd grows beyond 2GB. > Maybe I'm just being paranoid and not letting it grow > to where it needs to be (if it caches). I'm used to > apache processes running at <20Mb. AOLserver is NOT Apache. Get used to that. -- 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] Mention of AOLserver in Feb 2004 Linux Journal.
There is a good, if inconspicuous, mention of AOLserver in the Feb LJ. On page 46, in the feature on the Magnatune record label, the statement is made: "Apache 2 running PHP and OpenSSL serves all the HTML pages. When Magnatune was Slashdotted, I found that Apache could not keep up with the load for images. All HTTP image requests now are off-loaded to AOLserver, which had the lowest latency to serve images at high speeds." Later: "Mathopd [which they use to serve the very large streaming audio files] has more latency than AOLserver, which is why we don't use it to serve small images." Wow, somebody who really uses the right tool for each job. Apache for the HTML and PHP stuff, AOLserver for machine-gunning images out, and Mathopd for serving very large files at high speeds. But it is a NICE mention of AOLserver. -- Lamar Owen Director of Information Technology Pisgah Astronomical Research Institute 1 PARI Drive Rosman, NC 28772 (828)862-5554 www.pari.edu -- 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] Mention of AOLserver in Feb 2004 Linux Journal.
On 2004.01.08, Lamar Owen <[EMAIL PROTECTED]> wrote: > Wow, somebody who really uses the right tool for each job. Apache for the > HTML and PHP stuff, AOLserver for machine-gunning images out, and Mathopd for > serving very large files at high speeds. I assume that first sentence was dripping with sarcasm ... because the irony is that AOL itself doesn't use AOLserver for serving images. *snicker* But yeah, it *is* nice to see AOLserver get positive press. Yay. -- 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.
Re: [AOLSERVER] nsd and memory leaks
> > I was running nsd v.3.4.2 on a fairly active website > > (FreeBSD 4.x os) for a few weeks and had some > > trouble with the nsd process growing. I was restarting > > the process every few days as it grew to 40-60Mb. > > 40-60MB is nothing. I'd worry if your nsd grows beyond 2GB. Doing what? This particular machine only has a 512mb of ram, and serves mostly static content. I have bigger plans for it though. > > Maybe I'm just being paranoid and not letting it grow > > to where it needs to be (if it caches). I'm used to > > apache processes running at <20Mb. > > AOLserver is NOT Apache. Get used to that. I'll try to keep them straight. Thanks for the tip. -- Dulcius Ex Asperis -- 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] nsd and memory leaks
On 2004.01.08, John Shafto <[EMAIL PROTECTED]> wrote: > > 40-60MB is nothing. I'd worry if your nsd grows beyond 2GB. > > Doing what? Just about anything. If your stacksize is set to, say, 1 MB ... and you've got 20 threads for handling connections, you're looking at a nsd footprint of at least 20 MB. 40-60 MB is very reasonable for a site of any non-trivial amount of traffic. > This particular machine only has a 512mb of ram, and serves mostly > static content. I have bigger plans for it though. Look at the nsd.tcl config. ... see what different settings are set to. It's very believable that an out-of-the-box config would produce an nsd in the 40-60 MB ballpark. -- 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.
Re: [AOLSERVER] nsd and memory leaks
On Thu, 2004-01-08 at 21:33, John Shafto wrote: > > > I was running nsd v.3.4.2 on a fairly active website > > > (FreeBSD 4.x os) for a few weeks and had some > > > trouble with the nsd process growing. I was restarting > > > the process every few days as it grew to 40-60Mb. > > > > 40-60MB is nothing. I'd worry if your nsd grows beyond 2GB. > > Doing what? > This particular machine only has a 512mb of ram, one of my sites is running AOLServer 4.0 CVS (GM keeps hanging in schedule_timeout for me), OpenACS 5.0 beta 4, and sits at roughly 125mb in use after 3 weeks. 40k uniques/day Another site running AOLServer 4.0 CVS/OpenACS 5.0 beta 1 sits at 98mb in use after 23 days, an AOLServer 3/OpenACS 4.6.3 sits at 72mb after 47 days. I don't think 60mb is out of line. By the same token, I do have apache machines burning 200mb serving less traffic than the 125mb nsd that I have. So, it all depends on what you're doing. -- 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] Mention of AOLserver in Feb 2004 Linux Journal.
On Thu, Jan 08, 2004 at 09:15:49PM -0500, Lamar Owen wrote: > There is a good, if inconspicuous, mention of AOLserver in the Feb LJ. On > page 46, in the feature on the Magnatune record label, the statement is made: > "Apache 2 running PHP and OpenSSL serves all the HTML pages. When Magnatune > was Slashdotted, I found that Apache could not keep up with the load for > images. All HTTP image requests now are off-loaded to AOLserver, which had > the lowest latency to serve images at high speeds." Later: "Mathopd [which > they use to serve the very large streaming audio files] has more latency than > AOLserver, which is why we don't use it to serve small images." Why would anyone care about the "latency" of serving small images? Last I heard a human being viewing images in a browser is not exactly senstive to small latencies the way a parellel MPI program might be, after all. Or are they talking about absurdly large latency differences between Mathopd and AOLserver, like several seconds or more? -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] nsd and memory leaks
> > >[Dossy] > > > 40-60MB is nothing. I'd worry if your nsd grows beyond 2GB. > > > > Doing what? > > Just about anything. If your stacksize is set to, say, 1 MB ... and > you've got 20 threads for handling connections, you're looking at a nsd > footprint of at least 20 MB. 40-60 MB is very reasonable for a site of > any non-trivial amount of traffic. Okay, that sounds reasonable, but 2GB? What kind of work load would drive an nsd process up into the gigabytes of memory usage? > > This particular machine only has a 512mb of ram, and serves mostly > > static content. I have bigger plans for it though. > > Look at the nsd.tcl config. ... see what different settings are set to. > It's very believable that an out-of-the-box config would produce an nsd > in the 40-60 MB ballpark. That would be tolerable on a fairly loaded site, doing goodly amounts of database stuff and such. The site I am testing my first production AOLserver on is only doing mild static stuff with a few light cgi calls. I wondered where (if) it was going to stop growing. The way it was creeping looked suspiciously like a leak to me, which appears to have been confirmed by Scott. (I rebuilt with 'Ns_DStringInit(&dsPtr);' banged out of nscgi.c, and have been running it for four hours. It's sitting, apparently stable, at 14.5mb now.) -- 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] nsopenssl 3.0 beta 11
Beta 11 is now on my site (http://scottg.net). A fix for problems with downloading/uploading files that are larger than your average web page. /s. -- 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.
