Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Unknown error

I have installed JIRA service desk with MySQL8.0.

When I setting up database, I can't connect DB connector 'mysql-connector-java-8.0.21'.

The problem was passed by copying three files 'mysql-connector-java-8.0.19', 'mysql-connector-java-5.1.48', 'mysql-connector-java-8.0.21' to lib folder of JIRA.

But when entering license key, I've got 'unknown error' message.

I tried it again after dropping db and reinstall JIRA service desk. 

I've got same message.

3 answers

2 votes
Andy Heinzer Atlassian Team Oct 08, 2020

Hi @junghyeon 

I understand that you are trying to install Jira Service Desk Server, but it looks like you are having problems in regards to the MySQL database that you are trying to use here.  The error message you posted indicates that the database is most likely not configured in the way that Jira is expecting.  If it was, then Jira would be able to create the tables (such as cwd_users) that are needed for Jira to work correctly.

Note that until Jira 8.12 and Jira Service Desk 4.12.0, we did not have MySQL 8 support at all. MySQL 5.6 and 5.7 versions are supported, but these have always been recommended to use the 5.1.x JDBC driver.  Jira Server now has support for MySQL 8, but only for 4.12.0 and higher versions of Jira Service Desk Server.  I'm not sure which version of Jira Service Desk you are trying to install here, but if this is a version before one of these, then you won't be able to make this work with that database version.  In cases like that, I'd recommend using a MySQL 5.7 database.

I would recommend trying to closely follow the database setup guide that corresponds to your version of Jira and MySQL, for example, Connecting Jira applications to MySQL 8.0 - Server 8.13 has step-by-step instructions to follow here for 8.13 / 4.13. If you're using a different version, then there is a selector on that page you can follow to select a different version of the document.

 

I agree with the previous advice to only have a single MySQL JDBC driver in the $JIRAINSTALL/lib/ folder.  But what version that should be will depend upon the database version and the version of Jira. Our docs should be up to date with the correct versions here, but if they are not, I am interested to try to correct this.

 

Please let me know what version of Jira Service Desk you are trying to setup here, as it will likely make a difference in regards to the next steps to troubleshoot this problem;

Andy

Thank your for your answer.

I'm trying to install JIRA Service Desk 4.12.2 X64 with MySQL 8.0.

Trouble 1:

