I was having problems with the following appearing in the Apache logs:
Had to create DBD::mysql::db::imp_data_size unexpectedly at
/usr/lib/perl5/site_perl/5.005/i386-linux/DBI.pm line 703.
[Wed Jul 18 04:50:32 2001] [error] Undefined subroutine &DBD::mysql::db::_login
called at /usr/lib/perl5/site_perl/5.005/i386-linux/DBD/mysql.pm line 1
I have now fixed this problem by switching MySQL from a src compiled version to
the RPM installed version. This suggests to me that the perl module is having
trouble finding a header or include file it needs to set the imp_data_size
variable.
Hope this helps.
Tim Atkinson
Systems Administrator
iTouch Australia
ph: +61 (0)2 9409 9600
fax: +62 (0)2 9409 9611
email: tim.atkinson@itouch.com.au
|+ I have now fixed this problem by switching MySQL from a src compiled version to
|+ the RPM installed version. This suggests to me that the perl module is having
|+ trouble finding a header or include file it needs to set the imp_data_size
|+ variable.
Just curious, do you know if before your mysql headers were in
/usr/local/include/mysql ? I’ve seen before that some programs
assume the mysql headers will be in /usr/include. I’ve seen this quite
a bit with FreeBSD atleast, in the code I’ve written.
darrin walton, darrinw@nixc.net
They were in /usr/local/mysql/include/mysql which was probably most of the
problem. However I have never had an issue with php+mysql before with it in this
location.
Either way… rt is working now.From: “Darrin Walton” darrinw@nixc.net
To: “Tim Atkinson” tim.atkinson@itouch.com.au
Cc: rt-users@lists.fsck.com
Sent: Thursday, July 19, 2001 12:40 PM
Subject: Re: [rt-users] MySQL problems… SOLVED!!!
|+ I have now fixed this problem by switching MySQL from a src compiled
version to
|+ the RPM installed version. This suggests to me that the perl module is
having
|+ trouble finding a header or include file it needs to set the
imp_data_size
|+ variable.
Just curious, do you know if before your mysql headers were in
/usr/local/include/mysql ? I’ve seen before that some programs
assume the mysql headers will be in /usr/include. I’ve seen this quite
a bit with FreeBSD atleast, in the code I’ve written.
–
darrin walton, darrinw@nixc.net
|+ They were in /usr/local/mysql/include/mysql which was probably most of the
|+ problem. However I have never had an issue with php+mysql before with it in this
|+ location.
Quite strange, never seen them in that location. What OS was this? Just
curious so I can update my mysql_check routine for gnu configure.
|+ Either way… rt is working now.
cool, i’m still struggling with getting mailing to work with sendmail.
darrin walton, darrinw@nixc.net
It was RedHat 6.2 with kernel 2.2.19 and MySQL installed in /usr/local/mysql
from sourceFrom: “Darrin Walton” darrinw@nixc.net
To: “Tim Atkinson” tim.atkinson@itouch.com.au
Cc: rt-users@lists.fsck.com
Sent: Thursday, July 19, 2001 2:11 PM
Subject: Re: [rt-users] MySQL problems… SOLVED!!!
|+ They were in /usr/local/mysql/include/mysql which was probably most of
the
|+ problem. However I have never had an issue with php+mysql before with it
in this
|+ location.
Quite strange, never seen them in that location. What OS was this? Just
curious so I can update my mysql_check routine for gnu configure.
|+ Either way… rt is working now.
cool, i’m still struggling with getting mailing to work with sendmail.
–
darrin walton, darrinw@nixc.net
I was having problems with the following appearing in the Apache logs:
Had to create DBD::mysql::db::imp_data_size unexpectedly at
/usr/lib/perl5/site_perl/5.005/i386-linux/DBI.pm line 703.
[Wed Jul 18 04:50:32 2001] [error] Undefined subroutine
&DBD::mysql::db::_login called at
/usr/lib/perl5/site_perl/5.005/i386-linux/DBD/mysql.pm line 1
I have now fixed this problem by switching MySQL from a src compiled version
to the RPM installed version. This suggests to me that the perl module is
having trouble finding a header or include file it needs to set the
imp_data_size variable.
For what it’s worth, I was having the exact same problem as Tim (at least, I was
receiving exactly the same errors in the logfiles) but I found a different solution:
I ended up manually deleting a number of perl modules, downloading fresh,
known good copies from http://www.helgrim.com/perlmodules/ (THANKS
Feargal …) and reinstalled. The list ended up including:
DBI-1.16
DBIx-SearchBuilder-0.40
DBIx-DataSource-0.02
Msql-Mysql-modules-1.2216
Storable-1.0.11
libapreq-0.31
Apache-Session-1.53
ApacheDBI-0.88
I had previously tried un/re-installing just the msql-mysql module, but that
didn’t seem to be sufficient. Something in the list above seemed to fix
the problem.
Hopefully, this’ll help someone else.
-Steve.
Steve Nolan
Vancouver Island Regional Library
Systems Support Services
(250) 758-4697 x 217