I've successfully setup a mysql 5.1 based database: "jiradb" that is fully accessible by a separate user: "jiradbuser". I've setup cgi scripts to access the db with no problems via bash and perl (using DBI pm). When I config the db for jira using the config.sh and pressig the "Test Connection" button, I get the error:
Error connecting to database
Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received
any packets from the server.
The only relative error message comes from a massive java trackback in /opt/atlassian/jira/logs/catalina.out file:
Sep 20, 2011 3:51:10 PM org.apache.catalina.core.StandardServer await
WARNING: StandardServer.await: Invalid command '' received
2011-09-21 11:40:01,941 http-8080-1 ERROR anonymous 700x37x1 1ie8v0y 192.168.220.55 /secure/SetupDatabase.jspa [atlassian.config.bootstrap.DefaultAtlassianBootstrapManager] Could not successfully test your database:
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
.. stuff deleted
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Unknown Source)
Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
I'm not a Java guy so any help would be appreciated....Brent
Anyone else setup a new mysql 5.1 db with the latest Jira?
Found an answer but we still have a problem. Shows up when pressing the "Test Connection" button from the config.sh script.
The only hostname that can be specified is either "localhost" or 127.0.0.1 where my /etc/hosts files specifies:
root@jiraa:~# cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 jiraa.belairnetworks.com jiraa
and my IP address is
root@jiraa:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:0c:29:75:5f:5e
inet addr:172.16.1.126 Bcast:172.16.1.255 Mask:255.255.254.0
... stuff deleted
I can't use jiraa, jiraa.belairnetworks.com or 172.16.1.126.
Note: This network configuration was automatically setup during the Ubuntu install, I changed nothing.
This mysql bug describes my problem exactly but when I checked the jar filelist, it was using mysql-connector-java-5.1.10.jar so it didn't fix my problem. I went to the Oracle/mysql site, and the latest version was 5.1.17 so I replaced the .10 with the .17 version and restarted the jira service but not difference.
Not as familiar with java or jars but I assumes a simply swap of the jar files and a restart of jira should pick up the later .17 version. Correct?
Why is something simple so hard.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Try to change database user login information that host. like this 'localhost' -> '%'
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you using non-standard port for the jdbc?
There is a bug reported for version 5.1.9 mysql-jdbc-driver: http://bugs.mysql.com/bug.php?id=47494
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You should take a look at this info.
http://confluence.atlassian.com/display/JIRA/Connecting+JIRA+to+MySQL
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, I have been following this instructions to a T both the manual setup and the GUI setup.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register NowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.