DT 6.1 - Upgrade - Purepaths unknows
Any immediate help will be appreciated.... i was upgrading a prod server...
After upgrade, collectors were not connecting and finally I removed all from under the instances directory and created new. Connected now but purepaths are showing..... unknown..
I had another collector with cache preserved etc… but agents using that also are showing unknown..
JVM restart did fix the issue but wondering why this happened... Any pointers on how to avoid it before I upgrade the rest of the servers.
Collectors also I had originally migrated using the dtmigration.jar.
Hi Jibi
This is typically caused by problems with the class cache on the Collectors. Not sure if that is the case in your case.
It is odd that the Collectors didnt reconnect after you upgraded the server. This is something you should look into. Anything in the log files that would indicate what the problem was? Maybe opening a support ticket?
Andi - Thanks. I have opened the case SUPDT-5507.
I think it will be better to have a version number for the dtmigration.jar too.. One the server which I had issue, by mistake I had used the one from 5.5 version...
Hey Jibi,
thanks again yet another time.
I talked to Tom (release management) and he´s investigating to include the version in the jar file name as it is in the zip.
For the time being I bolded "use the latest..." and added a sentence to check the version at run-time. (against documentation or the zip file name)
Thanks
G.
Hi Jibi,
thanks for the input, I appreciate each consideration for improving migration.
We considered this option but decided not to go with it. It would interefere with the automated use of the tool, having to manually replace the version each time where we know some of our customers have these steps automated. Furthermore it suggests that the version of the tool has to match the Dynatrace version and that it is updated with each release (which was the case most of the time, but is not in general). For instance if no change is necessary, the 6.1 migration tool would be used to migrate from 6.1 to 6.2 without updating the version.
I think it would be best to delete the tool after migration and always follow the migration guide of the version that you are migrating to, which will instruct and remind you to update to the version mentioned there.
Futhermore, the version of the tool at hand can be determined in the help text, also each run shows it and it is in the jar-manifest.
You can however always rename file of course. Thanks for the understanding that we keep it that way for now.
Regards,
Thomas
