Re: Proble by Build mod_perl as a DSO outside the Apache Source Treevia APXS
On Fri, 9 Nov 2001, SubbaReddy M wrote: Hello Gurus, please help me to get update for mod_perl. [...] PLEASE -don't- post any HTML mails on the list. We are humans here, not browsers.
Re: Proble by Build mod_perl as a DSO outside the Apache Source Tree via APXS
Sorry, my intention is to express the problem area. so that, expect the exact solution. Please, if you have solution, kindly respond or put on known one. I am eagrly, waiting for solution. Thank you, -SubbaReddy - Original Message - From: Mohit Agarwal [EMAIL PROTECTED] To: SubbaReddy M [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, November 09, 2001 12:21 AM Subject: Re: Proble by Build mod_perl as a DSO outside the Apache Source Tree via APXS On Fri, 9 Nov 2001, SubbaReddy M wrote: Hello Gurus, please help me to get update for mod_perl. [...] PLEASE -don't- post any HTML mails on the list. We are humans here, not browsers. ---BeginMessage--- Hello Gurus, please help me to get update for mod_perl. I have good run apache 1.3, which has got by default on Installing the Linux 6.2 (Redhat) Now I install perl 5.6.1 and To extend an already installed Apache with mod_perl I followed the steps in http://perl.apache.org/guide/install.html#Build_mod_perl_as_a_DSO_outside_ But, unable to access the apache httpd from browser ( http://192.168.1.235/ ). i.e., Build mod_perl as a DSO outside the Apache Source Tree via APXS This will build the DSO libperl.so outside the Apache source tree with the new Apache 1.3 support tool apxs and install it into the existing Apache hierarchy. When I checked log file of the httpd, seems something ERROR [root@qclinux /root]# tail /etc/log/httpd/error_log Apache/1.3.12 (Unix) (Red Hat/Linux) PHP/3.0.15 mod_perl/1.26 configured -- resuming normal operations configured -- resuming normal operations Size magic not implemented. When I tried from browser not any page and checked log file [root@qclinux /root]# tail /var/log/httpd/error_log [Fri Nov 9 07:16:44 2001] [notice] child pid 856 exit signal Segmentation fault (11) [Fri Nov 9 07:16:44 2001] [notice] child pid 855 exit signal Segmentation fault (11) [Fri Nov 9 07:16:45 2001] [notice] child pid 860 exit signal Segmentation fault (11) [Fri Nov 9 07:16:45 2001] [notice] child pid 859 exit signal Segmentation fault (11) Please, kindly give me suggestion to get on work mod_perl with existing Apache. because, it has some many loaded module. I am facing so many problem to get work with new apache + mod_perl. So I want to continue with existing Apache and new mod_perl environment. Thanks in advance. -SubbaReddy M ---End Message---
[input needed] mod_perl training and commercial support info
I want to create 2 more info pages on the mod_perl site: 1. mod_perl commercial support 2. mod_perl training companies Currently I have: com. support: a href=http://www.covalent.net/;Covalent Technologies/a training: a href=http://training.gbdirect.co.uk/courses/linux/customized_and_bespoke.html;GBdirect/a If your company fits into any of these plese send *me* the URL and a *short* description. Thanks. _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: Proble by Build mod_perl as a DSO outside the Apache Source Tree via APXS
When I tried from browser not any page and checked log file [root@qclinux /root]# tail /var/log/httpd/error_log [Fri Nov 9 07:16:44 2001] [notice] child pid 856 exit signal Segmentation fault (11) [Fri Nov 9 07:16:44 2001] [notice] child pid 855 exit signal Segmentation fault (11) [Fri Nov 9 07:16:45 2001] [notice] child pid 860 exit signal Segmentation fault (11) [Fri Nov 9 07:16:45 2001] [notice] child pid 859 exit signal Segmentation fault (11) Please, kindly give me suggestion to get on work mod_perl with existing Apache. because, it has some many loaded module. I am facing so many problem to get work with new apache + mod_perl. Since you have a segfault, we cannot help you until you send us the backtrace. See the SUPPORT file in your source distro which explains how to do that. _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: Proble by Build mod_perl as a DSO outside the Apache Source Tree via APXS
SubbaReddy M wrote: How can I get backtrace info to send you? If you want to solve your problem at least read the replies thoroughly and you will be all set. Here it is again. And DO NOT reply to me, but to the list. Since you have a segfault, we cannot help you until you send us the backtrace. See the SUPPORT file in your source distro which explains how to do that. _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: Proble by Build mod_perl as a DSO outside the Apache Source Tree via APXS
Oh, thank you very much hamptone, I am really waitinting for replies. This is type encouragement is require for new bies. thank you and let you know the progress. -SubbaReddy But, - Original Message - From: hamptone [EMAIL PROTECTED] To: SubbaReddy M [EMAIL PROTECTED] Sent: Friday, November 09, 2001 3:03 AM Subject: Re: Proble by Build mod_perl as a DSO outside the Apache Source Tree via APXS Try my tips for doing this at: www.hamptonandassociates.net/apache_tips.htm Good luck. - Original Message - From: SubbaReddy M [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 09, 2001 4:02 PM Subject: Proble by Build mod_perl as a DSO outside the Apache Source Tree via APXS Hello Gurus, please help me to get update for mod_perl. I have good run apache 1.3, which has got by default on Installing the Linux 6.2 (Redhat) Now I install perl 5.6.1 and To extend an already installed Apache with mod_perl I followed the steps in http://perl.apache.org/guide/install.html#Build_mod_perl_as_a_DSO_outside_ But, unable to access the apache httpd from browser ( http://192.168.1.235/ ). i.e., Build mod_perl as a DSO outside the Apache Source Tree via APXS This will build the DSO libperl.so outside the Apache source tree with the new Apache 1.3 support tool apxs and install it into the existing Apache hierarchy. When I checked log file of the httpd, seems something ERROR [root@qclinux /root]# tail /etc/log/httpd/error_log Apache/1.3.12 (Unix) (Red Hat/Linux) PHP/3.0.15 mod_perl/1.26 configured -- resuming normal operations configured -- resuming normal operations Size magic not implemented. When I tried from browser not any page and checked log file [root@qclinux /root]# tail /var/log/httpd/error_log [Fri Nov 9 07:16:44 2001] [notice] child pid 856 exit signal Segmentation fault (11) [Fri Nov 9 07:16:44 2001] [notice] child pid 855 exit signal Segmentation fault (11) [Fri Nov 9 07:16:45 2001] [notice] child pid 860 exit signal Segmentation fault (11) [Fri Nov 9 07:16:45 2001] [notice] child pid 859 exit signal Segmentation fault (11) Please, kindly give me suggestion to get on work mod_perl with existing Apache. because, it has some many loaded module. I am facing so many problem to get work with new apache + mod_perl. So I want to continue with existing Apache and new mod_perl environment. Thanks in advance. -SubbaReddy M
ProxyPass and DirectoryIndex
On port 80, I'm running a non-mod_perl httpd. On port 8001, I'm running a mod_perl httpd. Port 80 is ProxyPassing to port 8001 like this: RewriteRule ^/(.+)\.asp$ http://127.0.0.1:8001/$1.asp [p] The httpds have different DocumentRoots however, so if I visit http://mysite.com/ it will return a directory index rather than calling the index.asp file. My current solution is to touch index.asp in the port 80 DocumentRoot and have DirectoryIndex index.asp so that it knows to ProxyPass those requests. I'd have to touch index.asp manually for every directory, though. Is there a better way around this?
Re: ProxyPass and DirectoryIndex
On Fri, 9 Nov 2001, Philip Mak wrote: On port 80, I'm running a non-mod_perl httpd. On port 8001, I'm running a mod_perl httpd. Port 80 is ProxyPassing to port 8001 like this: RewriteRule ^/(.+)\.asp$ http://127.0.0.1:8001/$1.asp [p] The httpds have different DocumentRoots however, so if I visit http://mysite.com/ it will return a directory index rather than calling the index.asp file. My current solution is to touch index.asp in the port 80 DocumentRoot and have DirectoryIndex index.asp so that it knows to ProxyPass those requests. I'd have to touch index.asp manually for every directory, though. Is there a better way around this? Why do you use RewriteRule instead of ProxyPass ? ProxyPass/http://127.0.0.1:8081/ Or do you have static files that you don't want to pass to mod_perl ? You can try with my mod_accel: ftp://ftp.lexa.ru/pub/apache-rus/contrib/mod_accel-1.0.6.tar.gz It's replacement of mod_proxy. Documentation in Russian only. But you configuration is simple and can be following: AccelCacheRoot cache AccelNoCacheon AccelPass / http://127.0.0.1:8081/ AccelNoPass ~*\.jpg$ ~*\.gif$ It's Unix only. It can probably run on Win32 under CygWin - but I didn't try it. Igor Sysoev
Re: mod_dir DirectoryIndex vs. $r-uri() manipulation
* David Pisoni [EMAIL PROTECTED] wrote: Hello again modperlers, I am using perl 5.6.1 / Apache 1.3.20 / mod_perl 1.26. I have an interesting problem which maybe someone could shed some light on : I have an early phase handler (can be done as either a PerlPostReadRequestHandler or a PerlTransHandler) which manipulates the request URI. The purpose of the handler is to strip out the first segment of the URI path and employ that as a user type string. I presently have it as a TransHandler which returns DECLINED, expecting Apache to continue URI translation based on the new URI setting. For almost all types of URIs this functionality is working: it works for files in the DocumentRoot, it works for PerlHandlers declared in Location blocks, and it works for Alias mapped paths. Only one thing breaks... The one URI type which isn't resolved correctly is DirectoryIndex-resolved paths. If mod_autoindex is on, then an AutoIndex directory listing is displayed. If mod_autoindex is off, a NOT FOUND error is displayed. If I access the same directory without the URI manipulation (and without the extra user type segment), the DirectoryIndex-specified file is served as expected. I thought to myself, maybe the mod_dir resolution wants to be before any declared PerlTransHandler (even though mod_autoindex comes after) so I tried moving my handler to a PostReadRequestHandler. Same effect though -- something is short-circuiting the DirectoryIndex function of mod_dir. Anyone else encounter this? Any ideas how to resolve? Don't try to strip the uri in sub requests ($r-is_main()). --Nikolaus
Re: mod_dir DirectoryIndex vs. $r-uri() manipulation
* David Pisoni [EMAIL PROTECTED] wrote: Hello again modperlers, I am using perl 5.6.1 / Apache 1.3.20 / mod_perl 1.26. I have an interesting problem which maybe someone could shed some light on : I have an early phase handler (can be done as either a PerlPostReadRequestHandler or a PerlTransHandler) which manipulates the request URI. The purpose of the handler is to strip out the first segment of the URI path and employ that as a user type string. I presently have it as a TransHandler which returns DECLINED, expecting Apache to continue URI translation based on the new URI setting. For almost all types of URIs this functionality is working: it works for files in the DocumentRoot, it works for PerlHandlers declared in Location blocks, and it works for Alias mapped paths. Only one thing breaks... The one URI type which isn't resolved correctly is DirectoryIndex-resolved paths. If mod_autoindex is on, then an AutoIndex directory listing is displayed. If mod_autoindex is off, a NOT FOUND error is displayed. If I access the same directory without the URI manipulation (and without the extra user type segment), the DirectoryIndex-specified file is served as expected. I thought to myself, maybe the mod_dir resolution wants to be before any declared PerlTransHandler (even though mod_autoindex comes after) so I tried moving my handler to a PostReadRequestHandler. Same effect though -- something is short-circuiting the DirectoryIndex function of mod_dir. Anyone else encounter this? Any ideas how to resolve? Don't try to strip the uri in sub requests ($r-is_main()). --Nikolaus I don't. Indeed, if I did, other parts of the system would fail terribly. My handler begins with : return undef unless ($r-is_main()) and proceeds as described above. Thanks, David
[JOB] OpenInteract developer wanted
A company I've been working with asked me to post this job. You'd be working with a substantial (and growing!) OpenInteract system that I designed and built, which could be a plus or a minus depending on how you look at it :-) Feel free to ask me for details. Chris URL with full description: http://jobs.perl.org/job/97 Location: (USA) Pittsburgh, Pennsylvania Hours: Full-time, onsite Description: This position will join a team responsible for the development and maintenance of an interactive data management system for internal use. Position requires significant experience with intranet development using OpenInteract, HTML, Perl, SQL, and Apache/mod_perl. DB2 on AS/400 is also desired. Experience in a Win32 environment needed with possible Linux migration. Knowledge/Experience: BA/BS with minimum 4 years progressively responsible experience within administrative computing environment; demonstrated experience on a technical team; excellent analytical skills; detailed knowledge of database design and relational technology with demonstrable mastery Experience with OpenInteract, Template Toolkit, SQL, Perl and programmatically generated HTML very highly desired. Also: Apache/mod_perl administration, knowledge of MySQL and IBM DB2 on AS/400, C/C++, thin client or web driven applications development experience. Contact information: To apply or for information, send resume, salary requirements, references and a sample of your work (a small web-dbi script or something) to [EMAIL PROTECTED] No 3rd Parties please. Only US Citizens or authorized to Work for any employer in the US. P.S. Recruiters are 3rd parties, see above.
Re: ProxyPass and DirectoryIndex
On Fri, 9 Nov 2001, Philip Mak wrote: On port 80, I'm running a non-mod_perl httpd. On port 8001, I'm running a mod_perl httpd. Port 80 is ProxyPassing to port 8001 like this: RewriteRule ^/(.+)\.asp$ http://127.0.0.1:8001/$1.asp [p] The httpds have different DocumentRoots however, so if I visit http://mysite.com/ it will return a directory index rather than calling the index.asp file. My current solution is to touch index.asp in the port 80 DocumentRoot and have DirectoryIndex index.asp so that it knows to ProxyPass those requests. I'd have to touch index.asp manually for every directory, though. Is there a better way around this? How about: RewriteRule ^(.*)/$ http://127.0.0.1:8001$1/index.asp [p] -Balazs
Apache configuration
I've heard lots of people talking about doing Apache configuration via Perl sections and mod_perl, but I can't find any examples! I've looked on Sourceforge, the Guide, and dug through google. The Eagle book has the best stuff I've found so far, but it's hard for me to believe that noone has done anything with it since then. Any pointers? -- /chris Neither sweat, nor blood, nor frustration, or lousy manuals nor missing parts, or wrong parts shall keep me from my task.
Re: ProxyPass and DirectoryIndex
My current solution is to touch index.asp in the port 80 DocumentRoot and have DirectoryIndex index.asp so that it knows to ProxyPass those requests. I'd have to touch index.asp manually for every directory, though. Is there a better way around this? RewriteRule ^/$ http://127.0.0.1:8001/ [p] That would only pass the main directory; it won't take care of this problem for the subdirectories. Why do you use RewriteRule instead of ProxyPass ? ProxyPass/http://127.0.0.1:8081/ Or do you have static files that you don't want to pass to mod_perl ? I have static files that I don't want to pass to mod_perl. RewriteRule ^(.*)/$ http://127.0.0.1:8001$1/index.asp [p] That looks like it will ProxyPass every directory to the mod_perl enabled httpd. It would make index.html not work anymore, though. I think the optimal solution would: - display index.html if it is present in the non-mod_perl web directory - else display index.asp if it is present in the mod_perl web directory - else display a directory listing (if Options +Indexes is on) I'm thinking that this is not possible, at least not without having to make some really ugly configuration hack? You can try with my mod_accel: ftp://ftp.lexa.ru/pub/apache-rus/contrib/mod_accel-1.0.6.tar.gz AccelCacheRoot cache AccelNoCacheon AccelPass / http://127.0.0.1:8081/ AccelNoPass ~*\.jpg$ ~*\.gif$ Hmm, so that would pass any URL that doesn't end in .jpg or .gif. While not semantically equivalent to what I'm doing, I think it would actually work for my case (I just have to specify what extensions NOT to pass).
Re: Re: ProxyPass and DirectoryIndex
On Fri, Nov 09, 2001 at 02:17:44PM -0500, Philip Mak wrote:
RewriteRule ^(.*)/$ http://127.0.0.1:8001$1/index.asp [p]
That looks like it will ProxyPass every directory to the mod_perl enabled
httpd. It would make index.html not work anymore, though. I think the
optimal solution would:
- display index.html if it is present in the non-mod_perl web directory
- else display index.asp if it is present in the mod_perl web directory
- else display a directory listing (if Options +Indexes is on)
I'm thinking that this is not possible, at least not without having to
make some really ugly configuration hack?
How about this:
Directory /path/to/static/files/
RewriteCond%{REQUEST_FILENAME} -d
RewriteCond%{REQUEST_FILENAME}index.html!-f
RewriteCond/path/to/dynamic/files%{REQUEST_URI}/index.asp -f
RewriteRule^(.*)$ http://127.0.0.1:8001$1/index.asp [P]
/Directory
--
Andy [EMAIL PROTECTED] - http://anime.mikomi.org/ - Community Anime Reviews
And the moral of this message is...
To a Californian, all New Yorkers are cold; even in heat they rarely go
above fifty-eight degrees. If you collapse on a street in New York, plan
to spend a few days there.
-- From East vs. West: The War Between the Coasts
Re: ProxyPass and DirectoryIndex
Philip Mak [EMAIL PROTECTED] writes: My current solution is to touch index.asp in the port 80 DocumentRoot and have DirectoryIndex index.asp so that it knows to ProxyPass those requests. I'd have to touch index.asp manually for every directory, though. Is there a better way around this? To ease your task... I think there might be a better solution that does not involve this index.asp file, but I can't think of it now. == #!/bin/bash cd document_root for i in `find -type d` do cd $i touch index.asp cd - done == See you, -- Godoy. [EMAIL PROTECTED] Solutions Developer - Conectiva Inc. - http://en.conectiva.com Desenvolvedor de Soluções - Conectiva S.A. - http://www.conectiva.com.br msg22363/pgp0.pgp Description: PGP signature
Re: Apache configuration
On Fri, 9 Nov 2001, Christopher Hicks wrote: I've heard lots of people talking about doing Apache configuration via Perl sections and mod_perl, but I can't find any examples! I've looked on Sourceforge, the Guide, and dug through google. The Eagle book has the best stuff I've found so far, but it's hard for me to believe that noone has done anything with it since then. Any pointers? http://perl.apache.org/guide/config.html#Apache_Configuration_in_Perl Eagle book one is good, too.
Re: ProxyPass and DirectoryIndex
On Fri, 9 Nov 2001, Balazs Rauznitz wrote: On Fri, 9 Nov 2001, Philip Mak wrote: On port 80, I'm running a non-mod_perl httpd. On port 8001, I'm running a mod_perl httpd. Port 80 is ProxyPassing to port 8001 like this: RewriteRule ^/(.+)\.asp$ http://127.0.0.1:8001/$1.asp [p] The httpds have different DocumentRoots however, so if I visit http://mysite.com/ it will return a directory index rather than calling the index.asp file. My current solution is to touch index.asp in the port 80 DocumentRoot and have DirectoryIndex index.asp so that it knows to ProxyPass those requests. I'd have to touch index.asp manually for every directory, though. Is there a better way around this? How about: RewriteRule ^(.*)/$ http://127.0.0.1:8001$1/index.asp [p] In any case you need to double directory hierachy to allow mod_dir handle redirects from /dir to /dir/. Even without touching index.asp. Igor Sysoev
Re: ProxyPass and DirectoryIndex
On Fri, 9 Nov 2001, Philip Mak wrote: You can try with my mod_accel: ftp://ftp.lexa.ru/pub/apache-rus/contrib/mod_accel-1.0.6.tar.gz AccelCacheRoot cache AccelNoCacheon AccelPass / http://127.0.0.1:8081/ AccelNoPass ~*\.jpg$ ~*\.gif$ Hmm, so that would pass any URL that doesn't end in .jpg or .gif. While not semantically equivalent to what I'm doing, I think it would actually work for my case (I just have to specify what extensions NOT to pass). You can specify not only extension but any Apache regexp or location: AccelNoPass /some_static_location AccelNoPass /download ~*\.jpg$ ~*\.gif$ '*' after '~' means case-insensitive regexp. '~\.jpg$' is case-sensitive regexp. Also with mod_accel you will have other benefits - it allows to make a real backend buffering, to use busy locks and to limit connections to backend. Igor Sysoev
Re: [JOB] OpenInteract developer wanted
You can check on this link for required info: http://perl.apache.org/guide/ best of luck. -SubbaReddy - Original Message - From: Chris Winters [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, November 09, 2001 10:35 AM Subject: [JOB] OpenInteract developer wanted A company I've been working with asked me to post this job. You'd be working with a substantial (and growing!) OpenInteract system that I designed and built, which could be a plus or a minus depending on how you look at it :-) Feel free to ask me for details. Chris URL with full description: http://jobs.perl.org/job/97 Location: (USA) Pittsburgh, Pennsylvania Hours: Full-time, onsite Description: This position will join a team responsible for the development and maintenance of an interactive data management system for internal use. Position requires significant experience with intranet development using OpenInteract, HTML, Perl, SQL, and Apache/mod_perl. DB2 on AS/400 is also desired. Experience in a Win32 environment needed with possible Linux migration. Knowledge/Experience: BA/BS with minimum 4 years progressively responsible experience within administrative computing environment; demonstrated experience on a technical team; excellent analytical skills; detailed knowledge of database design and relational technology with demonstrable mastery Experience with OpenInteract, Template Toolkit, SQL, Perl and programmatically generated HTML very highly desired. Also: Apache/mod_perl administration, knowledge of MySQL and IBM DB2 on AS/400, C/C++, thin client or web driven applications development experience. Contact information: To apply or for information, send resume, salary requirements, references and a sample of your work (a small web-dbi script or something) to [EMAIL PROTECTED] No 3rd Parties please. Only US Citizens or authorized to Work for any employer in the US. P.S. Recruiters are 3rd parties, see above.
Here is my backtrace, please solove my problem
Hello, [root@qclinux mod_perl-1.26]# gdb httpd 14947 GNU gdb 19991004 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-redhat-linux... (no debugging symbols found)... /soft/Apache-ASP-2.27/make_httpd/mod_perl-1.26/14947: No such file or directory. Attaching to program: /usr/sbin/httpd, Pid 14947 Reading symbols from /lib/libNoVersion.so.1...done. Reading symbols from /lib/libm.so.6...done. Reading symbols from /lib/libcrypt.so.1...done. Reading symbols from /lib/libdb.so.2...done. Reading symbols from /lib/libdl.so.2...done. Reading symbols from /lib/libc.so.6...done. Reading symbols from /lib/ld-linux.so.2...done. Reading symbols from /lib/libnss_files.so.2...done. Reading symbols from /usr/lib/gconv/ISO8859-1.so...done. Reading symbols from /etc/httpd/modules/mod_vhost_alias.so...done. Reading symbols from /etc/httpd/modules/mod_env.so...done. Reading symbols from /etc/httpd/modules/mod_log_config.so...done. Reading symbols from /etc/httpd/modules/mod_log_agent.so...done. Reading symbols from /etc/httpd/modules/mod_log_referer.so...done. Reading symbols from /etc/httpd/modules/mod_mime.so...done. ---Type return to continue, or q return to quit--- Reading symbols from /etc/httpd/modules/mod_negotiation.so...done. Reading symbols from /etc/httpd/modules/mod_status.so...done. Reading symbols from /etc/httpd/modules/mod_info.so...done. Reading symbols from /etc/httpd/modules/mod_include.so...done. Reading symbols from /etc/httpd/modules/mod_autoindex.so...done. Reading symbols from /etc/httpd/modules/mod_dir.so...done. Reading symbols from /etc/httpd/modules/mod_cgi.so...done. Reading symbols from /etc/httpd/modules/mod_asis.so...done. Reading symbols from /etc/httpd/modules/mod_imap.so...done. Reading symbols from /etc/httpd/modules/mod_actions.so...done. Reading symbols from /etc/httpd/modules/mod_userdir.so...done. Reading symbols from /etc/httpd/modules/mod_alias.so...done. Reading symbols from /etc/httpd/modules/mod_rewrite.so...done. Reading symbols from /etc/httpd/modules/mod_access.so...done. Reading symbols from /etc/httpd/modules/mod_auth.so...done. Reading symbols from /etc/httpd/modules/mod_auth_anon.so...done. Reading symbols from /etc/httpd/modules/mod_auth_db.so...done. Reading symbols from /etc/httpd/modules/mod_digest.so...done. Reading symbols from /etc/httpd/modules/libproxy.so...done. Reading symbols from /etc/httpd/modules/mod_expires.so...done. Reading symbols from /etc/httpd/modules/mod_headers.so...done. Reading symbols from /etc/httpd/modules/mod_usertrack.so...done. Reading symbols from /etc/httpd/modules/mod_setenvif.so...done. ---Type return to continue, or q return to quit--- Reading symbols from /etc/httpd/modules/libperl.so...done. Reading symbols from /lib/libnsl.so.1...done. Reading symbols from /lib/libutil.so.1...done. Reading symbols from /etc/httpd/modules/libphp3.so...done. Reading symbols from /usr/lib/libgd.so.1...done. Reading symbols from /usr/lib/libttf.so.2...done. Reading symbols from /usr/lib/libgdbm.so.2...done. Reading symbols from /lib/libdb.so.3...done. Reading symbols from /usr/lib/libz.so.1...done. Reading symbols from /lib/libpam.so.0...done. Reading symbols from /lib/libresolv.so.2...done. Reading symbols from /usr/lib/apache/pgsql.so...done. Reading symbols from /usr/lib/libpq.so.2.0...done. Reading symbols from /usr/lib/apache/imap.so...done. Reading symbols from /usr/lib/apache/ldap.so...done. Reading symbols from /usr/lib/libldap.so.1...done. Reading symbols from /usr/lib/liblber.so.1...done. Reading symbols from /usr/lib/perl5/5.6.1/i686-linux/auto/SDBM_File/SDBM_File.so ...done. Reading symbols from /usr/lib/perl5/5.6.1/i686-linux/auto/IO/IO.so...done. Reading symbols from /usr/lib/perl5/site_perl/5.6.1/i686-linux/auto/Compress/Zli b/Zlib.so...done. Reading symbols from /usr/lib/perl5/5.6.1/i686-linux/auto/Data/Dumper/Dumper.so. ---Type return to continue, or q return to quit--- ..done. Reading symbols from /usr/lib/perl5/5.6.1/i686-linux/auto/Fcntl/Fcntl.so... done. Reading symbols from /usr/lib/perl5/site_perl/5.6.1/i686-linux/auto/Digest/MD5/M D5.so...done. Reading symbols from /usr/lib/perl5/site_perl/5.6.1/i686-linux/auto/Time/HiRes/H iRes.so...done. 0x4012817e in __select () from /lib/libc.so.6 (gdb) where #0 0x4012817e in __select () from /lib/libc.so.6 #1 0x0 in ?? () (gdb) source mod_perl-1.26/.gdbinit mod_perl-1.26/.gdbinit: No such file or directory. (gdb) source mod_perl-1.26/.gdbinit mod_perl-1.26/.gdbinit: No such file or directory. (gdb) curinfo Attempt to extract a component of a value that is not a structure pointer. (gdb) q The program is running. Quit anyway (and detach it)? (y or n) n Not confirmed. (gdb) install Undefined
with backtrace Fw: Proble by Build mod_perl as a DSO outside the Apache Source Tree via APXS
[root@qclinux mod_perl-1.26]# perl Makefile.PL PERL_DEBUG=1 EVERYTHING=1 DEBUG mode... ...adding `-g' to EXTRA_CFLAGS ...turning on PERL_TRACE ...setting PERL_DESTRUCT_LEVEL=2 Configure mod_perl with ../apache_1.3.22/src ? [y] Shall I build httpd in ../apache_1.3.22/src for you? [y] Appending mod_perl to src/Configuration Using config file: /soft/Apache-ASP-2.27/make_httpd/mod_perl-1.26/src/Configuration Creating Makefile + configured for Linux platform + setting C compiler to gcc + setting C pre-processor to gcc -E + checking for system header files + adding selected modules o perl_module uses ConfigStart/End + mod_perl build type: OBJ + setting up mod_perl build environment + id: mod_perl/1.26 + id: Perl/v5.6.1 (linux) [perl] + adjusting Apache build environment + enabling Perl support for SSI (mod_include) + using system Expat + checking sizeof various data types + doing sanity check on compiler and options Creating Makefile in support Creating Makefile in regex Creating Makefile in os/unix Creating Makefile in ap Creating Makefile in main Creating Makefile in modules/standard Creating Makefile in modules/perl EXTRA_CFLAGS: -DLINUX=22 -DMOD_PERL -DUSE_PERL_SSI -fno-strict-aliasing -I/u sr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DUSE_HSREGEX -D NO_DL_NEEDED PerlDispatchHandler.enabled PerlChildInitHandlerenabled PerlChildExitHandlerenabled PerlPostReadRequestHandler..enabled PerlTransHandlerenabled PerlHeaderParserHandler.enabled PerlAccessHandler...enabled PerlTransHandlerenabled PerlHeaderParserHandler.enabled PerlAccessHandler...enabled PerlAuthenHandler...enabled PerlAuthzHandlerenabled PerlTypeHandler.enabled PerlFixupHandlerenabled PerlHandler.enabled PerlLogHandler..enabled PerlInitHandler.enabled PerlCleanupHandler..enabled PerlRestartHandler..enabled PerlStackedHandlers.enabled PerlMethodHandlers..enabled PerlDirectiveHandlers...enabled PerlTableApienabled PerlLogApi..enabled PerlUriApi..enabled PerlUtilApi.enabled PerlFileApi.enabled PerlConnectionApi...enabled PerlServerApi...enabled PerlSectionsenabled PerlSSI.enabled Will run tests as User: 'nobody' Group: 'root' Checking CGI.pm VERSION..ok Checking for LWP::UserAgent..ok Checking for HTML::HeadParserok Writing Makefile for Apache Writing Makefile for Apache::Connection Writing Makefile for Apache::Constants Writing Makefile for Apache::File Writing Makefile for Apache::Leak Writing Makefile for Apache::Log Writing Makefile for Apache::ModuleConfig Writing Makefile for Apache::PerlRunXS Writing Makefile for Apache::Server Writing Makefile for Apache::Symbol Writing Makefile for Apache::Table Writing Makefile for Apache::URI Writing Makefile for Apache::Util Writing Makefile for mod_perl Thanks inadvance -SubbaReddy - Original Message - From: Stas Bekman [EMAIL PROTECTED] To: SubbaReddy M [EMAIL PROTECTED]; modperl list [EMAIL PROTECTED] Sent: Friday, November 09, 2001 2:02 AM Subject: Re: Proble by Build mod_perl as a DSO outside the Apache Source Tree via APXS SubbaReddy M wrote: How can I get backtrace info to send you? If you want to solve your problem at least read the replies thoroughly and you will be all set. Here it is again. And DO NOT reply to me, but to the list. Since you have a segfault, we cannot help you until you send us the backtrace. See the SUPPORT file in your source distro which explains how to do that. _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: ProxyPass and DirectoryIndex
On Fri, 9 Nov 2001, Jorge Godoy wrote:
Philip Mak [EMAIL PROTECTED] writes:
My current solution is to touch index.asp in the port 80 DocumentRoot
and have DirectoryIndex index.asp so that it knows to ProxyPass those
requests. I'd have to touch index.asp manually for every directory,
though. Is there a better way around this?
To ease your task... I think there might be a better solution that
does not involve this index.asp file, but I can't think of it now.
==
#!/bin/bash
cd document_root
for i in `find -type d`
do
cd $i
touch index.asp
cd -
done
==
If this is the only way then you don't need such a huge script. One line
will do:
find document_root -type d -exec touch \{\}/index.asp \;
Re: Here is my backtrace, please solove my problem
This is, i am geting. [root@qclinux mod_perl-1.26]# gdb httpd core GNU gdb 19991004 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-redhat-linux...(no debugging symbols found)... /soft/Apache-ASP-2.27/make_httpd/mod_perl-1.26/core: No such file or directory. (gdb) bt No stack. (gdb) /bt Undefined command: . Try help. (gdb) continue The program is not being run. (gdb) run -X -f `pwd`/t/conf/httpd.conf -d `pwd`/t Starting program: /usr/sbin/httpd -X -f `pwd`/t/conf/httpd.conf -d `pwd`/t Ouch! ap_mm_create(1048576, /soft/Apache-ASP-2.27/make_httpd/mod_perl-1.26/t/tmp/mm.19659) failed Error: MM: mm:core: failed to open semaphore file (No such file or directory): OS: No such file or directory Program exited with code 01. (gdb) Quit (gdb) bt No stack. (gdb) and i am really thankfull for your help. -SubbaReddy - Original Message - From: Barrie Slaymaker [EMAIL PROTECTED] To: SubbaReddy M [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, November 09, 2001 10:09 PM Subject: Re: Here is my backtrace, please solove my problem [Note the Reply-To] You're getting closer. Unfortunately, the backtrace you sent says that gdb attached to a running httpd and it happened to be sitting in select() when gdb attached on to it. At which point you grabbed the backtrace and exited, killing the httpd before recreating the problem. Instead, you need to cause the problem while debugging the httpd and, assuming it segfaults when in gdb, get the backtrace from where the problem occurred. Try the first recipe from SUPPORT: % cd mod_perl-x.xx % touch t/conf/srm.conf % gdb ../apache_x.xx/src/httpd (gdb) run -X -f `pwd`/t/conf/httpd.conf -d `pwd`/t [now make request that causes core dump] (gdb) bt or do what you did but gdb's 'continue' command to get the httpd to run again and make the offending request over and over until you get it to seg fault, *then* do the 'where'/'bt' command. The stack trace needs to be from the point of failure, not from some place in a (so far) healthy server... If you have a core file from the segfault, you can also do that recipe from SUPPORT: % gdb httpd core and do the 'bt' that's often a bit easier. - Barrie
