Segfaults with File::LibMagic

Hello, I've an Ubuntu 16.04 LTS , build my own perl5.20 with mod_perl-2.0.9 When I configure my app i get "Status OK " when running 'apache2ctl configtest' , but when I call 'apache2ctl restart' it segfaults, sometimes just with writing "segmentat

Re: [mp2] Segfaults in mpxs_Apache2__RequestRec_rflush

Hi, we use apache2-mpm-prefork, can threading issues still be an explanation for this kind of segfaults? It seems rather complicated to backport version 2.0.8 to wheezy on my first try. Regards Damian Am 27.02.2015 09:07, schrieb Steve Hay: On 24 February 2015 at 16:53, Damian Lukowski

Re: [mp2] Segfaults in mpxs_Apache2__RequestRec_rflush

On 24 February 2015 at 16:53, Damian Lukowski wrote: > Hi, > > we are encountering occasional connection disruptions caused by segmentation > faults in xs/Apache2/RequestIO/Apache2__RequestIO.h Our application is a > PerlResponseHandler based on Catalyst::View::Mason on Debian Wheezy. The > segfau

[mp2] Segfaults in mpxs_Apache2__RequestRec_rflush

Hi, we are encountering occasional connection disruptions caused by segmentation faults in xs/Apache2/RequestIO/Apache2__RequestIO.h Our application is a PerlResponseHandler based on Catalyst::View::Mason on Debian Wheezy. The segfault seems to always happen in mpxs_Apache2__RequestRec_rflush(). S

save_gp segfaults during restart

Something odd is going on with errsv in trunk. Without preloading apr::error I see lots of segfaults, but even preloading it doesn't fix them all. I'm running the latest 2.4 release with event. Testing now with the savegp calls commented out... Sent from my iPhone

Re: mod_perl segfaults, can't start Apache

