Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to import data from Bugzilla 4.0.2

Rob Butlin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 18, 2012

I'm trying to use the Jira External Import tool to import data from Bugzilla 4.0.2 and can't seem to connect the Bugzilla MySQL database. The bugzilla database I'm connecting to is hosted on the same server as the Jira installation, and is running a MySQL 5.0.67 database.

The steps taken to reproduce the issues are;

Jira Administration -> Import & Export -> External System Import -> Bugzilla

I enter the following information into the form; (NOTE: The MySQL database for bugzilla has the schema name 'bugs')

Bugzilla database URL: jdbc:mysql://localhost/bugs?autoReconnect=true&useUnicode=true

Database login name: root

Database login password: <root password="">

Driver name: com.mysql.jdbc.Driver

After clicking 'Next >>', the following error is displayed;

Errors

Could not connect to 'jdbc:mysql://localhost/bugs?autoReconnect=true&useUnicode=true&user=root&password=xxxxxx'

----------------

I'm able to connect to the MySQL database using MySQL Workbench.

Rob

2 answers

0 votes
Stephen Hartley
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 18, 2012

fghfghgfhfghfgh

0 votes
LucasA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 18, 2012

Hi Rob,

On the "Bugzilla database URL" the port is missing. Would you give a try using "jdbc:mysql://localhost:3306/bugs?autoReconnect=true&useUnicode=true" instead?

Best regards,
Lucas Timm

Stephen Hartley
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 18, 2012

Hi Lucas

I am also looking at this with Rob. I added the port as suggested and still get the same error. Does jira log the problem in more detail somewhere? There must be an underlying JDBC exception which might give us a pointer?

Thanks


Steve

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events