Closed
Bug 277304
Opened 20 years ago
Closed 20 years ago
checksetup.pl fails connecting to MySQL database
Categories
(Bugzilla :: Installation & Upgrading, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: akostocker, Assigned: zach)
Details
Hello, System specifics: P4 1.8 Ghz, 2 GB ram, running Mandrake 10.1 (kernel: 2.6.8.1-12mdk) I've installed all the required Perl Modules (running Perl 5.8.5), MySQL (ver. 4.1.8), and Apache (ver. 2.0.50). I created a symlink from the location of my Perl binary to /usr/bonsaitools/bin/perl. I've started MySQL and created a user named 'bugs'. I have run the checksetup.pl script as root, modified to put the correct password for 'bugs' in it, and then su'd to the apache user to run checksetup.pl again. It fails with the message: /usr/bonsaitools/bin/perl: symbol lookup error: /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/auto/DBD/mysql/mysql.so: undefined symbol: mysql_init Here is the complete output of the checksetup.pl run: -sh-2.05b$ ./checksetup.pl Checking perl modules ... Checking for AppConfig (v1.52) ok: found v1.56 Checking for CGI::Carp (any) ok: found v1.28 Checking for Data::Dumper (any) ok: found v2.121 Checking for Date::Parse (any) ok: found v2.27 Checking for DBI (v1.13) ok: found v1.46 Checking for DBD::mysql (v1.2209) ok: found v2.9004 Checking for File::Spec (v0.82) ok: found v3.01 Checking for File::Temp (any) ok: found v0.14 Checking for Template (v2.07) ok: found v2.14 Checking for Text::Wrap (v2001.0131) ok: found v2001.09292 Checking for CGI::Carp (any) ok: found v1.28 The following Perl modules are optional: Checking for GD (v1.19) ok: found v2.16 Checking for Chart::Base (v0.99) not found Checking for XML::Parser (any) ok: found v2.34 If you you want to see graphical bug dependency charts, you may install the optional libgd and the Perl modules GD-1.19 and Chart::Base-0.99b, e.g. by running (as root) perl -MCPAN -e'install "LDS/GD-1.19.tar.gz"' perl -MCPAN -e'install "N/NI/NINJAZ/Chart-0.99b.tar.gz"' Checking user setup ... Warning: you have entered a value for the "webservergroup" parameter in localconfig, but you are not running this script as root. This can cause permissions problems and decreased security. If you experience problems running Bugzilla scripts, log in as root and re-run this script, or remove the value of the "webservergroup" parameter. Note that any warnings about "uninitialized values" that you may see below are caused by this. Creating data directory ... Creating graphs directory... Creating .htaccess... Creating data/.htaccess... Creating template/.htaccess... Creating data/webdot/.htaccess... Removing existing compiled templates ... Precompiling templates ... /usr/bonsaitools/bin/perl: symbol lookup error: /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/auto/DBD/mysql/mysql.so: undefined symbol: mysql_init I have verified that the database is up and working by manually logging in as the 'bugs' user: # mysql -u bugs -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 12 to server version: 4.1.8-log Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> use test; Database changed mysql> show tables; +----------------+ | Tables_in_test | +----------------+ | squish | +----------------+ 1 row in set (0.00 sec) mysql> Please advise on how to proceed. Tony
Comment 1•20 years ago
|
||
That sounds like your DBI might be compiled against a different version of MySQL that you're using. Also, your DBI::MySQL is really, really new... I'm not sure I've yet used Bugzilla on a DBI that new. So that *might* also be the problem. But I suspect it's what I said above, actually. Let me know.
| Reporter | ||
Comment 2•20 years ago
|
||
Okay, I'm going to try recompiling the DBI this week and try again. I'll let you know how it goes.
| Reporter | ||
Comment 3•20 years ago
|
||
Okay, I recompiled the DBD::Mysql and then tried checksetup.pl again and this time it seemed to work. At least I did not get any error messages like I did before. I still don't know if Bugzilla is actually working or not, but this particular issue is now closed I believe. Thanks for the help!
Comment 4•20 years ago
|
||
Great. You're welcome. In the future, if you need support, you can use the mozilla-webtools mailing list. You can see information on it at http://www.bugzilla.org/support/, I think.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Updated•19 years ago
|
Severity: blocker → trivial
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•