Re: Apache::PerlVINC makes Apache segfault
> [Cc to Stas as the example in the guide is wrong, and Dave explains > the correct way] > > On Mon, Jul 31, 2000 at 03:42:18PM -0400, Dave Moore took time to write: > > > > duh...now that i've had some more coffee...the line: > > > > PerlVersionINC On > > > > must come before the PerlINC statement. PerlINC wont store that path > > unless PerlVersionINC is On. > > Ok, that corrected my problem, thanks a lot Dave. Thanks Patrick. I've udpated the guide. The man page should be corrected as well. > > dave > > On Mon, 31 Jul 2000, Dave Moore wrote: > > > > > you arent doing anything wrong. you probably just need to upgrade to the > > > latest version of Apache::ExtUtils. this is not the same ExtUtils that > > > comes with mod_perl 1.24. you will have to get it from the latest cvs > > > snapshot of mod_perl. you will also have to remake/install PerlVINC after > > > you install ExtUtils. see if that helps. > > > > > > On Sat, 29 Jul 2000, Patrick wrote: > > > > > > > Hi all, > > > > > > > > (debian potato) > > > > apache-ssl : 1.3.9.13-2 > > > > modperl : 1.21.2309-1 > > > > perl : 5.005 > > > > Apache::PerlVINC : 0.01 compiled by myself > > > > > > > > As recommended in the guide, i'm trying to use Apache::PerlVINC since > > > > I have 3 virtualhosts, and the same sets of modules for all three (same >namespace), in > > > > three separate directories (one production, two developpments). > > > > > > > > So I have in httpd.conf > > > > > > > > PerlModule Apache::PerlVINC > > > > PerlINC /opt/anciens/membres > > > > PerlVersionINC On > > > > PerlFixupHandler Apache::PerlVINC > > > > > > > > But as soon as I put these 4 lines, apache doesn't run anymore. > > > > An strace at start-up shows at the end : > > > > > > ..some stuff was here... > > > > > > > > It seems not to be happy not to found DESTROY.al, but after that i'm > > > > lost. > > > > What am I doing wrong ? How can I correct ? Is there another > > > > possibility to achieve the same goal ? > > > > (besides running different copies of Apache binded on different ports) > > > > > > > > If that's make a difference i'm also using Apache::StatINC > > > > > > > > Thanks in advance for your time and your answers. > > > > > > > > PS: modperl just rocks, kudos to everyone ! > > > > > > > > -- > > > > Patrick. > > > > Because if life has a meaning, we should already know it. > > > > > > > > -- > > Dave Moore > > Web Application Developer > > mailto:[EMAIL PROTECTED] > > > > ePALS Classroom Exchange > > http://www.epals.com/ > > Connecting more than 1.9 million students and teachers in 182 countries! > > -- > Patrick. > Because if life has a meaning, we should already know it. > _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://perl.org http://stason.org/TULARC http://singlesheaven.com http://perlmonth.com http://sourcegarden.org
Re: Apache::PerlVINC makes Apache segfault
[Cc to Stas as the example in the guide is wrong, and Dave explains the correct way] On Mon, Jul 31, 2000 at 03:42:18PM -0400, Dave Moore took time to write: > > duh...now that i've had some more coffee...the line: > > PerlVersionINC On > > must come before the PerlINC statement. PerlINC wont store that path > unless PerlVersionINC is On. Ok, that corrected my problem, thanks a lot Dave. > dave > On Mon, 31 Jul 2000, Dave Moore wrote: > > > you arent doing anything wrong. you probably just need to upgrade to the > > latest version of Apache::ExtUtils. this is not the same ExtUtils that > > comes with mod_perl 1.24. you will have to get it from the latest cvs > > snapshot of mod_perl. you will also have to remake/install PerlVINC after > > you install ExtUtils. see if that helps. > > > > On Sat, 29 Jul 2000, Patrick wrote: > > > > > Hi all, > > > > > > (debian potato) > > > apache-ssl : 1.3.9.13-2 > > > modperl : 1.21.2309-1 > > > perl : 5.005 > > > Apache::PerlVINC : 0.01 compiled by myself > > > > > > As recommended in the guide, i'm trying to use Apache::PerlVINC since > > > I have 3 virtualhosts, and the same sets of modules for all three (same >namespace), in > > > three separate directories (one production, two developpments). > > > > > > So I have in httpd.conf > > > > > > PerlModule Apache::PerlVINC > > > PerlINC /opt/anciens/membres > > > PerlVersionINC On > > > PerlFixupHandler Apache::PerlVINC > > > > > > But as soon as I put these 4 lines, apache doesn't run anymore. > > > An strace at start-up shows at the end : > > > > ..some stuff was here... > > > > > > It seems not to be happy not to found DESTROY.al, but after that i'm > > > lost. > > > What am I doing wrong ? How can I correct ? Is there another > > > possibility to achieve the same goal ? > > > (besides running different copies of Apache binded on different ports) > > > > > > If that's make a difference i'm also using Apache::StatINC > > > > > > Thanks in advance for your time and your answers. > > > > > > PS: modperl just rocks, kudos to everyone ! > > > > > > -- > > > Patrick. > > > Because if life has a meaning, we should already know it. > > > > > -- > Dave Moore > Web Application Developer > mailto:[EMAIL PROTECTED] > > ePALS Classroom Exchange > http://www.epals.com/ > Connecting more than 1.9 million students and teachers in 182 countries! -- Patrick. Because if life has a meaning, we should already know it. PGP signature
Re: Apache::PerlVINC makes Apache segfault
duh...now that i've had some more coffee...the line: PerlVersionINC On must come before the PerlINC statement. PerlINC wont store that path unless PerlVersionINC is On. dave On Mon, 31 Jul 2000, Dave Moore wrote: > you arent doing anything wrong. you probably just need to upgrade to the > latest version of Apache::ExtUtils. this is not the same ExtUtils that > comes with mod_perl 1.24. you will have to get it from the latest cvs > snapshot of mod_perl. you will also have to remake/install PerlVINC after > you install ExtUtils. see if that helps. > > On Sat, 29 Jul 2000, Patrick wrote: > > > Hi all, > > > > (debian potato) > > apache-ssl : 1.3.9.13-2 > > modperl : 1.21.2309-1 > > perl : 5.005 > > Apache::PerlVINC : 0.01 compiled by myself > > > > As recommended in the guide, i'm trying to use Apache::PerlVINC since > > I have 3 virtualhosts, and the same sets of modules for all three (same >namespace), in > > three separate directories (one production, two developpments). > > > > So I have in httpd.conf > > > > PerlModule Apache::PerlVINC > > PerlINC /opt/anciens/membres > > PerlVersionINC On > > PerlFixupHandler Apache::PerlVINC > > > > But as soon as I put these 4 lines, apache doesn't run anymore. > > An strace at start-up shows at the end : > > ..some stuff was here... > > > > It seems not to be happy not to found DESTROY.al, but after that i'm > > lost. > > What am I doing wrong ? How can I correct ? Is there another > > possibility to achieve the same goal ? > > (besides running different copies of Apache binded on different ports) > > > > If that's make a difference i'm also using Apache::StatINC > > > > Thanks in advance for your time and your answers. > > > > PS: modperl just rocks, kudos to everyone ! > > > > -- > > Patrick. > > Because if life has a meaning, we should already know it. > > -- Dave Moore Web Application Developer mailto:[EMAIL PROTECTED] ePALS Classroom Exchange http://www.epals.com/ Connecting more than 1.9 million students and teachers in 182 countries!
Re: Apache::PerlVINC makes Apache segfault
you arent doing anything wrong. you probably just need to upgrade to the
latest version of Apache::ExtUtils. this is not the same ExtUtils that
comes with mod_perl 1.24. you will have to get it from the latest cvs
snapshot of mod_perl. you will also have to remake/install PerlVINC after
you install ExtUtils. see if that helps.
On Sat, 29 Jul 2000, Patrick wrote:
> Hi all,
>
> (debian potato)
> apache-ssl : 1.3.9.13-2
> modperl : 1.21.2309-1
> perl : 5.005
> Apache::PerlVINC : 0.01 compiled by myself
>
> As recommended in the guide, i'm trying to use Apache::PerlVINC since
> I have 3 virtualhosts, and the same sets of modules for all three (same namespace),
>in
> three separate directories (one production, two developpments).
>
> So I have in httpd.conf
>
> PerlModule Apache::PerlVINC
> PerlINC /opt/anciens/membres
> PerlVersionINC On
> PerlFixupHandler Apache::PerlVINC
>
> But as soon as I put these 4 lines, apache doesn't run anymore.
> An strace at start-up shows at the end :
>
> stat("/usr/local/lib/site_perl/i386-linux/auto/Apache/PerlVINC/DESTROY.al",
>0xb93c) = -1 ENOENT (No such file or directory)
> open("/opt/anciens/membres/auto/Apache/PerlVINC/DESTROY.al", O_RDONLY) = -1 ENOENT
>(No such file or directory)
> open("/usr/lib/perl5/5.005/i386-linux/auto/Apache/PerlVINC/DESTROY.al", O_RDONLY) =
>-1 ENOENT (No such file or directory)
> open("/usr/lib/perl5/5.005/auto/Apache/PerlVINC/DESTROY.al", O_RDONLY) = -1 ENOENT
>(No such file or directory)
> open("/usr/local/lib/site_perl/i386-linux/auto/Apache/PerlVINC/DESTROY.al",
>O_RDONLY) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/site_perl/auto/Apache/PerlVINC/DESTROY.al", O_RDONLY) = -1
>ENOENT (No such file or directory)
> open("/usr/lib/perl5/auto/Apache/PerlVINC/DESTROY.al", O_RDONLY) = -1 ENOENT (No
>such file or directory)
> open("./auto/Apache/PerlVINC/DESTROY.al", O_RDONLY) = -1 ENOENT (No such file or
>directory)
> open("/etc/apache-ssl//auto/Apache/PerlVINC/DESTROY.al", O_RDONLY) = -1 ENOENT (No
>such file or directory)
> open("/etc/apache-ssl/lib/perl/auto/Apache/PerlVINC/DESTROY.al", O_RDONLY) = -1
>ENOENT (No such file or directory)
> rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
> rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
> rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
> rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
> rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
> rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
> rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
> rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
> rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
> rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
> munmap(0x403c4000, 22832) = 0
> munmap(0x403ca000, 57308) = 0
> munmap(0x403d8000, 27572) = 0
> munmap(0x403df000, 9864)= 0
> munmap(0x403e4000, 55824) = 0
> munmap(0x403f2000, 9064)= 0
> --- SIGSEGV (Erreur de segmentation) ---
> +++ killed by SIGSEGV +++
>
> It seems not to be happy not to found DESTROY.al, but after that i'm
> lost.
> What am I doing wrong ? How can I correct ? Is there another
> possibility to achieve the same goal ?
> (besides running different copies of Apache binded on different ports)
>
> If that's make a difference i'm also using Apache::StatINC
>
> Thanks in advance for your time and your answers.
>
> PS: modperl just rocks, kudos to everyone !
>
> --
> Patrick.
> Because if life has a meaning, we should already know it.
>
--
Dave Moore
Web Application Developer
mailto:[EMAIL PROTECTED]
ePALS Classroom Exchange
http://www.epals.com/
Connecting more than 1.9 million students and teachers in 182 countries!
RE: Apache::PerlVINC making apache kak
> "IM" == Ian Mahuron <[EMAIL PROTECTED]> writes: IM> You might start by staticly linking mod_perl. DSOs are evil. I disagree. DSOs are exceptionally useful.
Re: Apache::PerlVINC making apache kak
On Thu, 22 Jun 2000, dave moore wrote: > > Dave, > > WOW!! I know our name is not exactly rare (the producer of > Polka-Dot-Door), but what are the odds of being on the same mailing > list. Too wierd. Anyways. Hmmm. That is a pretty wierd coincidence. > > Correct me if I'm wrong on this, but Apache::PerlVINC has to be compiled > as a shared object that gets loaded on server startup. This is what > happens when you 'make' it. What I'm wondering is this: Do any custom > config directives work on your machine? > > Obviously its kaking not when it loads the module, but when it tries to > unload it. This is a total kludge and I may get flamed for suggesting > this, but try loading the shared object itself with LoadModule. Add this > line to your config: > > LoadModule XS_Apache__PerlVINC /usr/lib/perl5/path_to_file/PerlVINC.so > > Like I said, its a _total_ kludge and is NOT a solution to the problem. It > is merely a workaround. Good luck. > > David YE! It worked. It is a little kludgey but who cares! It's a dev server anyways. Thanks a million. > > On Wed, 21 Jun 2000, Dave Moore wrote: > > > Hey, > > > > I've installed Apache::PerlVINC, and PerlModule'd it in my httpd.conf > > file. Now whenever I start apache, it doesn't start and logs no errors. I > > am using: > > > > Apache 1.3.9 > > mod_perl 1.24 (compiled as DSO) > > Redhat 6.2 > > Perl 5.005_03 > > > > The thing that kaks it is the line 'PerlModule Apache::PerlVINC' in my > > config. As soon as I comment this line, everything works. This is the > > output through gdb: > > > > [root@artemis bin]# gdb -q httpd > > (gdb) b exit > > Breakpoint 1 at 0x805b6f4 > > (gdb) run -X -f /epals/conf/httpd.conf > > Starting program: /usr/local/apache/bin/httpd -X -f /epals/conf/httpd.conf > > Breakpoint 1 at 0x4011a1f2: file exit.c, line 40. > > > > Program received signal SIGSEGV, Segmentation fault. > > 0x80a5569 in ap_remove_module () > > (gdb) bt > > #0 0x80a5569 in ap_remove_module () > > #1 0x80a562f in ap_remove_loaded_module () > > #2 0x805bb3e in unload_module () > > #3 0x80a204e in run_cleanups () > > #4 0x80a087d in ap_clear_pool () > > #5 0x80b0833 in standalone_main () > > #6 0x80b10c3 in main () > > #7 0x401119cb in __libc_start_main (main=0x80b0d8c , argc=4, > > argv=0xbad4, init=0x805a854 <_init>, fini=0x80e4d8c <_fini>, > > rtld_fini=0x4000ae60 <_dl_fini>, stack_end=0xbacc) > > at ../sysdeps/generic/libc-start.c:92 > > (gdb) > > > > I dont know my ass from a hole in the ground when it comes to C, but if I > > huh.brutally honest. > > > had to guess, I'd say that the problem lies in Apache. ap_remove_module() > > is a function of apache (in http_config.c to be anal), but I can't figure > > out what it's trying to remove. (PerlVINC or mod_perl.so) I don't see why > > it would want to remove either but then again, I dont know much about > > much. > > > > I also noticed someone else on the list (Kees Vonk) have a problem similar > > to this when he upgraded from Apache 1.3.6 to 1.3.9. His bt was totally > > different but maybe thats because he was using SSL. > > > > I'm really stuck here. Literally. I can't move on until this problem is > > solved, so any help would be greatly appreciated. Thanks. > > > > dave > > > > Dave Moore > > Web Application Developer > > mailto:[EMAIL PROTECTED] > > > > ePALS Classroom Exchange > > http://www.epals.com/ > > The world's largest online classroom community - > > Connecting over 27,000 classrooms in 130 countries! > > > Dave Moore Web Developer > [EMAIL PROTECTED] www.hyperconnect.com > > -- Dave Moore Web Application Developer mailto:[EMAIL PROTECTED] ePALS Classroom Exchange http://www.epals.com/ The world's largest online classroom community - Connecting over 27,000 classrooms in 130 countries!
RE: Apache::PerlVINC making apache kak
You might start by staticly linking mod_perl. DSOs are evil. > -Original Message- > From: Dave Moore [mailto:[EMAIL PROTECTED]] > Sent: Thursday, June 22, 2000 09:22 AM > To: [EMAIL PROTECTED] > Subject: Re: Apache::PerlVINC making apache kak > > > On Wed, 21 Jun 2000, Dave Moore wrote: > > > Hey, > > > > I've installed Apache::PerlVINC, and PerlModule'd it in my httpd.conf > > file. Now whenever I start apache, it doesn't start and logs no > errors. I > > am using: > > > > Apache 1.3.9 > > mod_perl 1.24 (compiled as DSO) > > Redhat 6.2 > > Perl 5.005_03 > > > > The thing that kaks it is the line 'PerlModule Apache::PerlVINC' in my > > config. As soon as I comment this line, everything works. This is the > > output through gdb: > > > > [root@artemis bin]# gdb -q httpd > > (gdb) b exit > > Breakpoint 1 at 0x805b6f4 > > (gdb) run -X -f /epals/conf/httpd.conf > > Starting program: /usr/local/apache/bin/httpd -X -f > /epals/conf/httpd.conf > > Breakpoint 1 at 0x4011a1f2: file exit.c, line 40. > > > > Program received signal SIGSEGV, Segmentation fault. > > 0x80a5569 in ap_remove_module () > > (gdb) bt > > #0 0x80a5569 in ap_remove_module () > > #1 0x80a562f in ap_remove_loaded_module () > > #2 0x805bb3e in unload_module () > > #3 0x80a204e in run_cleanups () > > #4 0x80a087d in ap_clear_pool () > > #5 0x80b0833 in standalone_main () > > #6 0x80b10c3 in main () > > #7 0x401119cb in __libc_start_main (main=0x80b0d8c , argc=4, > > argv=0xbad4, init=0x805a854 <_init>, fini=0x80e4d8c <_fini>, > > rtld_fini=0x4000ae60 <_dl_fini>, stack_end=0xbacc) > > at ../sysdeps/generic/libc-start.c:92 > > (gdb) > > > > I dont know my ass from a hole in the ground when it comes to > C, but if I > > had to guess, I'd say that the problem lies in Apache. > ap_remove_module() > > is a function of apache (in http_config.c to be anal), but I > can't figure > > out what it's trying to remove. (PerlVINC or mod_perl.so) I > don't see why > > it would want to remove either but then again, I dont know much about > > much. > > > > I also noticed someone else on the list (Kees Vonk) have a > problem similar > > to this when he upgraded from Apache 1.3.6 to 1.3.9. His bt was totally > > different but maybe thats because he was using SSL. > > > > I'm really stuck here. Literally. I can't move on until this problem is > > solved, so any help would be greatly appreciated. Thanks. > > > > dave > > > > Dave Moore > > Web Application Developer > > mailto:[EMAIL PROTECTED] > > > > ePALS Classroom Exchange > > http://www.epals.com/ > > The world's largest online classroom community - > > Connecting over 27,000 classrooms in 130 countries! > > > > > > > > -- > Dave Moore > Web Application Developer > mailto:[EMAIL PROTECTED] > > ePALS Classroom Exchange > http://www.epals.com/ > The world's largest online classroom community - > Connecting over 27,000 classrooms in 130 countries! > > >
Re: Apache::PerlVINC making apache kak
On Wed, 21 Jun 2000, Dave Moore wrote: > Hey, > > I've installed Apache::PerlVINC, and PerlModule'd it in my httpd.conf > file. Now whenever I start apache, it doesn't start and logs no errors. I > am using: > > Apache 1.3.9 > mod_perl 1.24 (compiled as DSO) > Redhat 6.2 > Perl 5.005_03 > > The thing that kaks it is the line 'PerlModule Apache::PerlVINC' in my > config. As soon as I comment this line, everything works. This is the > output through gdb: > > [root@artemis bin]# gdb -q httpd > (gdb) b exit > Breakpoint 1 at 0x805b6f4 > (gdb) run -X -f /epals/conf/httpd.conf > Starting program: /usr/local/apache/bin/httpd -X -f /epals/conf/httpd.conf > Breakpoint 1 at 0x4011a1f2: file exit.c, line 40. > > Program received signal SIGSEGV, Segmentation fault. > 0x80a5569 in ap_remove_module () > (gdb) bt > #0 0x80a5569 in ap_remove_module () > #1 0x80a562f in ap_remove_loaded_module () > #2 0x805bb3e in unload_module () > #3 0x80a204e in run_cleanups () > #4 0x80a087d in ap_clear_pool () > #5 0x80b0833 in standalone_main () > #6 0x80b10c3 in main () > #7 0x401119cb in __libc_start_main (main=0x80b0d8c , argc=4, > argv=0xbad4, init=0x805a854 <_init>, fini=0x80e4d8c <_fini>, > rtld_fini=0x4000ae60 <_dl_fini>, stack_end=0xbacc) > at ../sysdeps/generic/libc-start.c:92 > (gdb) > > I dont know my ass from a hole in the ground when it comes to C, but if I > had to guess, I'd say that the problem lies in Apache. ap_remove_module() > is a function of apache (in http_config.c to be anal), but I can't figure > out what it's trying to remove. (PerlVINC or mod_perl.so) I don't see why > it would want to remove either but then again, I dont know much about > much. > > I also noticed someone else on the list (Kees Vonk) have a problem similar > to this when he upgraded from Apache 1.3.6 to 1.3.9. His bt was totally > different but maybe thats because he was using SSL. > > I'm really stuck here. Literally. I can't move on until this problem is > solved, so any help would be greatly appreciated. Thanks. > > dave > > Dave Moore > Web Application Developer > mailto:[EMAIL PROTECTED] > > ePALS Classroom Exchange > http://www.epals.com/ > The world's largest online classroom community - > Connecting over 27,000 classrooms in 130 countries! > > > -- Dave Moore Web Application Developer mailto:[EMAIL PROTECTED] ePALS Classroom Exchange http://www.epals.com/ The world's largest online classroom community - Connecting over 27,000 classrooms in 130 countries!
Re: Apache::PerlVINC making apache kak
Dave, WOW!! I know our name is not exactly rare (the producer of Polka-Dot-Door), but what are the odds of being on the same mailing list. Too wierd. Anyways. Correct me if I'm wrong on this, but Apache::PerlVINC has to be compiled as a shared object that gets loaded on server startup. This is what happens when you 'make' it. What I'm wondering is this: Do any custom config directives work on your machine? Obviously its kaking not when it loads the module, but when it tries to unload it. This is a total kludge and I may get flamed for suggesting this, but try loading the shared object itself with LoadModule. Add this line to your config: LoadModule XS_Apache__PerlVINC /usr/lib/perl5/path_to_file/PerlVINC.so Like I said, its a _total_ kludge and is NOT a solution to the problem. It is merely a workaround. Good luck. David On Wed, 21 Jun 2000, Dave Moore wrote: > Hey, > > I've installed Apache::PerlVINC, and PerlModule'd it in my httpd.conf > file. Now whenever I start apache, it doesn't start and logs no errors. I > am using: > > Apache 1.3.9 > mod_perl 1.24 (compiled as DSO) > Redhat 6.2 > Perl 5.005_03 > > The thing that kaks it is the line 'PerlModule Apache::PerlVINC' in my > config. As soon as I comment this line, everything works. This is the > output through gdb: > > [root@artemis bin]# gdb -q httpd > (gdb) b exit > Breakpoint 1 at 0x805b6f4 > (gdb) run -X -f /epals/conf/httpd.conf > Starting program: /usr/local/apache/bin/httpd -X -f /epals/conf/httpd.conf > Breakpoint 1 at 0x4011a1f2: file exit.c, line 40. > > Program received signal SIGSEGV, Segmentation fault. > 0x80a5569 in ap_remove_module () > (gdb) bt > #0 0x80a5569 in ap_remove_module () > #1 0x80a562f in ap_remove_loaded_module () > #2 0x805bb3e in unload_module () > #3 0x80a204e in run_cleanups () > #4 0x80a087d in ap_clear_pool () > #5 0x80b0833 in standalone_main () > #6 0x80b10c3 in main () > #7 0x401119cb in __libc_start_main (main=0x80b0d8c , argc=4, > argv=0xbad4, init=0x805a854 <_init>, fini=0x80e4d8c <_fini>, > rtld_fini=0x4000ae60 <_dl_fini>, stack_end=0xbacc) > at ../sysdeps/generic/libc-start.c:92 > (gdb) > > I dont know my ass from a hole in the ground when it comes to C, but if I huh.brutally honest. > had to guess, I'd say that the problem lies in Apache. ap_remove_module() > is a function of apache (in http_config.c to be anal), but I can't figure > out what it's trying to remove. (PerlVINC or mod_perl.so) I don't see why > it would want to remove either but then again, I dont know much about > much. > > I also noticed someone else on the list (Kees Vonk) have a problem similar > to this when he upgraded from Apache 1.3.6 to 1.3.9. His bt was totally > different but maybe thats because he was using SSL. > > I'm really stuck here. Literally. I can't move on until this problem is > solved, so any help would be greatly appreciated. Thanks. > > dave > > Dave Moore > Web Application Developer > mailto:[EMAIL PROTECTED] > > ePALS Classroom Exchange > http://www.epals.com/ > The world's largest online classroom community - > Connecting over 27,000 classrooms in 130 countries! Dave Moore Web Developer [EMAIL PROTECTED] www.hyperconnect.com
Re: Apache::PerlVINC again
Doug MacEachern wrote: > > The following works on Apache/1.3.6 (Unix) mod_perl/1.21 > > mod_ssl/2.3.5 OpenSSL/0.9.3a > > > > But when running on Apache/1.3.9 (Unix) mod_perl/1.21 > > mod_ssl/2.4.8 OpenSSL/0.9.4, I get the following problem > > which _appears_ (I am not 100% sure) to be caused by > > Apache::PerlVINC. I have the following section in my > > httpd.conf > ... > > The moment I uncomment the PerlVINC lines (or even just the first one) > > apache fails to start without any error message (STDOUT or logs > > (LogLevel > > debug)) or core file. > > you'll need to try this: [ ... snip ...] > try this: > > % gdb httpd > (gdb) b exit > (gdb) run -X > > whether it core dumps or exit() is called, post the output of: > > (gdb) bt Sorry about the delay, I have been side tracted with some other stuff, here is the requested output: % gdb httpd GNU gdb 4.18 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 "hppa2.0-hp-hpux10.20"... (gdb) b exit Breakpoint 1 at 0x3ec34 (gdb) run -X -DSSL -f /opt/ward/apache/conf/httpd_idv_virt_host_test.conf Starting program: /opt/ward/apache/bin/httpd -X -DSSL -f /opt/ward/apache/conf/httpd_idv_virt_host_test.conf warning: Unable to find __d_pid symbol in object file. warning: Suggest linking with /opt/langtools/lib/end.o. warning: GDB will be unable to track shl_load/shl_unload calls Breakpoint 1 at 0x7af47dd4 Perl default module loading beginning... Perl default module loading complete. [New process 21404] Detaching after fork from process 21404 Breakpoint 1, 0x7af47dd4 in exit () from /usr/lib/libc.1 (gdb) bt #0 0x7af47dd4 in exit () from /usr/lib/libc.1 #1 0x89e9c in ap_process_resource_config () #2 0x8aaa4 in ap_read_config () #3 0x99de0 in standalone_main () #4 0x9acb4 in main () (gdb) I hope this is helpfull, it would be good if I could get this resolved. Kees Vonk
Re: Apache::PerlVINC again
On Thu, 1 Jun 2000, Kees Vonk 7249 24549 wrote: > The following works on Apache/1.3.6 (Unix) mod_perl/1.21 > mod_ssl/2.3.5 OpenSSL/0.9.3a > > But when running on Apache/1.3.9 (Unix) mod_perl/1.21 > mod_ssl/2.4.8 OpenSSL/0.9.4, I get the following problem > which _appears_ (I am not 100% sure) to be caused by > Apache::PerlVINC. I have the following section in my > httpd.conf ... > The moment I uncomment the PerlVINC lines (or even just the first one) > apache fails to start without any error message (STDOUT or logs (LogLevel > debug)) or core file. you'll need to try this: Date: Thu, 25 May 2000 12:13:20 -0700 (PDT) From: Doug MacEachern <[EMAIL PROTECTED]> To: Roberto Bourgonjen <[EMAIL PROTECTED]> cc: [EMAIL PROTECTED] Subject: Re: httpd exits with apache-1.3.12 and mod_perl-1.21 on Redhat 6.2 On Wed, 24 May 2000, Roberto Bourgonjen wrote: > Hi all, > > I am encountering strange problems on redhat 6.2 installations with > rpm's apache-1.3.12-2 and mod_perl-1.21-10 (the latest available > versions from redhat. I _have_ to use rpm's). I've tried two machines. > > As soon as load certain modules the server exits immediately, without > producing the slightest error message. try this: % gdb httpd (gdb) b exit (gdb) run -X whether it core dumps or exit() is called, post the output of: (gdb) bt
Re: Apache::PerlVINC
On Wed, 24 May 2000, Kees Vonk 7249 24549 wrote:
> > try this in httpd.conf:
> >
> >
> > delete $INC{'Apache/PerlVINC.pm'};
> > require Apache::PerlVINC;
> >
>
> Apache start up now (why does mod_perl not do this, can you
> explain?), however I get the following error when trying to
> access a page that contains the reloaded module:
>
>
>
> [Wed May 24 09:00:15 2000] [warn] Apache::PerlVINC: reloading
> 'Ward/IDV/IDVDatabase.pm'
>
> [Wed May 24 09:00:15 2000] [error] Can't locate
> Ward/IDV/IDVDatabase.pm in @INC (@INC contains:) at
> /opt/perl5/lib/site_perl/PA-RISC1.1/Apache/PerlVINC.pm line
> 59.
>
> -
>
>
> I played around a little bit and found that I have to put the
> PerlVersionINC directive before the PerlINC directive (which
> makes sense looking at the code) and then that works (you
> might want to change this in your example, (and in the guide,
> Stas)).
Kees, thanks for the update. Will add this.
P.S. I watch the list even if I'm silent, so I pick all your notes
regarding the guide, even if I don't respond... So keep on those comming,
your contributions is what really makes the guide invaluable!
_
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://perl.org http://stason.org/TULARC
http://singlesheaven.com http://perlmonth.com http://sourcegarden.org
Re: Apache::PerlVINC
On Wed, 24 May 2000, Kees Vonk 7249 24549 wrote:
> > try this in httpd.conf:
> >
> >
> > delete $INC{'Apache/PerlVINC.pm'};
> > require Apache::PerlVINC;
> >
>
> Apache start up now (why does mod_perl not do this, can you
> explain?),
i can't explain because i haven't been able to reproduce it yet.
actually, i can explain this:
PerlModule Apache::PerlVINC
triggers a call to: ap_add_module(&XS_Apache__PerlVINC);
which makes the command table available to apache, for PerlINC, etc.
directives. when apache re-reads it's config at startup, it clears the
module list first. since Apache/PerlVINC.pm is already in %INC, Perl
would not try to re-load it, hence, skipping the call to ap_add_module(),
so apache can no longer see the Apache::PerlVINC command table. mod_perl
has logic to delete the %INC entry so it is re-loaded, but certain cases
seems to prevent that from happening. i'm not sure what case(s) that
is yet. the trick forces that to happen.
> however I get the following error when trying to
> access a page that contains the reloaded module:
...
> I played around a little bit and found that I have to put the
> PerlVersionINC directive before the PerlINC directive (which
> makes sense looking at the code) and then that works (you
> might want to change this in your example, (and in the guide,
> Stas)).
ok thanks!
> Thank you very much, your help has been invaluable.
no problem, glad you've found a solution.
> PS. my offer of helping out mainting this module still
> stands, I start understanding it better all the time.
ok, whenever you're ready, just say the word :)
Re: Apache::PerlVINC
> try this in httpd.conf:
>
>
> delete $INC{'Apache/PerlVINC.pm'};
> require Apache::PerlVINC;
>
Apache start up now (why does mod_perl not do this, can you
explain?), however I get the following error when trying to
access a page that contains the reloaded module:
[Wed May 24 09:00:15 2000] [warn] Apache::PerlVINC: reloading
'Ward/IDV/IDVDatabase.pm'
[Wed May 24 09:00:15 2000] [error] Can't locate
Ward/IDV/IDVDatabase.pm in @INC (@INC contains:) at
/opt/perl5/lib/site_perl/PA-RISC1.1/Apache/PerlVINC.pm line
59.
-
I played around a little bit and found that I have to put the
PerlVersionINC directive before the PerlINC directive (which
makes sense looking at the code) and then that works (you
might want to change this in your example, (and in the guide,
Stas)).
Thank you very much, your help has been invaluable.
Kees
PS. my offer of helping out mainting this module still
stands, I start understanding it better all the time.
Re: Apache::PerlVINC
On Tue, 23 May 2000, Kees Vonk 7249 24549 wrote:
> Ok, I have added 'use lib qw(/opt/ward/IDV/DEV/Modules);' to my startup.pl,
> but now I get the following error in my error log:
>
> Syntax error on line 339 of /opt/ward/apache/conf/httpd.conf:
> Invalid command 'PerlINC', perhaps mis-spelled or defined by a module not
> included in the server configuration
try this in httpd.conf:
delete $INC{'Apache/PerlVINC.pm'};
require Apache::PerlVINC;
mod_perl is supposed to do that for you, so the module is reloaded again
when apache re-reads it's configuration on startup.
Re: Apache::PerlVINC
> > I am testing the use of Apache::PerlVINC but I think I must > > do something wrong because I get an error on the PerlRequire > > statement in the following bit of httpd.conf when starting > > apache: > > > PerlINC /opt/ward/IDV/DEV/Modules > > PerlRequire Ward/IDV/IDVDatabase.pm > > PerlINC modifies @INC at request time to pick up the different version of > your PerlRequire'd module. however, mod_perl needs to be able to find > this module at startup time as well. you'll need to 'use lib ...' or > similar so your PerlRequire'd module can be found at startup time if it's > not already somewhere in @INC. Ok, I have added 'use lib qw(/opt/ward/IDV/DEV/Modules);' to my startup.pl, but now I get the following error in my error log: Syntax error on line 339 of /opt/ward/apache/conf/httpd.conf: Invalid command 'PerlINC', perhaps mis-spelled or defined by a module not included in the server configuration line 339 is the PerlINC line above. I have 'PerlModule Apache::PerlVINC' in my httpd.conf file (I have tried moving it to startup.pl, but that doesn't make any difference). Relevant part of httpd.conf attached again. Any other suggestions? Could it have something to do with my virtual host sections (I have more virtual host sections with Apache::PerlVINC stuff in)? Kees PS. I wouldn't mind helping out maintaining this module, but I am not sure I understand it 100%. (Like why is it failing in this situation.) I had a look at Makefile.PL and PerlVINC.pm, though I have to read up on DynaLoader, ExtUtils::MakeMaker and Apache::ExtUtils, I think I get the gist of it. For instance should PerlINC's 'errmsg' in Makefile.PL say 'a path' instead of 'On or Off'? But I presume that doesn't make any difference to my situation. PerlModule Apache::PerlVINC DocumentRoot /opt/ward/DocumentRoot SetEnv IDV_ENV DEV Alias /idv/ "/opt/ward/IDV/DEV/Scripts" Options +Indexes PerlAuthzHandler Ward::Authorise SetHandler perl-script PerlHandler Apache::Registry AuthType Basic AuthName "IDV Development" AuthAuthoritative on require idvenv DEV #line 339 PerlINC /opt/ward/IDV/DEV/Modules PerlVersionINC On PerlFixupHandler Apache::PerlVINC PerlRequire Ward/IDV/IDVDatabase.pm ## ## This can also go in a section ## SSLEngine on SSLCertificateFile/opt/ward/apache/conf/ssl.crt/server.crt SSLCertificateKeyFile /opt/ward/apache/conf/ssl.key/server.key SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown
Re: Apache::PerlVINC
On Thu, 18 May 2000, Kees Vonk 7249 24549 wrote: > I am testing the use of Apache::PerlVINC but I think I must > do something wrong because I get an error on the PerlRequire > statement in the following bit of httpd.conf when starting > apache: > PerlINC /opt/ward/IDV/DEV/Modules > PerlRequire Ward/IDV/IDVDatabase.pm PerlINC modifies @INC at request time to pick up the different version of your PerlRequire'd module. however, mod_perl needs to be able to find this module at startup time as well. you'll need to 'use lib ...' or similar so your PerlRequire'd module can be found at startup time if it's not already somewhere in @INC.
