Re: [AOLSERVER] PHP in AOLserver
Of course, the more popular languages weren't implemented with embeddability (embedibility?) in mind. [...] safely embedded in a multi-threaded application. I intended to reply to an earlier message regarding the suggestion that we try to support PHP in AOLserver, but Dossy's observation about thread-safety jogged my memory. There is (was?) a libphp.so for AOLserver, but it has been notoriously unstable. It stability is directly tied to the lack of thread-safety in PHP loadable modules. In addition, lots of PHP applications depend on stuff provided by Apache (mostly Apache-set environment variables) that AOLserver does not also provide. Several years ago I spent a substantial amount of time trying to get Imp (the IMAP webmail client) running in AOLserver--I abandoned the project when I realized that the thread-safety was just not there. The bottom line is that it's not sufficient to simply provide PHP in AOLserver, it would have to be PHP with enough Apacheness added to allow it to be a drop-in replacement for the huge number of PHP applications out there. --cro -- 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] php and AolServer
I've got a unfine problem with that combination. I downloaed php4.4 from the php pages and now the following happens. Sometims the php pages get parsed and displayed correctly on other times I see the source code and on yet other times I just see an empty window. Even with the simples php file I got this behaviour: example 1 this is my php file xin html ?php phpinfo(); ? /html can't be much simpler now whil using firefox to display that page: and nothing is shown neither the html nor some information one the first visit of that file with Mozilla I got an empty page, after reloading I got the informatoin I expected but it looks messed up: value auto_prepend_fileno valueno value browscapno valueno value default_charsetno valueno value default_mimetypetext/htmltext/html define_syslog_variablesOffOff disable_classesno valueno value disable_functionsno valueno value display_errorsOffOff display_startup_errorsOffOff doc_rootno valueno value docref_extno valueno value docref_rootno valueno value enable_dlOnOn error_append_stringno valueno value error_logno valueno value error_prepend_stringno valueno value error_reporting20472047 expose_phpOnOn extension_dir././ file_uploadsOnOn gpc_orderGPCGPC highlight.bg#FF#FF highlight.comment#FF8000#FF8000 highlight.default#BB#BB highlight.html#00#00 highlight.keyword#007700#007700 highlight.string#DD#DD html_errorsOnOn ignore_repeated_errorsOffOff ignore_repeated_sourceOffOff ignore_user_abortOffOff implicit_flushOffOff include_path.:/usr/local/lib/php.:/usr/local/lib/php log_errorsOnOn log_errors_max_len10241024 magic_quotes_gpcOffOff magic_quotes_runtimeOffOff magic_quotes_sybaseOffOff max_execution_time3030 max_input_time6060 open_basedirno valueno value output_buffering40964096 output_handlerno valueno value post_max_size8M8M precision1414 register_argc_argvOffOff register_globalsOffOff report_memleaksOnOn safe_modeOffOff safe_mode_exec_dirno valueno value safe_mode_gidOffOff safe_mode_include_dirno valueno value sendmail_fromno valueno value sendmail_path/usr/sbin/sendmail -t -i /usr/sbin/sendmail -t -i serialize_precision100100 short_open_tagOnOn SMTPlocalhostlocalhost smtp_port2525 sql.safe_modeOffOff track_errorsOffOff unserialize_callback_funcno valueno value upload_max_filesize2M2M upload_tmp_dirno valueno value user_dirno valueno value variables_orderGPCSGPCS xmlrpc_error_number00 xmlrpc_errorsOffOff y2k_complianceOnOn AOLserver SAPI module version $Id: aolserver.c,v 1.72.2.4 2003/05/31 01:37:44 sniper Exp $ Build date Mar 8 2005 at 00:14:44 It's AOLServer 4.0.10 from Debian php4.4 downloaded from the php sites System Debian/Linux AMD64 unstable. Regards Friedrich -- 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] AOLServer + PHP
It seems the patches are needed for PHP4.4 to get it running under AOLServer, I should have checked before my last mail Regards Friedrich -- 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] php and AolServer
Dear Friedrich, Been there, seen that... See http://www.panoptic.com/wiki/aolserver/1314 for the relevant patch. Also make sure to change the settings for stacksize as documented. If not, aolserver4-nsd will crash! Since you have debian you will need the following files to speed up starting create the following files and make sure that size 0: /etc/ld.so.nohwcap /etc/ld.so.preload To speed up php you might want to compile without the shared options. libphp4.so will become bigger, but the throughput increases dramaticly. (tested with apache benchmark) Regards Fred Peeterman Systems Administrator TerraTec Electronic GmbH Herrenpfad 38 D 41334 Nettetal Tel: +49-2157-8179-997 Fax: +49-2157-8179-22 Email: [EMAIL PROTECTED] http://www.terratec.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] php and AolServer
Thanks, I do not care about speed yet. It will be more then fast enough for my needs. I just wanted to be sure that I've the chance to make some PHP running under AOLServer, there are other solutions available but it seems quite few PHP solutoins are quite a bit better then what is available as OpenACS package, and well I have some PHP runnin (yes shame on me ;-), and am not keen on transfering all the data from one Database layout to another... Regards Friedrich -- 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] php-cgi problem
Thanks, both solutions (the shell script, and new nscgi) work, still with necessity of REDIRECT_STATUS parameter. Martin -- 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] php-cgi problem
Hello, I can not make PHP4 to work as cgi (with nscgi). I added an option of: ns_param REDIRECT_STATUS 1 so that it try to work at all. Still, however, PHP can not find script files, with the only output of: 'No input file specified.' I do not want to use php module, since I do not use it regularly and I do not want to destabilize server. Thanks, Martin -- 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] PHP works, but content-length is zero
Hey, I'm playing around with the php module (libphp5.so). Using a browser, I get nothing displayed, so I telnetted in and I get the desired page, but the content length header is set to zero: HTTP/1.0 200 OK X-Powered-By: PHP/5.0.4 MIME-Version: 1.0 Date: Sat, 18 Jun 2005 15:20:29 GMT Server: AOLserver/4.0.9 Content-Type: text/html Content-Length: 0 Connection: close html head titlePHP Test/title /head body pHello World/p/body /html Does anyone have a clue what I should do? tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] PHP works, but content-length is zero
In a message dated 6/18/05 11:35:09 AM, [EMAIL PROTECTED] writes: I'm playing around with the php module (libphp5.so). Using a browser, I get nothing displayed, so I telnetted in and I get the desired page, but the content length header is set to zero: HTTP/1.0 200 OK X-Powered-By: PHP/5.0.4 MIME-Version: 1.0 Date: Sat, 18 Jun 2005 15:20:29 GMT Server: AOLserver/4.0.9 Content-Type: text/html Content-Length: 0 Connection: close Hmm -- perhaps the module is setting length to zero (or not setting it at all and it's initialized to zero) and the code is spitting that out when the intended behavior is no header, i.e., stream-based response. Setting length to -1 would supress the header -- code is in nsd/return.c. BTW: In 4.5 there's a function, Ns_ConnFlush, which is designed to handle these sorts of results, streamed or all batched up, character encoded and/or gzip'ed. Most of the code was private to ADP previously -- it was factored out so other modules such as PHP could benefit. -Jim 2">
Re: [AOLSERVER] PHP works, but content-length is zero
On Saturday 18 June 2005 08:48, Jim Davidson wrote: Hmm -- perhaps the module is setting length to zero (or not setting it at all and it's initialized to zero) and the code is spitting that out when the intended behavior is no header, i.e., stream-based response.Setting length to -1 would supress the header -- code is in nsd/return.c. Okay, it looks like the aolserver module calls php_execute_script, but never updates the conn structure. It also seems that this module only executes one file, so maybe you have to write your php code to deal with this. I'll try hacking the code to hold -1 and see what happens. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] PHP works, but content-length is zero
On 2005.06.18, Tom Jackson [EMAIL PROTECTED] wrote: I'm playing around with the php module (libphp5.so). Using a browser, I get nothing displayed, so I telnetted in and I get the desired page, but the content length header is set to zero: [...] Does anyone have a clue what I should do? PHP requires a patch to work as a module inside AOLserver: http://panoptic.com/wiki/aolserver/HowToSetUpPHPUnderAOLserver Alternatively, you can now use nscgi from CVS HEAD and run php-cgi under AOLserver, as well. -- 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] PHP works, but content-length is zero
Dossy is right it does require the php patch the other thing you'll notice is that it can only be added to one virtual server instance. But other than that it runs pretty well p Dossy Shiobara wrote: On 2005.06.18, Tom Jackson [EMAIL PROTECTED] wrote: I'm playing around with the php module (libphp5.so). Using a browser, I get nothing displayed, so I telnetted in and I get the desired page, but the content length header is set to zero: [...] Does anyone have a clue what I should do? PHP requires a patch to work as a module inside AOLserver: http://panoptic.com/wiki/aolserver/HowToSetUpPHPUnderAOLserver Alternatively, you can now use nscgi from CVS HEAD and run php-cgi under AOLserver, as well. -- 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] aolserver/php
Using a different threaded test tool that compares the actual output to an expected output, I ran 150k tests with a 100% pass rate. This is with 20 concurrent request threads. To handle the load I added this to my config: ns_parammaxthreads 512 ns_paramminthreads 10 I am running PHP 5.0.0, AOLserver 4.0.5 on Linux 2.4.24 (RedHat 7.2). rob Dossy Shiobara wrote: On 2004.07.23, Noah Robin [EMAIL PROTECTED] wrote: So, in the interest of science (and probably masochism) I compiled PHP 4.3.8 (with the aolserver.c patch from panoptic) against aolserver 3.5.10 and 4.0.7 last night, and ran some load tests. Result: on linux 2.4.26, and the only PHP configure option was --with-aolserver=, I was seeing a failure rate of ~6% for a page that only called phpinfo(). Load test: /usr/sbin/ab2 -n10 -c25 http://localhost:8000/ (ab2 being the version of 'ab' that ships with apache2). Lets see what I get on my system: $ uname -a Linux ecwav 2.6.5 #3 Thu May 6 06:57:14 EDT 2004 i686 GNU/Linux $ cat /proc/cpuinfo | grep model name model name : Intel(R) Pentium(R) III CPU family 1266MHz $ cat test.php ? phpinfo(); ? $ ab -c25 -n1 http://panoptic.com/test.php This is ApacheBench, Version 1.3d $Revision: 1.67 $ apache-1.3 Copyright (c) 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ Copyright (c) 1998-2002 The Apache Software Foundation, http://www.apache.org/ Benchmarking panoptic.com (be patient) Completed 1000 requests Completed 2000 requests Completed 3000 requests Completed 4000 requests Completed 5000 requests Completed 6000 requests Completed 7000 requests Completed 8000 requests Completed 9000 requests Finished 1 requests Server Software:AOLserver/4.0.7 Server Hostname:panoptic.com Server Port:80 Document Path: /test.php Document Length:23519 bytes Concurrency Level: 25 Time taken for tests: 30.294 seconds Complete requests: 1 Failed requests:3 (Connect: 0, Length: 3, Exceptions: 0) Broken pipe errors: 0 Total transferred: 236933670 bytes HTML transferred: 235213498 bytes Requests per second:330.10 [#/sec] (mean) Time per request: 75.73 [ms] (mean) Time per request: 3.03 [ms] (mean, across all concurrent requests) Transfer rate: 7821.14 [Kbytes/sec] received Connnection Times (ms) min mean[+/-sd] median max Connect:045 370.0 0 9012 Processing: 326 139.5 17 6325 Waiting:026 139.5 17 6325 Total: 371 398.6 17 9031 Percentage of the requests served within a certain time (ms) 50% 17 66% 18 75% 19 80% 21 90% 29 95% 33 98%355 99% 3022 100% 9031 (last request) PHP 4.3.7RC1 This failure rate is obviously not going to cut it for production use, and I was wondering if anyone had seen this before. Nothing in the server.log file during the failures; the access log shows that sometimes the request simply returned zero-length content. Thread stack-size has been set to 1M. Anyone seen this before? =) Hmm, in my test above, we see 3 failures out of 10,000 -- 0.03% -- is probably reasonable for a production site. Nothing emitted into the server log, nor the php4.log either. Let me crank up ab to -v99 and see if I can get the failures to happen again ... Failed requests:2 (Connect: 0, Length: 2, Exceptions: 0) OK, so it happened again. Looking at the log ... nothing enlightening. Lets ask Google. It knows everything ... Aha. OK -- those Length errors can *probably* be ignored -- ApacheBench registers a Length failure if the HTTP response length varies from the initial response, which it CAN do for the test.php page that calls phpinfo(), since the output can vary. Look in the PHP Variables section towards the bottom of the page at _SERVER[REMOTE_PORT] -- as it goes from to 1, the length of the document goes up by 1 byte causing a length failure. Same thing happens in the other direction, as it goes from 32000 back down to 1000-something. I agree with you, a true 6% failure rate is unacceptable. On my test environment, I'm seeing effectively a 0% failure rate. -- 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
[AOLSERVER] aolserver/php
So, in the interest of science (and probably masochism) I compiled PHP 4.3.8 (with the aolserver.c patch from panoptic) against aolserver 3.5.10 and 4.0.7 last night, and ran some load tests. Result: on linux 2.4.26, and the only PHP configure option was --with-aolserver=, I was seeing a failure rate of ~6% for a page that only called phpinfo(). Load test: /usr/sbin/ab2 -n10 -c25 http://localhost:8000/ (ab2 being the version of 'ab' that ships with apache2). This failure rate is obviously not going to cut it for production use, and I was wondering if anyone had seen this before. Nothing in the server.log file during the failures; the access log shows that sometimes the request simply returned zero-length content. Thread stack-size has been set to 1M. Anyone seen this before? =) Noah Robin System Administrator, America Online 703.265.2925 #include remarks/witty.h -- 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/php
I haven't been able to duplicate this. I see ab reporting some errors but according to the AOLserver logs it is doing the right thing. I have zero previous experience with ab though, so a lot of this is from the hip. Part of the problem may be that PHP isn't setting a content-length header and ab is getting confused. The length that it is reporting for me for a PHP 5.0.0 phpinfo command is less than the actual output (33292 by ab versus 33422 actual bytes). I set verbosity to 5 to log everything and the output seems truncated as well. My guess is that it logs just bit of data from the first read but I don't know for sure yet. For exceptions, I get Protocol driver not attached. Whether this is an AOLserver-caused problem or not I don't know yet. I think this maps to EADDRNOTAVAIL. It may essentially just be connection refused if aolserver ran out of connection threads. Even with smaller batches of requests it fails. I've been testing with 1000 requests and 20 threads and finding errors. Note that ab does some wierd stuff. If you request 1000 connections you'll get more like 1002. Seems it doesn't count very well. I tested with AOLserver 4.0.5, PHP 4.3.7 and PHP 5.0.0 on Linux 2.4.24. rob Noah Robin wrote: So, in the interest of science (and probably masochism) I compiled PHP 4.3.8 (with the aolserver.c patch from panoptic) against aolserver 3.5.10 and 4.0.7 last night, and ran some load tests. Result: on linux 2.4.26, and the only PHP configure option was --with-aolserver=, I was seeing a failure rate of ~6% for a page that only called phpinfo(). Load test: /usr/sbin/ab2 -n10 -c25 http://localhost:8000/ (ab2 being the version of 'ab' that ships with apache2). This failure rate is obviously not going to cut it for production use, and I was wondering if anyone had seen this before. Nothing in the server.log file during the failures; the access log shows that sometimes the request simply returned zero-length content. Thread stack-size has been set to 1M. Anyone seen this before? =) Noah Robin System Administrator, America Online 703.265.2925 #include remarks/witty.h -- 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/php
On 2004.07.23, Noah Robin [EMAIL PROTECTED] wrote: So, in the interest of science (and probably masochism) I compiled PHP 4.3.8 (with the aolserver.c patch from panoptic) against aolserver 3.5.10 and 4.0.7 last night, and ran some load tests. Result: on linux 2.4.26, and the only PHP configure option was --with-aolserver=, I was seeing a failure rate of ~6% for a page that only called phpinfo(). Load test: /usr/sbin/ab2 -n10 -c25 http://localhost:8000/ (ab2 being the version of 'ab' that ships with apache2). Lets see what I get on my system: $ uname -a Linux ecwav 2.6.5 #3 Thu May 6 06:57:14 EDT 2004 i686 GNU/Linux $ cat /proc/cpuinfo | grep model name model name : Intel(R) Pentium(R) III CPU family 1266MHz $ cat test.php ? phpinfo(); ? $ ab -c25 -n1 http://panoptic.com/test.php This is ApacheBench, Version 1.3d $Revision: 1.67 $ apache-1.3 Copyright (c) 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ Copyright (c) 1998-2002 The Apache Software Foundation, http://www.apache.org/ Benchmarking panoptic.com (be patient) Completed 1000 requests Completed 2000 requests Completed 3000 requests Completed 4000 requests Completed 5000 requests Completed 6000 requests Completed 7000 requests Completed 8000 requests Completed 9000 requests Finished 1 requests Server Software:AOLserver/4.0.7 Server Hostname:panoptic.com Server Port:80 Document Path: /test.php Document Length:23519 bytes Concurrency Level: 25 Time taken for tests: 30.294 seconds Complete requests: 1 Failed requests:3 (Connect: 0, Length: 3, Exceptions: 0) Broken pipe errors: 0 Total transferred: 236933670 bytes HTML transferred: 235213498 bytes Requests per second:330.10 [#/sec] (mean) Time per request: 75.73 [ms] (mean) Time per request: 3.03 [ms] (mean, across all concurrent requests) Transfer rate: 7821.14 [Kbytes/sec] received Connnection Times (ms) min mean[+/-sd] median max Connect:045 370.0 0 9012 Processing: 326 139.5 17 6325 Waiting:026 139.5 17 6325 Total: 371 398.6 17 9031 Percentage of the requests served within a certain time (ms) 50% 17 66% 18 75% 19 80% 21 90% 29 95% 33 98%355 99% 3022 100% 9031 (last request) PHP 4.3.7RC1 This failure rate is obviously not going to cut it for production use, and I was wondering if anyone had seen this before. Nothing in the server.log file during the failures; the access log shows that sometimes the request simply returned zero-length content. Thread stack-size has been set to 1M. Anyone seen this before? =) Hmm, in my test above, we see 3 failures out of 10,000 -- 0.03% -- is probably reasonable for a production site. Nothing emitted into the server log, nor the php4.log either. Let me crank up ab to -v99 and see if I can get the failures to happen again ... Failed requests:2 (Connect: 0, Length: 2, Exceptions: 0) OK, so it happened again. Looking at the log ... nothing enlightening. Lets ask Google. It knows everything ... Aha. OK -- those Length errors can *probably* be ignored -- ApacheBench registers a Length failure if the HTTP response length varies from the initial response, which it CAN do for the test.php page that calls phpinfo(), since the output can vary. Look in the PHP Variables section towards the bottom of the page at _SERVER[REMOTE_PORT] -- as it goes from to 1, the length of the document goes up by 1 byte causing a length failure. Same thing happens in the other direction, as it goes from 32000 back down to 1000-something. I agree with you, a true 6% failure rate is unacceptable. On my test environment, I'm seeing effectively a 0% failure rate. -- 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] PHP security issue
I thought folks might be interested in this: http://security.e-matters.de/advisories/112004.html Rob Seeger -- 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] PHP and AOLserver Re: [AOLSERVER] ANN: New project leader for AOLserver
On Fri, May 21, 2004 at 11:10:31AM +0200, Dani?l Mantione wrote: On Fri, 21 May 2004, Bernd Eidenschink wrote: PHP works with AOLserver, at least some folks use it. I don't know how well maintained the bridge ist, nor if PHP can be compiled with 4.0, but supporting PHP would be absolutely no harm. I would think of it as the honeypot. It would allow people to use and maintain their (needed) PHP applications and let them eventually get used to TCL. EXACTLY. Yes, but it does not make sense. Why would you run AOLserver if you want to run PHP-scripts? Even I run them on Apache. Supporting PHP might sound There are some good reasons. E.g., some OpenACS users are running PHP in AOLserver solely in order to run some webmail app which happens to be written in PHP. I don't remember whether they did so or not, but by running it inside AOLserver, they should be able to integrate its login and authentication with that of their OpenACS website. http://openacs.org/doc/current/install-squirrelmail.html http://openacs.org/forums/message-view?message_id=155447 http://openacs.org/forums/message-view?message_id=158125 http://openacs.org/forums/message-view?message_id=85405 comfortable to people, and it'll definately help them to run their legacy scripts, but it is not what AOLserver is about. AOLserver can only be used to it full potential if TCL is used. That's just not true. I'm sure the SMLserver guys thought they were using AOLserver to its full potential, and it lookes like they never touched any Tcl code at all, just Standard ML and C. Using Tcl is generally the simplest and easiest way to use AOLserver to its full potential. - that's probably true. The message to new users should be Yes. You have to switch to TCL, but, don't worry, we're sure you'll regret that you didn't do it before instead of Switch to AOLserver, it's easy and nothing has to change for you. No, VERY bad idea. No users HAVE to do anything, it is up to them. We're here merely to give learned and practical advice, point out alternate and better ways to solve problems, etc. AOLserver is very powerful and very flexible, this gives you the freedom to do what you want. Personally I think Tcl is, overall, a fabulous language, and it's tight integration with AOLserver make both even better. But others, perhaps out of ignorance, don't share that view. If a whole bunch of PHP users suddenly appear, start using AOLserver, and never touch Tcl at all, that would be just fine! Once they're committed to using AOLserver at all, some of them will no doubt gradually join us in the more traditional world of AOLserver Tcl, ADP, and C code. But if they don't, cool, that's still fine. And leaving all those theoretical new PHP users aside, strong Java, PHP, and whatever support is a good thing for *ME*. Not because I have any particular plans to use Java or PHP - I don't. But AOLserver is one of my favorite tools, and all else being equal, the more problems I can potentially apply it to, the better. E.g., I'm told that TagSoup happens to be the best available parser library for messy real-world HTML, and it happens to be written in Java. If I needed to, I could probably run that in AOLserver, and that gives me warm fuzzy feelings. http://sourceforge.net/projects/tagsoup/ Similarly, I LIKE the fact that Standard ML and Python, to at least some degree, are both integrated with AOLserver. I've idly thought about looking into the doing the same for Erlang. -- 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] aolserver + php
On Fri, Jun 06, 2003 at 06:38:45AM -0700, Patrick Spence wrote: - 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 FreeBSD 5.0-RELEASE it is. And php works fine, if I don't use mysql functions from it. Seems I've got to send a bug report to php.net ;) -- 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
Micha Nasiadka wrote: 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 FreeBSD 5.0-RELEASE it is. And php works fine, if I don't use mysql functions from it. Seems I've got to send a bug report to php.net ;) Just a quick thought. Perhaps do a ldd on mysql.so in php, libphp4.so and libmysqlclient (the one used in mysql.so). -- WK -- 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
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 + 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] 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/
[AOLSERVER] php under aolserver...
How exactly does PHP run under AOLserver? I understand it can run as a module instead of just CGI, but does anyone know the gory details? Is there a PHP engine loaded per thread? Is it pre-loaded or is it loaded when a PHP script is hit? (should this be directed to the php-dev list?) -- Gabriel Ricard [EMAIL PROTECTED]
[AOLSERVER] php + aolserver
Hi, I'm trying to get php to work with aolserver . I am using aolserver3.3ad13-oacs1-beta-src.tar.gz and php-4.2.2 I configured php like this: ./configure --with-aolserver=/usr/local/aolserver \ --with-aolserver-src=/usr/local/src/oacs/aolserver \ --with-pgsql=/usr/local/pgsql \ --without-mysql the whole thing went well and I did a 'make install' and that went well also. but the 2 apps don't talk to each other. Don't I have to put the .so file in aolserver's lib folder? where do I get that?
Re: [AOLSERVER] php + aolserver (is it stable?)
Whenever I think about php + aolserver, I am struck by what I've seen in the past. Comments at the php sites that php + aolserver isn't stable or ready for production. Am I confused about this? Also, do php programs embedded within aolserver benefit from: A) aolserver's db connection pooling? B) aolserver's multithreaded model? C) ??? Due to the stability issues, I haven't seen much value in adding php to aolserver, and not just letting apache and aolserver run side by side with apache hosting php. ??? Thanks, Jerry
Re: [AOLSERVER] php + aolserver (is it stable?)
- Original Message - From: Sean Redmond [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, August 30, 2002 11:00 AM Subject: Re: [AOLSERVER] php + aolserver (is it stable?) It works fine almost all the time. I originally had this setup because we were using the same server (we only had one!) to try out openacs and to serve webmail, for which we were using SquirrelMail (written in PHP). Sometimes threads would hang -- it seemed that if users had inboxes with too many (i.e. thousands) of messages, php would time out, as its designed to do, but the aolserver thread wouldn't die, and enough hung threads would hang (but not crash) aolserver. It was nothing too terrible, so we just set a cron job to periodically restart the server to clear all the threads out before they got to that critical level. When we upgraded to RedHat 6.2 to 7.2, something in the webmail script that displayed the contents of the inbox consistently crashed aolserver. I've never been able to track it down, nor have I seen the problem with anything else. You can look at the bug (http://bugs.php.net/bug.php?id=14365) if you are interested. Now we have more servers so we use apache for webmail and aolserver for everything else (though no PHP except for webmail). So I wouldn't recommend it, and there certainly isn't any benefit, but if you have to use it, it will probably work. Unless it's SquirrelMail on a RedHat 7.* box -- that definitely will not work! Or a couple different forum packages.. they do the same thing.. takes AS down hard and fast.. really annoying. I am experimenting with PHP on Aolserver though simply due to the support by DreamWeaver MX via the phrakt extension for easy and rapid development of database applications. -- Patrick Spence arivenATarivenDOTcom www.RandomRamblings.com www.Ariven.com
Re: [AOLSERVER] [[AOLSERVER] PHP?]
I can give you a confidence-builder. Some AOLserver architects have been following the PHP discussions and helping them out with their AOLserver module--which comes with PHP, by the way. Kris On Tue, 2 Apr 2002 14:53:00 -0700, Ron Patterson [EMAIL PROTECTED] wrote: Been using it fine here, though not pushing it real hard. Using it on both Solaris 2.6 and Mandrake-Linux platforms with PostgreSQL, MySQL, Oracle8, and ODBC database access. Ron Michael Roberts [EMAIL PROTECTED] wrote: Has anyone used PHP under AOLserver? I'm not expecting anything like a tight integration, just have some code written for PHP that I'd like to expose on a site already running AOLserver. Any comments or try starting here would be welcome. Michael === Ron Patterson | USA.NET [EMAIL PROTECTED] | 1155 Kelly Johnson Blvd 719-785-2328 | Colorado Springs, CO 80920 AOL/Yahoo IM: RonPDude |
[AOLSERVER] PHP?
Has anyone used PHP under AOLserver? I'm not expecting anything like a tight integration, just have some code written for PHP that I'd like to expose on a site already running AOLserver. Any comments or try starting here would be welcome. Michael
Re: [AOLSERVER] PHP?
I have it running - It was pretty easy. Just follow the instructions in
the PHP install doc.
Build and edit yr conf.
I have the following
# php section
ns_param php ${bindir}/libphp4.so
ns_section ns/server/${servername}/module/php
ns_param map *.php
ns_param php_value session.auto_start 1
-Simon
-Original Message-
From: AOLserver Discussion [mailto:[EMAIL PROTECTED]] On Behalf
Of Michael Roberts
Sent: Tuesday, April 02, 2002 11:36 AM
To: [EMAIL PROTECTED]
Subject: [AOLSERVER] PHP?
Has anyone used PHP under AOLserver? I'm not expecting anything like a
tight integration, just have some code written for PHP that I'd like to
expose on a site already running AOLserver. Any comments or try
starting here would be welcome.
Michael
Re: [AOLSERVER] PHP?
I have it running - It was pretty easy. Do you know if the thread-safety issues have been solved? Has the module been stable for you? -- C. R. Oldham Director of Technology NCA Commission on Accreditation and School Improvement [EMAIL PROTECTED] V:800-525-9517 F:480-965-9423
Re: [AOLSERVER] [[AOLSERVER] PHP?]
Been using it fine here, though not pushing it real hard. Using it on both Solaris 2.6 and Mandrake-Linux platforms with PostgreSQL, MySQL, Oracle8, and ODBC database access. Ron Michael Roberts [EMAIL PROTECTED] wrote: Has anyone used PHP under AOLserver? I'm not expecting anything like a tight integration, just have some code written for PHP that I'd like to expose on a site already running AOLserver. Any comments or try starting here would be welcome. Michael === Ron Patterson | USA.NET [EMAIL PROTECTED] | 1155 Kelly Johnson Blvd 719-785-2328 | Colorado Springs, CO 80920 AOL/Yahoo IM: RonPDude |
Re: [AOLSERVER] PHP?
I've built it before (a while back) so that part doesn't scare me. But somehow I'd forgotten that it is a scripting language, not a webserver, and so I was pleasantly surprised to realize today that I can keep my AOLserver platform and still use this code. The conf info was *exactly* what I was looking for; thanks! Michael Simon Gibson wrote: I have it running - It was pretty easy. Just follow the instructions in the PHP install doc.
Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
Scott, I've been using this Aolserver 3.0 + PHP 4.0.6 for over a year with no problem -- this is new (mis)behavior. In what I'm trying to setup now, the PHP version is the same, but I'm trying to use new versions of Aolserver (3.4.2) and RedHat (7.2, old server has 6.2). I cannot think of any way that Aolserver is causing this problem for PHP, though. At 06:59 PM 11/26/2001 -0600, you wrote: Hi Sean, Is this something you can fix on your own? It's possible that the PHP module for AOLserver is doing this (i.e. it's building a path without checking for relative paths); I'm not sure as I've never used the module or PHP. /s. Sean Redmond Brooklyn Museum of Art
Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
I hate to say it, but drop back to 3.0 and test on RH 7.2. If it breaks, then there's something different in the combo between AOLserver and RedHat 7.2. If it works, then upgrade to AOLserver 3.1 and test, then 3.2 and test etc. until you get to 3.4.2, also on RedHat 7.2. Let's find out which upgrade breaks it. When it breaks, get a backtrace with GDB, then look at the sources where it breaks and see what's changed between the code that broke and the version before it. Frankly, I'm surprised that a bad path would cause a segfault, which leads me to believe that some var or pointer isn't being initialized before use. /s. Scott, I've been using this Aolserver 3.0 + PHP 4.0.6 for over a year with no problem -- this is new (mis)behavior. In what I'm trying to setup now, the PHP version is the same, but I'm trying to use new versions of Aolserver (3.4.2) and RedHat (7.2, old server has 6.2). I cannot think of any way that Aolserver is causing this problem for PHP, though. At 06:59 PM 11/26/2001 -0600, you wrote: Hi Sean, Is this something you can fix on your own? It's possible that the PHP module for AOLserver is doing this (i.e. it's building a path without checking for relative paths); I'm not sure as I've never used the module or PHP. /s. Sean Redmond Brooklyn Museum of Art
Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
At 11:24 AM 11/27/2001 -0500, Scott Goodwin wrote: I hate to say it, but drop back to 3.0 and test on RH 7.2. If it breaks, then there's something different in the combo between AOLserver and RedHat 7.2. Actually, I tried that and ran into the same problem. Sean Redmond Brooklyn Museum of Art
Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
Ok, then it sounds like an interaction problem between AOLserver and RedHat 7.2 (or more likely the PHP module and 7.2). Can you post the backtrace? /s. At 11:24 AM 11/27/2001 -0500, Scott Goodwin wrote: I hate to say it, but drop back to 3.0 and test on RH 7.2. If it breaks, then there's something different in the combo between AOLserver and RedHat 7.2. Actually, I tried that and ran into the same problem. Sean Redmond Brooklyn Museum of Art
Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
On 2001.11.27, Scott Goodwin [EMAIL PROTECTED] wrote: Frankly, I'm surprised that a bad path would cause a segfault, which leads me to believe that some var or pointer isn't being initialized before use. My WAG would be that this is some keep people from busting out of a chroot jail code that's busted. The path that PHP is trying to canonicalize is of the form ../ and a segfault on that smells fishy of things like this. RH6 to RH7 made the jump from libc5 to glibc2, right? Hmm... -- 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)
Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
At 12:22 PM 11/27/2001 -0500, you wrote: On 2001.11.27, Scott Goodwin [EMAIL PROTECTED] wrote: Frankly, I'm surprised that a bad path would cause a segfault, which leads me to believe that some var or pointer isn't being initialized before use. My WAG would be that this is some keep people from busting out of a chroot jail code that's busted. The path that PHP is trying to canonicalize is of the form ../ and a segfault on that smells fishy of things like this. RH6 to RH7 made the jump from libc5 to glibc2, right? Hmm... -- Dossy This is what worries me since the same segfault happens with 3.0 and 3.4.2. However, I can't believe I'm the ONLY person in the world trying to install this combination. They're pretty much the same but here are the stack traces for both versions of Aolserver: Aolserver 3.0 -- Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 4101 (LWP 17152)] 0x400afdd3 in canonicalize ( name=0x8396940 /usr/local/aolserver-3.0/servers/webmail/pages/squirrelmail-1.2.0-rc2/src/../src/load_prefs.php, resolved=0x403bc12c ) at canonicalize.c:88 88 canonicalize.c: No such file or directory. in canonicalize.c (gdb) bt #0 0x400afdd3 in canonicalize ( name=0x8396940 /usr/local/aolserver-3.0/servers/webmail/pages/squirrelmail-1.2.0-rc2/src/../src/load_prefs.php, resolved=0x403bc12c ) at canonicalize.c:88 #1 0x40291659 in virtual_file_ex (state=0x403bd164, path=0x8226f54 ../src/load_prefs.php, verify_path=0) at tsrm_virtual_cwd.c:299 #2 0x4020abcc in expand_filepath (filepath=0x8226f54 ../src/load_prefs.php, real_path=0x0) at fopen_wrappers.c:531 #3 0x4020a23f in php_fopen_and_set_opened_path ( path=0x8226f54 ../src/load_prefs.php, mode=0x402a5c47 rb, opened_path=0x403bf3e4) at fopen_wrappers.c:237 #4 0x4020a859 in php_fopen_with_path ( filename=0x8226f54 ../src/load_prefs.php, mode=0x402a5c47 rb, path=0x402a707b .:/usr/local/lib/php, opened_path=0x403bf3e4) at fopen_wrappers.c:391 #5 0x4020aa88 in php_fopen_url_wrapper ( path=0x8226f54 ../src/load_prefs.php, mode=0x402a5c47 rb, options=1, issock=0x403bf2b0, socketd=0x403bf2b4, opened_path=0x403bf3e4) at fopen_wrappers.c:470 #6 0x40208481 in php_fopen_wrapper_for_zend ( filename=0x8226f54 ../src/load_prefs.php, opened_path=0x403bf3e4) at main.c:477 #7 0x401ffd7e in open_file_for_scanning () from /usr/local/aolserver-3.0/bin/libphp4.so #8 0x40200124 in compile_file () from /usr/local/aolserver-3.0/bin/libphp4.so #9 0x402002c4 in compile_filename () from /usr/local/aolserver-3.0/bin/libphp4.so #10 0x401eac66 in execute (op_array=0x81de830, executor_globals=0x81a5bd0) at ./zend_execute.c:2028 #11 0x401e89f3 in execute (op_array=0x82c5b20, executor_globals=0x81a5bd0) at ./zend_execute.c:1544 #12 0x401e89f3 in execute (op_array=0x82c5100, executor_globals=0x81a5bd0) at ./zend_execute.c:1544 #13 0x401e89f3 in execute (op_array=0x82c24c0, executor_globals=0x81a5bd0) at ./zend_execute.c:1544 #14 0x401e89f3 in execute (op_array=0x816b74c, executor_globals=0x81a5bd0) at ./zend_execute.c:1544 #15 0x401f6dbd in zend_execute_scripts (type=8, compiler_globals=0x8161868, executor_globals=0x81a5bd0, file_count=3) at zend.c:752 #16 0x40209967 in php_execute_script (primary_file=0x403cb6fc, compiler_globals=0x8161868, executor_globals=0x81a5bd0, core_globals=0x81644b0) at main.c:1206 #17 0x40207732 in php_ns_module_main (ns_context=0x8165340, sapi_globals=0x816cd08) at aolserver.c:434 #18 0x4020797f in php_ns_request_handler (context=0x8119450, conn=0x812a308) at aolserver.c:519 #19 0x08070c63 in Ns_ConnRunRequest (conn=0x812a308) at op.c:196 #20 0x08076dbe in ConnRun (connPtr=0x812a308) at serv.c:755 #21 0x08076745 in NsConnThread (arg=0x81b1728) at serv.c:554 #22 0x080c8430 in NsThreadMain (arg=0x82420f0) at thread.c:226 #23 0x4002ec6f in pthread_start_thread (arg=0x403cbbe0) at manager.c:284 #24 0x4002ed5f in pthread_start_thread_event (arg=0x403cbbe0) at manager.c:308 Aolserver 3.4.2 -- [New Thread 5126 (LWP 12186)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 5126 (LWP 12186)] 0x4013fa38 in ___lxstat64 (vers=3, name=0x403cd01c /usr, buf=0x403ce04c) at ../sysdeps/unix/sysv/linux/lxstat64.c:52 52 ../sysdeps/unix/sysv/linux/lxstat64.c: No such file or directory. in ../sysdeps/unix/sysv/linux/lxstat64.c (gdb) bt #0 0x4013fa38 in ___lxstat64 (vers=3, name=0x403cd01c /usr, buf=0x403ce04c) at ../sysdeps/unix/sysv/linux/lxstat64.c:52 #1 0x400afb7c in canonicalize ( name=0x8280b90 /usr/local/aolserver-3.4.2/servers/webmail/pages/squirrelmail-1.2.0-rc2/src/../src/load_prefs.php, resolved=0x403ce10c ) at canonicalize.c:150 #2 0x402cd659 in virtual_file_ex (state=0x403cf13c, path=0x83d3704
Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
On Tuesday 27 November 2001 12:22 pm, Dossy wrote: On 2001.11.27, Scott Goodwin [EMAIL PROTECTED] wrote: Frankly, I'm surprised that a bad path would cause a segfault, which leads me to believe that some var or pointer isn't being initialized before use. My WAG would be that this is some keep people from busting out of a chroot jail code that's busted. The path that PHP is trying to canonicalize is of the form ../ and a segfault on that smells fishy of things like this. RH6 to RH7 made the jump from libc5 to glibc2, right? Hmm... No. RH6 = glibc 2.1 RH7= glibc 2.2 -- 7.1 and 7.2 are kernel 2.4. The last Red Hat with libc5 was 4.2. Red Hat 5.0 did the libc5-glibc 2.0 upgrade. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11
Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
On 2001.11.27, Sean Redmond [EMAIL PROTECTED] wrote: 0x400afdd3 in canonicalize ( name=0x8396940 /usr/local/aolserver-3.0/servers/webmail/pages/squirrelmail-1.2.0-rc2/src/../src/load_prefs.php, resolved=0x403bc12c ) at canonicalize.c:88 88 canonicalize.c: No such file or directory. in canonicalize.c Could you add the directory containing the PHP source to your gdb init, as well, and send that backtrace? I'm guessing that's where canonicalize.c lives, and it'd be interesting to see what line 88 is actually doing that causes the segfault ... (gdb) bt #0 0x4013fa38 in ___lxstat64 (vers=3, name=0x403cd01c /usr, buf=0x403ce04c) at ../sysdeps/unix/sysv/linux/lxstat64.c:52 This is a little more telling. I wonder where *buf points to ... which we'd know looking at canonicalize.c ... -- 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)
Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
At 01:22 PM 11/27/2001 -0500, you wrote: Could you add the directory containing the PHP source to your gdb init, as well, and send that backtrace? I'm guessing that's where canonicalize.c lives, and it'd be interesting to see what line 88 is actually doing that causes the segfault ... I did (tsrm_virtual_cwd.c, for instance, is part of PHP) but but there is no file called canonicalize.c on my system. Is it built into gcc or something? It seems to be part of stdlib. BTW, if I build PHP with --enable-debug Aolserver crashes on startup: [27/Nov/2001:12:12:42][14963.1024][-main-] Warning: modload: failed to load '/usr/local/aolserver/bin/libphp4.so': '/usr/local/aolserver/bin/libphp4.so: undefined symbol: tsrm_error' [27/Nov/2001:12:12:42][14963.1024][-main-] Fatal: modload: failed to load module '/usr/local/aolserver/bin/libphp4.so' Sean Redmond Brooklyn Museum of Art
Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
On 2001.11.27, Sean Redmond [EMAIL PROTECTED] wrote: At 01:22 PM 11/27/2001 -0500, you wrote: Could you add the directory containing the PHP source to your gdb init, as well, and send that backtrace? I'm guessing that's where canonicalize.c lives, and it'd be interesting to see what line 88 is actually doing that causes the segfault ... I did (tsrm_virtual_cwd.c, for instance, is part of PHP) but but there is no file called canonicalize.c on my system. Is it built into gcc or something? It seems to be part of stdlib. Against your AOLserver 3.0 and RH7 setup, could you re-run gdb and produce the crash, then type up then list as commands to gdb once it segfaults? Send that output. It may help us. -- 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)
Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
(gdb) up
#1 0x40291659 in virtual_file_ex (state=0x403ac164,
path=0x833a694 ../src/load_prefs.php, verify_path=0)
at tsrm_virtual_cwd.c:299
299 if (realpath(tmp, resolved_path)) {
(gdb) list
294 ptr += state-cwd_length;
295 *ptr++ = DEFAULT_SLASH;
296 memcpy(ptr, path, path_length);
297 ptr += path_length;
298 *ptr = '\0';
299 if (realpath(tmp, resolved_path)) {
300 path = resolved_path;
301 path_length = strlen(path);
302 }
303 free(tmp);
At 02:10 PM 11/27/2001 -0500, Dossy wrote:
Against your AOLserver 3.0 and RH7 setup, could you re-run gdb
and produce the crash, then type up then list as commands
to gdb once it segfaults?
Send that output. It may help us.
-- Dossy
Sean Redmond
Brooklyn Museum of Art
Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
Okay. Could you provide the source for the entire virtual_file_ex()
function from tsrm_virtual_cwd.c file?
-- Dossy
On 2001.11.27, Sean Redmond [EMAIL PROTECTED] wrote:
(gdb) up
#1 0x40291659 in virtual_file_ex (state=0x403ac164,
path=0x833a694 ../src/load_prefs.php, verify_path=0)
at tsrm_virtual_cwd.c:299
299 if (realpath(tmp, resolved_path)) {
(gdb) list
294 ptr += state-cwd_length;
295 *ptr++ = DEFAULT_SLASH;
296 memcpy(ptr, path, path_length);
297 ptr += path_length;
298 *ptr = '\0';
299 if (realpath(tmp, resolved_path)) {
300 path = resolved_path;
301 path_length = strlen(path);
302 }
303 free(tmp);
At 02:10 PM 11/27/2001 -0500, Dossy wrote:
Against your AOLserver 3.0 and RH7 setup, could you re-run gdb
and produce the crash, then type up then list as commands
to gdb once it segfaults?
Send that output. It may help us.
-- Dossy
Sean Redmond
Brooklyn Museum of Art
--
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)
Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
My next suggestion will require learning a bit of gdb, but
I'd try setting a breakpoint on line 298, and when it stops
I'd inspect what's actually contained in *tmp.
Why they built *ptr (and thus, *tmp) the way they did
baffles me, too.
One suggestion, delete line 287 (I think) which I'm marking
with *** :
} else { /* Concat current directory with relative path and then run
realpath() on it */
char *tmp;
char *ptr; *** THIS LINE ***
The locally scoped *ptr masks the *ptr defined at the
function scope (char *ptr, *path_copy;) ... I don't
think this is the culprit, but who knows. Removing line
287's definition shouldn't cause any additional problems
after reading the code.
Try making this small change, and recompiling the PHP
module, and see what happens.
-- Dossy
On 2001.11.27, Sean Redmond [EMAIL PROTECTED] wrote:
Here it is (marked line 299 with )
/* Resolve path relatively to state and put the real path into state */
/* returns 0 for ok, 1 for error */
CWD_API int virtual_file_ex(cwd_state *state, const char *path,
verify_path_func verify_path)
{
int path_length = strlen(path);
char *ptr, *path_copy;
char *tok = NULL;
int ptr_length;
cwd_state *old_state;
int ret = 0;
int copy_amount = -1;
char *free_path;
unsigned char is_absolute = 0;
#ifndef TSRM_WIN32
char resolved_path[MAXPATHLEN];
#endif
if (path_length == 0)
return (0);
#if !defined(TSRM_WIN32) !defined(__BEOS__)
if (IS_ABSOLUTE_PATH(path, path_length)) {
if (realpath(path, resolved_path)) {
path = resolved_path;
path_length = strlen(path);
}
} else { /* Concat current directory with relative path and then
run realpath() on it */
char *tmp;
char *ptr;
ptr = tmp = (char *)
malloc(state-cwd_length+path_length+sizeof(/));
if (!tmp) {
return 1;
}
memcpy(ptr, state-cwd, state-cwd_length);
ptr += state-cwd_length;
*ptr++ = DEFAULT_SLASH;
memcpy(ptr, path, path_length);
ptr += path_length;
*ptr = '\0';
if (realpath(tmp, resolved_path)) { //
path = resolved_path;
path_length = strlen(path);
}
free(tmp);
}
#endif
free_path = path_copy = tsrm_strndup(path, path_length);
old_state = (cwd_state *) malloc(sizeof(cwd_state));
CWD_STATE_COPY(old_state, state);
#if VIRTUAL_CWD_DEBUG
fprintf(stderr,cwd = %s path = %s\n, state-cwd, path);
#endif
if (IS_ABSOLUTE_PATH(path_copy, path_length)) {
copy_amount = COPY_WHEN_ABSOLUTE;
is_absolute = 1;
#ifdef TSRM_WIN32
} else if (IS_UNC_PATH(path_copy, path_length)) {
copy_amount = 1;
is_absolute = 1;
} else if (IS_SLASH(path_copy[0])) {
copy_amount = 2;
#endif
}
if (copy_amount != -1) {
state-cwd = (char *) realloc(state-cwd, copy_amount + 1);
if (copy_amount) {
if (is_absolute) {
memcpy(state-cwd, path_copy, copy_amount);
path_copy += copy_amount;
} else {
memcpy(state-cwd, old_state-cwd,
copy_amount);
}
}
state-cwd[copy_amount] = '\0';
state-cwd_length = copy_amount;
}
ptr = tsrm_strtok_r(path_copy, TOKENIZER_STRING, tok);
while (ptr) {
ptr_length = strlen(ptr);
if (IS_DIRECTORY_UP(ptr, ptr_length)) {
char save;
save = DEFAULT_SLASH;
#define PREVIOUS state-cwd[state-cwd_length - 1]
while (IS_ABSOLUTE_PATH(state-cwd,
state-cwd_length)
!IS_SLASH(PREVIOUS)) {
save = PREVIOUS;
PREVIOUS = '\0';
state-cwd_length--;
}
if (!IS_ABSOLUTE_PATH(state-cwd,
state-cwd_length)) {
state-cwd[state-cwd_length++] = save;
state-cwd[state-cwd_length] = '\0';
} else {
PREVIOUS = '\0';
state-cwd_length--;
}
} else if (!IS_DIRECTORY_CURRENT(ptr, ptr_length)) {
[AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
Hello, No one seems to want to touch this, not on the Aolserver list, not on the PHP list, not on the SquirrelMail list. However, I'm going to try again. On a server running RedHat Linux 7.2, I've got Aolserver 3.4.2 compiled and working fine, and PHP 4.0.6 compiled as a module and working fine except when it segfaults. It occurs consistently when loading SquirrelMail's (1.2.0-rc2) src/right_main.php, though I think the problem is really in the called function sqi_mailbox_list from functions/imap_mailbox.php. Exactly what the server is trying to do when it crashes I haven't yet figured out. The PHP source distribution warns about trouble with multi-threaded servers, but the suggested workaround, removing a line of code, refers to a line that no longer appears to be in the code anyway. Has anyone had a similar problem? Can anyone help me solve this problem or debug it more accurately? I currently have Aolserver 3.0, SquirrelMail 1.0.6, and PHP 4.0.6 running with no problems on another server under RedHat 6.2 (I'm trying to migrate our webmail onto a new machine) so this is very frustrating. Thanks. Sean Redmond Brooklyn Museum of Art
Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
At 03:27 PM 11/26/2001 -0500, you wrote: Hi Sean, have you run AOLserver under GDB yet to find out where it is segfaulting? Here's an example of how to do that. Thanks. It is happening when in the PHP statement include ../src/load_prefs.php; The relative path is expanded to /usr/local/aolserver-3.4.2/servers/webmail/pages/squirrelmail-1.2.0-rc2/src/../src/load_prefs.php instead of: /usr/local/aolserver-3.4.2/servers/webmail/pages/squirrelmail-1.2.0-rc2/src/load_prefs.php I.e the .. is not treated correctly. It seems to be PHP's fault. here is the relevant output of gdb: [New Thread 6151 (LWP 26839)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 6151 (LWP 26839)] 0x400afdd3 in canonicalize ( name=0x4083b278 /usr/local/aolserver-3.4.2/servers/webmail/pages/squirrelmail-1.2.0-rc2/src/../src/load_prefs.php, resolved=0x4053414c ) at canonicalize.c:88 88 canonicalize.c: No such file or directory. in canonicalize.c (gdb) bt #0 0x400afdd3 in canonicalize ( name=0x4083b278 /usr/local/aolserver-3.4.2/servers/webmail/pages/squirrelmail-1.2.0-rc2/src/../src/load_prefs.php, resolved=0x4053414c ) at canonicalize.c:88 #1 0x402be679 in virtual_file_ex (state=0x40535184, path=0x40665cd4 ../src/load_prefs.php, verify_path=0) at tsrm_virtual_cwd.c:299 #2 0x402423cc in expand_filepath ( filepath=0x40665cd4 ../src/load_prefs.php, real_path=0x0) at fopen_wrappers.c:531 #3 0x40241a3f in php_fopen_and_set_opened_path ( path=0x40665cd4 ../src/load_prefs.php, mode=0x402d2627 rb, opened_path=0x405373b4) at fopen_wrappers.c:237 #4 0x40242059 in php_fopen_with_path ( filename=0x40665cd4 ../src/load_prefs.php, mode=0x402d2627 rb, path=0x8178b38 .:/usr/local/lib/php:/home/aol30/webmail/pages/webmail/src, opened_path=0x405373b4) at fopen_wrappers.c:391 #5 0x40242288 in php_fopen_url_wrapper ( path=0x40665cd4 ../src/load_prefs.php, mode=0x402d2627 rb, options=1, issock=0x405372d0, socketd=0x405372d4, opened_path=0x405373b4) at fopen_wrappers.c:470 #6 0x4023fc81 in php_fopen_wrapper_for_zend ( filename=0x40665cd4 ../src/load_prefs.php, opened_path=0x405373b4) at main.c:477 #7 0x40239074 in open_file_for_scanning (file_handle=0x405373ac, compiler_globals=0x40630900) at zend_language_scanner_cc.cc:2899 #8 0x402394ee in compile_file (file_handle=0x405373ac, type=2, compiler_globals=0x40630900) at zend_language_scanner_cc.cc:2966 #9 0x4023966b in compile_filename (type=2, filename=0x406d92bc, compiler_globals=0x40630900, executor_globals=0x4061f440) at zend_language_scanner_cc.cc:3022 #10 0x40224016 in execute (op_array=0x406be8d0, executor_globals=0x4061f440) at ./zend_execute.c:2028 #11 0x40221da3 in execute (op_array=0x40774028, executor_globals=0x4061f440) at ./zend_execute.c:1544 #12 0x40221da3 in execute (op_array=0x407721a0, executor_globals=0x4061f440) at ./zend_execute.c:1544 #13 0x40221da3 in execute (op_array=0x4075b340, executor_globals=0x4061f440) at ./zend_execute.c:1544 #14 0x40221da3 in execute (op_array=0x40643c3c, executor_globals=0x4061f440) at ./zend_execute.c:1544 #15 0x4023016d in zend_execute_scripts (type=8, compiler_globals=0x40630900, executor_globals=0x4061f440, file_count=3) at zend.c:752 #16 0x40241167 in php_execute_script (primary_file=0x405436cc, compiler_globals=0x40630900, executor_globals=0x4061f440, core_globals=0x4061f740) at main.c:1206 #17 0x4023ef32 in php_ns_module_main (ns_context=0x40625bb0, sapi_globals=0x40632968) at aolserver.c:434 #18 0x4023f17f in php_ns_request_handler (context=0x8187c08, conn=0x819dc60) at aolserver.c:519 #19 0x08077bb7 in Ns_ConnRunRequest (conn=0x819dc60) at op.c:196 #20 0x0807e2c2 in ConnRun (connPtr=0x819dc60) at serv.c:882 #21 0x0807dc10 in NsConnThread (arg=0x40604300) at serv.c:671 #22 0x0811833b in NsThreadMain (arg=0x40604310) at thread.c:228 #23 0x4002ec6f in pthread_start_thread (arg=0x40543be0) at manager.c:284 #24 0x4002ed5f in pthread_start_thread_event (arg=0x40543be0) at manager.c:308 Sean Redmond Brooklyn Museum of Art
Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
Hi Sean, Is this something you can fix on your own? It's possible that the PHP module for AOLserver is doing this (i.e. it's building a path without checking for relative paths); I'm not sure as I've never used the module or PHP. /s. -+-+-+-+-+-+-+-+-+-+-+-+- If to err is human, I must be more human than most. Scott S. Goodwin u: http://scottg.net e: [EMAIL PROTECTED] p: 850.897.6830 aim: scottgnet - Original Message - From: Sean Redmond [EMAIL PROTECTED] To: AOLserver Discussion [EMAIL PROTECTED] Sent: Monday, November 26, 2001 4:06 PM Subject: Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail At 03:27 PM 11/26/2001 -0500, you wrote: Hi Sean, have you run AOLserver under GDB yet to find out where it is segfaulting? Here's an example of how to do that. Thanks. It is happening when in the PHP statement include ../src/load_prefs.php; The relative path is expanded to /usr/local/aolserver-3.4.2/servers/webmail/pages/squirrelmail-1.2.0-rc2/src/ ../src/load_prefs.php instead of: /usr/local/aolserver-3.4.2/servers/webmail/pages/squirrelmail-1.2.0-rc2/src/ load_prefs.php I.e the .. is not treated correctly. It seems to be PHP's fault. here is the relevant output of gdb: [New Thread 6151 (LWP 26839)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 6151 (LWP 26839)] 0x400afdd3 in canonicalize ( name=0x4083b278 /usr/local/aolserver-3.4.2/servers/webmail/pages/squirrelmail-1.2.0-rc2/src /../src/load_prefs.php, resolved=0x4053414c ) at canonicalize.c:88 88 canonicalize.c: No such file or directory. in canonicalize.c (gdb) bt #0 0x400afdd3 in canonicalize ( name=0x4083b278 /usr/local/aolserver-3.4.2/servers/webmail/pages/squirrelmail-1.2.0-rc2/src /../src/load_prefs.php, resolved=0x4053414c ) at canonicalize.c:88 #1 0x402be679 in virtual_file_ex (state=0x40535184, path=0x40665cd4 ../src/load_prefs.php, verify_path=0) at tsrm_virtual_cwd.c:299 #2 0x402423cc in expand_filepath ( filepath=0x40665cd4 ../src/load_prefs.php, real_path=0x0) at fopen_wrappers.c:531 #3 0x40241a3f in php_fopen_and_set_opened_path ( path=0x40665cd4 ../src/load_prefs.php, mode=0x402d2627 rb, opened_path=0x405373b4) at fopen_wrappers.c:237 #4 0x40242059 in php_fopen_with_path ( filename=0x40665cd4 ../src/load_prefs.php, mode=0x402d2627 rb, path=0x8178b38 .:/usr/local/lib/php:/home/aol30/webmail/pages/webmail/src, opened_path=0x405373b4) at fopen_wrappers.c:391 #5 0x40242288 in php_fopen_url_wrapper ( path=0x40665cd4 ../src/load_prefs.php, mode=0x402d2627 rb, options=1, issock=0x405372d0, socketd=0x405372d4, opened_path=0x405373b4) at fopen_wrappers.c:470 #6 0x4023fc81 in php_fopen_wrapper_for_zend ( filename=0x40665cd4 ../src/load_prefs.php, opened_path=0x405373b4) at main.c:477 #7 0x40239074 in open_file_for_scanning (file_handle=0x405373ac, compiler_globals=0x40630900) at zend_language_scanner_cc.cc:2899 #8 0x402394ee in compile_file (file_handle=0x405373ac, type=2, compiler_globals=0x40630900) at zend_language_scanner_cc.cc:2966 #9 0x4023966b in compile_filename (type=2, filename=0x406d92bc, compiler_globals=0x40630900, executor_globals=0x4061f440) at zend_language_scanner_cc.cc:3022 #10 0x40224016 in execute (op_array=0x406be8d0, executor_globals=0x4061f440) at ./zend_execute.c:2028 #11 0x40221da3 in execute (op_array=0x40774028, executor_globals=0x4061f440) at ./zend_execute.c:1544 #12 0x40221da3 in execute (op_array=0x407721a0, executor_globals=0x4061f440) at ./zend_execute.c:1544 #13 0x40221da3 in execute (op_array=0x4075b340, executor_globals=0x4061f440) at ./zend_execute.c:1544 #14 0x40221da3 in execute (op_array=0x40643c3c, executor_globals=0x4061f440) at ./zend_execute.c:1544 #15 0x4023016d in zend_execute_scripts (type=8, compiler_globals=0x40630900, executor_globals=0x4061f440, file_count=3) at zend.c:752 #16 0x40241167 in php_execute_script (primary_file=0x405436cc, compiler_globals=0x40630900, executor_globals=0x4061f440, core_globals=0x4061f740) at main.c:1206 #17 0x4023ef32 in php_ns_module_main (ns_context=0x40625bb0, sapi_globals=0x40632968) at aolserver.c:434 #18 0x4023f17f in php_ns_request_handler (context=0x8187c08, conn=0x819dc60) at aolserver.c:519 #19 0x08077bb7 in Ns_ConnRunRequest (conn=0x819dc60) at op.c:196 #20 0x0807e2c2 in ConnRun (connPtr=0x819dc60) at serv.c:882 #21 0x0807dc10 in NsConnThread (arg=0x40604300) at serv.c:671 #22 0x0811833b in NsThreadMain (arg=0x40604310) at thread.c:228 #23 0x4002ec6f in pthread_start_thread (arg=0x40543be0) at manager.c:284 #24 0x4002ed5f in pthread_start_thread_event (arg=0x40543be0) at manager.c:308 Sean Redmond Brooklyn Museum of Art
Re: [AOLSERVER] Again, Segfault with Aolserver, PHP, SquirrelMail
Hi Sean, have you run AOLserver under GDB yet to find out where it is segfaulting? Here's an example of how to do that. Put this into a file called gdbinit, substituting the things in parens with something appropriate and adjusting pathnames: === BEGIN : CUT == directory /usr/local/src/aolserver directory /usr/local/src/(other source dir) directory /usr/local/src/(other source dir) set args -f -u (user) -g (group) -t /usr/local/aolserver/nsd.tcl -s (servername) run == END : CUT then run: gdb -x gdbinit /usr/local/bin/aolserver/bin/nsd After the process segfaults, type bt at the GDB prompt (bt = backtrace). This should give you the function, source code line # etc. of where the fault is occurring. /s. Hello, No one seems to want to touch this, not on the Aolserver list, not on the PHP list, not on the SquirrelMail list. However, I'm going to try again. On a server running RedHat Linux 7.2, I've got Aolserver 3.4.2 compiled and working fine, and PHP 4.0.6 compiled as a module and working fine except when it segfaults. It occurs consistently when loading SquirrelMail's (1.2.0-rc2) src/right_main.php, though I think the problem is really in the called function sqi_mailbox_list from functions/imap_mailbox.php. Exactly what the server is trying to do when it crashes I haven't yet figured out. The PHP source distribution warns about trouble with multi-threaded servers, but the suggested workaround, removing a line of code, refers to a line that no longer appears to be in the code anyway. Has anyone had a similar problem? Can anyone help me solve this problem or debug it more accurately? I currently have Aolserver 3.0, SquirrelMail 1.0.6, and PHP 4.0.6 running with no problems on another server under RedHat 6.2 (I'm trying to migrate our webmail onto a new machine) so this is very frustrating. Thanks. Sean Redmond Brooklyn Museum of Art
