Bitbucket Server missing table

[Chao_Guo]

Bitbucket server crashed with log below and cannot restart:

Caused by: org.hibernate.HibernateException: Missing table: sta_cmt_disc_comment_activity
 at org.hibernate.cfg.Configuration.validateSchema(Configuration.java:1335) ~[hibernate-core-4.3.11.Final.jar:4.3.11.Final]
 at org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:175) ~[hibernate-core-4.3.11.Final.jar:4.3.11.Final]
 at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:525) ~[hibernate-core-4.3.11.Final.jar:4.3.11.Final]
 at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1859) ~[hibernate-core-4.3.11.Final.jar:4.3.11.Final]
 at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1930) ~[hibernate-core-4.3.11.Final.jar:4.3.11.Final]
 at org.springframework.orm.hibernate4.LocalSessionFactoryBuilder.buildSessionFactory(LocalSessionFactoryBuilder.java:372) ~[spring-orm-4.3.0.RELEASE.jar:4.3.0.RELEASE]
 at org.springframework.orm.hibernate4.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:454) ~[spring-orm-4.3.0.RELEASE.jar:4.3.0.RELEASE]
 at com.atlassian.stash.internal.hibernate.ExtendedLocalSessionFactoryBean.buildSessionFactory(ExtendedLocalSessionFactoryBean.java:99) ~[bitbucket-dao-impl-4.9.1.jar:na]
 at org.springframework.orm.hibernate4.LocalSessionFactoryBean.afterPropertiesSet(LocalSessionFactoryBean.java:439) ~[spring-orm-4.3.0.RELEASE.jar:4.3.0.RELEASE]
 ... 5 common frames omitted

 It prompts that "SpringMVC dispatcher [springMvc] could not be started" on the web page.

What's wrong with it and how can we fix it?

[Christian Glockner]

Hi Chao,

Are you trying to upgrade Bitbucket Server when this problem occurs? Or were you just installing?

Cheers,

Christian

Premier Support Engineer

Atlassian

[Zhu Han]

Hi, 

Thanks for your reply.

This instance has run for a long period and have upgraded it from 4.x to 5.8.2 3 months ago, because the version was about to become end of life. And it continued to run stably until this morning(9:42 CST).

we had not found anything wrong or suspicious when upgrading the server, so I think it is not like likely directly related to the upgrade. But we can not completely rule out that possibility either. 

[Christian Glockner]

Hi Zhu,

Which backend database type are you using?

Cheers,

Christian

Premier Support Engineer

Atlassian

[Zhu Han]

Hi, 

We are using PostgreSQL as backend database

[Chao_Guo]

Well, problem resolved.

it happened that,  the instance was installed years ago and my colleagues created a systemd service to manage it. but after upgrading the server we forgot to alter the paths in the service file. so when for some unknown reasons the old version started up, it made the whole server unavailable

sorry to bother you.