Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JIRA had problems starting up

Amnat Prasert February 16, 2018

Hello

 

I have problem about transfer license to new server (The old server crash).

I have setup JIRA on new server and after I'm import existing data.

I have got this picture below. That tell "JIRA Software expires on 17/08/1475".

Can anyone help me?

2018-02-16_15-38-49.jpg

3 answers

1 accepted

0 votes
Answer accepted
Amnat Prasert February 19, 2019

Hi all

 

To whom have problem like me. This is workaround to resolved this problem

update these parameter in java option of tomcat

 

-Duser.language=en
-Duser.region=US

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 20, 2018

I have seen this kind of error before with another user that had the system regional locale set to Thailand.  I suspect that there might be a different calendar on systems with that local region which might be why the license believes it has expired.

Perhaps you can get around this problem by changing the calendar on the operating system to a Julian calendar.   Could you let me know what OS you are using, and perhaps I can help find more information on the specifics of how to do that depending on your operating system.

Amnat Prasert February 20, 2018

Hi Andrew

 

What is "Julian Calendar"? How to setup?

My OS is Windows server 2012 R2.

 

Thank.

Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 21, 2018

So, I also had to do some learning about this too.  I'd recommend the wiki page on Date and time notation in Thailand just for some background on the differences.   Since it appears that the license thinks the year is 1475, I think this coincides with the 543 year offset between the Buddhist calendar and the Gregorian calendar (I thought it was Julian, but technically it's Gregorian).   Which means the 1475 + 543 = 2018.  

In which case I think your license is actual still valid (at least until 17th day of August), but because the operating system seems to be using this different calendar of year, I don't believe that Jira is correctly identifying this difference.

You will need to navigate to the Control panel in windows.  The screenshot below is one way this looks in 2008 instance.  I realize the view might look different in 2012, but basically, I think we will need to change the Region settings of this machine, at least temporarily.

 

controlpanel1.png

contpan2.png

From there, try to change the "Format" to a different selection, such as English (United States).   I am expecting this to change the Windows operating system region settings to use the Gregorian calendar.  After to change this setting, click Ok, and then I would recommend restarting the Operating system.

From there see if you can get Jira to start up without this error.

Amnat Prasert February 22, 2018

I have to check regional setting on my server that get same your setting.

And I have to set location from Thailand to United State. Will retry to setup JIRA again.

 

2018-02-22_15-36-45.jpg

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 16, 2018

That is very odd.  Is the date/time on your server correct?

Amnat Prasert February 16, 2018

Hi Nic

 

My time server is correct.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 16, 2018

The reason I asked that is that the licence date calculation is sometimes a bit squiffy when you set a server to run way in the past (before 2000).  But that's not the case here.

Two things to try

1.  Go to your my.atlassian account and get a new copy of the licence key to paste in (click the link near the end of the error message to get a pop-up for it)

2. If that does not help, then could you look at the atlassian-jira.log and see the full error that happens when it gets to this point?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events