Importing Bugzilla data when it uses a Unix socket rather than a TCP Port

Subject says most of it...

It looks like our Bugzilla set up uses a Unix socket (/var/run/mysqld/mysqld.sock) rather than a tcp port, so the importer doesn't even start. Is there a workaround?

2 answers

1 accepted

0 votes
Accepted answer
Yilin Mo Atlassian Team May 26, 2013

You can probably temporary switch the mode to the TCP connection during the importing procedure :

http://www.chriswpage.com/2010/04/mysql-force-localhost-to-use-tcp-instead-of-unix-socket-file

as importer plugin currently not supported for the Unix socket connection.

Yilin,

I switched it as suggested, and the import worked just fine!

Thank you.

Paul

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,084 views 4 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you