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

Accepted Answer
0 votes
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
Posted Tuesday in Jira

Looking for anyone who made the switch to Data Center

The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...

47 views 0 2
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