Installing on OS X Mavericks

[Kenny Millar]

Hi all.



I am trying to set up bugzilla on my Mac OS X (Mavericks) machine.

I have MySql, Apache and PERL all installed and running.



When I run ./checksetup.pl I get the following output:



install_driver(mysql) failed: Attempt to reload DBD/mysql.pm aborted.

Compilation failed in require at (eval 1232) line 3, <DATA> line 577.



at Bugzilla/DB.pm line 1265.



This seems to suggest some problem connecting to MySql

I can confirm that I can connect to MySql from the command line using the
exact same name and password as is stored in the localconfig file.



I'm not sure where to go from here.

Has anyone implemented a successful installation on Mac OS X?

Any ideas?



-Kenny

[Thorsten Schöning]

Guten Tag Kenny Millar,
am Donnerstag, 7. November 2013 um 14:49 schrieben Sie:

> install_driver(mysql) failed: Attempt to reload DBD/mysql.pm aborted.

[...]

> This seems to suggest some problem connecting to MySql

No, the issue is with your Perl MySQL package, it can't be loaded by
Bugzilla. You need to install DBD-mysql with all it's binary
dependencies, preferable using your package manager or if that doesn't
provide the package using CPAN. Something like:

perl -MCPAN -e shell
install DBD::mysql

There may be some development packages needed to successfully install,
but CPAN should tell you about those.

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning E-Mail:Thorsten....@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/

Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

[Kenny Millar]

Thank you!
I will follow up on that and see if I can get it working.

-Kenny

_______________________________________________
support-bugzilla mailing list
support-...@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-bugzilla
PLEASE put support-...@lists.mozilla.org in the To: field when you
reply.

[Kenny Millar]

Thanks for your help so far.
I tried using cpan to install DBI and now I get the following....

When I run ./checksetup.pl it gives a strange entry for DBI:
Checking perl modules...
Checking for CGI.pm (v3.51) ok: found v3.63
Checking for Digest-SHA (any) ok: found v5.71
Checking for TimeDate (v2.23) ok: found v2.24
Checking for DateTime (v0.28) ok: found v0.77
Checking for DateTime-TimeZone (v0.71) ok: found v1.51
Checking for DBI (v1.614) found v1.63
Checking for Template-Toolkit (v2.22) ok: found v2.25
<snip>

So it finds DBI V1.63, but it does not say OK, and then later in the output
it says:

COMMANDS TO INSTALL REQUIRED MODULES (You *must* run all these commands
and then re-run checksetup.pl):

/usr/bin/perl install-module.pl DBI

And so I run the required command to install the required module and it just
says everything is OK, probably because it finds v1.63:
sh-3.2# ./install-module.pl DBI
Checking for CPAN (v1.81) ok: found v2.00
Checking for YAML (any) ok: found v0.84
Checking for ExtUtils-MakeMaker (v6.31) ok: found v6.6302
Reading '/var/root/.cpan/Metadata'
Database was generated on Thu, 07 Nov 2013 19:41:02 GMT
Installing DBI version 1.630...
DBI is up to date (1.630).

So I can not move forward from here! Install won't continue because it moans
about DBI not being installed, but it is. The DBI install does nothing
because it's already up to date!

Any ideas? Has anyone get bugzilla working in a recent Mac OS X install?

The full output of checkinstall.pl is attached (if the list allows
attachments).

[Dave Miller]

The dots in a version number are not decimal points, they are just position separators. 63 is less than 614, therefore you have an older version installed than what it's looking for. It's possible the author of this module forgot that and the one you have installed is really supposed to be 1.630. Might require some trickery to make it work :(

>------------------------------------------------------------------------

>
>_______________________________________________
>support-bugzilla mailing list
>support-...@lists.mozilla.org
>https://lists.mozilla.org/listinfo/support-bugzilla
>PLEASE put support-...@lists.mozilla.org in the To: field when you
>reply.

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

[Thorsten Schöning]

Guten Tag Dave Miller,
am Freitag, 8. November 2013 um 07:08 schrieben Sie:

> It's possible
> the author of this module forgot that and the one you have installed
> is really supposed to be 1.630.

[...]

>>Installing DBI version 1.630...
>>DBI is up to date (1.630).

Dave gave the right hint, the problem is with the version check in
Bugzilla::Install::Requirements::have_vers. This function assumes that
installing modules using CPAN with more than 2 digits after the .
should not be interpreted as numeric values, but intermediate
versions, meaning it uses 630 as something between 63 and 64.

# CGI's versioning scheme went 2.75, 2.751, 2.752, 2.753, 2.76
# That breaks the standard version tests, so we need to manually correct
# the version
if ($module eq 'CGI' && $vnum =~ /(2\.7\d)(\d+)/) {
$vnum = $1 . "." . $2;
}
# CPAN did a similar thing, where it has versions like 1.9304.
if ($module eq 'CPAN' and $vnum =~ /^(\d\.\d{2})\d{2}$/) {
$vnum = $1;
}

You may try the following:

if ($module eq 'CPAN' and $package ne 'DBI' and $vnum =~ /^(\d\.\d{2})\d{2}$/) {
$vnum = $1;
}

If that works you may want to file a bug:

http://www.bugzilla.org/developers/reporting_bugs.html

[Dave Miller]

According to CPAN, the current version is indeed 1.630. I smell a bug
in DBI...

Appending installation info to
/Library/Perl/Updates/5.12.4/darwin-thread-multi-2level/perllocal.pod
TIMB/DBI-1.630.tar.gz
/usr/bin/make install -- OK
rmbp:~ admin$ perl -MDBI -e 'print "$DBI::VERSION\n"'
1.63

Indeed.

Looks like there's a "$VERSION = eval $VERSION;" near the top of the
installed DBI.pm file... without any additional packaging that would
cause Perl to decide to treat it as a float and remove the trailing
zeros. commenting out that line seems to fix it enough for
checksetup.pl to pass. I couldn't tell you if it's safe to leave that
commented out or not though. I've no clue what the purpose of it is.

Dave Miller wrote:
> The dots in a version number are not decimal points, they are just
> position separators. 63 is less than 614, therefore you have an older

> version installed than what it's looking for. It's possible the

> author of this module forgot that and the one you have installed is

> really supposed to be 1.630. Might require some trickery to make it
> work :(
>
> Kenny Millar <kenny...@mac.com> wrote:
>> Thanks for your help so far. I tried using cpan to install DBI and
>> now I get the following....
>>
>> When I run ./checksetup.pl it gives a strange entry for DBI:
>> Checking perl modules... Checking for CGI.pm (v3.51)
>> ok: found v3.63 Checking for Digest-SHA (any) ok:
>> found v5.71 Checking for TimeDate (v2.23) ok: found
>> v2.24 Checking for DateTime (v0.28) ok: found v0.77
>> Checking for DateTime-TimeZone (v0.71) ok: found v1.51
>> Checking for DBI (v1.614) found v1.63 Checking
>> for Template-Toolkit (v2.22) ok: found v2.25 <snip>
>>
>> So it finds DBI V1.63, but it does not say OK, and then later in
>> the output it says:
>>
>> COMMANDS TO INSTALL REQUIRED MODULES (You *must* run all these
>> commands and then re-run checksetup.pl):
>>
>> /usr/bin/perl install-module.pl DBI
>>
>> And so I run the required command to install the required module
>> and it just says everything is OK, probably because it finds
>> v1.63: sh-3.2# ./install-module.pl DBI Checking for
>> CPAN (v1.81) ok: found v2.00 Checking for YAML
>> (any) ok: found v0.84 Checking for ExtUtils-MakeMaker
>> (v6.31) ok: found v6.6302 Reading '/var/root/.cpan/Metadata'

>> Database was generated on Thu, 07 Nov 2013 19:41:02 GMT Installing

>> DBI version 1.630... DBI is up to date (1.630).
>>

>> Mit freundlichen Grüßen,
>>
>> Thorsten Schöning
>>
>> -- Thorsten Schöning E-Mail:Thorsten....@AM-SoFT.de
>> AM-SoFT IT-Systeme http://www.AM-SoFT.de/
>>
>> Telefon...........05151- 9468- 55 Fax...............05151- 9468-
>> 88 Mobil..............0178-8 9468- 04
>>
>> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG
>> Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>>

>> _______________________________________________ support-bugzilla
>> mailing list support-...@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/support-bugzilla PLEASE put
>> support-...@lists.mozilla.org in the To: field when you
>> reply.
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>>
_______________________________________________
>> support-bugzilla mailing list support-...@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/support-bugzilla PLEASE put
>> support-...@lists.mozilla.org in the To: field when you
>> reply.
>

--

Dave Miller http://www.justdave.net/
IT Infrastructure Engineer, Mozilla http://www.mozilla.org/
Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/

[Dave Miller]

Except that in this case the version really is meant to be in the 600s
and not an extra digit on the end for a minor version. Our special-case
for this one would have to be adding the 0 on the end for that specific
version. Fortunately there never was a 1.63, it went from 1.57 to 1.601
and staying at 3 digits after the dot ever since. (there are some sub
versions after that, but they do the underscore in the middle, which we
deal with)

As I just posted, the bug is in DBI's version reporting. It's
internally doing an 'eval' on the version number after setting it which
makes Perl treat it like a float instead of a string. :( I submitted
the bug to the DBI maintainer.

Thorsten Schöning wrote:
> Guten Tag Dave Miller, am Freitag, 8. November 2013 um 07:08
> schrieben Sie:
>

>> It's possible the author of this module forgot that and the one you
>> have installed is really supposed to be 1.630.

> [...]

>>> Installing DBI version 1.630... DBI is up to date (1.630).
>

> Dave gave the right hint, the problem is with the version check in
> Bugzilla::Install::Requirements::have_vers. This function assumes
> that installing modules using CPAN with more than 2 digits after the
> . should not be interpreted as numeric values, but intermediate
> versions, meaning it uses 630 as something between 63 and 64.
>
> # CGI's versioning scheme went 2.75, 2.751, 2.752, 2.753, 2.76 # That
> breaks the standard version tests, so we need to manually correct #
> the version if ($module eq 'CGI' && $vnum =~ /(2\.7\d)(\d+)/) { $vnum
> = $1 . "." . $2; } # CPAN did a similar thing, where it has versions
> like 1.9304. if ($module eq 'CPAN' and $vnum =~ /^(\d\.\d{2})\d{2}$/)
> { $vnum = $1; }
>
> You may try the following:
>
> if ($module eq 'CPAN' and $package ne 'DBI' and $vnum =~
> /^(\d\.\d{2})\d{2}$/) { $vnum = $1; }
>
> If that works you may want to file a bug:
>
> http://www.bugzilla.org/developers/reporting_bugs.html
>

> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>

--

[Thorsten Schöning]

Guten Tag Dave Miller,
am Freitag, 8. November 2013 um 09:15 schrieben Sie:

> As I just posted, the bug is in DBI's version reporting. It's
> internally doing an 'eval' on the version number after setting it which
> makes Perl treat it like a float instead of a string. :( I submitted
> the bug to the DBI maintainer.

You're right, looks like I misinterpreted the regex, it only matches 4
digits after the dot at all, not three like in this special case.

> /^(\d\.\d{2})\d{2}$/

Mit freundlichen Grüßen,

Thorsten Schöning

--

[Dave Miller]

Dave Miller wrote:
> I submitted the bug to the DBI maintainer.

And got my reply back finally, here's the ticket:
https://rt.cpan.org/Public/Bug/Display.html?id=90142

[Kenny Millar]

Thanks Dave and Thorsten,

I edited the file so it would accept 1.63 and it now passes the requirements
check for DBI, however I am now back to my original problem, where I
started. At the end of checksetup I now get this again:

Checking for DBD-mysql (v4.001) ok: found v4.025
There was an error connecting to MySQL:

install_driver(mysql) failed: Attempt to reload DBD/mysql.pm aborted.

Compilation failed in require at (eval 1233) line 3, <DATA> line 577.

at Bugzilla/DB.pm line 1265.

This might have several reasons:

* MySQL is not running.
* MySQL is running, but there is a problem either in the
server configuration or the database access rights. Read the Bugzilla
Guide in the doc directory. The section about database configuration
should help.
* Your password for the 'bugs' user, specified in $db_pass, is
incorrect, in './localconfig'.
* There is a subtle problem with Perl, DBI, or MySQL. Make
sure all settings in './localconfig' are correct. If all else fails, set
'$db_check' to 0.

So I am back to the failing mysql connection.
I have again verified that I can connect to mysql using the db_user and
db_password which are in the localconfig file, and that there is 'bugs'
database therein.


Stumped again :-(

-Kenny


-----Original Message-----
From: support-bugzilla
[mailto:support-bugzilla-bounces+kennymillar=mac...@lists.mozilla.org] On
Behalf Of Dave Miller
Sent: 08 November 2013 08:49
To: support-...@lists.mozilla.org
Subject: Re: Installing on OS X Mavericks

[Kenny Millar]

Some more information..
Here's what I can tell you about my installation:

It is OS X Mavericks, 10.9 Build 13A603
I have apache as the webserver.
mysql -V shows: "mysql Ver 14.14 Distrib 5.6.14, for osx10.7 (x86_64) using
EditLineWrapper"
The user I am logged in as is called 'bugzilla', it is an administrator.
I can browse to http://localhost/~bugzilla and see that the web server is
working.
At the command line in terminal I can type 'mysql -p' without a path and log
into MySql with the root user password.
At the command line in terminal I can type 'mysql --user=bugs -p' and log
into MySQL with the 'bugs' username and password.
The bugzilla tarball is extracted to /Users/bugzilla/Sites/bz
The $db_user and $db_pass entries in localconfig are correct.
The $webservergroup in localconfig is set to '_www';
$db_sock is set to '';
$db_port is set to 0;

I have attached my localconfig file in case it is of any use. Don't worry I
have redacted the password :-)
I have also attached the full output from running ./checksetup in case it is
of any use.

I have followed all the instructions in section 2.2.2.2 of the Bugzilla
Guide

If I set db_check to 0 then checksetup still fails with a similar error.

I hope this is all useful, I'd like to get bugzilla running, but I'm kinda
stumped for now.

[Andreas Hauser]

Hi Kenny,

I had the exactly same problem while installing Bugzilla 4.4.1 on OS X Mavericks.
The problem at my system was a missing path-link to 'libmysqlclient.18.dylib'.

Without this path the 'check setup.pl' script can't find de necessary files for DBD::mysql.

To check the path I use command:
cd /Library/Perl/5.16/darwin-thread-multi-2level/auto/DBD/mysql
otool -L mysql.bundle

output:
mysql.bundle:
libmysqlclient.18.dylib (compatibility version 18.0.0, current version 18.0.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1197.1.1)

Problem was the first line.
To avoid this problem I add a symbolic link to 'libmysqlclient.18.dylib' with following command:
sudo ln -s /usr/local/mysql/lib/libmysqlclient.18.dylib /usr/lib/libmysqlclient.18.dylib

After this I was able to successfully install Bugzilla.

Hope this workaround will help you.

Greetz,
Andy

[nthi...@gmail.com]

On Friday, January 3, 2014 7:30:50 AM UTC-6, Andreas Hauser wrote:
>
> sudo ln -s /usr/local/mysql/lib/libmysqlclient.18.dylib /usr/lib/libmysqlclient.18.dylib
>

Thanks Andreas, very helpful

[brianouimette]

I received one other error and had to create a symbolic link. Now everything
is 100% operational

sudo ln -s /usr/local/mysql/lib/libmysqlclient.18.dylib
/usr/lib/libmysqlclient.18.dylib

--
View this message in context: http://mozilla.6506.n7.nabble.com/Installing-on-OS-X-Mavericks-tp297746p311436.html
Sent from the Bugzilla - Users mailing list archive at Nabble.com.