I use Confluence 6.15.4 which is connected to an LDAP server for the user management. Last week I removed two users from the LDAP directory. Then they were mentioned in "Unsynced from Directory" tab of the "Users" view in "USER & SECURITY". I removed them there too by performing the "Delete" action. Now I have the problem that I cannot edit a page that has been created by them if the option "Notify watchers" is enabled. In that case I get the message "Unable to communicate with server. Saving is not possible at the moment.". If I disable this option, then I can save the changes. In the top of the page I see the comment "Created by user-f2b34, last modified by XXX YYY 22 minutes ago." How can I solve this problem?
Hello there, @Rico Petrick ! The issue that you are currently facing can be caused by a number of factors. Some of them are database drivers, problems within your own database or a third-party application that is affecting the correct behavior of Confluence.
We could start by ruling out the possibility of this issue affecting your whole instance.
For this, we can do this:
- Create a new page
- Get a few users to watch this watch page
- Select the Notify Watchers option
- Check if you can edit the page
Now, to try and circumvent this issue, there are a few things we can try:
- Check that your database driver is compatible [Confluence Server] [Confluence 6.15] Database JDBC Drivers
- Rebuild the ancestor table [Confluence Server] [Confluence 6.15] Rebuilding the ancestor table
- Enable safe mode and check if the issue persists [Confluence Server] Disabling and enabling apps
- Try restarting your instance
Some notes regarding the procedures described above:
- You should not remove or alter your database driver before creating a backup of the current one and we should also make sure that Confluence is not running when doing so.
- Rebuilding the ancestor table does take time and it is a good practice to create a database backup before doing it. Instance downtime is required.
- Enabling safe mode will disable all user-installed apps and users will not be able to use their features while this is enabled. Instance downtime is strongly advised.
Let us hear from you, Udo! Keep us up to date with your findings.
Hi @Diego_Canto_Rodrigues, maybe my original post was not clear enough, therefore a more detailed explanation:
So the problem cannot occur for newly created pages, it can only happen for pages that already exist and where we see as the user who created the page something like user-f2b34 instead of a real user name.
I started the "Rebuild the ancestor table" job, but this did not help.
I assume the problem occurs because the deleted user is still marked as watcher for that page which has been created by him and now the system tries to send a notification about the changed page to someone who has disappeared. Therefore I see two solutions:
Any ideas how to achieve this?
Thanks everyone for answering last week’s question. The winner of the random drawing from those who commented is: @LarryBrock I’ll contact you separately with your prize details. This wee...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events