We have Octopus version 22.214.171.1248 installed.
I’m adding a new environment using portal using Environments > “Add environment” button, but after postback no new item is displayed. Same thing happens when I try to add machine to an existing environment. When I check this instance of Octopus with command line and octo.exe, I can see that new items were added to db. I’ve also noticed that in tab “Tasks” latest entry is few days old, and there should be some tasks from today.
I’ve installed Octopus (the same version as on server) on my local machine and imported backup of raven db from server - and all new entries can be seen on “Environments” page without anything being changed. Additionally, task from today are also listed.
I’ve restarted Octopus service and web site on server - but no change can be seen.
Could you suggest me what can cause such behavior and can be done do “unfreeze”. Unfortunately the obvious answer “update your Octopus” is currently not an option.
Thanks for getting in touch! Can you try to run the following process: http://octopusdeploy.com/blog/resetting-raven-indexes
This is the guide to resetting raven indexes in 1.6
Let me know if that resolves your issue.
No change in “Environments” tab after resetting indexes. However, in “Tasks” tab everything is displayed up to date.
I’ve noticed that in RavenDB Management Studio list of environments is the same as in “Environments” tab - yet Octo.exe lists all, even those new missing from “Environments” tab\RavenDB Management Studio.
Any further suggestions?
Thanks for the reply. Roughly how many environments do you have? I don’t suppose it’s 129 or more?
Currently we have little less than 40 environments.
Sorry for the delay in a reply. As usual with 1.6 these things are very hard to diagnose. We think a screen sharing session might be our only way to figure this out.
Could you please pick a time that suits: https://octopusdeploy.acuityscheduling.com/schedule.php
We were able to fix this problem with following steps:
- Backup DB using Octopus on server.
- Import DB backup to Octopus on local machine.
- Copy folder with DB files from local machine to server.
- Change the location of DB files in Octopus tools to newly copied folder.
- Restart Octopus.
- After few minutes and Octopus blue rings everything started to work as it should.
However we still have no idea why this problem occurred…
I am glad you got this working. Honestly we do not know what it is either, 1.6 does not have as many troubleshooting avenues.