Cant able to connect jira 5.1 to mysql 5.1

I tried to connect Jira to Mysql,which are installed inside a virtual machine.

I am getting the log file as below.:

2012-08-08 18:41:37,609 main INFO [jira.config.database.SystemTenantDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/jiranew/dbconfig.xml
2012-08-08 18:41:48,283 main INFO [atlassian.jira.startup.JiraStartupLogger]

****************
JIRA starting...
****************

2012-08-08 18:41:48,304 main INFO [atlassian.jira.startup.JiraStartupLogger]

___ Environment _____________________________

JIRA Build : 5.1#768-sha1:38ad524e8304c25f0d2e7eaa88ad827b3f7625e4
Build Date : Thu Jul 05 00:00:00 IST 2012
JIRA Installation Type : Standalone
Application Server : Apache Tomcat/6.0.32 - Servlet API 2.5
Java Version : 1.6.0_26 - Sun Microsystems Inc.
Current Working Directory : /opt/atlassian/jira/jiranew/bin
Maximum Allowable Memory : 742MB
Total Memory : 247MB
Free Memory : 181MB
Used Memory : 66MB
Memory Pool: Code Cache : Code Cache: init = 2555904(2496K) used = 1007680(984K) committed = 2555904(2496K) max = 50331648(49152K)
Memory Pool: Eden Space : Eden Space: init = 71630848(69952K) used = 68973424(67356K) committed = 71630848(69952K) max = 214827008(209792K)
Memory Pool: Survivor Space : Survivor Space: init = 8912896(8704K) used = 0(0K) committed = 8912896(8704K) max = 26804224(26176K)
Memory Pool: Tenured Gen : Tenured Gen: init = 178978816(174784K) used = 0(0K) committed = 178978816(174784K) max = 536870912(524288K)
Memory Pool: Perm Gen : Perm Gen: init = 21757952(21248K) used = 16381744(15997K) committed = 21757952(21248K) max = 268435456(262144K)
JVM Input Arguments : -Djava.util.logging.config.file=/opt/atlassian/jira/jiranew/conf/logging.properties -XX:MaxPermSize=256m -Xms256m -Xmx768m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -XX:+PrintGCDateStamps -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/opt/atlassian/jira/jiranew/endorsed -Dcatalina.base=/opt/atlassian/jira/jiranew -Dcatalina.home=/opt/atlassian/jira/jiranew -Djava.io.tmpdir=/opt/atlassian/jira/jiranew/temp

___ Java System Properties _________________

atlassian.standalone : JIRA
catalina.base : /opt/atlassian/jira/jiranew
catalina.home : /opt/atlassian/jira/jiranew
catalina.useNaming : true
common.loader : ${catalina.base}/lib,
${catalina.base}/lib/*.jar,
${catalina.home}/lib,
${catalina.home}/lib/*.jar
file.encoding : UTF-8
file.encoding.pkg : sun.io
java.awt.graphicsenv : sun.awt.X11GraphicsEnvironment
java.awt.headless : true
java.awt.printerjob : sun.print.PSPrinterJob
java.class.version : 50.0
java.home : /opt/atlassian/jira/jiranew/jre
java.io.tmpdir : /opt/atlassian/jira/jiranew/temp
java.naming.factory.initial : org.apache.naming.java.javaURLContextFactory
java.naming.factory.url.pkgs : org.apache.naming
java.runtime.name : Java(TM) SE Runtime Environment
java.runtime.version : 1.6.0_26-b03
java.specification.name : Java Platform API Specification
java.specification.vendor : Sun Microsystems Inc.
java.specification.version : 1.6
java.util.logging.config.file : /opt/atlassian/jira/jiranew/conf/logging.properties
java.util.logging.manager : org.apache.juli.ClassLoaderLogManager
java.vendor : Sun Microsystems Inc.
java.vendor.url : http://java.sun.com/
java.vendor.url.bug : http://java.sun.com/cgi-bin/bugreport.cgi
java.version : 1.6.0_26
java.vm.info : mixed mode
java.vm.name : Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.name : Java Virtual Machine Specification
java.vm.specification.vendor : Sun Microsystems Inc.
java.vm.specification.version : 1.0
java.vm.vendor : Sun Microsystems Inc.
java.vm.version : 20.1-b02
mail.mime.decodeparameters : true
org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER : true
os.arch : amd64
os.name : Linux
os.version : 2.6.32-38-generic
package.access : sun.,
org.apache.catalina.,
org.apache.coyote.,
org.apache.tomcat.,
org.apache.jasper.,
sun.beans.
package.definition : sun.,
java.,
org.apache.catalina.,
org.apache.coyote.,
org.apache.tomcat.,
org.apache.jasper.
server.loader :
shared.loader :
sun.arch.data.model : 64
sun.boot.library.path : /opt/atlassian/jira/jiranew/jre/lib/amd64
sun.cpu.endian : little
sun.cpu.isalist :
sun.desktop : gnome
sun.io.unicode.encoding : UnicodeLittle
sun.java.command : org.apache.catalina.startup.Bootstrap start
sun.java.launcher : SUN_STANDARD
sun.jnu.encoding : UTF-8
sun.management.compiler : HotSpot 64-Bit Tiered Compilers
sun.os.patch.level : unknown
tomcat.util.buf.StringCache.byte.enabled : true
user.country : IN
user.dir : /opt/atlassian/jira/jiranew/bin
user.home : /home/jira
user.language : en
user.name : jira
user.timezone : Asia/Kolkata

2012-08-08 18:41:48,723 main INFO [atlassian.jira.startup.JiraStartupLogger] Running JIRA startup checks.
2012-08-08 18:41:49,566 main INFO [atlassian.jira.startup.JiraHomeStartupCheck] The jira.home directory '/var/atlassian/application-data/jira/jiranew' is validated and locked for exclusive use by this instance.
2012-08-08 18:41:49,567 main INFO [atlassian.jira.startup.JiraStartupLogger] JIRA pre-database startup checks completed successfully.
2012-08-08 18:41:54,712 main INFO [jira.config.database.SystemTenantDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/jiranew/dbconfig.xml
2012-08-08 18:41:56,612 main INFO [jira.config.database.DatabaseConfigurationManagerImpl] Now running Database Checklist Launcher
2012-08-08 18:42:00,181 main ERROR [NoModule] Error getting datasource via DBCP: JdbcDatasourceInfo{uri='jdbc:mysql://dbserver:3306/jiradb?useUnicode=true&characterEncoding=UTF8&sessionVariables=storage_engine=InnoDB', driverClassName='com.mysql.jdbc.Driver', username='jiradbuser', password='********', isolationLevel='null', connectionProperties=null, connectionPoolInfo=ConnectionPoolInfo{maxSize=20, minSize=20, initialSize=null, maxIdle=20, maxWait=30000, sleepTime=300000, lifeTime=600000, deadLockMaxWait=600000, deadLockRetryWait=10000, validationQuery='select 1', minEvictableTimeMillis=60000, timeBetweenEvictionRunsMillis=300000, poolPreparedStatements=null, testOnBorrow=null, testOnReturn=null, testWhileIdle=true, maxOpenPreparedStatements=null, numTestsPerEvictionRun=null, removeAbandonedTimeout=300, validationQueryTimeout=3, defaultCatalog=null}}
org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (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 org.apache.commons.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549)
at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)
at org.apache.commons.dbcp.BasicDataSource.setLogWriter(BasicDataSource.java:1134)
at org.ofbiz.core.entity.transaction.DBCPConnectionFactory.getConnection(DBCPConnectionFactory.java:109)
at org.ofbiz.core.entity.ConnectionFactory.tryGenericConnectionSources(ConnectionFactory.java:69)
at org.ofbiz.core.entity.transaction.JNDIFactory.getConnection(JNDIFactory.java:146)
at org.ofbiz.core.entity.TransactionFactory.getConnection(TransactionFactory.java:101)
at org.ofbiz.core.entity.ConnectionFactory.getConnection(ConnectionFactory.java:59)
at com.atlassian.jira.ofbiz.DefaultOfBizConnectionFactory.getConnection(DefaultOfBizConnectionFactory.java:28)
at com.atlassian.jira.upgrade.util.UpgradeUtils.tableExists(UpgradeUtils.java:100)
at com.atlassian.jira.appconsistency.db.MinimumUpgradableVersionCheck.databaseSetup(MinimumUpgradableVersionCheck.java:49)
at com.atlassian.jira.appconsistency.db.MinimumUpgradableVersionCheck.isOk(MinimumUpgradableVersionCheck.java:30)
at com.atlassian.jira.startup.JiraDatabaseConfigChecklist.doStartupChecks(JiraDatabaseConfigChecklist.java:63)
at com.atlassian.jira.startup.JiraDatabaseConfigChecklist.startupOK(JiraDatabaseConfigChecklist.java:51)
at com.atlassian.jira.startup.DatabaseChecklistLauncher.start(DatabaseChecklistLauncher.java:35)
at com.atlassian.jira.startup.DefaultJiraLauncher$2.run(DefaultJiraLauncher.java:90)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:284)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseConfigured(DatabaseConfigurationManagerImpl.java:175)
at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:85)
at com.atlassian.jira.startup.DefaultJiraLauncher.access$100(DefaultJiraLauncher.java:24)
at com.atlassian.jira.startup.DefaultJiraLauncher$1.run(DefaultJiraLauncher.java:61)
at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:33)
at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:56)
at com.atlassian.jira.startup.LauncherContextListener$1.create(LauncherContextListener.java:67)
at com.atlassian.jira.startup.LauncherContextListener$1.create(LauncherContextListener.java:62)
at com.atlassian.multitenant.impl.MultiTenantComponentMapImpl.get(MultiTenantComponentMapImpl.java:121)
at com.atlassian.multitenant.impl.MultiTenantComponentMapImpl.onTenantStart(MultiTenantComponentMapImpl.java:165)
at com.atlassian.multitenant.impl.DefaultMultiTenantManager$1.consume(DefaultMultiTenantManager.java:134)
at com.atlassian.multitenant.impl.DefaultMultiTenantManager$1.consume(DefaultMultiTenantManager.java:131)
at com.atlassian.multitenant.impl.DefaultMultiTenantManager.runForEachListener(DefaultMultiTenantManager.java:256)
at com.atlassian.multitenant.impl.DefaultMultiTenantManager.startTenant(DefaultMultiTenantManager.java:130)
at com.atlassian.multitenant.impl.DefaultMultiTenantManager.startAll(DefaultMultiTenantManager.java:203)
at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:95) <+12> (StandardContext.java:4205) (StandardContext.java:4704) (ContainerBase.java:1053) (StandardHost.java:840) (ContainerBase.java:1053) (StandardEngine.java:463) (StandardService.java:525) (StandardServer.java:754) (Catalina.java:595)
at java.lang.reflect.Method.invoke(Unknown Source) <+2> (Bootstrap.java:289) (Bootstrap.java:414)
Caused by: 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)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) <+2>
at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1074)
at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2214)
at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:781)
at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:46) <+3>
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:352)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:284)
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1556)
at org.apache.commons.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1545)
... 47 more
Caused by: 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)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1074)
at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:343)
at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2137)
... 60 more
Caused by: java.net.UnknownHostException: dbserver
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$1.lookupAllHostAddr(Unknown Source)
at java.net.InetAddress.getAddressFromNameService(Unknown Source)
at java.net.InetAddress.getAllByName0(Unknown Source)
at java.net.InetAddress.getAllByName(Unknown Source)
at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:243)
at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:292)
... 61 more
2012-08-08 18:42:00,721 main ERROR [atlassian.jira.startup.LauncherContextListener] Unable to start JIRA.
com.atlassian.jira.exception.DataAccessException: 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 com.atlassian.jira.upgrade.util.UpgradeUtils.tableExists(UpgradeUtils.java:127)
at com.atlassian.jira.appconsistency.db.MinimumUpgradableVersionCheck.databaseSetup(MinimumUpgradableVersionCheck.java:49)
at com.atlassian.jira.appconsistency.db.MinimumUpgradableVersionCheck.isOk(MinimumUpgradableVersionCheck.java:30)
at com.atlassian.jira.startup.JiraDatabaseConfigChecklist.doStartupChecks(JiraDatabaseConfigChecklist.java:63)
at com.atlassian.jira.startup.JiraDatabaseConfigChecklist.startupOK(JiraDatabaseConfigChecklist.java:51)
at com.atlassian.jira.startup.DatabaseChecklistLauncher.start(DatabaseChecklistLauncher.java:35)
at com.atlassian.jira.startup.DefaultJiraLauncher$2.run(DefaultJiraLauncher.java:90)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:284)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseConfigured(DatabaseConfigurationManagerImpl.java:175)
at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:85)
at com.atlassian.jira.startup.DefaultJiraLauncher.access$100(DefaultJiraLauncher.java:24)
at com.atlassian.jira.startup.DefaultJiraLauncher$1.run(DefaultJiraLauncher.java:61)
at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:33)
at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:56)
at com.atlassian.jira.startup.LauncherContextListener$1.create(LauncherContextListener.java:67)
at com.atlassian.jira.startup.LauncherContextListener$1.create(LauncherContextListener.java:62)
at com.atlassian.multitenant.impl.MultiTenantComponentMapImpl.get(MultiTenantComponentMapImpl.java:121)
at com.atlassian.multitenant.impl.MultiTenantComponentMapImpl.onTenantStart(MultiTenantComponentMapImpl.java:165)
at com.atlassian.multitenant.impl.DefaultMultiTenantManager$1.consume(DefaultMultiTenantManager.java:134)
at com.atlassian.multitenant.impl.DefaultMultiTenantManager$1.consume(DefaultMultiTenantManager.java:131)
at com.atlassian.multitenant.impl.DefaultMultiTenantManager.runForEachListener(DefaultMultiTenantManager.java:256)
at com.atlassian.multitenant.impl.DefaultMultiTenantManager.startTenant(DefaultMultiTenantManager.java:130)
at com.atlassian.multitenant.impl.DefaultMultiTenantManager.startAll(DefaultMultiTenantManager.java:203)
at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:95) <+12> (StandardContext.java:4205) (StandardContext.java:4704) (ContainerBase.java:1053) (StandardHost.java:840) (ContainerBase.java:1053) (StandardEngine.java:463) (StandardService.java:525) (StandardServer.java:754) (Catalina.java:595)
at java.lang.reflect.Method.invoke(Unknown Source) <+2> (Bootstrap.java:289) (Bootstrap.java:414)
Caused by: 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)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) <+2>
at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1074)
at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2214)
at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:781)
at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:46) <+3>
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:352)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:284)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at org.ofbiz.core.entity.ConnectionFactory.tryGenericConnectionSources(ConnectionFactory.java:87)
at org.ofbiz.core.entity.transaction.JNDIFactory.getConnection(JNDIFactory.java:146)
at org.ofbiz.core.entity.TransactionFactory.getConnection(TransactionFactory.java:101)
at org.ofbiz.core.entity.ConnectionFactory.getConnection(ConnectionFactory.java:59)
at com.atlassian.jira.ofbiz.DefaultOfBizConnectionFactory.getConnection(DefaultOfBizConnectionFactory.java:28)
at com.atlassian.jira.upgrade.util.UpgradeUtils.tableExists(UpgradeUtils.java:100)
... 38 more
Caused by: 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)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1074)
at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:343)
at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2137)
... 55 more
Caused by: java.net.UnknownHostException: dbserver
at java.net.InetAddress.getAllByName0(Unknown Source)
at java.net.InetAddress.getAllByName(Unknown Source)
at java.net.InetAddress.getAllByName(Unknown Source)
at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:243)
at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:292)

PLEASE GIVE ME A SOLUTION TO ME AS SOON AS POSSIBLE...

thanks

10 answers

1 accepted

Looking at your log.txt, your server name is now "server&" when probably it should be "server". You simply have a typo there. Also, please ping server and see if responds (Check your network conenctivity or ask somebody to check it for you)

hi Radu,

No i tried with "server" also...now i changed it to "localhost" with mysql in another seperate VM.then alo i am getting the log as:

Nithin,

You say A and non-A in this post; you said to Jobin: mysql it's in the same VM, now you tell me it's another VM.The problem is very simple, you are still providing the wrong database host to JIRA.

I really believe you need on-site help from somebody with a fair knowledge of TCP; or please read some TCP tutorials.

hi Radu,

thanks for your response.

for now as a test i am trying the environment with jira and mysql on same VM, if it get succeeded i can move to my actual need(jira and mysql in seperate).thats what i said to jobin.

thank you

Then, instead of server / dbserver, put 127.0.0.1 and retry (or the public IP of the machine)

radu,

i tried with that too dude ...but its not getting done.

Hi Nithin,

The UnknownHostException means that the server JIRA is running on can't find the server you have specified to use as the database server. Is "dbserver" the name of your MySQL server as that's what JIRA is looking for (jdbc:mysql://dbserver:3306/jiradb?useUnicode=true&characterEncoding=UTF8&sessionVariables=storage_engine=InnoDB)

If the name of the server is incorrect, update the details in dbconfig.xml and try again.

Hope that helps?

Andrew.

Yeap, the error is Caused by: java.net.UnknownHostException: dbserver

Either update your hosts (adding an entry for dbserver) - not recommended, either update your resolv.conf (adding the DNS resolver correctly) or simply change the 'dbserver' to real name / IP.

Hi Andrew,

Thank u for your reply..

I have tried by updating my server name "server" to the dbconfig.xml file but still it is showing the error as in my log file attachment. (log.txt) (as now i amtrying with jira and mysql in the same vm but my actual need is to have them in seperate VM)

Please relty me ASAP...

Thank u..:)

Hi Andrew,

Thank u for your reply..

I have tried by updating my server name "server" to the dbconfig.xml file but still it is showing the error as in my log file attachment. (log.txt) (as now i amtrying with jira and mysql in the same vm but my actual need is to have them in seperate VM)

Please relpy me ASAP...

Thank u..:)

Hi Nithin,

Looking at the log file it's now trying to connect to jdbc:mysql://server&:3306/jiradb?useUnicode=true&characterEncoding=UTF8&sessionVariables=storage_engine=InnoDB

Try changing "server&" to the actual hostname or IP address of the server that MySQL is running on, if that's on the same VM as JIRA then using the following connection URL should work:

jdbc:mysql://localhost:3306/jiradb?useUnicode=true&characterEncoding=UTF8&sessionVariables=storage_engine=InnoDB

Regs,

Andrew.

1 vote

The problem is in your network. You are not able to connect to the MySQL server properly I guess. Is it on same machine? If so, try with 127.0.0.1 as ip. If not, try using a MySQL client and see if you can connect.

Hi Jobin,

Thank u for your reply..

I have tried by updating my server name "server" to the dbconfig.xml file but still it is showing the error as in my log file attachment. (log.txt) (as now i amtrying with jira and mysql in the same vm but my actual need is to have them in seperate VM)

Please relty me ASAP...

Thank u..:)

Hi Jobin,

Thank u for your reply..

I have tried by updating my server name "server" and also with ip address to the dbconfig.xml file but still it is showing the error as in my log file attachment. (log.txt) (as now i am trying with jira and mysql in the same vm but my actual need is to have them in seperate VM)

Please relpy me ASAP...

Thank u..:)

I guess there is nothing we can do to help because it is a connectivity issue. You will need your network guys involved.

Hi Jobin,

but my set up is in same VM...how will effect the connectivity issues?

when i tried with config.sh file (for using JIRA configuration tool) it is showing that

No JRE_HOME or JAVA_HOME environment variable is set - attempting to just run java command
Loading application properties from /opt/atlassian/jira/jiranew/atlassian-jira/WEB-INF/classes/jira-application.properties
Reading database configuration from /var/atlassian/application-data/jira/jiranew/dbconfig.xml

...but still JIRA configuration tool is coming and i am getting a connection error when i tried with the mysql connection.

But when i start Jira using start-jira.sh it is showing JRE_HOME="/opt/atlassian/jira/"....

how to resolve this problem of connecting to mysql...

My SET UP:

jira installed in ubuntu with atlassian-jira-5.1.2-x64.bin installer

i neeed to connect with mysql which is installed in seperate VM(both jira and mysql in seperate VM)

i didnt installed any java package into the ubuntu system...but after deployment in the VM where i have installed jira, when i type which java, it is showing "/usr/vmware-jre/bin/java"

please kindly give me a fast solution..

hi,

when i edit my dbconfig file and restart jira i am getting the jira as shown below...log file is same as i uploaded earlier.

Nithin, like Radu says, at least get the ping work between the machines before even thinking about JIRA and MySQL.

And can you tell the IP addresses of your VMs, which u said that u tried?

hi renjith,

ip that i have given is 192.168.0.153(jira n mysql in seperete vm...jira on 192,168,0,155 and mysql on 192.168.0.153)...but now i can able to connect to mysql which is in the same vm....

hi guys...

thanks to all helped me till now...now i can connect to mysql in the same vm where jira installed...

i just go through the browser settings without going through jira configuration tool or dbconfig.xml file...now it is working for me with jira and mysql in same vm....

did i want to set up any additional things to connect to mysql in seperate vm?(mysql client or anything?)..

please help me...i am getting the error when i try to connect...

Hi Nithin,

You don't need a special MySQL client or anything, I think you've still got a general connectivity problem between your JIRA VM and your MySQL VM.

You said that the IP of the MySQL VM was 192.168.0.153? From a command line on your JIRA VM can you get a connection if you enter "telnet 192.168.0.153 3306" without the quotes? If you don't get a connection using telnet you need to troubleshoot the network first and get that working before trying to connect using JIRA.

Hope that helps?

Andrew.

Hi andrew,

i tried with what you have said me.(telnet 192.168.0.154(my new mysql vm ip is 192.168.0.154 and jira is 192.168.0.155)).but iam getting as follows:

nithin@appserver:~$ telnet 192.168.0.154 3306
Trying 192.168.0.154...
telnet: Unable to connect to remote host: Connection refused
nithin@appserver:~$

and when i tried to connect the db with jira i am getting the console as(i tried with ip,dbserver(name of mysql server) all showing same result)...

i am using a proxy server to connect all these vm to access internet(squid proxy-ip-192.168.0.114:3128)

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Wednesday in Jira

Join our webinar: How 1B+ feature flag events helped us build the new Jira

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...

93 views 0 1
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