But JIRA Service Desk issued error(https://community.atlassian.com/t5/Jira-Service-Desk-questions/Database-is-not-Empty-issue/qaq-p/1490625) if I only copy MySQL connector Ver 8.0.19 or 8.0.21 to lib folder. When I copied two versions of connector (5.1.48 and 8.0.xx), it was passed.

 

Trouble 2:

After that, during entering license key, I've got 'unknown error' message.

the log file shows:

2020-10-05 18:32:56,817+0900 JIRA-Bootstrap ERROR [c.a.jira.startup.JiraStartupLogger] Cannot obtain Jira system information
com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT COUNT(U.ID) FROM cwd_user U (Table 'jiradb.cwd_user' doesn't exist)

 

I think JIRA Service Desk has a bug for connector of MySQL 8. Some function require connector ver 5.x and others require ver 8.x.

Confluence is working correctly on the same system without any trouble in regarding  to MySQL 8.0 and connector.

I tried to install JIRA Service Desk 4.13 with MySQL8.0 after drop database and create again.

But It shows same error(empty issue).

What are you doing differently to what the installation docs say to do?

I just followed the instruction. But failed to installation due to empty issue.

Andy Heinzer Atlassian Team Oct 13, 2020

Thanks for the additional information here. 

Please do not use two MySQL jbdc jar files in the $JIRAINSTALL/lib folder at the same time.  The main reason being that when this happens, we don't have a clear understanding of which jar is being used to communicate with the database.  It is possible that Jira might be trying to use both and that might be a factor in the confusion here.

In my own environment I just spun up a MySQL 8.0.21 instance, and I also used the 8.0.2.1 jbdc jar file only.  I was able to complete the installation of the same version of Jira 8.12.2 (Jira Service Desk 4.12.2), although I did find that I needed adjust one of my grant statements.  Our current documentation states to:

GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,REFERENCES,ALTER,INDEX on <JIRADB>.* TO '<USERNAME>'@'<JIRA_SERVER_HOSTNAME>';
flush privileges;

Because when I tried this in my own environment, I got an error of:

Error Code: 1410. You are not allowed to create a user with GRANT

And instead I had to change that to be:

GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,REFERENCES,ALTER,INDEX on jiradb.* TO jira;
flush privileges;

Where my database name is 'jiradb' and the mysql user name was 'jira'.  It seems that the output error I got from this version of MySQL believed I was trying to create a user rather than grant that existing user permissions.

Once I did this, I then used the Jira Config Tool in order to setup Jira to connect to this new database.  This worked, although I found that I was not able to test the connection using this utility as I kept getting an error of:

The server time zone value 'CDT' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the serverTimezone configuration property) to use a more specifc time zone value if you want to utilize time zone support.

Found though that I could get past this by setting up a time_zone for MySQL:

SET GLOBAL time_zone = '-6:00';

After that, I just started Jira and the setup wizard was able to accept my license key, and configure the admin user.  Everything looks good.

 

In my experience the error you are seeing is most likely caused by a misconfiguration of Jira, or the database, or possibly both.  I can see from the error message you have posted that Jira is not able to create the needed tables to setup the database as it needs to. 

I would recommend trying once more with only the 8.0.21 jbdc jar file in the /lib/ directory and with a newly created database once more.  If this still fails, then I would want to take a closer look at the $JIRAINSTALL/logs/catalina.out file that is generated at this time.  This file will have a lot more details about your environment and details about how Jira is trying to communicate with the database itself.

Please let me know.

Andy

Dear Andy

Thank you for kind reply.

Here is catalina.2020-10-14.log file:

----------------------------------------

14-Oct-2020 20:11:55.295 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 서버 버전 이름: Apache Tomcat/8.5.57
14-Oct-2020 20:11:55.298 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Server 빌드 시각: Jun 30 2020 21:49:10 UTC
14-Oct-2020 20:11:55.298 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Server 버전 번호: 8.5.57.0
14-Oct-2020 20:11:55.298 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 운영체제 이름: Windows 10
14-Oct-2020 20:11:55.298 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 운영체제 버전: 10.0
14-Oct-2020 20:11:55.298 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 아키텍처: amd64
14-Oct-2020 20:11:55.298 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 자바 홈: C:\Program Files\Atlassian\Jira\jre
14-Oct-2020 20:11:55.298 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log JVM 버전: 1.8.0_202-b08
14-Oct-2020 20:11:55.298 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log JVM 벤더: Oracle Corporation
14-Oct-2020 20:11:55.298 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: C:\Program Files\Atlassian\Jira
14-Oct-2020 20:11:55.301 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: C:\Program Files\Atlassian\Jira
14-Oct-2020 20:11:55.301 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Djava.awt.headless=true
14-Oct-2020 20:11:55.301 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Datlassian.standalone=JIRA
14-Oct-2020 20:11:55.301 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
14-Oct-2020 20:11:55.301 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Dmail.mime.decodeparameters=true
14-Oct-2020 20:11:55.302 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory
14-Oct-2020 20:11:55.302 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:-OmitStackTraceInFastThrow
14-Oct-2020 20:11:55.302 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:+ExplicitGCInvokesConcurrent
14-Oct-2020 20:11:55.302 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:+PrintGCDetails
14-Oct-2020 20:11:55.302 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:+PrintGCDateStamps
14-Oct-2020 20:11:55.302 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:+PrintGCTimeStamps
14-Oct-2020 20:11:55.302 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:+PrintGCCause
14-Oct-2020 20:11:55.302 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:+UseGCLogFileRotation
14-Oct-2020 20:11:55.302 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:NumberOfGCLogFiles=5
14-Oct-2020 20:11:55.302 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:GCLogFileSize=20M
14-Oct-2020 20:11:55.303 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Xloggc:C:\Program Files\Atlassian\Jira\logs\atlassian-jira-gc-%t.log
14-Oct-2020 20:11:55.303 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:InitialCodeCacheSize=32m
14-Oct-2020 20:11:55.303 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:ReservedCodeCacheSize=512m
14-Oct-2020 20:11:55.303 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Dcatalina.home=C:\Program Files\Atlassian\Jira
14-Oct-2020 20:11:55.303 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Dcatalina.base=C:\Program Files\Atlassian\Jira
14-Oct-2020 20:11:55.303 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Dignore.endorsed.dirs=C:\Program Files\Atlassian\Jira\endorsed
14-Oct-2020 20:11:55.303 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Djava.io.tmpdir=C:\Program Files\Atlassian\Jira\temp
14-Oct-2020 20:11:55.303 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
14-Oct-2020 20:11:55.303 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Djava.util.logging.config.file=C:\Program Files\Atlassian\Jira\conf\logging.properties
14-Oct-2020 20:11:55.303 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: exit
14-Oct-2020 20:11:55.303 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: abort
14-Oct-2020 20:11:55.303 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Xms384m
14-Oct-2020 20:11:55.303 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Xmx2048m
14-Oct-2020 20:11:55.303 정보 [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR 버전 [1.7.0]을(를) 사용한, APR 기반 Apache Tomcat Native 라이브러리 [1.2.24]을(를) 로드했습니다.
14-Oct-2020 20:11:55.303 정보 [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR 용량정보들: IPv6 [true], sendfile [true], accept filters [false], random [true].
14-Oct-2020 20:11:55.303 정보 [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL 설정: useAprConnector [false], useOpenSSL [true]
14-Oct-2020 20:11:55.308 정보 [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL이 성공적으로 초기화되었습니다: [OpenSSL 1.1.1g 21 Apr 2020]
14-Oct-2020 20:11:55.415 정보 [main] org.apache.coyote.AbstractProtocol.init 프로토콜 핸들러 ["http-nio-8080"]을(를) 초기화합니다.
14-Oct-2020 20:11:55.423 정보 [main] org.apache.catalina.startup.Catalina.load Initialization processed in 400 ms
14-Oct-2020 20:11:55.430 정보 [main] org.apache.catalina.core.StandardService.startInternal 서비스 [Catalina]을(를) 시작합니다.
14-Oct-2020 20:11:55.430 정보 [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.57
14-Oct-2020 20:11:55.438 심각 [Catalina-startStop-1] org.apache.catalina.startup.HostConfig.beforeStart 배치를 위한 디렉토리 [C:\Program Files\Atlassian\Jira\conf\Catalina\localhost]을(를) 생성할 수 없습니다.
14-Oct-2020 20:12:00.705 정보 [main] org.apache.coyote.AbstractProtocol.start 프로토콜 핸들러 ["http-nio-8080"]을(를) 시작합니다.
14-Oct-2020 20:12:00.713 정보 [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
14-Oct-2020 20:12:00.722 정보 [main] org.apache.catalina.startup.Catalina.start Server startup in 5298 ms

 

Here is jiraservicedesk121020210536-stdout.2020-10-14.log file(Last two rows):

----------------------------------------

14-Oct-2020 20:12:00.722 정보 [main] org.apache.catalina.startup.Catalina.start Server startup in 5298 ms
Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.

There are many issues regarding `com.mysql.jdbc.Driver'.

New version of MySQL connector use the class 'com.mysql.cj.jdbc.Driver'.

Can I correct it by myself? or should the atlassian team fix it?

Andy Heinzer Atlassian Team Oct 15, 2020

Thanks for posting this log.  I was actually expecting to see more log entries in that log here.  But this error message of

Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.

does give us a good clue here.  This means that your $JIRAHOME/dbconfig.xml file is currently using an incorrect <driver-class> directive for MySQL 8.   Below is my dbconfig.xml  (with my database password redacted).

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

<jira-database-config>
<name>defaultDS</name>
<delegator-name>default</delegator-name>
<database-type>mysql8</database-type>
<jdbc-datasource>
<url>jdbc:mysql://address=(protocol=tcp)(host=localhost)(port=3306)/jiradb?sessionVariables=default_storage_engine=InnoDB</url>
<driver-class>com.mysql.cj.jdbc.Driver</driver-class>
<username>jira</username>
<password>password</password>
<pool-min-size>30</pool-min-size>
<pool-max-size>30</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>30</pool-max-idle>
<pool-remove-abandoned>true</pool-remove-abandoned>
<pool-remove-abandoned-timeout>300</pool-remove-abandoned-timeout>
<pool-test-on-borrow>false</pool-test-on-borrow>
<pool-test-while-idle>true</pool-test-while-idle>
<validation-query-timeout>3</validation-query-timeout>
</jdbc-datasource>
</jira-database-config>

 

Try changing the <driver-class> in this file to match my example, save this file, and then restart Jira once more.  That should fix that particular error.  I would be interested to see if that is sufficient to let Jira get further into this setup and installation process.  If it is still not working, please send along the updated catalina.out file and I'd be happy to take a closer look here.

Andy

There is no error regarding 'Not empty issue' when dbconfig.xml file created as your recommendation.

But there is still 'unknown error' message during entering license key.

the log file(catalina.2020-10-20.log) shows:

20-Oct-2020 09:06:07.238 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 서버 버전 이름: Apache Tomcat/8.5.57
20-Oct-2020 09:06:07.267 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Server 빌드 시각: Jun 30 2020 21:49:10 UTC
20-Oct-2020 09:06:07.267 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log Server 버전 번호: 8.5.57.0
20-Oct-2020 09:06:07.267 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 운영체제 이름: Windows 10
20-Oct-2020 09:06:07.267 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 운영체제 버전: 10.0
20-Oct-2020 09:06:07.267 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 아키텍처: amd64
20-Oct-2020 09:06:07.268 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 자바 홈: C:\Program Files\Atlassian\Jira\jre
20-Oct-2020 09:06:07.268 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log JVM 버전: 1.8.0_202-b08
20-Oct-2020 09:06:07.268 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log JVM 벤더: Oracle Corporation
20-Oct-2020 09:06:07.268 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: C:\Program Files\Atlassian\Jira
20-Oct-2020 09:06:07.270 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: C:\Program Files\Atlassian\Jira
20-Oct-2020 09:06:07.271 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Djava.awt.headless=true
20-Oct-2020 09:06:07.271 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Datlassian.standalone=JIRA
20-Oct-2020 09:06:07.271 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
20-Oct-2020 09:06:07.271 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Dmail.mime.decodeparameters=true
20-Oct-2020 09:06:07.271 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory
20-Oct-2020 09:06:07.271 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:-OmitStackTraceInFastThrow
20-Oct-2020 09:06:07.271 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:+ExplicitGCInvokesConcurrent
20-Oct-2020 09:06:07.271 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:+PrintGCDetails
20-Oct-2020 09:06:07.271 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:+PrintGCDateStamps
20-Oct-2020 09:06:07.271 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:+PrintGCTimeStamps
20-Oct-2020 09:06:07.271 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:+PrintGCCause
20-Oct-2020 09:06:07.271 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:+UseGCLogFileRotation
20-Oct-2020 09:06:07.271 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:NumberOfGCLogFiles=5
20-Oct-2020 09:06:07.271 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:GCLogFileSize=20M
20-Oct-2020 09:06:07.272 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Xloggc:C:\Program Files\Atlassian\Jira\logs\atlassian-jira-gc-%t.log
20-Oct-2020 09:06:07.272 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:InitialCodeCacheSize=32m
20-Oct-2020 09:06:07.272 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -XX:ReservedCodeCacheSize=512m
20-Oct-2020 09:06:07.272 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Dcatalina.home=C:\Program Files\Atlassian\Jira
20-Oct-2020 09:06:07.272 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Dcatalina.base=C:\Program Files\Atlassian\Jira
20-Oct-2020 09:06:07.272 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Dignore.endorsed.dirs=C:\Program Files\Atlassian\Jira\endorsed
20-Oct-2020 09:06:07.272 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Djava.io.tmpdir=C:\Program Files\Atlassian\Jira\temp
20-Oct-2020 09:06:07.272 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
20-Oct-2020 09:06:07.272 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Djava.util.logging.config.file=C:\Program Files\Atlassian\Jira\conf\logging.properties
20-Oct-2020 09:06:07.272 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: exit
20-Oct-2020 09:06:07.272 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: abort
20-Oct-2020 09:06:07.272 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Xms384m
20-Oct-2020 09:06:07.272 정보 [main] org.apache.catalina.startup.VersionLoggerListener.log 명령 행 아규먼트: -Xmx2048m
20-Oct-2020 09:06:07.272 정보 [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR 버전 [1.7.0]을(를) 사용한, APR 기반 Apache Tomcat Native 라이브러리 [1.2.24]을(를) 로드했습니다.
20-Oct-2020 09:06:07.272 정보 [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR 용량정보들: IPv6 [true], sendfile [true], accept filters [false], random [true].
20-Oct-2020 09:06:07.272 정보 [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL 설정: useAprConnector [false], useOpenSSL [true]
20-Oct-2020 09:06:07.287 정보 [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL이 성공적으로 초기화되었습니다: [OpenSSL 1.1.1g 21 Apr 2020]
20-Oct-2020 09:06:07.474 정보 [main] org.apache.coyote.AbstractProtocol.init 프로토콜 핸들러 ["http-nio-8080"]을(를) 초기화합니다.
20-Oct-2020 09:06:07.482 정보 [main] org.apache.catalina.startup.Catalina.load Initialization processed in 609 ms
20-Oct-2020 09:06:07.490 정보 [main] org.apache.catalina.core.StandardService.startInternal 서비스 [Catalina]을(를) 시작합니다.
20-Oct-2020 09:06:07.490 정보 [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.57
20-Oct-2020 09:07:00.852 정보 [main] org.apache.coyote.AbstractProtocol.start 프로토콜 핸들러 ["http-nio-8080"]을(를) 시작합니다.
20-Oct-2020 09:07:00.860 정보 [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
20-Oct-2020 09:07:00.870 정보 [main] org.apache.catalina.startup.Catalina.start Server startup in 53387 ms

 

the log file(jiraservicedesk121020210536-stdout.2020-10-20.log) shows in last paragraph:

2020-10-20 09:08:16,587+0900 http-nio-8080-exec-16 ERROR anonymous 548x5x1 3egl74 0:0:0:0:0:0:0:1 /secure/SetupDatabase!default.jspa [c.a.jira.startup.DatabaseInitialImporter] 
2020-10-20 09:08:16,589+0900 http-nio-8080-exec-16 ERROR anonymous 548x5x1 3egl74 0:0:0:0:0:0:0:1 /secure/SetupDatabase!default.jspa [c.a.jira.startup.DatabaseInitialImporter] 데이터 가져오는 오류: com.atlassian.cache.CacheException: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, application_name, lower_application_name, created_date, updated_date, active, description, application_type, credential FROM cwd_application (Table 'jiradb.cwd_application' doesn't exist)
2020-10-20 09:08:37,523+0900 Modification Check:thread-1 INFO [c.a.jira.startup.JiraStartupLogger]

___ Modifications ___________________________

Modified Files : jira-application.properties
Removed Files : None

 

Andy Heinzer Atlassian Team Oct 21, 2020

@junghyeon It still appears that the database has not been created in a way that allows the Jira application to create the tables that it requires to operate.   Would you be willing to share with us your dbconfig.xml here?  Of course, we do not want to see your actual password or the exact address of the database as Community is a public site, but the other information in that file could prove useful for us to understand the configuration that Jira has when it starts up.

This should also be able to tell us the name of the sql user, and the name of the SQL database itself.  With that information, we can then better advise specific SQL configuration steps that need to happen in order to make sure that the Jira application can configure this database correctly.

I would also recommend creating a brand new database as per the steps in Connecting Jira applications to MySQL 8.0 - Server 8.13.  This way we can more certain that the past attempts to setup are not influencing the current state.

Andy

Here is my dbconfig.xml

I used the username 'root' to remove any permission trouble for this installation.

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

<jira-database-config>
<name>defaultDS</name>
<delegator-name>default</delegator-name>
<database-type>mysql8</database-type>
<jdbc-datasource>
<url>jdbc:mysql://address=(protocol=tcp)(host=localhost)(port=3306)/jiradb?sessionVariables=default_storage_engine=InnoDB</url>
<driver-class>com.mysql.cj.jdbc.Driver</driver-class>
<username>root</username>
<password>password</password>
<pool-min-size>30</pool-min-size>
<pool-max-size>30</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>30</pool-max-idle>
<pool-remove-abandoned>true</pool-remove-abandoned>
<pool-remove-abandoned-timeout>300</pool-remove-abandoned-timeout>
<pool-test-on-borrow>false</pool-test-on-borrow>
<pool-test-while-idle>true</pool-test-while-idle>
<validation-query-timeout>3</validation-query-timeout>
</jdbc-datasource>
</jira-database-config>
Andy Heinzer Atlassian Team Oct 26, 2020

I would not run the Jira application itself as root, nor would I suggest using the root sql user for connecting to the database.  Our guide in Connecting Jira applications to MySQL 8.0 - Server 8.13 specifically indicates for you to create a new sql user (jiradbuser in that guide), and then grant that account the specified rights.

Although root can grant rights to any user account, it does not always mean that it has all the needed permissions for each database at all times.

Actually, I used other user account having all right. But It has a  'Not empty issue' & 'unknown error'.

For test purpose, now I'm using root and has a same trouble with other user account.

@junghyeonfrom initial inspection it looks like you are using three connector for same database, I think you just need one.

Can please check your error log and share some more details. They are located inside home directory's logs folder.

Here is log information regarding error:

2020-10-05 18:32:56,817+0900 JIRA-Bootstrap ERROR [c.a.jira.startup.JiraStartupLogger] Cannot obtain Jira system information
com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT COUNT(U.ID) FROM cwd_user U (Table 'jiradb.cwd_user' doesn't exist)

 

Could you explain me what it means?

It looks like a database issue, can you do these steps,

  • Stop Jira
  • Delete or create new database
  • Check you have admin level access on database (you can grant to specific user and use that)
  • Delete existing Jira Home and create a new directory.

Inside Jira just use single connector for mysql in lib, and then start your Jira.

I tried as the steps but it issue same error.

When I use single connector, there is an empty issue (https://community.atlassian.com/t5/Jira-Service-Desk-questions/Database-is-not-Empty-issue/qaq-p/1490625)

Two connector are required (mysql-connector-java-5.1.48 and mysql-connector-java-8.0.19 or later)

I think JIRA Service Desk has a bug for connector of MySQL 8.

It does not create the table 'cwd_user'.

Does I need the JIRA to operate JIRA Service Desk?

I only installed JIRA Service Desk.

Ok, you need to simplify back to a supported configuration.

You only want one connector, and you should only have a single database driver.  Tomcat will only be loading one of them whatever you do, but I don't know which one it will be trying to load.  But read the install instructions for MySQL for your version of Jira and make sure you install only one driver of a version that the instructions say is valid.

Go into the database and drop the existing database completely, then recreate it and run the installer again.  If your end-goal is Jira Service Desk, use the installer for that, rather than Core or Software.  (Software and Service Desk both need Jira installed, but the installers for them are bundles of Jira Core + Application, you don't need to install Jira first)

May I get any answer from atlassian team?

I have asked a friend to post this to community channel for Atlassian Team's help.

Like Dave Liao likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
4.12.2
TAGS
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

241 views 1 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you