Re: 1.24 to 1.24_01 spinning httpds on startup (solved)

2000-12-21 Thread Doug MacEachern

On Tue, 28 Nov 2000, Michael J Schout wrote:

 About a month or 2 ago, I had posted a problem where I tried to upgrade from:
... 
 And reported that after doing this, my httpds would spin on startup.  When I
 turned on MOD_PERL_TRACE=all, it was showing that it was stuck in an infinite
 loop processing configuration stuff.  I posted the mod_perl trace for it as
 well.
 
 I have finally gotten a chance to revisit this and it turns out that what was
 causing problems was that I had in my httpd.conf:
 
 Perl
 $PerlRequire = '/some/path/file.pl';
 /Perl

this has been fixed in the cvs tree.




Re: 1.24 to 1.24_01 spinning httpds on startup (solved)

2000-11-30 Thread Ask Bjoern Hansen

On Tue, 28 Nov 2000, Michael J Schout wrote:

 Perl
 $PerlRequire = '/some/path/file.pl';
 /Perl
 
 Changing this to:
 
 Perl
 push @PerlRequire, '/some/path/file.pl';
 /Perl
 
 Fixed the problem under 1.24_01 for me and everything appears to be kosher now.
 
 Maybe the behavior of PerlRequire has changed between 1.24 and 1.24_01?  

Hmn... Happens to me too after upgrading from 1.24 to 1.24_01
(Apache 1.3.12).

#0  0x400fe7f9 in _IO_vfprintf (s=0xbf800474, 
format=0x81433b5 "_(eval %lu)", ap=0xbf80053c) at
vfprintf.c:209
#1  0x4010c0b3 in _IO_vsprintf (string=0xbf80056c "", 
format=0x81433b5 "_(eval %lu)", args=0xbf80053c) at
iovsprintf.c:47
#2  0x4010676f in sprintf (s=0xbf80056c "", 
format=0x81433b5 "_(eval %lu)") at sprintf.c:38
#3  0x811037c in Perl_pp_entereval ()
#4  0x80c9997 in perl_eval_sv ()
#5  0x808b9ee in perl_require_module ()
#6  0x808a126 in perl_section ()
#7  0x8089fac in perl_section_self_boot ()
#8  0x808816a in perl_cmd_require ()
#9  0x809ffd7 in ap_clear_module_list ()
#10 0x80a0423 in ap_handle_command ()
#11 0x8089b34 in perl_handle_command ()
#12 0x808a445 in perl_section ()
#13 0x8089fac in perl_section_self_boot ()
#14 0x808816a in perl_cmd_require ()
#15 0x809ffd7 in ap_clear_module_list ()
#16 0x80a0423 in ap_handle_command ()
#17 0x8089b34 in perl_handle_command ()
#18 0x808a445 in perl_section ()
#19 0x8089fac in perl_section_self_boot ()
[... repeating ...]

I don't see any changes to the Perl configure code...

Perl
 $PerlRequire = '/tmp/startup.pl';
/Perl

$ cat /tmp/startup.pl
warn "works?";
1;


  - ask

-- 
ask bjoern hansen - http://ask.netcetera.dk/
more than 70M impressions per day, http://valueclick.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




RE: 1.24 to 1.24_01 spinning httpds on startup (solved)

2000-11-30 Thread Geoffrey Young


I think I remember a thread on dev that talked about this...

http://archive.covalent.net/modperl-cvs/2000/09/0050.xml was maybe the cause
of the change in behavior?

HTH

--Geoff



 -Original Message-
 From: Ask Bjoern Hansen [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, November 30, 2000 3:12 AM
 To: Michael J Schout
 Cc: [EMAIL PROTECTED]
 Subject: Re: 1.24 to 1.24_01 spinning httpds on startup (solved)
 
 
 On Tue, 28 Nov 2000, Michael J Schout wrote:
 
  Perl
  $PerlRequire = '/some/path/file.pl';
  /Perl
  
  Changing this to:
  
  Perl
  push @PerlRequire, '/some/path/file.pl';
  /Perl
  
  Fixed the problem under 1.24_01 for me and everything 
 appears to be kosher now.
  
  Maybe the behavior of PerlRequire has changed between 1.24 
 and 1.24_01?  
 
 Hmn... Happens to me too after upgrading from 1.24 to 1.24_01
 (Apache 1.3.12).
 
 #0  0x400fe7f9 in _IO_vfprintf (s=0xbf800474, 
 format=0x81433b5 "_(eval %lu)", ap=0xbf80053c) at
 vfprintf.c:209
 #1  0x4010c0b3 in _IO_vsprintf (string=0xbf80056c "", 
 format=0x81433b5 "_(eval %lu)", args=0xbf80053c) at
 iovsprintf.c:47
 #2  0x4010676f in sprintf (s=0xbf80056c "", 
 format=0x81433b5 "_(eval %lu)") at sprintf.c:38
 #3  0x811037c in Perl_pp_entereval ()
 #4  0x80c9997 in perl_eval_sv ()
 #5  0x808b9ee in perl_require_module ()
 #6  0x808a126 in perl_section ()
 #7  0x8089fac in perl_section_self_boot ()
 #8  0x808816a in perl_cmd_require ()
 #9  0x809ffd7 in ap_clear_module_list ()
 #10 0x80a0423 in ap_handle_command ()
 #11 0x8089b34 in perl_handle_command ()
 #12 0x808a445 in perl_section ()
 #13 0x8089fac in perl_section_self_boot ()
 #14 0x808816a in perl_cmd_require ()
 #15 0x809ffd7 in ap_clear_module_list ()
 #16 0x80a0423 in ap_handle_command ()
 #17 0x8089b34 in perl_handle_command ()
 #18 0x808a445 in perl_section ()
 #19 0x8089fac in perl_section_self_boot ()
 [... repeating ...]
 
 I don't see any changes to the Perl configure code...
 
 Perl
  $PerlRequire = '/tmp/startup.pl';
 /Perl
 
 $ cat /tmp/startup.pl
 warn "works?";
 1;
 
 
   - ask
 
 -- 
 ask bjoern hansen - http://ask.netcetera.dk/
 more than 70M impressions per day, http://valueclick.com
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




1.24 to 1.24_01 spinning httpds on startup (solved)

2000-11-28 Thread Michael J Schout

About a month or 2 ago, I had posted a problem where I tried to upgrade from:

Redhat Linux 6.2,
perl 5.6.0
Apache 1.3.12
mod_perl 1.24
mod_ssl 2.6.6

to 

Redhat Linux 6.2
perl 5.6.0
Apache 1.3.14
mod_perl 1.24_01
mod_ssl 2.7.1

And reported that after doing this, my httpds would spin on startup.  When I
turned on MOD_PERL_TRACE=all, it was showing that it was stuck in an infinite
loop processing configuration stuff.  I posted the mod_perl trace for it as
well.

I have finally gotten a chance to revisit this and it turns out that what was
causing problems was that I had in my httpd.conf:

Perl
$PerlRequire = '/some/path/file.pl';
/Perl

Changing this to:

Perl
push @PerlRequire, '/some/path/file.pl';
/Perl

Fixed the problem under 1.24_01 for me and everything appears to be kosher now.

Maybe the behavior of PerlRequire has changed between 1.24 and 1.24_01?  

Anyways, I wanted to post this to the list in hopes that this might help others
who may have stumbled onto this problem.

Regards,
Mike



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]