I have a server on which I have installed Jira application. Now we have changed the IP schema and since then I am not able to access Jira. In catalina.out log I have found below error
2016-04-18 13:12:55,958 localhost-startStop-1 ERROR [o.o.c.entity.jdbc.DatabaseUtil] Unable to establish a connection with the database... Error was:org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
2016-04-18 13:12:55,959 localhost-startStop-1 ERROR [o.o.c.entity.jdbc.DatabaseUtil] Could not get table name information from the database, aborting.
2016-04-18 13:12:55,982 localhost-startStop-1 ERROR [NoModule] Error getting datasource via DBCP: JdbcDatasourceInfo{uri='jdbc:postgresql://192.168.1.228:5432/jira', driverClassName='org.postgresql.Driver', username='super', 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=null, minEvictableTimeMillis=null, timeBetweenEvictionRunsMillis=null, poolPreparedStatements=null, testOnBorrow=null, testOnReturn=null, testWhileIdle=null, maxOpenPreparedStatements=null, numTestsPerEvictionRun=null, removeAbandonedTimeout=300, validationQueryTimeout=null, defaultCatalog=null}}
java.lang.RuntimeException: javax.management.InstanceAlreadyExistsException: com.atlassian.jira:name=BasicDataSource
Any idea where and how to change that IP?
I go into /opt/atlassian/jira/bin folder and run ./config.sh
There I entered proper details and then save the config.
This time dbconfig.xml file generated in /var/atlassian/application-data/jira/ folder.
And my issue resolved.
Related
So I am trying to use my xampp server and for the life of me can't understand why my ProFTPD will not turn on. It only became cause for concern when I saw the word "bogon" in the application log. Can anyone translate to me what the application log means and maybe how I go about troubleshooting the problem ?
Stopping all servers...
Stopping Apache Web Server...
/Applications/XAMPP/xamppfiles/apache2/scripts/ctl.sh : httpd stopped
Stopping MySQL Database...
/Applications/XAMPP/xamppfiles/mysql/scripts/ctl.sh : mysql stopped
Starting ProFTPD...
Exit code: 8
Stdout:
Checking syntax of configuration file
proftpd config test fails, aborting
Stderr:
bogon proftpd[3948]: warning: unable to determine IP address of 'bogon'
bogon proftpd[3948]: error: no valid servers configured
bogon proftpd[3948]: Fatal: error processing configuration file '/Applications/XAMPP/xamppfiles/etc/proftpd.conf'
I'm new to Scala with SBT and I'm trying to figure out the new IntelliJIDE.
When I follow the tutorial for setting up the below shows up:
ERRORS Server access Error: Connection timed out: connect
url=https://repo1.maven.org/maven2/org/scala-sbt/sbt/0.13.13/sbt-0.13.13.pom
Server access Error: Connection timed out: connect
url=https://repo1.maven.org/maven2/org/scala-sbt/sbt/0.13.13/sbt-0.13.13.jar
Server access Error: Connection timed out: connect
url=https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt/0.13.13/ivys/ivy.xml
Server access Error: Connection timed out: connect
url=https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.scala-sbt/sbt/0.13.13/ivys/ivy.xml
After adding the below artifact its still the same
Artifact added
sbt artifact does not exist on the repos that are being accessed.
Add the following repository and then it will be able to fetch sbt:
https://repo.lightbend.com/typesafe/ivy-releases/
Android application returns error while creating connection with Open Fire while it works fine at my local server.
10-07 14:58:32.347 26785-27124/com.testing.online_soping_app E/XMPPChatDemoActivity: Could not connect to http://demo.vaidiksolutions.in:5222.: remote-server-timeout(504) Could not connect to https://demo.vaidiksolutions.in:5222.
-- caused by: java.net.UnknownHostException: Host is unresolved: http://demo.vaidiksolutions.in
10-07 14:58:32.347 26785-27124/com.testing.online_soping_app E/XMPPChatDemoActivity: Failed to log in as mohit
10-07 14:58:32.347 26785-27124/com.testing.online_soping_app E/XMPPChatDemoActivity: java.lang.IllegalStateException: Not connected to server.
It looks like DNS failed to resolve this domain. Have you tried to ping the server domain?
If the ping is OK, you may try to connect using IP directly.
On starting jboss I am getting the following error :
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
State: NOTYETINSTALLED
Depends On Me:
jboss.ejb:service=EJBTimerService,persistencePolicy=database
jboss:service=KeyGeneratorFactory,type=HiLo
jboss.mq:service=StateManager
jboss.mq:service=PersistenceManager
And for all database connections in the servlet I get the following exception :
org.postgresql.util.PSQLException: FATAL: password a
uthentication failed for user "poll"
It was working fine and all of a sudden I started getting these errors. My password is correct. I even tried changing the password and then tried again it showed the same exception. What is happening here?
The DefaultDS data source is what the name suggests; the default datasource. It ships with JBoss and is configured to use the Hypersonic (ie in-memory) database. JBoss uses the DefaultDS datasource to read/write internal queues, timed events, etc
Check the file ../conf/standardjbosscmp-jdbc.xml to see what you've got configured for the DefaultDS datasource. It sounds like you've edited that file unintentionally. Unless you need to persist internal queues etc across boots, just leave it as shipped using Hypersonic.
See the JBoss doc for more.
I am currently trying to evaluate AWS for my company and was trying to follow the tutorials on the web.
http://developer.amazonwebservices.com/connect/entry.jspa?externalID=2241
However I get the below error during startup of the server instance:
Unable to associated Elastic IP with cluster: Unable to detect that the Elastic IP was orrectly associated.
java.lang.Exception: Unable to detect that the Elastic IP was correctly associated
at com.amazonaws.ec2.cluster.Cluster.associateElasticIp(Cluster.java:802)
at com.amazonaws.ec2.cluster.Cluster.start(Cluster.java:311)
at com.amazonaws.eclipse.wtp.ElasticClusterBehavior.launch(ElasticClusterBehavior.java:611)
at com.amazonaws.eclipse.wtp.Ec2LaunchConfigurationDelegate.launch(Ec2LaunchConfigurationDelegate.java:47)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696)
at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3051)
at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3001)
at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:300)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Then after a while, another error occur:
Unable to publish server configuration files: Unable to copy remote file after trying 4 timeslocal file: 'XXXXXXXX/XXX.zip'
Results from first attempt:
Unexpected exception: java.net.ConnectException: Connection timed out: connect
root cause: java.net.ConnectException: Connection timed out: connect
at com.amazonaws.eclipse.ec2.RemoteCommandUtils.copyRemoteFile(RemoteCommandUtils.java:128)
at com.amazonaws.eclipse.wtp.tomcat.Ec2TomcatServer.publishServerConfiguration(Ec2TomcatServer.java:172)
at com.amazonaws.ec2.cluster.Cluster.publishServerConfiguration(Cluster.java:369)
at com.amazonaws.eclipse.wtp.ElasticClusterBehavior.publishServer(ElasticClusterBehavior.java:538)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:866)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2731)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:278)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Can anyone point me to what I'm doing wrong?
I followed the tutorials and the video tutorials on youtube exactly.
Best Regards
~Jeffrey
Problem has been resolved, it is due to the Elastic IP being assigned to the Server on creation.
Eclipse is unable to connect to the server if it is used.