Jira and Confluence configuration issues

The server restarted yesterday, and then a lot of services needed to be restarted, running an automation script,

View the Tomcat status, both normal and then access the server and discover that Tomcat Jira and Wikr (confluence) are automatically turned off;

Find out why, awkward time has come:

To Jira_home under find clues, found Dbconfig.xml and jira.lock These two files, judge should be the boot lock file, hence deleted;

Restart Tomcat, behind the cool things come!!!!

Jira actually need to reconfigure!!!!

Alas, the hands of the cheap Ah, no way to find information, ask Daniel, the solution is as follows:

Replace the contents of the Dbconfig.xml file with:

<?xml version= "1.0" encoding= "UTF-8"?>

<jira-database-config>

<name>defaultDS</name>

<delegator-name>default</delegator-name>

<database-type>MySQL</database-type>

<jdbc-datasource>

<url>jdbc:mysql://localhost:3306/jira_new? useunicode=true&amp;characterencoding= Utf8&amp;sessionvariables=storage_engine=innodb</url>

<driver-class>com.mysql.jdbc.Driver</driver-class>

<username>Jira</username>

<password>jiradev169</password>

<pool-min-size>20</pool-min-size>

<pool-max-size>20</pool-max-size>

<pool-max-wait>30000</pool-max-wait>

<validation-query>select 1</validation-query>

<min-evictable-idle-time-millis>60000</min-evictable-idle-time-millis>

<time-between-eviction-runs-millis>300000</time-between-eviction-runs-millis>

<pool-max-idle>20</pool-max-idle>

<pool-remove-abandoned>true</pool-remove-abandoned>

<pool-remove-abandoned-timeout>300</pool-remove-abandoned-timeout>

<pool-test-while-idle>true</pool-test-while-idle>

<validation-query-timeout>3</validation-query-timeout>

</jdbc-datasource>

</jira-database-config>

Where the red word for the need to make changes in the place, different server is not the same situation, the use of what database, port, account password;

To this step, thought, should be OK! Restart Tomcat;

Haha, the heart of the flowering, can be normal access, but the problem came again, into the page, the control console graphics display garbled!!

What the hell is going on here?

No way, still want to find Ah!

Start with the database! After all, the service has been started, and can be accessed, nothing more than a database call problem;

View database users, sure enough!! Jira User no more!!

Create a Jira user and then empower:

Grant all privileges the jira.* to [e-mail protected] '% ' identified by ' jiradevhost ';

Restart Tomcat to successfully solve the problem!!!

Jira problem solved, then wiki? Visit to see!

error!!!!

Oh, my God, what the hell!

Check! Under the Wiki_home directory, look at the confluence configuration file to find the rows related to Username&password;

Well, fortunately I am witty, database password and account incorrect, modify it, restart tomcat!

Jira and wiki successfully visit!

Alas, for this incident, really do not die will not die Ah!!

So for the importance of backup! Whether it is a database or application, you need to do a backup! Otherwise, I am in this situation, really want to die of heart have!!!

Jira and Confluence configuration issues