Re: Anyone get Apache::PerlVINC to work?
sorry for the late reply but.. i've never personally used PerlVINC on any version of mod_perl 1.24, i had experienced the silent death on startup problem myself with both versions of VINC. upgrading Apache::ExtUtils fixed it for me. the fix is not part of any official mod_perl release. ie you have to get it from the cvs snapshot. http://perl.apache.org/from-cvs/modperl/ you dont need to install the whole thing, just the latest version of Apache::ExtUtils. its needed for when you compile and install PerlVINC. the version you need is 1.04 and the version that comes with mod_perl 1.24 is 1.03. just run this on the command line to see which version you have: perl -MApache::ExtUtils -e'print $Apache::ExtUtils::VERSION."\n";' even with this, i dont know for sure that it (VINC) will work with any version mod_perl before 1.24. i simply dont have the time to test against every version. if you cant get it to work with 1.22, maybe it is time for an upgrade. dave On Sat, 19 Aug 2000, Stas Bekman wrote: On Fri, 18 Aug 2000, Tom Lancaster wrote: That's the version I'm using, and it's in the docs for that module that the problem I'm having is described. It claims to be fixable by using the latest ExtUtils. I guess not :( Oh, Ok. I thought I've been using an older version of it. I suppose I'd better update my mod_perl. Definitely worth to give it a try. Stas Bekman wrote: On Fri, 18 Aug 2000, Tom Lancaster wrote: I get the behaviour described in the BUGS section of the docs: server silently fails to start. However, I'm using the latest version of Apache::ExtUtils, as recommended. Also using mod_perl 1.22, Apache 1.3.12, Apache::ASP 2.03. Has anyone got PerlVINC to work with this combo? Use the latest version, it's not a part of the Apache::ExtUtils, but distributed in a separate package: Module id = Apache::PerlVINC CPAN_USERID DAVEM (Dave Moore [EMAIL PROTECTED]) CPAN_VERSION 0.02 CPAN_FILED/DA/DAVEM/Apache-PerlVINC-0.02.tar.gz MANPAGEApache::PerlVINC - Allows versioning of modules among directories or v-hosts. It's about a time to upgrade the mod_perl server as well :) _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://apachetoday.com http://jazzvalley.com http://singlesheaven.com http://perlmonth.com perl.org apache.org _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://apachetoday.com http://jazzvalley.com http://singlesheaven.com http://perlmonth.com perl.org apache.org -- 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: custom server string
On Thu, 10 Aug 2000, Thomas von Elling Skifter Eibner wrote: On Tue, Aug 08, 2000 at 05:55:19PM -0400, Dave Moore wrote: i need to change the outgoing Server header on all requests to our site. dont ask why I would want to do that. i have my orders. i read some old posts from the 90's which said I would have to write my own send_http_header() method. sounds fun but id rather not. Is this still the case and if so...why? has anyone else had to do this? Is it the whole of the Server string you want to change or do you just want to add your own module name? If it is the later you can make a simple little module in C that uses the ap_add_version_component() function. If you want to change the whole Server string you'd probably have to edit the source files of apache. yeahthe whole enchilada. thats what we ended up doing. puting it right in the source and recompiling[sigh]. oh well, even still, mod_perl rules. -- Thomas Eibner -- 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!
custom server string
i need to change the outgoing Server header on all requests to our site. dont ask why I would want to do that. i have my orders. i read some old posts from the 90's which said I would have to write my own send_http_header() method. sounds fun but id rather not. Is this still the case and if so...why? has anyone else had to do this? dave -- 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: Seg Fault (11)
On Fri, 4 Aug 2000, Bill Jones wrote: Using Raven's (www.covalent.com) build, I want to use mod_perl as a DSO -- no errors during build: Apache/1.3.12 (Unix) secured_by_Raven/1.5.1 mod_perl/1.24 PHP/4.0.1pl2 However, trying to use mod_perl's DSO causes Seg Fault (11) Any thoughts, comments, or ideas would be most appreciated :) TIA; -Sneex- :] - FCCJ * 501 W State St * Jacksonville, Fl 32202 * 904/632-3089 - mod_perl and php4 dont mix well together, there has been a few posts about this in the past. try running it through gdb to get a stack backtrace. that might provide some more clues. -- 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 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!
[ ANNOUNCE ] Apache::PerlVINC v0.02
All, ok. after much twiddling and tweaking, I have finished a version of Apache::PerlVINC that I feel comfortable with. I changed _alot_ of things in it. maybe too much. i thought it would be nice if _everybody_ had a chance to flame me, so I am including a link so you can download it and try it. http://dave.devel.epals.com/misc/Apache-PerlVINC-0.02.tar.gz Apache::PerlVINC is a module that allows multiple versions of a script or module to run on the same server. It works by reloading the specified files at request. Because of this, it is meant for use only in a development environment. I totally revamped the directives. I removed the PerlVersionINC On/Off directive. I didn't see the need for it once DIR_CREATE is involved. Secondly, I traded the use of PerlRequire with PerlVersion. the reasoning behind this was so that if the file wasn't there, the server would still start. Also, this way you dont have to worry about setting PERL5LIB or "use lib 'xxx'". I thought it might make things easier and more intuitive. if I am wrong, Im sure i'll hear about it. I think my biggest concern is for all the people using it already; it doesn't work like it used to. They will have to change their config directives to upgrade. Is that really a big deal? Also, the docs that Stas Bekman wrote will be outdated by this release. I can spruce those up if necessary. If I receive no response, I will assume either everyone likes it or nobody cares, and I will publish it to CPAN. 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!
Re: DIR_MERGE and .htaccess
On Wed, 5 Jul 2000, Matt Sergeant wrote: On Tue, 4 Jul 2000, Rick Myers wrote: On Jul 04, 2000 at 14:40:26 +0100, Matt Sergeant twiddled the keys to say: Shouldn't DIR_MERGE be called when .htaccess files are found at different levels, e.g: /axkit/.htaccess and /axkit/test/.htaccess I ask for /axkit/test/test.xsp I would have expected it to ask for both .htaccess files and try and merge the two using DIR_MERGE, but it doesn't. Am I missing something, or is this expected functionality? I can't answer that question, but a while back I noticed that sometimes PerlSetVar's weren't being seen by $r-dir_config as I'd expected. Namely, within the "global" section of a VirtualHost. I wrote a little module as an example, but never got around to voicing anything about it. From what I saw then, DIR_MERGE nor SERVER_MERGE ever got called at all. Maybe we're missing the same thing? Maybe. I think this is a core Apache problem. It seems that DIR_MERGE isn't called for two matching Files sections either, which is disappointing for me. I'd like to be able to go: Files *.xsp ... /Files Files example.xsp ... /Files And have both sections merged. I'm using DIR_MERGE etc to make my own config directives and I was having similar problems with it. I'm probably wrong but I think DIR_MERGE gets called when merging directives in either Location or Directory sections and not Files. Furthermore, any directives created above that section, unless they themselves are in a Location or Directory section are not merged. I dont know if this behaviour is expected or if I just suck. Either way, I found that when I called DIR_MERGE on a top level dir (whose parent is the server itself), it would get passed itself as both parent and current dir objects. I had to use Apache::CmdParms to get server config objects and merge them myself on server start. This probably doesn't help much and neither will this. DIR_MERGE never gets called at request time for me. Sample config: VirtualHost www.blah.com MyDirective On Location /dir/ MyOtherDirective On # dir merges with itself?! Location /VirtualHost DIR_MERGE does not do what I expected. Maybe I have to have this too: Location /dir/subdir/ MyOtherDirective On Location Then DIR_MERGE will get called to merge /dir/ and /dir/subdir/. Maybe. I hope you can find something usefull in my ramblings. 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!
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 main, 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!
