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 vote
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 Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,311 views 14 20
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot