nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

60201 : Create ACL entries for projects (post-bootstrap) exception

v8lust

We are migrating our bamboo instance from CentOS to Ubuntu (leaving Crowd, JIRA and Confluence on the existing CentOS host). We have dumped and restored PostGreSQL and copied accross the bamboo-home directory. The delivered properties file from Atlassian has been updated for our file path. The preconditions seemed fine, and the database connection and migrations looked OK, then a HTTP connection to places unknown has failed.

echo "bamboo.home=/atlassian/bamboo/bamboo-home" >> atlassian-bamboo-6.2.2/atlassian-bamboo/WEB-INF/classes/bamboo-init.properties

./atlassian-bamboo-6.2.2/bin/start-bamboo.sh -fg

...

2017-11-17 01:08:44,908 INFO [16-UpgradeTaskBackgroundThread:pool-31-thread-1] [AbstractUpgradeManager] --------------------------------------------------------
2017-11-17 01:08:44,909 INFO [16-UpgradeTaskBackgroundThread:pool-31-thread-1] [AbstractUpgradeManager] 60201 : Create ACL entries for projects (post-bootstrap)
2017-11-17 01:08:44,909 INFO [16-UpgradeTaskBackgroundThread:pool-31-thread-1] [AbstractUpgradeManager] --------------------------------------------------------
2017-11-17 01:08:44,959 INFO [16-UpgradeTaskBackgroundThread:pool-31-thread-1] [UpgradeTask60201CreateProjectAcls] Found 4 projects in total
2017-11-17 01:08:45,109 INFO [16-UpgradeTaskBackgroundThread:pool-31-thread-1] [HttpMethodDirector] I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused)
2017-11-17 01:08:45,110 INFO [16-UpgradeTaskBackgroundThread:pool-31-thread-1] [HttpMethodDirector] Retrying request
2017-11-17 01:08:45,111 INFO [16-UpgradeTaskBackgroundThread:pool-31-thread-1] [HttpMethodDirector] I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused)
2017-11-17 01:08:45,111 INFO [16-UpgradeTaskBackgroundThread:pool-31-thread-1] [HttpMethodDirector] Retrying request
2017-11-17 01:08:45,111 INFO [16-UpgradeTaskBackgroundThread:pool-31-thread-1] [HttpMethodDirector] I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused)
2017-11-17 01:08:45,111 INFO [16-UpgradeTaskBackgroundThread:pool-31-thread-1] [HttpMethodDirector] Retrying request
2017-11-17 01:08:45,114 ERROR [16-UpgradeTaskBackgroundThread:pool-31-thread-1] [DefaultUserAccessor] com.atlassian.crowd.exception.OperationFailedException: java.net.ConnectException: Connection refused (Connection refused)
com.atlassian.user.EntityException: com.atlassian.crowd.exception.OperationFailedException: java.net.ConnectException: Connection refused (Connection refused)

Accepted answers

Ellie Z

Hi Jules and Amy,

Thanks for reaching out to the Atlassian Community today!

From the log snippet that you've posted, it looks like Bamboo's connection to Crowd was refused on the Crowd side. Specifically, we can see that in the following section:

2017-11-17 01:08:45,114 ERROR [16-UpgradeTaskBackgroundThread:pool-31-thread-1] [DefaultUserAccessor] com.atlassian.crowd.exception.OperationFailedException: java.net.ConnectException: Connection refused (Connection refused)
com.atlassian.user.EntityException: com.atlassian.crowd.exception.OperationFailedException: java.net.ConnectException: Connection refused (Connection refused)

Since Bamboo has been moved to a new server, could you please check the following:

Can you ping the Crowd server from the new Bamboo server?
Connection refused error while integrating client application with Crowd
Is Bamboo's new IP address added to the "Remote Applications" section of Crowd:
Specifying an Application's Address or Hostname

Please don't hesitate to reach out if you have any additional questions or concerns.

Thanks!
Elias Zeidan | Bamboo Support

All comments

Ellie Z

Hi Jules and Amy,

Thanks for reaching out to the Atlassian Community today!

From the log snippet that you've posted, it looks like Bamboo's connection to Crowd was refused on the Crowd side. Specifically, we can see that in the following section:

2017-11-17 01:08:45,114 ERROR [16-UpgradeTaskBackgroundThread:pool-31-thread-1] [DefaultUserAccessor] com.atlassian.crowd.exception.OperationFailedException: java.net.ConnectException: Connection refused (Connection refused)
com.atlassian.user.EntityException: com.atlassian.crowd.exception.OperationFailedException: java.net.ConnectException: Connection refused (Connection refused)

Since Bamboo has been moved to a new server, could you please check the following:

Can you ping the Crowd server from the new Bamboo server?
Connection refused error while integrating client application with Crowd
Is Bamboo's new IP address added to the "Remote Applications" section of Crowd:
Specifying an Application's Address or Hostname

Please don't hesitate to reach out if you have any additional questions or concerns.

Thanks!
Elias Zeidan | Bamboo Support

v8lust

Thanks for the guidance, I didn't forgot Crowd becomes the exclusive IAM solution in bamboo (I thought I could start it up and reconfigure once the UI was up). Now knowing this, Is there a way to change where it looks for Crowd, as I believe the current address is is looking for is localhost:8095?

If worse comes to worse, I can restart the old instance, reconfigure it in the UI, and start the migration process over.

Ellie Z

Hi!

Thanks for your reply. I apologize for the delayed response.

To ensure the correct configuration on the new server, could you please do the following:

Stop Bamboo
Replace the contents of <bamboo-home>/xml-data/configuration/atlassian-user.xml with:
```
<atlassian-user>
    <repositories>
        <hibernate name="Hibernate Repository" key="hibernateRepository" description="Hibernate Repository" cache="true"/>
    </repositories>
</atlassian-user>&nbsp;
```
This will set Bamboo to use the internal user repository, with the original admin user
- If needed, you can reset the admin password by following the process in Restoring passwords to recover admin users
Start Bamboo – it should complete the installation/upgrade
Configure the instance to use Crowd as the user repository

Thanks!

Elias

v8lust

Thanks for that, the migrations appear to have completed. Can you advise is the base URL is in the database or in bamboo-home (cannot access as the application is attempting to redirect to the original location)?