Tried to upgrade confluence from 4.03 to 4.3.2 Now site is down.

logo System Error

A system error has occurred — our apologies!

For immediate troubleshooting, consult our knowledge base for a solution.

If you would like to receive support from Atlassian's support team, ask your Confluence administrator to create a support issue on Atlassian's support system with the following information:

a description of your problem and what you were doing at the time it occurred

a copy of the error and system information found below

a copy of the application logs (if possible).

Your Confluence administrator can use the support request form to create a support ticket which will include this information.

We will respond as promptly as possible.

Thank you!

Return to site homepage…

Cause

com.atlassian.spring.container.ComponentNotFoundException: Failed to find component: No bean named 'translationModeManager' is defined

at com.atlassian.spring.container.SpringContainerContext.getComponent(SpringContainerContext.java:79)

caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'translationModeManager' is defined

at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:387)

1 answer

Hi there,

In order to narrow down the root cause of your issue further, you would need to review your Confluence logs which is located in <Conf_HOME_Dir>/logs/atlassian-confluence.log.

For troubleshooting purposes, you could also try the following steps on your staging environment for your upgrade test.

  1. Shutdown Confluence
  2. Revert database and home directory to pre-upgrade state
  3. Remove the following directories
    • <tt><confluence-home>/bundled-plugins</tt>
    • <tt><confluence-home>/plugins-cache</tt>
    • <tt><confluence-home>/plugins-osgi-cache</tt>
    • <tt><confluence-home>/plugins-temp</tt>
  4. Rename your<tt>atlassian-confluence.log</tt>which is located in<tt><confluence-home/logs/</tt>
  5. Restart Confluence upgrade process

To avoid any issue on your production instance during the upgrade process, we highly recommend you to create a cloned instance. Hope it helps.

Cheers,
Septa Cahyadiputra

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Featured Groups

Tuesday tips & tricks: What is the Atlassian Community?

It's officially Tuesday, which means it's officially time for another tip to help you better navigate this space we call the Atlassian Community. 😄 I got a great question from community member, Sa...

145 views 6 8
View post

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you