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

This widget could not be displayed.
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.

This widget could not be displayed.

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
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

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