Re: [AOLSERVER] aolserver + php
Micha³Nasiadka said: Hi. I've expierenced problems with running php on aolserver. Aolserver is segfaulting, while trying to use phpmyadmin, so I think it's something linked to mysql connectivity from php. Tried changing stacksize, tried even the devel versions of php, no luck. Can anybody help? What did you set your stacksize to? -- [EMAIL PROTECTED] www.RandomRamblings.com -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] [ aolserver-Feature Requests-746579 ] Server instance controller process
This is a very useful feature that would be very helpful for new users especially. I think it's so good, I would prefer to see it integrated such that you trigger it with a command line flag to nsd at start time. Many of you use other tools to perform watchdog activities, which is great. But others in the community who aren't as outspoken as the experts on this list might be running one-shot web sites where this feature would reduce the complexity of monitoring and restarting AOLserver should it fail. My vote is to put it in. /s. On Saturday, May 31, 2003, at 12:07 PM, Zoran Vasiljevic wrote: On Saturday 31 May 2003 18:43, you wrote: How many lines of code and how many man-hours will it take to implement in C? How long will it take to review all the code to ensure you've neither introduced any new bugs or otherwise broken already existing code? We have it running for about 3 years already. No need to develop anything since it is already there. It does not change anything related to the main server so it needs no extra testing. It is just an C-equivalent of your shell-script and it alows you to: nsd -s -t config.tcl and forget about it. It logs worker start/stop/restart in system logfile so its easy to track. Also, as a stand-alone script or program, folks running even older AOLserver 3.3.x could take advantage of it, rather than being forced to upgrade to either 4.x or 3.5.x ... or were you planning to backport this change all the way back? Ah Seeing all those responses... I think I'll just keep our own patched nsd copy and leave all as-is. It took me more time to write all those anwers, than to write the small C-routine we're talking about. If everybody is happy with shell/daemontools/whatever there is no reason for me to do anything here, obviously. Apparently, we have a very different usage pattern than most of the other users... Cheers, Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
[AOLSERVER] ConnsPerThread, nsxml and 'memory leak'
Although very well documented, it looks like the ConnsPerThread configuration parameter is unimplemented. I've checked in 3.4, 3.5 and 4.0beta8. Can anyone confirm this? Is there any special reason why it is not implemented? Now on to the real questions . . . We have an aolserver here that is setup as an xml-rpc server. It currenlty handles about 20-30 requests a day so it deals w/ twice that number of xml documents each day (request and response). Currently we need to restart nsd about once a week because it runs out of memory. I've gone through the hassle of loading everything into purify, and even though the process grows to about 150MB, it reports only about 20k of leaked memory. After a lot of debugging I've come to the following conclusion: It looks like ns_xml doc delete $id does not free _all_ resources used for that document. Some information is kept around for cleanup later. Under aolserver 3.x (and later I assume) this cleanup in handled by a call to Ns_TclRegisterDeferred which will not get called till the interpreter is cleaned up (which may never happen). Under previous versions of aolserver this cleanup was called by executing an ns_atclose command which would execute once the connection is closed. (look for the #ifdef NS_AOLSERVER_3_PLUS line in the code). So, under v3.x since the interpreters are not deleted till shutdown, the cleanup handlers don't get called and the process ends up using a ton of memory - non of which is reported as leaked because it cleans it up when the server shuts down. I've changed the code to call Ns_RegisterCleanup instead of Ns_TclRegisterDeferred, but that really freeked out the system, eventually resulting in segfaults. So then I changed the code to do what it did in pre 3.x versions of aolserver and everything seems to be peachy-keen. Now that the disertation is over . . . does any of that make sense? It doesn't seem like I should have to schedule the at_close to happen (or at least there should be an equivelent C call), and I would think calls to ns_xml doc delete should cleaup _everything_. And what's with the un-implemented connsperthread anyway Or am I completly wrong here? One other note. We've been using libxml 2.4.22 forever and tried to upgrade to 2.5.7 - but aolserver seems to segfault on invalid xml documents under 2.5.7 and it has something to do with the ctxt-_private variable being used to store a pointer to the interpreter. Is it possible 2.5.7 uses this field in a different way? Thanks for any information, Matthew Krenzer -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] [ aolserver-Feature Requests-746579 ] Server instance controller process
Scott Goodwin wrote: My vote is to put it in. /s. I agree completely. Feature: it is backwards and forward compatible with existing scripts AND it will make AOLserver implementation easier for newcomers by eliminating one more piece of the puzzle. Jerry -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] [ aolserver-Feature Requests-746579 ] Server instance controller process
My vote is to put it in too. It sounds particularly useful on Win32 where its harder to do the watchdog type stuff, and where quite honestly you need a second watchdog watching the first watchdog ;-) In older AOLservers there seemed to be a '-k' command line option to kill the running server. Could that be re-instated at the same time as a way of signalling to the server this is an intentional STOP signal so that it doesn't automatically restart? (I'd have thought this could be done with real SIGNALS, but wouldn't necessarily have to work that way - it could be a request to a configurable URL e.g. /STOP that changes some flag internally and shuts the server down. For the security conscious this could be password protected, require some cryptographic data along with the request, could be limited to request from the localhost etc. etc.) -Original Message- From: AOLserver Discussion [mailto:[EMAIL PROTECTED] Behalf Of Scott Goodwin Sent: Thursday, June 05, 2003 6:54 PM To: [EMAIL PROTECTED] Subject: Re: [AOLSERVER] [ aolserver-Feature Requests-746579 ] Server instance controller process This is a very useful feature that would be very helpful for new users especially. I think it's so good, I would prefer to see it integrated such that you trigger it with a command line flag to nsd at start time. Many of you use other tools to perform watchdog activities, which is great. But others in the community who aren't as outspoken as the experts on this list might be running one-shot web sites where this feature would reduce the complexity of monitoring and restarting AOLserver should it fail. My vote is to put it in. /s. On Saturday, May 31, 2003, at 12:07 PM, Zoran Vasiljevic wrote: On Saturday 31 May 2003 18:43, you wrote: How many lines of code and how many man-hours will it take to implement in C? How long will it take to review all the code to ensure you've neither introduced any new bugs or otherwise broken already existing code? We have it running for about 3 years already. No need to develop anything since it is already there. It does not change anything related to the main server so it needs no extra testing. It is just an C-equivalent of your shell-script and it alows you to: nsd -s -t config.tcl and forget about it. It logs worker start/stop/restart in system logfile so its easy to track. Also, as a stand-alone script or program, folks running even older AOLserver 3.3.x could take advantage of it, rather than being forced to upgrade to either 4.x or 3.5.x ... or were you planning to backport this change all the way back? Ah Seeing all those responses... I think I'll just keep our own patched nsd copy and leave all as-is. It took me more time to write all those anwers, than to write the small C-routine we're talking about. If everybody is happy with shell/daemontools/whatever there is no reason for me to do anything here, obviously. Apparently, we have a very different usage pattern than most of the other users... Cheers, Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] aolserver + php
What version of PHP and AOLserver are you running? You might want to also contact the folks at php.org as they actually maintain the AOLserver/PHP module. Micha Nasiadka wrote: Hi. I've expierenced problems with running php on aolserver. Aolserver is segfaulting, while trying to use phpmyadmin, so I think it's something linked to mysql connectivity from php. Tried changing stacksize, tried even the devel versions of php, no luck. Can anybody help? -- Nathan Folkman Technical Mgr., AOLserver/NPE/NES Web Services and Publishing -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Anyone had this error before?
Those errors occur when the connection is interrupted in mid-download, such as when a user hits the browser stop before an image is completely downloaded. Doug --- Doug Harris(202) 473-3118 [EMAIL PROTECTED] XD [EMAIL PROTECTED] Sent by: AOLserver Discussion [EMAIL PROTECTED] 06/05/2003 01:38 PM Please respond to AOLserver Discussion To: [EMAIL PROTECTED] cc: Subject:[AOLSERVER] Anyone had this error before? Anyone has any ideas what these errors are? [05/Jun/2003:13:23:20][16795.284][-conn196-] Error: ora8.c:4358:stream_write_lob error writing to connection. incomplete write of 0 out of 16384 [05/Jun/2003:13:23:20][16795.284][-conn196-] Error: can't write to connection for writing. received error Resource temporarily unavailable can't write to connection for writing. received error Resource temporarily unavailable Running AOLServer3.2 with aD Oracle Driver, seems error is from this part of the code: ns_ora write_blob $db select $img_column from $img_table where $image_column_id = $image_id It happend maybe 5 times a day with no apperant patterns. thanks, XD -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ConnsPerThread, nsxml and 'memory leak'
Thanks for tracking this down. Would you mind filing a few bug reports on SF? Thanks again! Matthew Krenzer wrote: Although very well documented, it looks like the ConnsPerThread configuration parameter is unimplemented. I've checked in 3.4, 3.5 and 4.0beta8. Can anyone confirm this? Is there any special reason why it is not implemented? Now on to the real questions . . . We have an aolserver here that is setup as an xml-rpc server. It currenlty handles about 20-30 requests a day so it deals w/ twice that number of xml documents each day (request and response). Currently we need to restart nsd about once a week because it runs out of memory. I've gone through the hassle of loading everything into purify, and even though the process grows to about 150MB, it reports only about 20k of leaked memory. After a lot of debugging I've come to the following conclusion: It looks like ns_xml doc delete $id does not free _all_ resources used for that document. Some information is kept around for cleanup later. Under aolserver 3.x (and later I assume) this cleanup in handled by a call to Ns_TclRegisterDeferred which will not get called till the interpreter is cleaned up (which may never happen). Under previous versions of aolserver this cleanup was called by executing an ns_atclose command which would execute once the connection is closed. (look for the #ifdef NS_AOLSERVER_3_PLUS line in the code). So, under v3.x since the interpreters are not deleted till shutdown, the cleanup handlers don't get called and the process ends up using a ton of memory - non of which is reported as leaked because it cleans it up when the server shuts down. I've changed the code to call Ns_RegisterCleanup instead of Ns_TclRegisterDeferred, but that really freeked out the system, eventually resulting in segfaults. So then I changed the code to do what it did in pre 3.x versions of aolserver and everything seems to be peachy-keen. Now that the disertation is over . . . does any of that make sense? It doesn't seem like I should have to schedule the at_close to happen (or at least there should be an equivelent C call), and I would think calls to ns_xml doc delete should cleaup _everything_. And what's with the un-implemented connsperthread anyway Or am I completly wrong here? One other note. We've been using libxml 2.4.22 forever and tried to upgrade to 2.5.7 - but aolserver seems to segfault on invalid xml documents under 2.5.7 and it has something to do with the ctxt-_private variable being used to store a pointer to the interpreter. Is it possible 2.5.7 uses this field in a different way? Thanks for any information, Matthew Krenzer -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- Nathan Folkman Technical Mgr., AOLserver/NPE/NES Web Services and Publishing -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ConnsPerThread, nsxml and 'memory leak'
On Thursday 05 June 2003 20:12, you wrote: Although very well documented, it looks like the ConnsPerThread configuration parameter is unimplemented. I've checked in 3.4, 3.5 and 4.0beta8. Can anyone confirm this? Is there any special reason why it is not implemented? Good hint. Mind filling-in SF bug report on that? Now on to the real questions . . . I've changed the code to call Ns_RegisterCleanup instead of Ns_TclRegisterDeferred, but that really freeked out the system, eventually resulting in segfaults. So then I changed the code to do what it did in pre 3.x versions of aolserver and everything seems to be peachy-keen. Can you provide some diffs and include them into the bug you have entered in SF, as requested above? One other note. We've been using libxml 2.4.22 forever and tried to upgrade to 2.5.7 - but aolserver seems to segfault on invalid xml documents under 2.5.7 and it has something to do with the ctxt-_private variable being used to store a pointer to the interpreter. Is it possible 2.5.7 uses this field in a different way? Personally, I have no C-level experience with ns_xml. Maybe the implementor can comment on this? Anyways, thanks for your feedback. We'll see what we can do here. Those memory problems are really frustrating, I know. Cheers, Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] [ aolserver-Feature Requests-746579 ] Server instance
We still have instances where AOLServer (3.2) goes deaf for some reason. The nsd processes are there, but they aren't handling any requests. So while I think this suggestion is a good idea, it probably won't take the place of watchdog monitoring, at least not for real production sites. Are you running? and Are you answering requests? are not the same question... Jim This is a very useful feature that would be very helpful for new users especially. I think it's so good, I would prefer to see it integrated such that you trigger it with a command line flag to nsd at start time. Many of you use other tools to perform watchdog activities, which is great. But others in the community who aren't as outspoken as the experts on this list might be running one-shot web sites where this feature would reduce the complexity of monitoring and restarting AOLserver should it fail. My vote is to put it in. /s. On Saturday, May 31, 2003, at 12:07 PM, Zoran Vasiljevic wrote: On Saturday 31 May 2003 18:43, you wrote: How many lines of code and how many man-hours will it take to implement in C? How long will it take to review all the code to ensure you've neither introduced any new bugs or otherwise broken already existing code? We have it running for about 3 years already. No need to develop anything since it is already there. It does not change anything related to the main server so it needs no extra testing. It is just an C-equivalent of your shell-script and it alows you to: nsd -s -t config.tcl and forget about it. It logs worker start/stop/restart in system logfile so its easy to track. Also, as a stand-alone script or program, folks running even older AOLserver 3.3.x could take advantage of it, rather than being forced to upgrade to either 4.x or 3.5.x ... or were you planning to backport this change all the way back? Ah Seeing all those responses... I think I'll just keep our own patched nsd copy and leave all as-is. It took me more time to write all those anwers, than to write the small C-routine we're talking about. If everybody is happy with shell/daemontools/whatever there is no reason for me to do anything here, obviously. Apparently, we have a very different usage pattern than most of the other users... Cheers, Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] [ aolserver-Feature Requests-746579 ] Server instance
-Original Message- From: AOLserver Discussion [mailto:[EMAIL PROTECTED] Behalf Of Jim Wilcoxson Sent: Thursday, June 05, 2003 9:35 PM To: [EMAIL PROTECTED] Subject: Re: [AOLSERVER] [ aolserver-Feature Requests-746579 ] Server instance We still have instances where AOLServer (3.2) goes deaf for some reason. The nsd processes are there, but they aren't handling any requests. So while I think this suggestion is a good idea, it probably won't take the place of watchdog monitoring, at least not for real production sites. Are you running? and Are you answering requests? are not the same question... Jim True, but you only need one of those monitoring functions and in the event that it isn't answering requests the monitoring process should just be able to send it a signal to get it back into an operational state rather than worry about the complexities ;-) of restarting it. Different users will have different needs, but its nice if the option is there rather than *having* to use a watchdog because there's no alternative. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
[AOLSERVER] Bytecode-compiled Tcl question
Hello, I am getting a SIGABRT when evaluating string objects in AOLserver 4.0 b6. The pseudocode is: interp=Ns_GetConnInterp (Ns_GetConn ()) obj = Tcl_NewStringObj (utf8string, len) Tcl_IncrRefCount (obj) repeat a_few_times Tcl_EvalObjEx (interp, obj, 0) end Tcl_DecrRefCount (obj) /* NOTE: this statement happens later, and in a different thread */ This sequence runs OK in a load test, but once AOLserver decides to get rid of a connection thread after load goes down, and run cleanup handlers, an invalid memory block appears, leading to ABRT. Am I doing something wrong? Crash debug info follows. Thanks! Alex alloc: invalid block: 97df00: 0 70 ef [1] __sigprocmask(0x0, 0xfb980bd0, 0x0, 0x, 0x, 0x0), at 0xfee59d18 [2] _resetsig(0xfee6c9ac, 0x0, 0x0, 0x0, 0xfb981e3c, 0xfb981e40), at 0xfee4f354 [3] _sigon(0xfee743c0, 0xfee742a0, 0xfb981e38, 0xfb980ca4, 0x6, 0xfeecdf94), at 0xfee4eb10 [4] _thrp_kill(0x0, 0x9, 0x6, 0xfee6c9ac, 0xfb981dc0, 0xff24ecd0), at 0xfee518e4 [5] abort(0xfef35ad4, 0xfef3d5d4, 0xfef39738, 0xfef39738, 0x70, 0xef), at 0xfeeb95d0 =[6] Tcl_PanicVA(format = 0xff22e2ec "alloc: invalid block: %p: %x %x %x\n", argList = 0xfb980ea8), line 106 in "tclPanic.c" [7] Tcl_Panic(arg1 = 0xff22e2ec "alloc: invalid block: %p: %x %x %x\n", ...), line 134 in "tclPanic.c" [8] Ptr2Block(ptr = 0x97df08 "ns_adp_parse"), line 750 in "tclThreadAlloc.c" [9] TclpFree(ptr = 0x97df08 "ns_adp_parse"), line 390 in "tclThreadAlloc.c" [10] Tcl_Free(ptr = 0x97df08 "ns_adp_parse"), line 1160 in "tclCkalloc.c" [11] Tcl_InvalidateStringRep(objPtr = 0x7fe128), line 868 in "tclObj.c" [12] TclFreeObj(objPtr = 0x7fe128), line 679 in "tclObj.c" [13] TclReleaseLiteral(interp = 0xd44588, objPtr = 0x7fe128), line 745 in "tclLiteral.c" [14] TclCleanupByteCode(codePtr = 0xa8d330), line 652 in "tclCompile.c" [15] FreeByteCodeInternalRep(objPtr = 0xcc2d60), line 538 in "tclCompile.c" [16] TclFreeObj(objPtr = 0xcc2d60), line 677 in "tclObj.c" -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_eval is EVIL in AOLserver 4
On Friday 06 June 2003 04:28, you wrote:
The implementation in AOLserver 4 is very, very different. The script is
executed then the ENTIRE set of namespaces and procs are saved to the
server's tcl.script pointer.
This effect is not exactly stated in the docs, right, but it is the way
the new mechanism (look at ns_ictl) is working, yes.
The purpose was to enable people to sync-up interps at runtime
allowing for dynamical load of packages and stuff, w/o bringing
the server down or doing some custom tcl sourcing.
This means that when interpreters are updated (as happens when an
interpreter's created for a new thread, for instance) ALL of the global
variables in the new thread have the values in the old thread. ns_eval {
...script ... } , then, is really a synch all interpreters command that
first evaluates the given script.
Yes, it is rather sync all interpreters and in all threads behaviour.
One EVIL side effect of this is that some of the standard ns_* Tcl API is
implemented in Tcl, in some cases using global variables. So, for
instance, I have a test case in which the following code:
set form_size [ns_set size [ns_getform]]
Well, this is kind of bad, I agree. Heh, ns_evil, ... I like it :)
fails because another script has done an ns_eval and _ns_form was set in
that thread to t3. In the failing thread [ns_getform] has never been
called, yet it's seeing _ns_form with the value t3 - an ns_set which does
not exist in its context, of course.
This is ... non-intuitive. Especially if one RTFMs and expects the
behavior to be at least someone like the behavior that's described ...
So much has changed in 4.0... were all trying to keep all pieces
fit together.
BTW, the FM's would love to see volunteers that would spend
an hour or two with some of them :)
Now the one use of ns_eval in OpenACS that causes the above problem can be
fixed by simply switching to nsvs (probably a good idea anyway) but the
documentation for ns_eval should be changed, perhaps? I have a hard time
seeing the new functionality being all that useful ...
After some thinking, I came to conclusion that actually both functionalities
are very useful. Sometimes I just want to sync-up the interps, for whatever
reason, with just one hit (as what new ns_eval does). Sometimes I may want
to run one single command in all interps not replicating the whole interp
enchilada over and over (like the older one does).
I would love to hear some other oppinions. But, I'm already thinking about
what we'd need to do so that both approaches are available.
Cheers,
Zoran
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list: http://www.aolserver.com/listserv.html
List information and options: http://listserv.aol.com/
Re: [AOLSERVER] [ aolserver-Feature Requests-746579 ] Server instance
On Thursday 05 June 2003 22:35, you wrote: for real production sites. Are you running? and Are you answering requests? are not the same question... Indeed they are not. I'd add some more confusion by extending the second to Are you *correctly* answering requests? So, the solution window may vary between a very simple dumb one Are you still running? to some AI-based custom behaviour, which is, by it's very nature, hard (if possible at all) to properly generalize. Now, reality is: there is *none* of the above in nsd as-is now! I wanted to have at least the most simple and obvious one and I'm sure that this would help (and simplify work of) many people. One has yet to find the well-balanced approach how far to go towards the other extreme. Since you have quite a long record using the nsd over time, maybe you can contribute some ideas about this matter to SF RFE? Cheers, Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] [ aolserver-Feature Requests-746579 ] Server instance
On Friday 06 June 2003 09:50, you wrote: At the risk of adding complexity to the parent process, I wouldn't mind seeing such a monitoring facility added to the parent process. That implies, the parent (watchdog) should have at least one thread with the instantiated Tcl interp with ns_* command set loaded, right? We can put some ns/server/watchdog section and fill in some variables there, one of whoch could point to a file with Tcl procs to run for checking. Sort of that, hm... ? Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] [ aolserver-Feature Requests-746579 ] Server instance
Zoran Vasiljevic wrote: On Friday 06 June 2003 09:50, you wrote: At the risk of adding complexity to the parent process, I wouldn't mind seeing such a monitoring facility added to the parent process. That implies, the parent (watchdog) should have at least one thread with the instantiated Tcl interp with ns_* command set loaded, right? We can put some ns/server/watchdog section and fill in some variables there, one of whoch could point to a file with Tcl procs to run for checking. Sort of that, hm... ? Zoran Not necessarily. Maybe. It would be nice to be able to use Tcl to communicate and implement parent process modules and functions. But maybe it's simpler and more reliable just to put in a bare bones http get implementation Jerry -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] [ aolserver-Feature Requests-746579 ] Server instance
On Friday 06 June 2003 10:29, you wrote: But maybe it's simpler and more reliable just to put in a bare bones http get implementation For people using aolserver as http-server, well, ok. But there are others, not necessarily employing it as http-server at all. I think in order to have a general solution, one should at least allow some limited scripting capabilites for the watchdog, if need be. On the other side, having the watchdog as simple is possible is equaly (if not more) important. It would be fine to hear some other comments. Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_eval is EVIL in AOLserver 4
On Friday 06 June 2003 11:48, you wrote: Zoran Vasiljevic wrote: I would love to hear some other oppinions. But, I'm already thinking about what we'd need to do so that both approaches are available. My simple guess would be that the easiest solution would be to 1/ create a temporary interpreter 2/ eval the initialization code in it 3/ eval the code entered in ns_eval 4/ grab the new initialization code Good point :) Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] aolserver + php
On Thu, Jun 05, 2003 at 10:55:44AM -0600, Patrick Spence wrote: Micha?Nasiadka said: Hi. I've expierenced problems with running php on aolserver. Aolserver is segfaulting, while trying to use phpmyadmin, so I think it's something linked to mysql connectivity from php. Tried changing stacksize, tried even the devel versions of php, no luck. Can anybody help? What did you set your stacksize to? I believe it was 512*1024. -- Michal Nasiadka [EMAIL PROTECTED] -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] aolserver + php
- Original Message - From: Micha Nasiadka [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, June 06, 2003 6:16 AM Subject: Re: [AOLSERVER] aolserver + php On Thu, Jun 05, 2003 at 10:55:44AM -0600, Patrick Spence wrote: Micha?Nasiadka said: Hi. I've expierenced problems with running php on aolserver. Aolserver is segfaulting, while trying to use phpmyadmin, so I think it's something linked to mysql connectivity from php. Tried changing stacksize, tried even the devel versions of php, no luck. Can anybody help? What did you set your stacksize to? I believe it was 512*1024. What version of linux are you running.. at one point one of the up2date upgrades on one of the dns libraries on redhat caused serious memory issues and caused segfaulting on dns lookups especially with php running -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_eval is EVIL in AOLserver 4
On Friday 06 June 2003 02:53 am, Zoran Vasiljevic wrote: On Friday 06 June 2003 11:48, you wrote: Zoran Vasiljevic wrote: I would love to hear some other oppinions. But, I'm already thinking about what we'd need to do so that both approaches are available. My simple guess would be that the easiest solution would be to 1/ create a temporary interpreter 2/ eval the initialization code in it 3/ eval the code entered in ns_eval 4/ grab the new initialization code Good point :) Zoran Yes, this would be an easy spin-off of the existing code I believe. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_eval is EVIL in AOLserver 4
On Friday 06 June 2003 16:12, Don Baccus wrote: On Friday 06 June 2003 02:53 am, Zoran Vasiljevic wrote: On Friday 06 June 2003 11:48, you wrote: Zoran Vasiljevic wrote: I would love to hear some other oppinions. But, I'm already thinking about what we'd need to do so that both approaches are available. My simple guess would be that the easiest solution would be to 1/ create a temporary interpreter 2/ eval the initialization code in it 3/ eval the code entered in ns_eval 4/ grab the new initialization code Good point :) Zoran Yes, this would be an easy spin-off of the existing code I believe. Nevertheles, to be really fair, there is some more work to be done under the hood to get this working. The problem is in 1/. Simple interp create won't work since script passed to ns_eval might contain ns_* commands which are not part of the virgin Tcl interp. I will have to investigate what we need to do to get the 1/ run properly. When this is solved, the rest is trivial. Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_eval is EVIL in AOLserver 4
Don Baccus wrote: I would love to have time to contribute to AOLserver It sounds like you just contributed 4 hours tracking down a bug. Yes, that's my thinking, too. An ns_sync tthat copies state and ns_eval that works as it did in AOLserver3 would probably both be useful. how about: ns_interp sync ns_interp eval ? --Tom Jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_eval is EVIL in AOLserver 4
On Thursday 05 June 2003 22:28, Don Baccus wrote: The implementation in AOLserver 4 is very, very different. The script is executed then the ENTIRE set of namespaces and procs are saved to the server's tcl.script pointer. Argh! One EVIL side effect of this is that some of the standard ns_* Tcl API is implemented in Tcl, in some cases using global variables. So, for instance, I have a test case in which the following code: The other side effect (that we've been seeing complained about lately) is related to the following in acs-tcl: 00-database-procs-oracle.tcl:global errorInfo errorCode 00-database-procs-oracle.tcl:global db_state 00-database-procs-oracle.tcl:global errorInfo errorCode 00-database-procs-oracle.tcl:global env 00-database-procs-oracle.tcl:global env 00-database-procs-postgresql.tcl:global errorInfo errorCode 00-database-procs-postgresql.tcl:global errorInfo errorCode 00-database-procs-postgresql.tcl:global db_state 00-database-procs-postgresql.tcl:global errorInfo errorCode 00-database-procs-postgresql.tcl:global tcl_platform 00-database-procs-postgresql.tcl:global errorCode 00-database-procs.tcl:global db_state 00-database-procs.tcl: global errorInfo errorCode 00-database-procs.tcl: global errorInfo errorCode 00-database-procs.tcl:global db_state 00-database-procs.tcl:global errorInfo errorCode 00-database-procs.tcl: global errorInfo errorCode 00-database-procs.tcl: global errorInfo errorCode 00-database-procs.tcl:global db_state 00-database-procs.tcl: global errorInfo errorCode 00-database-procs.tcl: global errorInfo errorCode 00-database-procs.tcl: global errorInfo errorCode 00-database-procs.tcl: global errorInfo errorCode 00-database-procs.tcl:global db_state 00-database-procs.tcl:global db_state 00-database-procs.tcl:# global db_state(handles) is a list of handles that have been allocated. 00-database-procs.tcl:# global db_state(n_handles_used) is the number of handles in this list that are Methinks this could have bad side-effects, particularly if a thread without a pool and without handles executes ns_eval. The next invocation of any of the db_* API could produce the uninitialized pool result 'nsdb0' (I knew I remembered that from somewhere -- I've seen the nsdb0 result before when a pool wasn't properly initialized (way back when the PostgreSQL driver was being beta tested for PostgreSQL 6.2.1, and AOLserver was at 2.2)). Maybe I'm wrong, but I did trace through all of that code, and the only way I could see ns_pg_bind getting passed a table name of nsdb0 was through something external to the thread changing the global state variable 'db_state'. Now maybe I'm not grokking it correctly, but the proc 'db_with_handle' is mixing state between a global and an nsv (through a call to db_nth_pool_name, which uses the nsv 'db_available_pools'). Again, maybe I'm off-base a little, but I went through the code the other day (after Mohan's report of a driver issue, which isn't really a driver issue) and determined that the code paths in AOLserver 3.x and AOLserver 4.x for pool creation, handle availability and creation, and the various data structures between the database driver, the pool API, and the handle API hadn't changed in a significant way. But this behavior of ns_eval could explain that problem, depending upon the timing of its execution, as well as where the ns_eval was used. So, when a patch for OpenACS that doesn't use ns_eval is ready, those of you who have problems with the nsdb0 stuff, if yu could please determine whether the elimination of ns_eval fixes it. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_eval is EVIL in AOLserver 4
On Friday 06 June 2003 17:11, Don Baccus wrote:
On Friday 06 June 2003 08:03 am, Zoran Vasiljevic wrote:
Nevertheles, to be really fair, there is some more work to be done
under the hood to get this working. The problem is in 1/.
Simple interp create won't work since script passed to ns_eval
might contain ns_* commands which are not part of the virgin
Tcl interp.
These get defined if you run the THREAD_INIT callbacks registered by
various modules to define their ns_* API commands, no? Or are there others
I'm not aware of? As I said, yesterday afternoon was the first time I
looked at this code so I don't pretend to understand all of it fully.
Look for InitInterp() in nsd/tclinit.c. The problem is that, although most of
the commands are already loaded (call to NsTclAddCmds(interp, itPtr))
those created by running traces (as registered by loaded modules)
are run only in the context of the running virtual server.
My initial idea was to simply make the Nsd as static package by doing
Tcl_StaticPackage() at the end of InitInterp() and then do from Tcl:
set interp [interp create]
$interp eval {load Nsd}
$interp eval [ns_ictl get]
and so on... but this won't get the proper virtual server context
so it'll skip the traces. Phew. I must dig little bit more there.
Zoran
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list: http://www.aolserver.com/listserv.html
List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_eval is EVIL in AOLserver 4
On Friday 06 June 2003 17:11, you wrote: how about: ns_interp sync ns_interp eval ? Hey Tom, thanks! You just gave me the idea: extend the Tcl interp with custom ns_interp and do the necessary plumbing on C level before returning the interp to caller. This might work. Have to check yet. I think the first interp subcommand we'd override would be the create, so: interp create == ns_interp create but with additional step of preparing the interp aolserver-way so we get all those extended commands. Well, this would mean we'd need to introduce new ns_* command to the cmd set. Let see if anybody comes with the better idea. If not, I think this might be the way to go. This could also take the ns_markfordelete, for example: ns_interp markfordelete or similar. Well, well... Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_eval is EVIL in AOLserver 4
On Friday 06 June 2003 08:15 am, Zoran Vasiljevic wrote:
My initial idea was to simply make the Nsd as static package by doing
Tcl_StaticPackage() at the end of InitInterp() and then do from Tcl:
set interp [interp create]
$interp eval {load Nsd}
$interp eval [ns_ictl get]
and so on... but this won't get the proper virtual server context
so it'll skip the traces. Phew. I must dig little bit more there.
Right, if you skip the traces you don't get the module-defined ns_* commands,
we're on the same page here ... as far as this bit goes anyway.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list: http://www.aolserver.com/listserv.html
List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_eval is EVIL in AOLserver 4
On Friday 06 June 2003 08:12 am, Lamar Owen wrote: On Thursday 05 June 2003 22:28, Don Baccus wrote: The implementation in AOLserver 4 is very, very different. The script is executed then the ENTIRE set of namespaces and procs are saved to the server's tcl.script pointer. Argh! One EVIL side effect of this is that some of the standard ns_* Tcl API is implemented in Tcl, in some cases using global variables. So, for instance, I have a test case in which the following code: The other side effect (that we've been seeing complained about lately) is related to the following in acs-tcl I didn't bother mentioning these because I thought pointing out the problem with ns_getform would get people's attention :) I'd kludged around some of these by initializing them in the request processor before I figured out that our two calls to ns_evil were the problem. Methinks this could have bad side-effects, particularly if a thread without a pool and without handles executes ns_eval. The next invocation of any of the db_* API could produce the uninitialized pool result 'nsdb0' (I knew I remembered that from somewhere -- I've seen the nsdb0 result before when a pool wasn't properly initialized (way back when the PostgreSQL driver was being beta tested for PostgreSQL 6.2.1, and AOLserver was at 2.2)). This was the first problem I ran into, indeed, after kludging around it I ran into the ns_getform problem and decided to start reading AOLserver sources since I had no idea that ns_eval was the problem ... But this behavior of ns_eval could explain that problem, depending upon the timing of its execution, as well as where the ns_eval was used. Yes, I believe you'll find that this is the problem. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] [ aolserver-Feature Requests-746579 ] Server instance
THis isn't the listserv I wanted to be connected to, how do i get off this one?? thanks -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_eval is EVIL in AOLserver 4
On Friday 06 June 2003 11:50, Don Baccus wrote: On Friday 06 June 2003 08:12 am, Lamar Owen wrote: The other side effect (that we've been seeing complained about lately) is related to the following in acs-tcl I didn't bother mentioning these because I thought pointing out the problem with ns_getform would get people's attention :) Excellent point. I just wanted to correlate, since the driver was initially questioned. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
[AOLSERVER] LISTSERV problems....
Sorry to post this to the list :-( I can't seem to get a response from LISTSERV, either by email or using the web interface. Whoever is an admin on this list, please email me. -- Tom Poindexter [EMAIL PROTECTED] http://www.nyx.net/~tpoindex/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_eval is EVIL in AOLserver 4
On Fri, 6 Jun 2003 11:12:43 -0400, Lamar Owen wrote: So, when a patch for OpenACS that doesn't use ns_eval is ready, those of you who have problems with the nsdb0 stuff, if yu could please determine whether the elimination of ns_eval fixes it. I made a patch http://openacs.org/bugtracker/openacs/patch?patch_number=165 and it gets rid of the nsdb0 problem for me and at least a few others who have emailed me. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_eval is EVIL in AOLserver 4
On Friday 06 June 2003 11:54 am, Vinod Kurup wrote: On Fri, 6 Jun 2003 11:12:43 -0400, Lamar Owen wrote: So, when a patch for OpenACS that doesn't use ns_eval is ready, those of you who have problems with the nsdb0 stuff, if yu could please determine whether the elimination of ns_eval fixes it. I made a patch http://openacs.org/bugtracker/openacs/patch?patch_number=165 and it gets rid of the nsdb0 problem for me and at least a few others who have emailed me. Hey, sweet, Vinod! Great doctoring of the code there! (for those of you not part of the OpenACS community, Vinod is a practicing MD. Isn't Open Source great?) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
[AOLSERVER] Ns_Tls
Hello, when I start AOLServer on NetBSD -current it gives an error: Ns_Tls: invalid key: 0: sould bee between 1 and 100 and dumps core. Can sombody tell me what it means? TIA Feri -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Ns_Tls
In a message dated 6/6/2003 6:03:40 PM Central Standard Time, [EMAIL PROTECTED] writes: Hello, when I start AOLServer on NetBSD -current it gives an error: Ns_Tls: invalid key: 0: sould bee between 1 and 100 and dumps core. Can sombody tell me what it means? TIA Feri which version? i had introduced a bug in 3.5.8. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_eval is EVIL in AOLserver 4
On Friday, June 6, 2003, at 05:42 PM, Don Baccus wrote: (for those of you not part of the OpenACS community, Vinod is a practicing MD. Isn't Open Source great?) Open Source definitely is great. I can't wait for the day that my patients come with error logs and gdb-hook-ups. Then my 2 worlds will be 1 and I'll be very happy. ;-) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
[AOLSERVER] Net access for patients ...
On Friday 06 June 2003 06:13 pm, you wrote: On Friday, June 6, 2003, at 05:42 PM, Don Baccus wrote: (for those of you not part of the OpenACS community, Vinod is a practicing MD. Isn't Open Source great?) Open Source definitely is great. I can't wait for the day that my patients come with error logs and gdb-hook-ups. Then my 2 worlds will be 1 and I'll be very happy. ;-) A guy I know - a research biochemist who is very fit and in his mid-fifties but has been having episodes of skipping heart beats, racing etc - was given a really cool device by OHSU, our local med school. They were unable to trigger any episodes when he was there in person, on the treadmill, etc so he triggers this device whenever he has an episode, then goes to the phone and uploads the data over a modem. Pretty cool! -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Net access for patients ...
On Friday 06 June 2003 06:27 pm, you wrote: A guy I know - a research biochemist who is very fit and in his mid-fifties but has been having episodes of skipping heart beats, racing etc - was given a really cool device by OHSU, our local med school. Sorry I meant to e-mail that to Vinod personally, not the list! :( -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Ns_Tls
On Fri, 6 Jun 2003 20:49:13 EDT Nathan Folkman [EMAIL PROTECTED] wrote: In a message dated 6/6/2003 6:03:40 PM Central Standard Time, [EMAIL PROTECTED] writes: Hello, when I start AOLServer on NetBSD -current it gives an error: Ns_Tls: invalid key: 0: sould bee between 1 and 100 and dumps core. Can sombody tell me what it means? TIA Feri which version? i had introduced a bug in 3.5.8. It is 4.0beta8. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
