Description & Error Message: Hi - at the weekend (13-05-2017) we upgraded our performance test environment (one MOM, 6 collectors, 1 APM DB) to version 10.5.1 with all hotfixes applied.
We upgraded 3 collectors using the installer - no issues.
We then produced a tar file from one of these collectors containing the 10.5.1 software and used that to upgrade the other 3 collectors. This is what we always do when we upgrade production as we have 30 collectors so its a faster way to do it.
The 3 collectors we did this way are not showing any historic data.
I can see that the where we did the upgrade via the installer logs show this ....
20170513 093650 GMT [INFO] [Manager] Using data directory: /app/data/SmartStor20170513 093650 GMT [INFO] [Manager] Available processors is 420170513 093650 GMT [INFO] [Manager] Loading metadata file: /app/data/SmartStor/metrics.metadata20170513 093652 GMT [INFO] [Manager.MetadataStore] Upgrading metadata to new version: 1
Then it parses all the smartstor archive…….
20170513 093714 GMT [INFO] [Manager] Finished populating metadata from /app/data/SmartStor and /app/data/archive - took 22657
However in the collectors where we upgraded via our tar file we only see
20170513 140620 BST [INFO] [Manager] Using data directory: /wload/zdkc/app/data/SmartStor20170513 140621 BST [INFO] [Manager] Available processors is 2420170513 140621 BST [INFO] [Manager] Finished slow scan from /wload/zdkc/app/data/SmartStor/1494676815000.data - took 7420170513 140621 BST [INFO] [Manager] Finished slow scan from /wload/zdkc/app/data/SmartStor/1494678990000.data - took 7120170513 140621 BST [INFO] [Manager] Finished slow scan from /wload/zdkc/app/data/SmartStor/1494680415000.spool - took 7120170513 140621 BST [INFO] [Manager.MetadataStore] Initialization of metadata took 672 ms
You don’t get this line in the ones we upgraded using the tar files
20170513 093652 GMT [INFO] [Manager.MetadataStore] Upgrading metadata to new version: 1
There must be a flag somewhere that gets set after the installer runs to say that the “Upgrading metadata” step has been done so it doesn’t run again.
How can we revert that so that we can force the metadata to be upgraded if it hasn't yet been done ?
From which version of APM you are upgraded?
In the logs where issue is coming the data files are not loading? I can see its been scanned but not upgraded. Can you share the log file here.
Its a 10.1 to 10.5 upgrade. I have opened a support case and the logs are there (00747658)
I'm looking at this further and have noticed that there is a new metadata property in the 10.5.1 config that wasnt there in 10.1
The metadata is now being writtent to ISCOPE/data, rather than /SMARTSOR/data as it used to be. So I think that I have tarred up a metadata file in ISCOPE/data and deployed that.
Is it possible that because the "new" metadata file was already present, the EM doesnt try to scan the metadata file. So if we stop the EM and delete the ISCOPE/data files and restart it will reload the metadata correctly ?
Yes it was changed from 10.1 to 10.5.
As you have opened a support ticket our engineer will analyse logs and help you. We are marking this as answered as support case is opened.
Kindly post the solution here hope it might be useful for others as well.