I am installing on Windows Server, My SQL 5.7. Everything fine but database connection fails with "Server Time Zone C.. U.. T.." error message. I have tried setting time zone in JIRA/bin/setenv.bat, and also in Windows Registry (Europe/London).
Rapidly losing patience with Jira installation support - pretty poor that simple installation required editing bat files and running regedit - surely the installer should set the environment? Any suggestions?
Hi Mark,
I am not familiar with the specific error message you are getting here. Where exactly do you see that message? Is this in the atlassian-jira.log file when Jira is starting up? Or have you tried to use the Config Tool in Jira in order to configure/test this connection?
Is MySQL installed to the same server as Jira?
When Jira is installed, it tends to default itself to using the timezone of the JVM instance it is loading up in, which in turn tends to use the default timezone of the base operating system. There are ways to tell the Jira application to use a different timezone, via some JVM startup arguments, but I'm not clear on why you should have to do this.
I am not aware of any requirement to have both jira and its database utilize the exact same timezone in order to work correctly. So I'm interested to learn more about this problem and the specific errors you are encountering and where so that we can try to troubleshoot this better.
It might help to run the following SQL statement against mysql to learn more about your database settings:
SELECT @@GLOBAL.time_zone, @@SESSION.time_zone;
Also what version of Windows Server is this?
Hi Andrew,
This is on Windows Server 2019, running on an AWS EC2 instance. MySQL is 5.7, Jira installed on the same machine as MySQL. From command line I can mysql -u jira -pp... and connect to the database, so the database itself is correct. The error is being reported using Test Connection from the web portal setup on Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Output from the above SQL queries returns SYSTEM for both commands.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Note that I have successfully installed Jira on other systems; it looks to be something particular to either Server 2019, or the particular setup the Amazon use for EC2 virtual server instances.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Mark,
I have a few suspicions of what might be happening, but right now I can't say for sure what is causing this. I'd like to gather some logs from this environment to better understand what is happening in Jira when it starts up and when this error happens. In order to gather those, I have created a support case for this in https://getsupport.atlassian.com/servicedesk/customer/portal/20/GHS-144123
Regards,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.