On Thu, May 7, 2009 at 4:41 PM, Brian Hirt wrote:
> I just built up a new mod_perl1.30 with apache 1.3.41 and started seeing
> segfaults in my logs. I ended up tracking the problem down to
> http://svn.apache.org/viewvc?view=rev&revision=555908
>
> It looks like a fix was committed almost 2 year
On Mon, Jun 30, 2008 at 10:54:20AM +0200, Tobias Kremer wrote:
> Any other ideas? Thanks!
It could be that your query(result) is too large for the
'max_allowed_packet' setting. The mysql-client that is connected to your
process will then silently die, giving the 'Lost mysql...' error as
result.
On Mon, Jun 30, 2008 at 4:54 AM, Tobias Kremer <[EMAIL PROTECTED]> wrote:
> We never fork and I thought that Apache::DBI takes care of checking if a
> connection went stale by utilizing DBI's/DBD::mysql's ping() method?
It does, but it can't stop you from doing things like putting a
database handl
Quoting Perrin Harkins <[EMAIL PROTECTED]>:
> On Fri, Jun 27, 2008 at 5:51 AM, Tobias Kremer <[EMAIL PROTECTED]> wrote:
> > Now if I could just get rid of those annoying random "Commands out of sync"
> and
> > "Lost connection to MySQL server during query" errors that happen once in a
> > while ...
On Fri, Jun 27, 2008 at 5:51 AM, Tobias Kremer <[EMAIL PROTECTED]> wrote:
> Now if I could just get rid of those annoying random "Commands out of sync"
> and
> "Lost connection to MySQL server during query" errors that happen once in a
> while ...
Those generally mean that you timed out (set MySQ
On AIX 5.2 I am using Perl 5.8.0, MySQL 5.0.51a, Apache 2.2.28, mod_perl
2.04, DBI 1.604 and DBD 4.0007 and it all works good.
--Brian
-Original Message-
From: Tobias Kremer [mailto:[EMAIL PROTECTED]
Sent: Friday, June 27, 2008 5:51 AM
To: modperl@perl.apache.org
Subject: Re: Segfault
Quoting Tobias Kremer <[EMAIL PROTECTED]>:
> On 25.06.2008, at 20:58, Amiri Barksdale wrote:
> > I had big trouble with DBD::mysql 4.007. I didn't get rid of my
> > segfault problem running mod_perl 1.31 until I went back to 4.004.
>
> Thanx. It really looks a lot like my problem:
>
> http://bugs.
On 25.06.2008, at 20:58, Amiri Barksdale wrote:
I had big trouble with DBD::mysql 4.007. I didn't get rid of my
segfault problem running mod_perl 1.31 until I went back to 4.004.
Thanx. It really looks a lot like my problem:
http://bugs.mysql.com/bug.php?id=36810
I'll try reverting to an ear
I had big trouble with DBD::mysql 4.007. I didn't get rid of my
segfault problem running mod_perl 1.31 until I went back to 4.004.
Amiri
On Jun 25, 2008, at 12:14 PM, Perrin Harkins wrote:
On Wed, Jun 25, 2008 at 5:49 AM, Tobias Kremer <[EMAIL PROTECTED]>
wrote:
After de-installing the la
On Wed, Jun 25, 2008 at 5:49 AM, Tobias Kremer <[EMAIL PROTECTED]> wrote:
> After de-installing the latest (self-rolled) DBI and DBD::mysql modules and
> installing the corresponding packages provided by Ubuntu (libdbd-mysql-perl
> and
> libdbi-perl) the segfaults are gone.
It sound like this is
Quoting André Warnier <[EMAIL PROTECTED]>:
> I don't know if the above versions are imposed to you, but in case you
> have a choice, I would recommend de-installing your Apache and mod_perl,
> and re-install the Apache 2.2 version and the mod_perl that goes with it.
> Apache 1.x and mod_perl 1.x ar
Quoting Tobias Kremer <[EMAIL PROTECTED]>:
> > - Ubuntu Feisty with apache-perl.
> > - stock Ubuntu Perl 5.8.8 (which unfortunately comes with threads)
> > - self-rolled DBD::mysql (against libmysqlclient15-dev), DBI and
> Apache::DBI
>
> I should have mentioned that we're using DBI 1.605, Apache:
> - Ubuntu Feisty with apache-perl.
> - stock Ubuntu Perl 5.8.8 (which unfortunately comes with threads)
> - self-rolled DBD::mysql (against libmysqlclient15-dev), DBI and Apache::DBI
I should have mentioned that we're using DBI 1.605, Apache::DBI 1.07 and
DBD::mysql 4.007. The Ubuntu apache-perl
Fred Moyer wrote:
>
> What version were you using that was causing the problems?
>
4.007.
Amiri
--
View this message in context:
http://www.nabble.com/Segfault-Help%21-%21--tp17599739p17675687.html
Sent from the mod_perl - General mailing list archive at Nabble.com.
What version were you using that was causing the problems?
amiribarksdale wrote:
It appears that downgrading DBD::mysql to version 4.004 has done the trick.
Amiri
--
Red Hot Penguin Consulting LLC
mod_perl/PostgreSQL consulting and implementation
http://www.redhotpenguin.com/
It appears that downgrading DBD::mysql to version 4.004 has done the trick.
Amiri
--
View this message in context:
http://www.nabble.com/Segfault-Help%21-%21--tp17599739p17668030.html
Sent from the mod_perl - General mailing list archive at Nabble.com.
I reinstalled mysql from source and recompiled my DBD::mysql against
its new libs, and I still get the same backtrace:
Using host libthread_db library "/lib64/tls/libthread_db.so.1".
...
#0 0x002a994cf93e in mysql_send_query ()
from /home/mysql/lib/mysql/libmysqlclient.so.15
(gdb) bt fu
Fred Moyer wrote:
>
> Can you post your httpd.conf and startup.pl?
>
> Are you using transactions?
>
I am not using transactions--I don't have any InnoDB tables, either.
Here is my httpd.conf:
ServerType standalone
ServerRoot "/usr/local/apache"
PidFile /usr/local/apache/logs/httpd.pid
Sco
amiribarksdale wrote:
Yes, I have the debug output on 2 already. It doesn't say much else than what
I posted.
Ah right, read DEBUG level in the thread, didn't get that you had
actually set the apache dbi debug level (despite the log entry clearly
indicating it).
Can you post your httpd.conf
Yes, I have the debug output on 2 already. It doesn't say much else than what
I posted.
Amiri
Fred Moyer wrote:
>
> amiribarksdale wrote:
>> No, they're not the same, because they cannot be the same any longer. In
>> the
>> server migration, I had to recompile and reinstall everything, becaus
amiribarksdale wrote:
No, they're not the same, because they cannot be the same any longer. In the
server migration, I had to recompile and reinstall everything, because of
those 32-bit and 64 bit errors. I just built everything back up from
barebones CentOS.
From my cursory look through the st
No, they're not the same, because they cannot be the same any longer. In the
server migration, I had to recompile and reinstall everything, because of
those 32-bit and 64 bit errors. I just built everything back up from
barebones CentOS.
Amiri
--
View this message in context:
http://www.nabble.
amiribarksdale wrote:
Yes, I moved from 32 bit to 64 bit. But I did exactly what you said. I
reinstalled everything--perl, apache, mysql, DBI, DBD::mysql, every single
module--the whole shebang. So it's not just some careless oversight or file
copy. Everything has already been rebuilt and recompi
Yes, I moved from 32 bit to 64 bit. But I did exactly what you said. I
reinstalled everything--perl, apache, mysql, DBI, DBD::mysql, every single
module--the whole shebang. So it's not just some careless oversight or file
copy. Everything has already been rebuilt and recompiled.
Amiri
--
View th
amiribarksdale wrote:
Does anyone have any guidance on what I should do here?
Amiri
From the archive thread: -
http://www.nabble.com/Segfault-Help%21-%21--tp17599739p17627528.html
"Here are two short snippets of gdb output from the other evening. Can
someone lead me in the right direction?
Does anyone have any guidance on what I should do here?
Amiri
--
View this message in context:
http://www.nabble.com/Segfault-Help%21-%21--tp17599739p17627528.html
Sent from the mod_perl - General mailing list archive at Nabble.com.
I realized after I posted the last bit that perhaps I should post the full
lib-loading output from gdb as well as the bt full. Here goes:
This GDB was configured as "x86_64-redhat-linux-gnu"...(no debugging symbols
found)
Using host libthread_db library "/lib64/tls/libthread_db.so.1".
Core was g
Here are some better and further details. I turned on DBI debugging, so I can
see that before a segfault, I get the error
Apache::DBI disconnect (overloaded)
I have also done some gdb backtraces--I put strace output before. Here is
one gdb full bt:
(gdb) bt full
#0 0x002a994e37be
On Mon, May 19, 2008 at 09:33:49PM +0300, Niko Tyni wrote:
> On Mon, May 19, 2008 at 11:12:08AM +0200, Louis-David Mitterrand wrote:
>
> > Since I've upgraded to perl 5.10 on my debian unstable/sid box I get a
> > segfault when using MasonX::Request::WithApacheSession:
> >
> > [Sat May 17 16
On Mon, May 19, 2008 at 11:12:08AM +0200, Louis-David Mitterrand wrote:
> Since I've upgraded to perl 5.10 on my debian unstable/sid box I get a
> segfault when using MasonX::Request::WithApacheSession:
>
> [Sat May 17 16:14:55 2008] [notice] Apache/2.2.8 (Debian)
> mod_apreq2-20051231/2.
On Mon, May 19, 2008 at 07:32:18AM -0700, Fred Moyer wrote:
> Louis-David Mitterrand wrote:
>> [this message elicited no answers so far from mason-users, so maybe the
>> modperl community might be of help, thanks]
>>
>> Hi,
>>
>> Since I've upgraded to perl 5.10 on my debian unstable/sid box I get
On Mon, May 19, 2008 at 10:31:06AM -0400, Perrin Harkins wrote:
> On Mon, May 19, 2008 at 5:12 AM, Louis-David Mitterrand
> >## When commented out perl 5.10 works fine
> >request_class =>
> > 'MasonX::Request::WithApacheSession',
> >
Louis-David Mitterrand wrote:
[this message elicited no answers so far from mason-users, so maybe the
modperl community might be of help, thanks]
Hi,
Since I've upgraded to perl 5.10 on my debian unstable/sid box I get a
segfault when using MasonX::Request::WithApacheSession:
[Sat Ma
On Mon, May 19, 2008 at 5:12 AM, Louis-David Mitterrand
>## When commented out perl 5.10 works fine
>request_class => 'MasonX::Request::WithApacheSession',
>session_class => 'Apache::Session::Postgres',
>
Raful Mr Mitchell H wrote:
Here is the complete script
Is this the script that was causing segfaults? It doesn't look anything
like what you originally posted.
#!/usr/bin/perl
package Handlers::Devices;
use DBI;
use HTML::Template;
use Apache2::RequestRec ();
use APR::Request::Param (
ate->output;
return Apache2::Const::OK;
}
1;
Mitchell Raful MCSE CCNP
MCB Quantico
Personal and Family Readiness (MRI)
3044 Catlin Avenue
Quantico, VA 22134
Com: 703-784-5991
DSN: 278-5991
Cell: 804-363-0731
-Original Message-
From: Colin Wetherbee [mailto:[EMAIL PROTECTED]
Sent: W
Raful Mr Mitchell H wrote:
My script looks like this
use Apache2::Request ();
my $req = Apache2::Request-> new($r)
my $data = req->{/param-name}/
//
It causes a segfault error. Any ideas?
Hello.
Please send us a bit more of your script. This snippet doesn't say much.
Colin
Are you using Apache::Reload?
I've found that I get similar issues when using that module when
developing under osx 10.3 and the same specs as you (although no
Embperl)-- turning off the module stops the irregular activity , as
does periodic apache restarts.
Am Montag, 21. Februar 2005 20:35 s
Hi,
Am Montag, 21. Februar 2005 20:35 schrieb Derrick Spell:
> I've got a Mac OS X 10.2 server loaded with Apache 2.0.52, mod_perl
> 2.0rc4, Perl 5.8.6, Embperl 2.0rc2 - All installed fresh by hand (no
> factory installations)
> At rather irregular intervals my apache children will segfault during
> Tyler, have you by chance read:
> http://perl.apache.org/docs/2.0/user/help/help.html#Resolving_Segmentation_Faults
> plus the short script that we can reproduce the problem with.
Maybe... I'll look into it in more detail later. My main point was
that no segmentation fault occurs in 1.99
Tyler MacDonald wrote:
-8<-- Start Bug Report 8<--
1. Problem Description:
Hello,
I just tried an upgrade to 2.0RC1... only to have to back out.
All of my scripts run fine, except for one -- which exits with a
segmentation fault reliably.
I found the problem actually. My common module has an AUTOLOAD that
allows me to say $common->foo instead of $common->{foo}. I pass
my Apache::Request ($apr) object around in this common object,
retreiving $apr by calling $common->apr and then calling param()
causes the crash. I guess the retur
On Thu, 2 Dec 2004, Chris Brown wrote:
> Right now I'm running Apache 1.3.31 with mod_perl 1.29. Perl is 5.8.3 on
> Fedora FC1
Well, I don't know anything about your specific problem but judging by
the lack of responses neither does anyone else. So here's what I'd
do:
- Download the latest Pe
43 matches
Mail list logo
