On Thu, Jan 28, 2010 at 04:30:04PM -0500, Pas Argenio wrote:
>I resolved it, finally. Stupidly, we had created a symbolic link:
>libmysqlclient.so.15 -> libmysqlclient.so.16.0.0
>(I guess our source build of mysql-5.1.32 only provides
>libmysqlclient.so.16.0.0 but DBD-mysql
I resolved it, finally. Stupidly, we had created a symbolic link:
libmysqlclient.so.15 -> libmysqlclient.so.16.0.0
(I guess our source build of mysql-5.1.32 only provides
libmysqlclient.so.16.0.0 but DBD-mysql-4.008 needs libmysqlclient.so.15)
The fix was to get the real libmysqlclient.so
2010/1/28 Pas Argenio :
> Thanks John. Currently, I'm building 32-bit for a Sparc platform and also
> with man CPAN modules such as DBI and DBD.
>
> I just rebuilt everything carefully, but still coring often before then
> displaying a page:
> Apache 2.2.8 Perl 5.10.0 mod_perl 2.0.3
>
> I a
Thanks John. Currently, I'm building 32-bit for a Sparc platform and also
with man CPAN modules such as DBI and DBD.
I just rebuilt everything carefully, but still coring often before then
displaying a page:
Apache 2.2.8 Perl 5.10.0 mod_perl 2.0.3
I also turned on perl internal malloc
Sh
In message <30a2344a1001271105t6c690071qb72eb53df2a68...@mail.gmail.com>, Pas A
rgenio writes:
>I'm building everything from source. I've rebuilt perl a half-dozen times
>both static & dynamic. I'm working on building 5.10.1 but it seems so
Does modperl's make test succeed?
Under Solaris, you n
Perl 5.10.1 is still relatively new, so you might want to give 5.8.9 a
shot. That is more heavily vetted on lesser used platforms such as
Solaris.
On Wed, Jan 27, 2010 at 9:28 AM, Pas Argenio wrote:
> I just fell back to Apache-2.2.8 but same problem. By the way, Tosh, how
> did you dump the li
No, wish I were. East coast US, unseasonably warm (we have more hot air in
general).
I'm building everything from source. I've rebuilt perl a half-dozen times
both static & dynamic. I'm working on building 5.10.1 but it seems so
different in the build defaults.
Still to try: mod_perl.2.0.3 and u
perl -V
I don't think it's an Apache issue, my purely superstitious feelings
based on the ravens I saw flying around this morning is that blame lies
with perl 5.10, I just don't trust even number releases, even less round
numbers cleanly divisible by 10.
But then $r scares me so...
Are you
I just fell back to Apache-2.2.8 but same problem. By the way, Tosh, how
did you dump the libperl info?
I'm getting more core dumps than you, but pages are displayed by the next
child to pick it up. Here is the most common stack trace (via Solaris'
pstack command):
Wed Jan 27 09:06:35 EST 2010
c
I'm seeing the same thing on my DEV server which is:
Server: Apache/2.2.11 (Ubuntu) mod_perl/2.0.4 Perl/v5.10.0
I see it in the mornings when it has been sitting around all night doing
nothing, and the first couple hits result in core dumps/seg faults, then
after pounding REFRESH like a mad mo
What OS are you running? What is the output of 'perl -V'?
On Tue, Jan 26, 2010 at 6:19 PM, Pas Argenio wrote:
> Sorry if this is naive, but has anyone gotten this combo to work? Upgraded
> to Apache 2.2.14, now crash on almost every request, then next httpd picks
> up the request and actually d
Sorry if this is naive, but has anyone gotten this combo to work? Upgraded
to Apache 2.2.14, now crash on almost every request, then next httpd picks
up the request and actually displays the page...
I've got massive core dumps all ending in malloc/free, truss shows last
operation was close()
12 matches
Mail list logo
