Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,461,956
Community Members
 
Community Events
176
Community Groups

Invalid object name 'CLUSTER_NODE_HEARTBEAT' after upgrading to Bamboo 8.0.2

I upgraded from 7.x to 8.0.2 yesterday, and since then my application log is filled with the following:

021-09-24 13:11:37,145 WARN [https-openssl-nio-443-exec-25] [SqlExceptionHelper] SQL Error: 208, SQLState: S0002
2021-09-24 13:11:37,145 ERROR [https-openssl-nio-443-exec-25] [SqlExceptionHelper] Invalid object name 'CLUSTER_NODE_HEARTBEAT'.
2021-09-24 13:11:37,145 WARN [https-openssl-nio-443-exec-25] [BambooRuntimeExceptionMapper] Unexpected error from REST call
org.springframework.dao.InvalidDataAccessResourceUsageException: error executing work; SQL [n/a]; nested exception is org.hibernate.exception.SQLGrammarException: error executing work

Is this related to Bamboo Datacenter? We're licensed for Bamboo Server, and the error suggests its perhaps looking to perform a cluster-related function that isn't applicable in our case (we're running a single instance of Bamboo Server). 

Bamboo otherwise appears to be working OK.

 

4 answers

1 vote

This issue has been fixed in 8.0.3 and later

1 vote

It's tracked at https://jira.atlassian.com/browse/BAM-21436 . Please use provided workaround until new version with fix is released

Same to us. Ticket created. Is any info how to solve this available?

0 votes

Please create support ticket at https://getsupport.atlassian.com so our engineers can review upgrade logs and provide CREATE TABLE statement to fix the issue.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events