User configuration changes access to wrong server Edited

We were running Confluence temporarily on a server ("192.168.111.74") and moved it to another server ("atlassian.anywhere.com").

I set up Confluence on the new server and restored the data with a backup of the old server. Now I wanted to delete some users, but that does not work. Removing a user from a group does not work either.

Confluence takes users from Jira which has also moved to the new server. 

Log file give a hint that there is communication to the old Confluence server (192.168.111.74). So there seems to be the old servers IP address still be stored anywhere in the system.

How to fix this?

 

=================================

2017-08-11 23:08:39,272 WARN [http-nio-8090-exec-4] [confluence.impl.hibernate.ConfluenceHibernateTransactionManager] doRollback Performing rollback. Transactions:
->[null]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT (Session #111193677)
-- referer: http://atlassian.anywhere.com:8090/admin/users/removeuserfromgroup.action?atl_token=a19ede5a1d8cf814a61dbb21863824374b6bac52&membersOfGroupTerm=confluence-users&username=at002 | url: /admin/users/removeuserfromgroup.action | traceId: 3f9b9f29a5b51c8b | userName: at003 | action: removeuserfromgroup
2017-08-11 23:09:12,833 INFO [Caesium-1-1] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache FULL synchronisation for directory [ 294913 ] starting
2017-08-11 23:09:17,872 INFO [Caesium-1-1] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache failed synchronisation complete for directory [ 294913 ] in [ 5039ms ]
2017-08-11 23:09:17,909 ERROR [Caesium-1-1] [atlassian.crowd.directory.DbCachingDirectoryPoller] pollChanges Error occurred while refreshing the cache for directory [ 294913 ].
-- url: /setup/longrunningtaskxml.action | traceId: 7e69673fa54f031d | userName: anonymous | referer: http://localhost:8090/setup/setup-restore-local.action | action: longrunningtaskxml
com.atlassian.crowd.exception.OperationFailedException: org.apache.http.conn.ConnectTimeoutException: Connect to 192.168.111.74:8080 [/192.168.111.74] failed: connect timed out
at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:425)

2 answers

Yes, that was updated.
The application seems to run quite ok apart from that and I have not detected any warnings yet.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Kesha Thillainayagam
Posted Friday in Confluence

We want to hear how your non-technical teams are using Confluence!

Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...

253 views 11 10
Join discussion

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