Our latest release comes packed with exciting new features, improved functionality, and bug fixes that make it the best version yet. 🥰
Main focus of the new version 4.6.6 are mainly functions in the import module, especially for import out of iTop. For a better user experience it comes with a nice 'Used by'
view for hosts, some sorting options and new copy functions for existing objects. In addition to the enhancements, we have encountered a bug that can cause orphanes in the container structure. This blogpost shows how you can check if your system is affected. If your system is affected, you can also check if an automatic cleanup is possible.
The problem might occur when editing containers at the same time. As an example: you use the API and the configuration frontend at exactly the same time and editing the same container.
To do this, you can simply run the rcovery check command as the root user.
oitc container_recover --check
Best case is that you will see the following output:
Great! You have nothing to do.
If you get the result Orphaned containers found!
don’t worry. Maybe you can fix it automatically with the following command:
oitc container_recover --recover
Hint: openITCOCKPIT generates a backup of MySQL database before doing any changes.
Best case is that you see the following output:
Congratulations you have a clean database.If you receive the following output, you do not need to panic either.
Some orphaned containers are still in use. Automatic fixing is not possible. Your monitoring is still running and there are no changes to the existing database.
Please contact the openITCOCKPIT enterprise support.
Please see the changelog for a complete list of new features, fixed bugs and improvements.
Please see the official documentation of how to update openITCOCKPIT.
Many thanks to all bug and issue finders! We appreciate your hard work to keep openITCOCKPIT stable and secure ❤️
Your openITCOCKPIT Team