Simple version: If you follow AWS guide Setting the Time for Your Linux Instance to use /etc/sysconfig/clock to configure the timezone in Amazon Linux 2, you may not be able to find it after a yum update. So the suggested way to adjust time is to use timedatectl. For example: sudo timedatectl set-timezone Australia/Sydney Detailed … Continue reading /etc/sysconfig/clock is removed after yum update in Amazon Linux 2
Have you seen this error in your Jira log? If so, then you are in the right place to solve it 🙂 2019-10-10 02:03:34,970 Caesium-1-4 ERROR ServiceRunner [c.a.j.p.devstatus.provider.DefaultDevSummaryPollService] Refresh failurecom.atlassian.jira.plugin.devstatus.provider.DataProviderRefreshFailure: Data Provider refresh failed with error code 400 and message - HTTP status 400 ] at com.atlassian.jira.plugin.devstatus.provider.DefaultCachingProviderHelper.refreshProvider(DefaultCachingProviderHelper.java:79) at com.atlassian.jira.plugin.devstatus.provider.DefaultDevSummaryPollService.handlePollingSuccess(DefaultDevSummaryPollService.java:69) at com.atlassian.jira.plugin.devstatus.provider.DefaultDevSummaryPollService.lambda$performPull$1(DefaultDevSummaryPollService.java:51) at com.atlassian.jira.plugin.devstatus.provider.source.applink.PollResult$PollResultSuccess.fold(PollResult.java:51) at com.atlassian.jira.plugin.devstatus.provider.DefaultDevSummaryPollService.performPull(DefaultDevSummaryPollService.java:47) … Continue reading Refresh failure com.atlassian.jira.plugin.devstatus.provider.DataProviderRefreshFailure: Data Provider refresh failed with error code 400 and message – HTTP status 400
If you get the java.lang.NullPointerException error page as above when you are trying to create a new issue, then most likely it has something to do with the Default Issue Type Scheme of your Jira. Follow the diagnoses steps in this knowledge base Jira server throws NullPointerException when creating new issues or changing project settings … Continue reading Creating new Jira issues throws java.lang.NullPointerException
We noticed that Jira startup time increased from 3+ mins to 20+ mins after a recent upgrade (7.10 to 7.12). After analysed a few restart relevant events in the logs, I found that there are some messages related to DB row migrations which were not there before the upgrade. Here is a example: 5/3/19 9:43:14.816 … Continue reading Jira takes long time to restart after upgrade
If you are seeing the above error in the Activity section of a Jira issue. Your Jira may have hit a Jira bug. Check this out - https://jira.atlassian.com/browse/JSDSERVER-5966 To confirm it, you can try: (1) Check the issue via API - https://<jira-server>/rest/api/2/issue/<issue-key>. (2) Search comment in the result, to see what you got there. In … Continue reading Error rendering ‘com.atlassian.jira.jira-view-issue-plugin:activitymodule’. Please contact your Jira administrators.
It is a known bug that UPM update causes JIRA Software and required bundled plugins to temporarily disable. We did not know know it until we experienced once in the production. A bad experience, but a good lesson to learn 😉 Interested to see how Jira looks like when it happens? Here you go:
We had a Bamboo incident the other day - lots of Bamboo agent went offline , and quite a few build plans have to wait in the queue for a long time. We checked the logs and saw something like "Agent could not access JMS invoker queue". JMS stands for Java Message Service which in … Continue reading Bamboo agent could not access jms invoker queue