On Tue, 14 Aug 2001, Aleksandr Vladimirskiy wrote:
Hi all,
I am running a perl 5.6.0, mod_perl 1.26, apache 1.3.19 on Solaris 2.6. I
get the following error in my logs:
[Tue Aug 14 10:45:10 2001] [notice] child pid 2630 exit signal
Segmentation Fault (11)
It looks like the child
Stas Bekman wrote:
No need for an apology :-) The trick is to build perl using the
Solaris malloc (-Dusemymalloc as a flag to Configure), then apache,
mod_perl and perl all agree on who manages memory.
Might I suggest that this golden piece of information find it's way into the
On Thu, 16 Aug 2001, Alan Burlison wrote:
Stas Bekman wrote:
No need for an apology :-) The trick is to build perl using the
Solaris malloc (-Dusemymalloc as a flag to Configure), then apache,
mod_perl and perl all agree on who manages memory.
Might I suggest that this golden
Thanks very much to all of you. I've upgraded my perl distro to 5.6.1 and
recompiled everything and the children stopped dying.
Alex
On Thu, 16 Aug 2001, Stas Bekman wrote:
The definitive answer is there for at least 2 years: If in doubt compile
statically, which covers Solaris as well. Why having a special case?
because solaris is a special case. as is any platform where perl defaults
to using its own malloc. the
On Thu, 16 Aug 2001, Stas Bekman wrote:
Currently what I've is:
* How do I build on Solaris with DSO?
= Build perl and mod_perl using the system malloc
that should be any platform where perl defaults to using its own malloc,
that is, if:
% perl -V:usemymalloc
reports:
usemymalloc='y'
On Thu, Aug 16, 2001 at 09:35:43AM -0700, Doug MacEachern wrote:
that should be any platform where perl defaults to using its own malloc,
that is, if:
% perl -V:usemymalloc
reports:
usemymalloc='y'
which is fine if:
% perl -V:bincompat5005
reports:
bincompat5005='undef';
but the
On Thu, 16 Aug 2001, Alex Povolotsky wrote:
This is perl, v5.6.1 built for sun4-solaris
# perl -V:usemymalloc
usemymalloc='n';
that's fine.
Seems like I'm suffering from dying children problem... My main apache
dies sometimes, bringing neraly everything (well, except
server-status)
No need for an apology :-) The trick is to build perl using the
Solaris malloc (-Dusemymalloc as a flag to Configure), then apache,
mod_perl and perl all agree on who manages memory.
Might I suggest that this golden piece of information find it's
way into the guide? It's so rare
-Original Message-
From: Rob Bloodgood [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 16, 2001 11:20 AM
To: Stas Bekman
Cc: mod_perl
Subject: RE: Children dying
sigh... I didn't see the other thread that spawned from my orignal post...
rendering this reply redundant. Apologies.
Hi Andrew,
On Tue, 14 Aug 2001, Andrew Ho wrote:
AVI am running a perl 5.6.0, mod_perl 1.26, apache 1.3.19 on Solaris 2.6.
[snip]
AV[Tue Aug 14 10:45:10 2001] [notice] child pid 2630 exit signal Segmentation Fault
(11)
[snip]
A few other folks have given useful references on how to get
Andrew Ho wrote:
A few other folks have given useful references on how to get stack traces,
as well as some other common causes of core dumps (compiling Apache with
its bundled expat is a big one). Here's another one--did you build
mod_perl on Solaris as a DSO? In general, you want to
Vasily S. Petrushin wrote:
Untrue. We ship mod_perl in Solaris 8 as a DSO, and it works fine.
Fine, point us please to documentation how to do it.
http://cpan.valueclick.com/authors/Doug_MacEachern/mod_perl-1.26.tar.gz
Alan Burlison
Hello,
AVI am running a perl 5.6.0, mod_perl 1.26, apache 1.3.19 on Solaris 2.6.
AHIn general, you want to compile mod_perl statically on Solaris because
AHit will core otherwise.
ABUntrue. We ship mod_perl in Solaris 8 as a DSO, and it works fine.
I apologize. Let me qualify my original
Andrew Ho wrote:
ABUntrue. We ship mod_perl in Solaris 8 as a DSO, and it works fine.
I apologize. Let me qualify my original statement. In general, you want to
compile mod_perl statically on Solaris 2.6 or 2.7 because in many
instances, it core dumps when built as a DSO. FWIW, my
AB Untrue. We ship mod_perl in Solaris 8 as a DSO, and it works
fine.
I apologize. Let me qualify my original statement. In general, you
want to compile mod_perl statically on Solaris 2.6 or 2.7 because
in many instances, it core dumps when built as a DSO. FWIW, my
particular
On Wed, 15 Aug 2001, Rob Bloodgood wrote:
AB Untrue. We ship mod_perl in Solaris 8 as a DSO, and it works
fine.
I apologize. Let me qualify my original statement. In general, you
want to compile mod_perl statically on Solaris 2.6 or 2.7 because
in many instances, it core dumps
On Tue, Aug 14, 2001 at 10:48:48AM -0400, Aleksandr Vladimirskiy wrote:
Hi all,
I am running a perl 5.6.0, mod_perl 1.26, apache 1.3.19 on Solaris 2.6. I
get the following error in my logs:
[Tue Aug 14 10:45:10 2001] [notice] child pid 2630 exit signal
Segmentation Fault (11)
It
Jim Smith wrote:
On Tue, Aug 14, 2001 at 10:48:48AM -0400, Aleksandr Vladimirskiy wrote:
Hi all,
I am running a perl 5.6.0, mod_perl 1.26, apache 1.3.19 on Solaris 2.6. I
get the following error in my logs:
[Tue Aug 14 10:45:10 2001] [notice] child pid 2630 exit signal
On Tue, 14 Aug 2001, Aleksandr Vladimirskiy wrote:
I am running a perl 5.6.0, mod_perl 1.26, apache 1.3.19 on Solaris 2.6. I
get the following error in my logs:
[Tue Aug 14 10:45:10 2001] [notice] child pid 2630 exit signal
Segmentation Fault (11)
It looks like the child serves a request
This happens whenever I do anything with mod_perl - serve a URL by a
handler I wrote or by a cgi script under Apache::Registry. If I knew what
was causing this I wouldn't be asking this list.
Alex
On Tue, 14 Aug 2001, Rasoul Hajikhani wrote:
Jim Smith wrote:
On Tue, Aug 14, 2001 at
I have also experienced the same without any [known] xml parsers or
templates.
-Original Message-
From: Aleksandr Vladimirskiy [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 1:54 PM
To: Rasoul Hajikhani
Cc: Jim Smith; [EMAIL PROTECTED]
Subject: Re: Children dying
Hello,
AVI am running a perl 5.6.0, mod_perl 1.26, apache 1.3.19 on Solaris 2.6.
AVI get the following error in my logs:
AV
AV[Tue Aug 14 10:45:10 2001] [notice] child pid 2630 exit signal Segmentation Fault
(11)
AV
AVIt looks like the child serves a request and immidiately dies.
A few other
Hi Andrew, thanks for the suggestions. I compiled mod_perl statically.
I haven't seen expat mentioned anywhere, can you expand on that?
Thanks
Alex
On Tue, 14 Aug 2001, Andrew Ho wrote:
Hello,
AVI am running a perl 5.6.0, mod_perl 1.26, apache 1.3.19 on Solaris 2.6.
AVI get the following
Hi Aleksandr,
Aleksandr Vladimirskiy wrote:
Hi Andrew, thanks for the suggestions. I compiled mod_perl statically.
I haven't seen expat mentioned anywhere, can you expand on that?
You can check by doing:
strings /path/to/apache/bin/httpd | grep -i XML
If you get anything back from that,
Hey, thanks I ran the command and no output, so I guess I don't have
expat?
On Tue, 14 Aug 2001, Kip Hampton wrote:
Hi Aleksandr,
Aleksandr Vladimirskiy wrote:
Hi Andrew, thanks for the suggestions. I compiled mod_perl statically.
I haven't seen expat mentioned anywhere, can you expand
Aleksandr Vladimirskiy [EMAIL PROTECTED] said something to this effect on 08/14/2001:
I am running a perl 5.6.0, mod_perl 1.26, apache 1.3.19 on Solaris 2.6.
I get the following error in my logs:
perl 5.6.0 has DynaLoader bug that minifests itself under
mod_perl. Upgrade to 5.6.1, downgrade to
I've got the same configuration and it's working fine.
No seg faults unless I cause'em.
If nothing else is giving you adequate information,
you can always remove code until it works. Not
very elegant but it works consistently.
--Jeff
On Tue, 14 Aug 2001, darren chamberlain wrote:
Aleksandr
28 matches
Mail list logo
