Bitbucket server failed to start up after upgrade from 5.3.1 to 5.9.0

[Xin Liu]

Self-hosted Bitbucket Server cannot start up after upgrade from 5.3.1 to 5.9.0, it seems to relate to this exception found in BITBUCKET_HOME/log/atlassian-bitbucket.log:

2018-03-20 06:16:13,726 ERROR [spring-startup] c.a.j.s.w.s.JohnsonDispatcherServlet SpringMVC dispatcher [springMvc] could not be started
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dailyAlertAnalyticsJob' defined in class path resource [stash-context.xml]: Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: The datetime zone id 'SystemV/PST8' is not recognised
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1628)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543)
at javax.servlet.GenericServlet.init(GenericServlet.java:158)
at java.lang.Thread.run(Thread.java:748)
... 15 frames trimmed
Caused by: java.lang.IllegalArgumentException: The datetime zone id 'SystemV/PST8' is not recognised
at org.joda.time.DateTimeZone.forTimeZone(DateTimeZone.java:374)
at com.atlassian.scheduler.caesium.impl.RunTimeCalculator.nextRunTime(RunTimeCalculator.java:102)
at com.atlassian.scheduler.caesium.impl.RunTimeCalculator.nextRunTime(RunTimeCalculator.java:70)
at com.atlassian.scheduler.caesium.impl.RunTimeCalculator.firstRunTime(RunTimeCalculator.java:47)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.scheduleClusteredJob(CaesiumSchedulerService.java:179)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.scheduleJob(CaesiumSchedulerService.java:137)
at com.atlassian.diagnostics.internal.analytics.DailyAlertAnalyticsJob.init(DailyAlertAnalyticsJob.java:54)
... 5 common frames omitted

What can I do now?

This server is always using UTC timezone, where does this "SystemV/PST8" come from?

[Xin Liu]

After deleting this bean from 5.9.0/app/WEB-INF/classes/stash-context.xml, it can start up.

Then I changed the timezone in system settings to UTC and added the bean back, now everything is running normally.

<bean id="dailyAlertAnalyticsJob" class="com.atlassian.diagnostics.internal.analytics.DailyAlertAnalyticsJob"
 init-method="init" destroy-method="destroy">
 <constructor-arg index="0" ref="eventPublisher"/>
 <constructor-arg index="1" ref="monitoringService"/>
 <constructor-arg index="2" ref="schedulerService"/>
</bean>

[slimatic]

Thanks! That helped. Removing the entry above addressed my issue.