Description of problem:
updating mysql,mysql-server and mysql-devel from 4.1.20-3.RHEL4.1.el4_6.1.i386 to 4.1.22-2.el4.i386 breaks RT 3.6.1 (http://www.bestpractical.com/rt/, an application written in Perl) with following errors:
Transactions not supported by database at /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi/DBI.pm line 1484.
I've rolled back the updates to mysql, mysql-server and mysql-devel and RT works well again.
Version-Release number of selected component (if applicable):
anytime you modify a RT ticket (a MySQL transaction) the error will come up.
Steps to Reproduce:
Probably perl-DBD-MySQL needs to be rebuilt against the updated version of MySQL libraries.
I can create a test package. Do you want to test it?
(In reply to comment #1)
> I can create a test package. Do you want to test it?
That would be good. Yes I can test it.
You can download this package _only_ for testing purposes from my home page http://mmaslano.fedorapeople.org/test_package/ This package isn't signed. Please let me know whether it's helped.
Still doesn't work. Got the same error.
I also tested with a simple transaction testing script from
and I got a similar error but stopped at a different line of DBI.pm
[root@hera alu]# ./commit_demo.pl -c
Transactions not supported by database at /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi/DBI.pm line 633.
Please confirm which perl-DBI and perl-DBD-MySQL package versions are involved here?
[root@hera alu]# rpm -qa |grep perl-D
[root@hera alu]# rpm -qa |grep mysql
Huh ... I cannot reproduce this. The commit_demo script works just fine on a RHEL4-U7 test machine,
using the released packages:
Marcela, were you able to reproduce the problem? Can you think of any other relevant variables?
Yes indeed. I tried on another RHEL4-U7 box and couldn't reproduce the error either.
But as I reported, I do have the problem on two RHEL4-U7 boxes, which are basically have the same installation (they are used as production+DR pair). Please let me know if you want more information about the configuration of the two boxes. Thanks.
What are the architectures of those boxes and which versions of mentioned packages did you install? Do you have Stacks product on some of them or cpan packages?
Yeah, we have to figure out what is the relevant difference between boxes with the problem and boxes without. It might be useful to diff the output of "rpm -qa | sort" from the different machines.
Created attachment 316268 [details]
perllocal.pod on hera the machine has the problem
Created attachment 316269 [details]
rpm -qa diff between the sick hera and the healthy prome
The architectures of hera and prome are both i386.
There are a few extra applications installed on hera: rt, moinmoin, nagios etc but I can't see how these applications would affect perl DBI access to mysql.
And as I said if I roll back mysql to 4.1.20-3 then the problem disappears.
It's still pretty un-obvious where the problem lies. Perl's not my strong suit, but I wonder if any of those perl package diffs could possibly affect this?
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life.
Please See https://access.redhat.com/support/policy/updates/errata/
If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.