After restarting the Machine, JIRA wouldn't connect to mySQL Database anymore. If i try to connect manually, the output says the following:
ERROR 2002 (HY000): Can't connect to local MySQL Server through Socket '/var/lib/mysql/mysql.sock' (111)
I haven't changed anything. Only shutdown, then making an Image of the Machine and after that booting up.
Can anyone help me?
Oops. I forgot. Can you check that MySQL is actually running? You get that error a lot when it's not running. Try "ps -ef | grep -i my"
Possibly, but I'm not sure. Could you also try
mysql -h 127.0.0.1 -u user -p
mysql -h ::1 -u user -p
And check the error messages carefully.
(Your Jira config looks absolutely fine, this is a problem with mysql connecting locally. It's a lot easier to debug with the mysql client than Jira)
I have tried everything you suggested, but without success. Unfortunately!
MySQL is not running. IPv6 (::1) is an Unknown Host and to 127.0.0.1 the client can't connect.
Here are my Results:
I have checked /etc/my.cnf. But I have no BaseDir. Only a DataDir.
Here is the File:
The command I gave you (ps -ef | grep -i my) clearly states that there are no processes with "mysql" in their name/description running.
MySQL server almost always runs at least one process with mysqld in the name of it, unless you've deliberately hacked it to run with a totally different name.
The service script is checking the wrong thing, probably a lock from an improper shutdown
Well, there's no processes to kill, because the server isn't running.
The situation you're in usually happens when the machine shuts down too "hard" for MySQL to stop in time, or you kill the mysql process with violence, not giving it enough time to clean up.
The first thing I'd try is "mv /var/lib/mysql/mysql.sock ~" - hopefully, that is the only hangover left, and that's what's blocking it. If I'm right about that, then your "./mysqld start" should restart the service and clean up anything else that is lying around. Before using it though, I'd read the logs to see if there are any warnings (they're usually quite good - they'll ask you to restart if there's any need to)
I have resolved the Issue.
Others with the same Problem, should do the followinig:
1. Rename "mysql.sock" to "mysql.sock.bak" (/var/lib/mysql)
2. Start the Service again: "service mysqld start"
3. Try to connect: mysql -h localhost -u user -p
4. Be happy! :-)
But one Thing you have to do additional. If you get the Message, that Jira is locked, you have to delete the File ".jira-home.lock" at the Jira Home Folder. Finally you have to restart the Server and all is fine again.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG