Bug Report

System Information

• Operating System Version - Ubuntu Linux - 22.04.4 LTS
• AMP version and build date - 2.5.0.0, 15/03/2024 19:18
• Which AMP release stream you're using - Mainline

I confirm:

• [x] that I have searched for an existing bug report for this issue.
• [x] that I am using the latest available version of AMP.
• [x] that my operating system is up-to-date.

Symptoms

• What are you trying to do? - Restart AMP without any errors or docker failures
• What are you expecting to happen? - All instances come up automatically without any errors
• What is actually happening? ('Nothing' is not an acceptable answer!) - AMP displays several errors saying that containers already exists and containers fail to boot automatically. All instances have to be manually started and they work fine upon starting them.

Reproduction

Enter reproductions steps here:

1. Reboot physical or virtual host that AMP sits on completely
2. Wait for AMP to start
3. Login to AMP
4. Errors appear saying that the docker containers that relate to the instances failed to start
5. Console shows that the containers already exist
6. Manually start the containers and they begin to work

Errors that appear: 15:21:29 docker: Error response from daemon: Conflict. The container name "/AMP_Creative01" is already in use by container "b4b47070275c808f808cb065230e07046ed8f1f06535f42f708fcb4e1a905ff1". You have to remove (or rename) that container to be able to reuse that name. See 'docker run --help'. 15:21:34 docker: Error response from daemon: Conflict. The container name "/AMP_LifeSim01" is already in use by container "778d3d07b6064b7e094ea301c5897f7556b56f40367dcd5770fa26800bf38ea4". You have to remove (or rename) that container to be able to reuse that name. See 'docker run --help'. 15:21:39 docker: Error response from daemon: Conflict. The container name "/AMP_Lobby01" is already in use by container "57d064c0139fafd76f8aae3c6f7d87398a06982ece9440f8a6b0d00b36e976ac". You have to remove (or rename) that container to be able to reuse that name.

Support Data: Attached

Your tools are outdated. Please make sure everything is up to date before opening tickets.

@PhonicUK I was told that doesnt matter and is been something thats on going for a while so i havent proceeded however it was something on my mind that i needed to do.

Can you tell me how to update the tools? I have updated to the latest version but tools are still 2.4.8

Indeed, I instructed them to make this issue. It's affecting my production setup as well which is up to date on Mainline.

AMPLOG 2024-03-26 01-36-54.log.txt Same problem. Full log from most recent restart

This should be addressed as of 2506 too. Needs retest.

docker still errors out a bit but does get killed by ampinstmgr on upgrade from 2.5.0.4 to 2.5.0.6 and doesn't need user intervention. able to upgrade with no problems