-
Bug
-
Resolution: Fixed
-
Low
-
Companion-1.0.0, Companion-1.1.0
-
9
-
Severity 3 - Minor
-
4
-
Summary
- When connected to the internet, the Companion App checks and compares the computer's time with the NTP time.
- If the time is out of sync, it will throw the error saying "System clock is incorrect"
- Sometimes the Companion App will start before the computer has time to sync with the NTP server, which will them prompt the error message as well.
Steps to replicate
- Set the Companion App to auto start on OS boot.
- Start the computer in another location where the local time is different.
- If the computer boots up, but has not synced with the NTP server to update it's time, the Companion App will throw the "System clock is incorrect" error.
- The issue can also be reproducible by simply changing the local time of the machine, and then setting it to update using the NTP server.
- Start the Atlassian Companion app, and it will throw the error, since it takes some time for the computer to sync with the NTP server time.
Expected behavior
- When starting up, the Companion app should wait awhile for the computer time to sync with the network time, to prevent the error message from appearing.
- Or, there should be an option to disable the checking.
Current behavior
- Companion App throws "System clock is incorrect" error message, as the computer has have the time to sync with the network time.
- In some cases, the app will crash on boot, and but works fine if started manually after.
[CONFSERVER-57798] Companion App throws System clock error if it starts up before the computer has synced with the NTP server
Hi folks, this issue is in the Companion App itself and is not related to the Confluence version.
Issue solved for us after upgrading to Confluence version 7.3.1 on Monday, March 16, 2020.
A fix for this issue is available in Companion 1.2.0. View the Release Notes to see what other issues are resolved.
If Companion is installed via the MSI, then it will need to be manually updated to the new version.