Jira upgrade 6.3.7 issue

Question

Hi,

We have upgraded JIRA from 6.0.7 to 6.3.7. After upgrade JIRA didn't startup.

This error was showing :-

Error occurred while starting component 'com.atlassian.jira.service.DefaultServiceManager'. caused by: Error creating underlying Quartz scheduler

Please help us in resolving this issue.

David Swain · Answer

I received the same error when upgrading to this version. When I looked in /log/atlassian-jira.log I saw several entries like: 2014-10-22 09:30:43,965 localhost-startStop-1 ERROR [core.entity.jdbc.DatabaseUtil] Could not create table "JQUARTZ_BLOB_TRIGGERS" 2014-10-22 09:30:43,965 localhost-startStop-1 ERROR [core.entity.jdbc.DatabaseUtil] SQL Exception while executing the following: CREATE TABLE JQUARTZ_BLOB_TRIGGERS (SCHED_NAME VARCHAR(120), TRIGGER_NAME VARCHAR(200) NOT NULL, TRIGGER_GROUP VARCHAR(200) NOT NULL, BLOB_DATA BLOB, CONSTRAINT PK_JQUARTZ_BLOB_TRIGGERS PRIMARY KEY (TRIGGER_NAME, TRIGGER_GROUP)) Error was: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytes Our db was set to use utf8 with myisam tables. myisam has a 1000 bytes total limit for a keyutf8 uses up to 3 bytes per characterwhen calculating requirements for keys mysql assumes the worst (ie 3 bytes per character)the key lengths in that table total 400 characters, ie 1200 bytes Resolution (for us):Stop JiraModify the database schema to use innodb tables as per the recommendations on the Atlassian website.(we did this by dumping the whole db to a file, using find/replace, dropping the db, then re-importing it)Modify /dbconfig.xml to include sessionVariables=storage_engine=InnoDB as per the instructions at https://confluence.atlassian.com/display/JIRA/Connecting+JIRA+to+MySQL Start Jira if your log doesn't show those same entries then this probably isn't the course of action for you, but I hope it is and that you can get running again. :- Dave

Boris Berenberg · Answer

We would need to see more of the error to understand what went wrong. Please collect the logs manually by going to /logs and /log combining all the logs into one zip file. Then send us the same thing as what you wrote above, and those logs to support@atlassian.com