Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Some Confluence plugins failed to start after upgrading from 7.3.2 to 7.3.5

booth-bro May 10, 2020

Following plugins failed to start after upgrading from 7.3.2 to 7.3.5
They were grayed out. When I manually enabled them. I got error messages:

"An unexpected error occurred. Refer to the logs for more information."
- Office Connector plugin 11.0.7
- Document Conversion Library, 2.1.5
- Confluence-files, 3.0.6
- Confluence view file macro, 4.1.1
- Confluence File Notification, 3.1.0
- Confluence Document Conversion Library, 5.0.6

I tried removing plugin cache directories as below. But it didn't help
# cd /var/atlassian/application-data/confluence/
# rm -fr plugins-cache/
# rm -fr plugins-osgi-cache/
# rm -fr plugins-temp/
# rm -fr bundled-plugins/

As the result, the attached files in the Confluence are not visible.

2 answers

1 accepted

0 votes
Answer accepted
booth-bro May 12, 2020

Just want to update this issue. Today I deleted the plugin cache directories described in my original post, and then restarted the Confluence server. The issue was resolved by itself. I don't what makes it to work this time. 

Now the all plugins mentioned in my original post are enabled, and the attachment files are accessible.   

0 votes
Ismael Jimoh
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 10, 2020

Hi @booth-bro 

Looking at the problem reported, it may be similar to this https://confluence.atlassian.com/confkb/unable-to-start-confluence-or-some-plugins-are-disabled-upon-startup-234652870.html

Can you follow the steps they suggested and let us know if it helps?

Thanks.

booth-bro May 11, 2020

Hi, Ismael_Jimoh

Thanks for the quick reply!

The issue you were referencing to seems to be related to Microsoft SQL Server. It recommended two actions:
1. set the CATALINA_OPTS="-Datlassian.plugins.enable.wait=300" in the setenv.sh file
2. make sure the transaction isolation level is set to "Read Committed with Row Versioning"

We use PostgreSQL 9.6 for our Confluence server. But I follow the steps anyway. Here is what I found out:
1. the CATALINA_OPTS in the setenv.sh file is already set to the suggested value. Following is the line I copied from the file:
CATALINA_OPTS="-Datlassian.plugins.enable.wait=300 ${CATALINA_OPTS}"

2. I logged into my PostgreSQL database and ran the following command. I found out that the default transaction isolation level is "read committed".

confluence=# SHOW default_transaction_isolation;
  read committed

PostgreSQL has the four transaction isolation levels shown below. The "read committed" level is the closest to MS SQL's "Read Committed with Row Versioning"
- Read uncommitted
- Read committed
- Repeatable read
- Serializable

Any further suggestions? Thanks!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
7.3.5
TAGS
AUG Leaders

Atlassian Community Events