Skip Menu |

This queue is for tickets about the DBD-Pg CPAN distribution.

Report information
The Basics
Id: 25725
Status: rejected
Priority: 0/
Queue: DBD-Pg

People
Owner: Nobody in particular
Requestors: koczan [...] cs.wisc.edu
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: DBD::Pg error with Kerberos on Solaris
Date: Fri, 23 Mar 2007 16:09:32 -0500
To: bug-dbd-pg [...] rt.cpan.org
From: Peter Koczan <koczan [...] cs.wisc.edu>
Hello, I believe I have found a bug is DBD::Pg on Solaris 5.8 (I know, it's old) relating to Kerberos. Every time a database script ends on a Solaris, I get this message: Assertion failed: (&(&_m->os)->n)->initialized == K5_MUTEX_DEBUG_INITIALIZED, file ../../../krb5-1.5.1/src/util/support/threads.c, line 388 /local.gazoo/grad/convertdata[4]: 5487 Abort(coredump) This only happens when I run a Perl-based app (e.g. vacuumdb doesn't give this error). I'm running DBD::Pg 1.49, Postgres 8.2. The servers are running on Linux and this bug does not show up in scripts run in Linux, leading me to believe that it's a client-only issue. The weird thing is that it only seems to happen at the end of a script. All database actions are completed successfully, leading me to believe this problem is somewhere in the disconnection or destruction of the connection. Version info... DBD::Pg 1.49 PostgreSQL 8.2.1 Solaris 5.8 Kerberos5 1.5.1 OpenSSL 0.9.8d Perl 5.8.6 Please let me know if you need any additional info. Thanks. Peter
Any chance you can try this on another libpq application? Perhaps psql or a quick C app. You might also try an email to pgsql-interfaces to see if anyone else has experienced this.
Subject: Re: [rt.cpan.org #25725] DBD::Pg error with Kerberos on Solaris
Date: Wed, 18 Jul 2007 12:30:42 -0500
To: bug-DBD-Pg [...] rt.cpan.org
From: Peter Koczan <koczan [...] cs.wisc.edu>
This error did not appear (or at least wasn't reported) when using psql. However, it looks like the bug was due to a specific version of Kerberos on Solaris, or at least our compiled version of it. Compiling the module against a libpq linked with an updated Kerberos fixed the bug. It appears that this was a Kerberos issue, not a database or driver issue. Peter DBD::Pg Developers via RT wrote: Show quoted text
> <URL: http://rt.cpan.org/Ticket/Display.html?id=25725 > > > Any chance you can try this on another libpq application? Perhaps psql > or a quick C app. You might also try an email to pgsql-interfaces to see > if anyone else has experienced this.