You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi everyone,
So I'm currently trying to upgrade our team calendar confluence plugin, but I'm seeing a weird behaviour. There seems to be a database lock when trying to update the plugin.
ID Type Waiting Wait Active Mode DB Table Index Ins Intent Special
201262 RECORD 1 00:09 00:09 X lab_confluence plugindata PRIMARY 0 rec but not gap
[RO] Locks (? for help) localhost, 5d, InnoDB 1s :-), 1.37k QPS, 65/2/0 con/run/cac thds, 5.7.23
________________________________________________ InnoDB Locks ________________________________________________
ID Type Waiting Wait Active Mode DB Table Index Ins Intent Special
201262 RECORD 1 00:10 00:10 X lab_confluence plugindata PRIMARY 0 rec but not gap
This happens everytime I try, and with all versions as well. We are currently using version 5.3.17 and trying to update to the latest since we want to update our confluence instance.
Has this happend to any of you?
We are using the following versions :
- Confluence 6.12.0
- MySQL 5.7
- JDBC 5.1.42
Thanks!
Frederick
Hello there!
In our ticket, we were able to solve the issue at hand by changing the my.cnf file.
The original was
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
symbolic-links=0
lower_case_table_names=1
default-storage-engine=InnoDB
collation_server=utf8_bin
character-set-server=utf8
transaction-isolation=READ-COMMITTED
max_allowed_packet=256M
binlog_format=row
innodb_log_file_size=2G
connect_timeout=1000
innodb_lock_wait_timeout=1000
wait_timeout=57600
interactive_timeout=57600
general_log = on
general_log_file=/var/log/mysql/query.log
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
and we changed it to:
Important notes
- Always backup your files before changing them
- Never apply changes to the database while Confluence is running
- Always have a rollback plan if things do not go as expected
- Try the changes in a test environment before applying to your production
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
#symbolic-links=0
lower_case_table_names=1
default-storage-engine=InnoDB
collation_server=utf8_bin
character-set-server=utf8
transaction-isolation=READ-COMMITTED
max_allowed_packet=768M
binlog_format=row
innodb_log_file_size=2G
#connect_timeout=1000
#innodb_lock_wait_timeout=1000
wait_timeout=28800
#interactive_timeout=28800
max_connections=500
general_log = on
general_log_file=/var/log/mysql/query.log
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
After changing the .cnf file, the Team Calendars plugin was successfully installed! Also, look out for interference from your anti-virus.
During the troubleshooting, Frederick was able to verify that the anti-virus software was interfering with the installation of other add ons as well.
Important notes
- Always backup your files before changing them
- Never apply changes to the database while Confluence is running
- Always have a rollback plan if things do not go as expected
- Try the changes in a test environment before applying to your production
Thank you for raising this issue with the Community Frederick! Hoping that our thread can help other customers as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.