Chris, that seems to have solved my problems. Though, I used the package env config as described in the Gentoo Wiki ( http://wiki.gentoo.org/wiki//etc/portage/env). For those having this problem, simple create the following problems and rebuild perl and mod_perl /etc/portage/env/www-apache_mod_p

Re: mod_perl segfaults, can't start Apache

I've been seeing the same problem on Gentoo. I think this is the same issue as described at http://www.gossamer-threads.com/lists/perl/porters/263222 . When perl is compiled, the optimisation switches in the CFLAGS in make.conf are used, together with some autodetected ones. When perl modules, s

Re: mod_perl segfaults, can't start Apache

> Any ideas on what to look for to determine the problem? That's amply documented on the homepage: → Reporting Bugs → → mod_perl 2.0 → → Resolving Segmentation Faults →

Re: mod_perl segfaults, can't start Apache

-6194 > Fax: (212) 994-4260 > Mobile: (917) 488-6248 > jnar...@seniorbridge.com > seniorbridge.com <http://www.seniorbridge.com/> > > [image: SeniorBridge] > > *From:* John Manko [mailto:john.ma...@gmail.com] > *Sent:* Monday, June 25, 2012 2:18 PM > *To:* Josh Narins &

Re: mod_perl segfaults, can't start Apache

ly prohibited. In said event, kindly reply to the sender > and destroy all entries of this message and any attachments from your > system. Thank you. > > *From:* John Manko [mailto:john.ma...@gmail.com] > *Sent:* Monday, June 25, 2012 12:58 PM > *To:* modperl@perl.apache.org >

Re: mod_perl segfaults, can't start Apache

Do you happen to be using a Xen virtual machine and running a redhat 6.1 or CentOS 6.1+ version of linux. I actually had opened a very similar ticket to this a couple of weeks back. The write-up here was the apparent problem that I'm assuming was causing my issue as a bug in glibc. https://bugzi

RE: mod_perl segfaults, can't start Apache

: John Manko [mailto:john.ma...@gmail.com] Sent: Monday, June 25, 2012 12:58 PM To: modperl@perl.apache.org Subject: mod_perl segfaults, can't start Apache mod_perl is failing with Apache, and I'm having trouble figuring out why. I'm running under Gentoo. mod_perl version 2.0.7 apa

mod_perl segfaults, can't start Apache

mod_perl is failing with Apache, and I'm having trouble figuring out why. I'm running under Gentoo. mod_perl version 2.0.7 apache version 2.2.22-r1, build with threads and worker MPM libperl version 5.10.1-r1 perl version 5.16.0 with ithreads support # /etc/init.d/apache2 start * Starting apach

Re: mod_perl 2.0.5 segfaults

On 12.12.2011 21:06, Torsten Förtsch wrote: On Monday, 12 December 2011 20:51:12 Jiří Pavlovský wrote: I wanted to upgrade my CentOS5 based system to new perl/mod_perl. So I build my perl 5.14.2 and mod_perl 2.0.5. I'm getting segfaults whenever I try to access the server. If it's

Re: mod_perl 2.0.5 segfaults

On Monday, 12 December 2011 20:51:12 Jiří Pavlovský wrote: > I wanted to upgrade my CentOS5 based system to new perl/mod_perl. > So I build my perl 5.14.2 and mod_perl 2.0.5. > > I'm getting segfaults whenever I try to access the server. If it's worker MPM try trunk. Tor

mod_perl 2.0.5 segfaults

Hello, I wanted to upgrade my CentOS5 based system to new perl/mod_perl. So I build my perl 5.14.2 and mod_perl 2.0.5. I'm getting segfaults whenever I try to access the server. I tried patch suggested here: that doesn't help.

Re: Re: I think AuthCookie(DBI) is causing segfaults?

On Sat, 2010-11-13 at 14:15 +0100, Tosh Cooey wrote: > I'm not quite ready to declare victory, but I think installing DBD from > source and getting more recent versions of DBD was the problem, and it > seems there's a lot of little things going wrong with DBD. > > What's going on there? When di

Re: Re: I think AuthCookie(DBI) is causing segfaults?

I'm not quite ready to declare victory, but I think installing DBD from source and getting more recent versions of DBD was the problem, and it seems there's a lot of little things going wrong with DBD. What's going on there? When did DBD::mysql become so problematic? It used to run so flawle

Re: I think AuthCookie(DBI) is causing segfaults?

Le jeudi 11 novembre 2010 à 00:58 +0100, Tosh Cooey a écrit : > Maybe Apache MPM prefork? How can I tell? Please read the section "How to Report Problems" on this page : http://perl.apache.org/docs/1.0/guide/help.html That should help quite a bit. -- Vincent Veyron http://marica.fr/ Lo

Re: I think AuthCookie(DBI) is causing segfaults?

Hi Tuomo, thank-you that was really helpful. I'm running prefork it seems. Here's the list if that's helpful: core.c mod_log_config.c mod_logio.c prefork.c http_core.c mod_so.c Also perhaps helpful is that I'm on Ubuntu 9.04 Jaunty with the latest libdbd-mysql-perl 4.008-1 which wa

Re: I think AuthCookie(DBI) is causing segfaults?

On Thu, Nov 11, 2010 at 12:58:23AM +0100, Tosh Cooey wrote: > Maybe Apache MPM prefork? How can I tell? Running httpd with the -l (ell) command line option will print a list of module names. If you see "prefork.c", you are using prefork, and if you see "worker.c", you are using the threaded MPM

Re: I think AuthCookie(DBI) is causing segfaults?

, then when a user tries to connect Apache segfaults. Here is debug output: [Wed Nov 10 22:37:04 2010] [error] auth_type DISKO::AUTH [Wed Nov 10 22:37:04 2010] [error] r=Apache2::RequestRec=SCALAR(0x81f6f290) authtype=DISKO::AUTH [Wed Nov 10 22:37:04 2010] [error] auth_name berlin3 [Wed Nov 10 22:37

Re: I think AuthCookie(DBI) is causing segfaults?

kieDBI.pm > for authentication against the DB. > > If the application has not been used for a while, a few hours, then when a > user tries to connect Apache segfaults.  Here is debug output: > > [Wed Nov 10 22:37:04 2010] [error] auth_type DISKO::AUTH > [Wed Nov 10 22:37:04

I think AuthCookie(DBI) is causing segfaults?

, then when a user tries to connect Apache segfaults. Here is debug output: [Wed Nov 10 22:37:04 2010] [error] auth_type DISKO::AUTH [Wed Nov 10 22:37:04 2010] [error] r=Apache2::RequestRec=SCALAR(0x81f6f290) authtype=DISKO::AUTH [Wed Nov 10 22:37:04 2010] [error] auth_name berlin3 [Wed Nov 10

Re: add_config proxypass segfaults.

Okay sorry my fault. I missed a quote. in the line $r->filename('proxy:http://www.nu.nl/); Now it works perfectly. Thank you very much for the golden tip. :-)

Re: add_config proxypass segfaults.

iment with it. I did move the code to the PerlTransHandler and the PerlMapToStorageHandler but the same effect. I thought it had something to do with the / but now I only get segfaults notmatter of I put slashes or not I am sure I saw it working. I did get results before. Anyway I an

Re: intermittent segfaults, ssl?

enSSL/0.9.8g > mod_apreq2-20051231/2.6.0 mod_perl/2.0.4 Perl/v5.10.0 > I'm also using HTML::Mason > > I've been getting intermittent segfaults like this: > child pid 10142 exit signal Segmentation fault (11) > ever since in installed Apache2 in March. > >

Re: intermittent segfaults, ssl?

mod_apreq2-20051231/2.6.0 mod_perl/2.0.4 Perl/v5.10.0 I'm also using HTML::Mason I've been getting intermittent segfaults like this: child pid 10142 exit signal Segmentation fault (11) ever since in installed Apache2 in March. I am going to try to debug this, but I thought I would ask

intermittent segfaults, ssl?

Hi, I have a server like this: Server Version: Apache/2.2.9 (Debian) mod_ssl/2.2.9 OpenSSL/0.9.8g mod_apreq2-20051231/2.6.0 mod_perl/2.0.4 Perl/v5.10.0 I'm also using HTML::Mason I've been getting intermittent segfaults like this: child pid 10142 exit signal Segmentation

Re: AW: print throwing intermittent Segfaults

Hello, I started to see the following when I setup a new server on CentOS 5.4 and installed perl modules from CPAN on Dec. 4: Denis Banovic wrote: This is from the error_log from the RedHat 5 Production machine: Apache2::RequestIO::print: (103) Software caused connection abort at The guys

AW: print throwing intermittent Segfaults [ solved ]

Hi Morten, Thanks a lot, By putting an eval around the code I found out, that the segfault was produced by next request to the same child after the $r->print failed. $r->print is still failing from time to time, but it's not producing segfaults anymore! Thanks Denis -Ur

RE: AW: print throwing intermittent Segfaults

: Re: AW: print throwing intermittent Segfaults Denis Banovic wrote: > Hi Willian, > > Thanks for your checklist, I've run through it, segfaults still there... > Right now it takes less then a minute from apache restart to the first > segfault. > This is from the error_lo

Re: AW: print throwing intermittent Segfaults

Denis Banovic wrote: Hi Willian, Thanks for your checklist, I've run through it, segfaults still there... Right now it takes less then a minute from apache restart to the first segfault. This is from the error_log from the RedHat 5 Production machine: Apache2::RequestIO::print: (103) Sof

AW: print throwing intermittent Segfaults

Hi Willian, Thanks for your checklist, I've run through it, segfaults still there... Right now it takes less then a minute from apache restart to the first segfault. This is from the error_log from the RedHat 5 Production machine: Apache2::RequestIO::print: (103) Software caused connection

Re: print throwing intermittent Segfaults

This is the list of stuff I usually start with when I get a problem that doesn't seem to be tied to a particular code path. * code path - perhaps a particular code path is only being exercised rarely, and it has a bug * forking - when child dies, all open descriptors in it's name space also ge

print throwing intermittent Segfaults

Hi Everybody, I'm having big problems with mod_perl throwing intermittent Segmentation faults our production machines on RHEL 4 & 5. To be able to produce a core dump on this segfaults I've installed mod_dumpcore from this tutorial: http://mituzas.lt/2009/09/26/getting-apache

Trivial changes to the Apache configuration result in segfaults for TWiki (installed as a mod_perl based application)

Hello All, I'm having a very strange problem with a mod_perl application: TWiki. Unrelated changes to the httpd.conf like adding an Alias or an Location section, or even adding or removing a comment result in segfaults in that application. Other applications, either cgi or Apache::Registry

intermittent segfaults, and weird messages in the error log

I've been getting intermittent segfaults for a couple of days now on our dev server, and i'm not really sure why. I can more or less reproduce them, but it's a hit or miss process. It only seems to affect 2 handlers for some reason, and based on what i'm seeing it

running into segfaults when migrating older mod_perl site to new server

Hi all, I have to move a site I made years ago in mod_perl to a new server, and now that I have, I keep running into segmentation faults when I load any of the pages: [Tue Jun 3 15:58:13 2008] [notice] child pid 12206 exit signal Segmentation fault (11) I have to admit, it's been a VERY long ti

Re: [mp 2.0.4-dev] mod_perl segfaults httpd with simple CGI redirect

On Nov 21, 2007 3:26 PM, David Eisner <[EMAIL PROTECTED]> wrote: > Second question: Is it a bug in mod_perl if referencing an old > Apache2::RequestRec object segfaults the server? It's certainly not desired behavior, but it's a tough thing to avoid. That code is provid

Re: [mp 2.0.4-dev] mod_perl segfaults httpd with simple CGI redirect

hat's going on. And I now have PerlWarn on (though it's still not warning me about that problem for some reason). Second question: Is it a bug in mod_perl if referencing an old Apache2::RequestRec object segfaults the server? I'd expect to get incorrect/unpredictable behavior and pe

Re: [mp 2.0.4-dev] mod_perl segfaults httpd with simple CGI redirect

On Nov 21, 2007 9:54 AM, David Eisner <[EMAIL PROTECTED]> wrote: > httpd segfaults when I access this CGI, on the second or subsequent > access (but not the first) after restarting the server: > > use CGI qw/:standard/; > use strict; > > my $q = CGI-&g

[mp 2.0.4-dev] mod_perl segfaults httpd with simple CGI redirect

-8<-- Start Bug Report 8<-- 1. Problem Description: [System: Solaris 9, apache-2.0.61, Perl 5.8.8, mod_perl 2.0.3, and also mod_perl 2.0.4-dev (from svn checkout yesterday). httpd segfaults when I access this CGI, on the second or subsequent acces

[mp2] mod_perl segfaults in XS_Apache2__RequestRec_send_cgi_header

-8<-- Start Bug Report 8<-- 1. Problem Description: Summary: mod_perl is making httpd segfault. I'm developing a PerlAccessHandler that will check for a cookie to see if the user has accepted a legal agreement before allowing them to visit a page. If the c

[mp1] Segfaults in ap_headers_out

Hi folks, About once every 15-45 minutes or so a httpd process will segfault when serving a modperl page. I've built apache httpd, modperl and perl with debuging symbols, and have gotten a few core images. Here are the relvent software versions: FreeBSD 6.1-RELEASE-p14 running an SMP kernel Per

Re: Troubleshooting Apache2 Segfaults

On 1/24/07, Robert Landrum <[EMAIL PROTECTED]> wrote: Perrin Harkins wrote: > My guess is that $self has a lifespan longer than one request, so you > are trying to use a $r object from a previous request. Would $r still be defined in that instance? Yes. What you're checking is that the refere

Re: Troubleshooting Apache2 Segfaults

Perrin Harkins wrote: My guess is that $self has a lifespan longer than one request, so you are trying to use a $r object from a previous request. Would $r still be defined in that instance? Rob

Re: Troubleshooting Apache2 Segfaults

On 1/24/07, Joel Gwynn <[EMAIL PROTECTED]> wrote: My understanding is that PerlSetVar is not a per-request directive. What am I missing? You mean dir_config? It's not per-request, but I'm guessing that $r in your code is an Apache2::RequestRec object, which is per-request. You have to call dir

Re: Troubleshooting Apache2 Segfaults

On 1/24/07, Perrin Harkins <[EMAIL PROTECTED]> wrote: On 1/24/07, Joel Gwynn <[EMAIL PROTECTED]> wrote: > OK. I replaced that line with a hard-coded file path, and now it's > looking much better. So I guess it's something about the Request > object. My guess is that $self has a lifespan longer

Re: Troubleshooting Apache2 Segfaults

On 1/24/07, Joel Gwynn <[EMAIL PROTECTED]> wrote: OK. I replaced that line with a hard-coded file path, and now it's looking much better. So I guess it's something about the Request object. My guess is that $self has a lifespan longer than one request, so you are trying to use a $r object fro

Re: Troubleshooting Apache2 Segfaults

On 1/24/07, Joel Gwynn <[EMAIL PROTECTED]> wrote: On 1/24/07, Robert Landrum <[EMAIL PROTECTED]> wrote: > Joel Gwynn wrote: > > Interesting. I just might be doing that: > > $config_file = $self->param('r')->dir_config('CONFIG_FILE'); > > > > In my section, I have this: > > > > PerlSetVar CONFIG

Re: Troubleshooting Apache2 Segfaults

On 1/24/07, Robert Landrum <[EMAIL PROTECTED]> wrote: Joel Gwynn wrote: > Interesting. I just might be doing that: > $config_file = $self->param('r')->dir_config('CONFIG_FILE'); > > In my section, I have this: > > PerlSetVar CONFIG_FILE /projects/funnyr_dev/private/config.ini > > And of course

Re: Troubleshooting Apache2 Segfaults

Joel Gwynn wrote: Interesting. I just might be doing that: $config_file = $self->param('r')->dir_config('CONFIG_FILE'); In my section, I have this: PerlSetVar CONFIG_FILE /projects/funnyr_dev/private/config.ini And of course I'm not using flock on that file. Hmmm. Try changing that up...

Re: Troubleshooting Apache2 Segfaults

Joel Gwynn wrote: Here's my backtrace, any ideas? #0 0xb7a58743 in modperl_dir_config (my_perl=0x81b6eb0, r=0x823ce98, s=0x203a6e6f, key=0x8800c38 "CONFIG_FILE", sv_val=0x0) at modperl_util.c:516 #1 0xb78dae84 in XS_Apache2__RequestRec_dir_config (my_perl=0x81b6eb0, cv=0x82cd074) at Requ

Re: Troubleshooting Apache2 Segfaults

On 1/22/07, Perrin Harkins <[EMAIL PROTECTED]> wrote: On 1/21/07, Joel Gwynn <[EMAIL PROTECTED]> wrote: > I've got a mod_perl application which segfaults on every 10th or so > requests. Here's what I get in my error log: > > [notice] child pid exit sign

Re: Troubleshooting Apache2 Segfaults

On 1/21/07, Joel Gwynn <[EMAIL PROTECTED]> wrote: I've got a mod_perl application which segfaults on every 10th or so requests. Here's what I get in my error log: [notice] child pid exit signal Segmentation fault (11) How would I go about troubleshooting this? There

Re: Troubleshooting Apache2 Segfaults

On Jan 22, 2007, at 9:12 AM, Joel Gwynn wrote: Is DEBUG_USER_LOGIC shorthand for something? No. You just have to make your own (USER_LOGIC) debugging lines, to try and figure out where you're segfaulting. The other option is this: http://search.cpan.org/~pgollucci/mod_perl-2.0.3/docs/de

Re: Troubleshooting Apache2 Segfaults

On 1/21/07, Jonathan Vanasco <[EMAIL PROTECTED]> wrote: On Jan 21, 2007, at 12:05 PM, Joel Gwynn wrote: > I've got a mod_perl application which segfaults on every 10th or so > requests. Here's what I get in my error log: > > [notice] child pid exit signal Seg

Re: Troubleshooting Apache2 Segfaults

On Jan 21, 2007, at 12:05 PM, Joel Gwynn wrote: I've got a mod_perl application which segfaults on every 10th or so requests. Here's what I get in my error log: [notice] child pid exit signal Segmentation fault (11) How would I go about troubleshooting this? toss

Troubleshooting Apache2 Segfaults

I'm running mod_perl 2.0.2 (I think) on apache 2 on Debian Linux 2.6.9-023stab033.6 I've got a mod_perl application which segfaults on every 10th or so requests. Here's what I get in my error log: [notice] child pid exit signal Segmentation fault (11) How would I go about

Re: mod_perl-2.0.2 causing segfaults

>> > > > > > Also, I tried restarting the interchange daemon with >> > > > > > PERL_SIGNALS=unsafe and the ALERT/segfaults came MUCH MUCH more >> > > > > > frequently. Does that tell us anything? >> > > > > &g

Re: mod_perl-2.0.2 causing segfaults

On Mon, 11 Dec 2006, Grant wrote: > > > > > Also, I tried restarting the interchange daemon with > > > > > PERL_SIGNALS=unsafe and the ALERT/segfaults came MUCH MUCH more > > > > > frequently. Does that tell us anything? > > > > &

Re: mod_perl-2.0.2 causing segfaults

> >> > > Also, I tried restarting the interchange daemon with > >> > > PERL_SIGNALS=unsafe and the ALERT/segfaults came MUCH MUCH more > >> > > frequently. Does that tell us anything? > >> > > >> > > >

Re: mod_perl-2.0.2 causing segfaults

daemon with > PERL_SIGNALS=unsafe and the ALERT/segfaults came MUCH MUCH more > frequently. Does that tell us anything? It would make sense that, when you have high load, there is a problem processing many concurrent requests which triggers the PIPE signal, so you should find out what the error

Re: mod_perl-2.0.2 causing segfaults

>> > > Also, I tried restarting the interchange daemon with >> > > PERL_SIGNALS=unsafe and the ALERT/segfaults came MUCH MUCH more >> > > frequently. Does that tell us anything? >> > >> > >> > It would make sense that, wh

Re: mod_perl-2.0.2 causing segfaults

or something else at this point? >> > >> > Also, I tried restarting the interchange daemon with >> > PERL_SIGNALS=unsafe and the ALERT/segfaults came MUCH MUCH more >> > frequently. Does that tell us anything? >> >> >> It would make sense that, when you

Re: mod_perl-2.0.2 causing segfaults

On Mon, 11 Dec 2006, Philip M. Gollucci wrote: Grant wrote: > > Also, I tried restarting the interchange daemon with > > PERL_SIGNALS=unsafe and the ALERT/segfaults came MUCH MUCH more > > frequently. Does that tell us anything? > > > It would make sense th

Re: mod_perl-2.0.2 causing segfaults

nterchange daemon with > PERL_SIGNALS=unsafe and the ALERT/segfaults came MUCH MUCH more > frequently. Does that tell us anything? It would make sense that, when you have high load, there is a problem processing many concurrent requests which triggers the PIPE signal, so you should find out

Re: mod_perl-2.0.2 causing segfaults

daemon with > PERL_SIGNALS=unsafe and the ALERT/segfaults came MUCH MUCH more > frequently. Does that tell us anything? It would make sense that, when you have high load, there is a problem processing many concurrent requests which triggers the PIPE signal, so you should find out what the error

Re: mod_perl-2.0.2 causing segfaults

daemon with > PERL_SIGNALS=unsafe and the ALERT/segfaults came MUCH MUCH more > frequently. Does that tell us anything? It would make sense that, when you have high load, there is a problem processing many concurrent requests which triggers the PIPE signal, so you should find out what the er

Re: mod_perl-2.0.2 causing segfaults

next thing to do is find out why it's failing? Can it be said whether it's a problem with mod_perl, Interchange::Link, interchange, or something else at this point? Also, I tried restarting the interchange daemon with PERL_SIGNALS=unsafe and the ALERT/segfaults came MUCH MUCH more

Re: mod_perl-2.0.2 causing segfaults

> Actually, the only place die_page is called in the module is: > > $SIG{PIPE} = sub { die_page($r); }; > > What does that mean? Have a look here: http://perldoc.perl.org/perlipc.html#Using-open()-for-IPC There is an error reading from or writing to a pipe. > > - Grant _

Re: mod_perl-2.0.2 causing segfaults

>> you need to find out why die_page is being called. > > Do you have any advice on the best way to do that? You could start by using caller(): my ($package, $filename, $line) = caller; within the sub, in order to see where it's being called from. Actually, the only place die_page is calle

Re: mod_perl-2.0.2 causing segfaults

On Sun, 10 Dec 2006, Grant wrote: [ ... ] you need to find out why die_page is being called. Do you have any advice on the best way to do that? You could start by using caller(): my ($package, $filename, $line) = caller; within the sub, in order to see where it's being called from. -- be

Re: httpd segfaults

Jonathan Vanasco wrote: On Aug 16, 2006, at 3:46 PM, Perrin Harkins wrote: On Wed, 2006-08-16 at 21:03 +0200, Jiří Pavlovský wrote: I think I see a place in my program where it crashes. It is a initialization routine I call on startup to get data from db and populate some caches. I can't see

Re: httpd segfaults

On Aug 16, 2006, at 3:46 PM, Perrin Harkins wrote: On Wed, 2006-08-16 at 21:03 +0200, Jiří Pavlovský wrote: I think I see a place in my program where it crashes. It is a initialization routine I call on startup to get data from db and populate some caches. I can't see anything wrong in my perl

Re: httpd segfaults

On Wed, 2006-08-16 at 21:03 +0200, Jiří Pavlovský wrote: > Yes, that is the case. With mod_perl 2.0.2 it did not matter what pg > libs I used. But the segfault happens when you try to use DBD::Pg, not mod_perl, right? If you just take out the Pg stuff, does it start ok? > I think I see a place

Re: httpd segfaults

Perrin Harkins wrote: On Wed, 2006-08-16 at 16:19 +0200, Jiří Pavlovský wrote: Httpd segfaults if I compile DBD::Pg against newer libreries and/or use newer mod_perl. So you're saying that it segfaults if you compile DBD::Pg against the Pg 8.1.4 libs or if you compile mod_perl

Re: httpd segfaults

On Wed, 2006-08-16 at 16:19 +0200, Jiří Pavlovský wrote: > Httpd segfaults if I compile DBD::Pg against newer libreries and/or use > newer mod_perl. So you're saying that it segfaults if you compile DBD::Pg against the Pg 8.1.4 libs or if you compile mod_perl 2.0.2 with apache 2.0.59?

httpd segfaults

is to downgrade to 1.99_09 and compile DBD::Pg against 7.4.x postgres libraries. Httpd segfaults if I compile DBD::Pg against newer libreries and/or use newer mod_perl. I can't see anything useful in logs. I tried debugging suggestions from the mod_perl website, but I just don't have en

Apache segfaults while running 'make test'

-8<-- Start Bug Report 8<-- 1. Problem Description: Apache segfaults when I run the test suite. 2. Used Components and their Configuration: *** mod_perl version 2.02 *** using /home/derek/mod_perl-2.0.2/lib/Apache2/BuildConfig.pm *** Makef

Re: No image creation in mod_perl (was RE: Apache2/MP2 Segfaults ...)

> This revelation of how Perl does not free up memory it allocates is > worrying, especially as I do process large documents regularly. > > If I read you right, you are saying that $r->child_terminate will force > the current thread to terminate, causing Apache to create a new thread. > Is that

Re: No image creation in mod_perl (was RE: Apache2/MP2 Segfaults ...)

Hey Carl, The only place where forking is useful is where you want something to continue processing after sending the response back to the client. You can achieve the same effective result by calling $r->child_terminate() (assuming your using pre-fork). The currently running child exits at th

RE: No image creation in mod_perl (was RE: Apache2/MP2 Segfaults ...)

I use Image::Imlib2 for on the fly image creation and it works fine for me. After the thumbnails are created, memory is restored to normal size. Image::Imlib2 is also very vast and easy to code. For filetypes that are not supported by imlib2, I use imagemagick which is using some more memory but

Re: No image creation in mod_perl (was RE: Apache2/MP2 Segfaults ...)

i generally don't like to do that in modperl unless i have enough webservers. i think its a bit of a waste of the mp resource. i do this: on upload, generate a thumbnail w/Image:Epeg (which is a super fast implementation of epeg. previously i compiled my own epeg tools and the perl mod i

Re: No image creation in mod_perl (was RE: Apache2/MP2 Segfaults ...)

Can you fork off a separate process to do this (that will die once it is completed)? The only place where forking is useful is where you want something to continue processing after sending the response back to the client. You can achieve the same effective result by calling $r->child_terminate(

Re: No image creation in mod_perl (was RE: Apache2/MP2 Segfaults ...)

On 3/27/06 6:21 AM, "Tom Schindl" <[EMAIL PROTECTED]> wrote: > Please note that this is not only true for Image-Creation but also if > you are restoring large string contents in a variable (e.g. after > processing a file-upload). > > Tom > > Frank Maas wrote: >> Tom, >> >> >>> As a sidenote

Re: No image creation in mod_perl (was RE: Apache2/MP2 Segfaults ...)

Please note that this is not only true for Image-Creation but also if you are restoring large string contents in a variable (e.g. after processing a file-upload). Tom Frank Maas wrote: > Tom, > > >>As a sidenote often it is not really desired/dangerous to run image >>creation as a mod_perl hand

Re: No image creation in mod_perl (was RE: Apache2/MP2 Segfaults ...)

Well image creation in mod_perl is not a bad idea if you ensure that the process is killed after it succeeded a certain memory. The problem in case of mod-perl/httpd is that that if every httpd-process is eating 20 MB of space only because you have created once an image. You must ensure that only v

No image creation in mod_perl (was RE: Apache2/MP2 Segfaults ...)

Tom, > As a sidenote often it is not really desired/dangerous to run image > creation as a mod_perl handler because of the nature of perl, memory > allocated once is never freed until the process shutdowns or is killed > (by your Apache::SizeLimit handler). Ah, you got me worried there... How in

Re: Apache2/MP2 Segfaults when loading Text::Textile

Tom Schindl wrote: > As a sidenote often it is not really desired/dangerous to run image > creation as a mod_perl handler because of the nature of perl, memory > allocated once is never freed until the process shutdowns or is killed > (by your Apache::SizeLimit handler). > > I'm not familiar with

Re: Apache2/MP2 Segfaults when loading Text::Textile

ick. Any incantation of pre loading this modules makes apache >>core. >> >>The funny part is, it only segfaults the main httpd process. apachectl >>start yields a core dump, but the child proc are created and serve pages >>just fineuntil an apachectl stop is issue

Re: Apache2/MP2 Segfaults when loading Text::Textile

Christopher H. Laco wrote: > That's in on the nose. Text::Textile uses Image::Size, which uses > Image::Magick. Any incantation of pre loading this modules makes apache > core. > > The funny part is, it only segfaults the main httpd process. apachectl > start yields a c

Re: Apache2/MP2 Segfaults when loading Text::Textile

BjXrn Erik Jacobsen wrote: > At 05:04 23.03.2006, you wrote: >> I'm working on a site running under Catalyst under ModPerl >> 2.0.2/Apache2.0.55. >> >> As soon as I tried loading Text::Textile in any way, apache segfaults, >> even when just doing apachectl con

Re: Apache2/MP2 Segfaults when loading Text::Textile

At 05:04 23.03.2006, you wrote: > > I'm working on a site running under Catalyst under ModPerl > 2.0.2/Apache2.0.55. > > As soon as I tried loading Text::Textile in any way, apache segfaults, > even when just doing apachectl configtest. > > Text::Textile is a pure p

Re: Apache2/MP2 Segfaults when loading Text::Textile

Christopher H. Laco wrote: > I'm working on a site running under Catalyst under ModPerl > 2.0.2/Apache2.0.55. > > As soon as I tried loading Text::Textile in any way, apache segfaults, > even when just doing apachectl configtest. > > Text::Textile is a pure perl

Apache2/MP2 Segfaults when loading Text::Textile

I'm working on a site running under Catalyst under ModPerl 2.0.2/Apache2.0.55. As soon as I tried loading Text::Textile in any way, apache segfaults, even when just doing apachectl configtest. Text::Textile is a pure perl module, and uses Exporter. Nothing special. I started rebuilding a

Re: [mp2] block & PerlOptions +Parent & PerlRequire segfaults on 2.0.2, but not 2.0.1

Eamon Daly wrote: > This patch worked like a charm for me. Thanks for the quick > response! Great, then a slightly different patch has been applied to SVN in change 371775, documented in change 371776 Now there are 2 identical ways to specify Switch inheritance: - PerlSwitches +inherit (the old

Re: [mp2] block & PerlOptions +Parent & PerlRequire segfaults on 2.0.2, but not 2.0.1

Cc: ; Sent: Friday, January 20, 2006 7:53 PM Subject: Re: [mp2] block & PerlOptions +Parent & PerlRequire segfaults on 2.0.2, but not 2.0.1 Eamon Daly wrote: 1. Problem Description: If I declare a section in httpd.conf, then define a virtual host with "PerlOptions +Pare

Re: [mp2] block & PerlOptions +Parent & PerlRequire segfaults on 2.0.2, but not 2.0.1

Eamon Daly wrote: > 1. Problem Description: > > If I declare a section in httpd.conf, then define > a virtual host with "PerlOptions +Parent", httpd dies with > a segfault on subsequent PerlRequires. This works in 2.0.1. > Here's a minimal example, tacked on to the end of the > default httpd.conf

  1   2   >