RE: Trouble with AxKit at runtime - XML parsing stage
I take your answer as a polite confirmation that I am the only one to make that mistake :-) Well, this seems to be the case. Now that I know the problem cause, this *is* obvious. Still, the guide doesn't clear things IMHO for one under the same weird false assumption that I had: "but the parent does not exit. Instead, the parent re-reads its configuration files, spawns a new set of child processes and continues to serve requests. It is almost equivalent to stopping and then restarting the server. " It seems a subtle point indeed - that although the libperl.so is external, it has already been mapped into the core back at the runtime loader stage, and will never be reloaded. Until I asked myself this question in this form (what exactly happens with the apache core and why isn't the module reloaded?) I didn't get it. I wonder why I was so sure that apache re-exec's itself. I am sure I saw it in some public domain server after our homegrown webserver implementation had done it that way, some 6 years ago. Was it cern httpd then, rather than ncsa/apache? Well, I could also notice there is no "-listen-fd 4" or smth. argument in the respawned httpd process cmdline, to tell the restarting process where to take the listening socket... I like this technique because it ensures there is no resource leak (other than, possibly, forgotten open fds) on restart. Do you know if really many people suffer from the memory leaks you mention at the link you gave? Should I patch apache so it has such restart semantics in addition to (as another sighandler? configurable?)/instead the current HUP behaviour? I mean, will such patch be really useful for someone? Vassilii -Original Message- From: Stas Bekman [mailto:[EMAIL PROTECTED]] Sent: Friday, December 15, 2000 11:50 AM To: Khachaturov, Vassilii Cc: '[EMAIL PROTECTED]' Subject: RE: Trouble with AxKit at runtime - XML parsing stage Stas: maybe you could add a small section to your Guide elaborating on dependencies of things and what has to be remade when things are upgraded? (Or I am the only one to make such stupid mistake?) Well, it's documentated: http://perl.apache.org/guide/control.html#Restarting_Techniques Of course you cannot send a process the HUP signal and expect it to fully stop and re-start, unless you know that it does that. Isn't it obvious that when you upgrade some binary you should quit the program that's depending on it and restart it?
Re: Trouble with AxKit at runtime - XML parsing stage
I believe that the Bizzar copy of array problem is related to a bug in
Perl 5.6 that was patched a while ago.
Make sure you are running the latest version of perl5.6
Also there is an AxKit users mailing list that you can post these
questions to:
[EMAIL PROTECTED]
--
Owen
[Snip]
[AxKit] : handler called for /x/test.xml
[AxKit] : checking if we process this resource
[AxKit] : media: screen, preferred style: #default
[AxKit] : getting styles and external entities from the XML
[AxKit] : styles and external entities not cached - calling get_styles()
[AxKit] : get_styles: creating XML::Parser
[AxKit] : get_styles: calling
XML::Parser-parse('/usr/local/apache/htdocs/x/test.xml')
[Wed Dec 13 16:17:27 2000] [error] [client 172.24.223.142] [AxKit]
[UnCaught] Bizarre copy of ARRAY in aassign at
/usr/local/lib/perl5/5.6.0/Carp/Heavy.pm line 79.
RE: Trouble with AxKit at runtime - XML parsing stage
Well, it's kind of recent. I downloaded built it just a couple of weeks ago, 10656 -rw-r--r-- 1 root other5443601 Nov 30 15:40 /usr/local/perl/CPAN/sources/authors/id/G/GS/GSAR/perl-5.6.0.tar.gz and also cpan doesn't give me any reinstall recommendations for it, which I take as a sign for running the correct version. Can you point me to the patch (or just tell me its date on cpan) you've mentioned so I can check whether it made its way to my perl? Thanks for pointing to the axkit list, I'll subscribe it for sure. I was just unsure that the problem is axkit-specific (I can be missing smth with apache/mod_perl/XML/dependant modules as well), so I wanted people with relevant expertise but not interested in AxKit itself have a chance. V. -Original Message- From: Owen Stenseth [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 14, 2000 10:37 AM To: Khachaturov, Vassilii Cc: '[EMAIL PROTECTED]' Subject: Re: Trouble with AxKit at runtime - XML parsing stage I believe that the Bizzar copy of array problem is related to a bug in Perl 5.6 that was patched a while ago. Make sure you are running the latest version of perl5.6
Re: Trouble with AxKit at runtime - XML parsing stage
On Thu, 14 Dec 2000, Owen Stenseth wrote: I believe that the Bizzar copy of array problem is related to a bug in Perl 5.6 that was patched a while ago. Make sure you are running the latest version of perl5.6 The latest version of 5.6 _is_ 5.6.0. The bizarre copy thing is fixed in CVS and 5.6.1 should incorporate this change. -dave /*== www.urth.org We await the New Sun ==*/
Re: Trouble with AxKit at runtime - XML parsing stage
Dave Rolsky wrote: On Thu, 14 Dec 2000, Owen Stenseth wrote: I believe that the Bizzar copy of array problem is related to a bug in Perl 5.6 that was patched a while ago. Make sure you are running the latest version of perl5.6 The latest version of 5.6 _is_ 5.6.0. The bizarre copy thing is fixed in CVS and 5.6.1 should incorporate this change. Ahh, my mistake thanks for the clarification. -- Owen
RE: Trouble with AxKit at runtime - XML parsing stage
I have followed the advice given by
http://axkit.org/cgi-bin/ezmlm-cgi?3:mss:798:200012:gigblllnbhflgdoplaci
with similar symptoms, and just reinstalled 5.6.0 from ActiveState 620
source.
Then I reinstalled XML::Parser and AxKit forcibly.
Unfortunately, the error still persists. :-(((
Any other ideas? Any ideas on the minor problem (1) I mentioned earlier on
this thread?
(See this thread earlier at
http://forum.swarthmore.edu/epigone/modperl/spilwhudimp )
V.
-Original Message-
From: Owen Stenseth [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 14, 2000 10:37 AM
To: Khachaturov, Vassilii
Cc: '[EMAIL PROTECTED]'
Subject: Re: Trouble with AxKit at runtime - XML parsing stage
I believe that the Bizzar copy of array problem is related to a bug in
Perl 5.6 that was patched a while ago.
Make sure you are running the latest version of perl5.6
Also there is an AxKit users mailing list that you can post these
questions to:
[EMAIL PROTECTED]
--
Owen
[Snip]
[AxKit] : handler called for /x/test.xml
[AxKit] : checking if we process this resource
[AxKit] : media: screen, preferred style: #default
[AxKit] : getting styles and external entities from the XML
[AxKit] : styles and external entities not cached - calling get_styles()
[AxKit] : get_styles: creating XML::Parser
[AxKit] : get_styles: calling
XML::Parser-parse('/usr/local/apache/htdocs/x/test.xml')
[Wed Dec 13 16:17:27 2000] [error] [client 172.24.223.142] [AxKit]
[UnCaught] Bizarre copy of ARRAY in aassign at
/usr/local/lib/perl5/5.6.0/Carp/Heavy.pm line 79.
RE: Trouble with AxKit at runtime - XML parsing stage
http://bugs.perl.org/perlbug.cgi?req=querybody=Bizarre+copy seems to yield only one bug relevant to my particular error message case - http://bugs.perl.org/perlbug.cgi?req=bidbid=20001207.005range=6012format= H which is still open. No patch/patchid seen there. Did you mean this bug, or another? Is there some informal patch around? V. -Original Message- From: Dave Rolsky [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 14, 2000 12:28 PM To: Khachaturov, Vassilii; '[EMAIL PROTECTED]' Subject: Re: Trouble with AxKit at runtime - XML parsing stage On Thu, 14 Dec 2000, Owen Stenseth wrote: I believe that the Bizzar copy of array problem is related to a bug in Perl 5.6 that was patched a while ago. Make sure you are running the latest version of perl5.6 The latest version of 5.6 _is_ 5.6.0. The bizarre copy thing is fixed in CVS and 5.6.1 should incorporate this change. -dave /*== www.urth.org We await the New Sun ==*/
RE: Trouble with AxKit at runtime - XML parsing stage
On Thu, 14 Dec 2000, Khachaturov, Vassilii wrote: http://bugs.perl.org/perlbug.cgi?req=querybody=Bizarre+copy seems to yield only one bug relevant to my particular error message case - http://bugs.perl.org/perlbug.cgi?req=bidbid=20001207.005range=6012format= H which is still open. No patch/patchid seen there. Did you mean this bug, or another? Is there some informal patch around? I'm pretty sure that's the bug. Sarathy said it was patched ages ago. I don't know why the bug's still open (you might want to let P5P know about that). -dave /*== www.urth.org We await the New Sun ==*/
RE: Trouble with AxKit at runtime - XML parsing stage
I am sad to inform you that this patch is obsolete. The CLEAR_ARGARRAY
has evolved a lot since this message. It is now in 5.6.0
#define CLEAR_ARGARRAY(ary) \
STMT_START { \
AvMAX(ary) += AvARRAY(ary) - AvALLOC(ary); \
SvPVX(ary) = (char*)AvALLOC(ary);\
AvFILLp(ary) = -1; \
} STMT_END
without any conditioning on the USE_ITHREADS #define.
So, my problem is still hurting me.
(To catchup, see this thread earlier at
http://forum.swarthmore.edu/epigone/modperl/spilwhudimp )
V.
-Original Message-
From: Khachaturov, Vassilii
Sent: Thursday, December 14, 2000 4:58 PM
To: 'Dave Rolsky'; '[EMAIL PROTECTED]'
Cc: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
Subject: RE: Trouble with AxKit at runtime - XML parsing stage
Yes, indeed, it's mentioned on
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2000-06/msg00200.html
in GSAR's own message!
P5P: why is the bug mentioned in the Orig Msg below still open then?
Thanks a lot to all that helped or tried to! Sorry for missing this on the
AxKit FAQ earlier.
(I will be posting further if this doesn't close the problem in my AxKit
case. It's possible
as there are # of bizarre copy bugs in different contexts)
RE: Trouble with AxKit at runtime - XML parsing stage
Yes, indeed, it's mentioned on http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2000-06/msg00200.html in GSAR's own message! P5P: why is the bug mentioned in the Orig Msg below still open then? Thanks a lot to all that helped or tried to! Sorry for missing this on the AxKit FAQ earlier. (I will be posting further if this doesn't close the problem in my AxKit case. It's possible as there are # of bizarre copy bugs in different contexts) V. -Original Message- From: Dave Rolsky [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 14, 2000 4:20 PM To: Khachaturov, Vassilii Cc: '[EMAIL PROTECTED]' Subject: RE: Trouble with AxKit at runtime - XML parsing stage On Thu, 14 Dec 2000, Khachaturov, Vassilii wrote: http://bugs.perl.org/perlbug.cgi?req=querybody=Bizarre+copy seems to yield only one bug relevant to my particular error message case - http://bugs.perl.org/perlbug.cgi?req=bidbid=20001207.005range=6012format= H which is still open. No patch/patchid seen there. Did you mean this bug, or another? Is there some informal patch around? I'm pretty sure that's the bug. Sarathy said it was patched ages ago. I don't know why the bug's still open (you might want to let P5P know about that). -dave /*== www.urth.org We await the New Sun ==*/
Re: Trouble with AxKit at runtime - XML parsing stage
Dave Rolsky wrote: On Thu, 14 Dec 2000, Khachaturov, Vassilii wrote: http://bugs.perl.org/perlbug.cgi?req=querybody=Bizarre+copy seems to yield only one bug relevant to my particular error message case - http://bugs.perl.org/perlbug.cgi?req=bidbid=20001207.005range=6012format= H which is still open. No patch/patchid seen there. Did you mean this bug, or another? Is there some informal patch around? I'm pretty sure that's the bug. Sarathy said it was patched ages ago. I don't know why the bug's still open (you might want to let P5P know about that). The patch is here: http://www.geocrawler.com/archives/3/182/2000/6/0/3863601/
RE: Trouble with AxKit at runtime - XML parsing stage
Unfortunately, this is the same obsolete patch I mentioned http://forum.swarthmore.edu/epigone/modperl/spilwhudimp/6B1DF6EEBA51D31182F2 [EMAIL PROTECTED] and it is irrelevant for the perl5.6.0 currently on CPAN :-( -Original Message- From: Jeremy Howard [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 14, 2000 6:43 PM To: Dave Rolsky; Khachaturov, Vassilii Cc: [EMAIL PROTECTED]; Stas Bekman Subject: Re: Trouble with AxKit at runtime - XML parsing stage Dave Rolsky wrote: On Thu, 14 Dec 2000, Khachaturov, Vassilii wrote: http://bugs.perl.org/perlbug.cgi?req=querybody=Bizarre+copy seems to yield only one bug relevant to my particular error message case - http://bugs.perl.org/perlbug.cgi?req=bidbid=20001207.005range=6012format= H which is still open. No patch/patchid seen there. Did you mean this bug, or another? Is there some informal patch around? I'm pretty sure that's the bug. Sarathy said it was patched ages ago. I don't know why the bug's still open (you might want to let P5P know about that). The patch is here: http://www.geocrawler.com/archives/3/182/2000/6/0/3863601/
