How to investigate DM upgrade stuck after uploading package?

Solved773 viewsupgrade
1
0 Comments

Hi Dojo,

I successfully installed a new DM Agent and want to upgrade it to the latest FR. After the package upload, nothing is executed anymore.

How can I investigate this?

SLNet logging

Jens Vandewalle [SLC] [DevOps Enabler] Selected answer as best 21st October 2021

2 Answers

4
9.33K 0 Comments

Further investigation showed us that multiple NICs were configured without an IP address and no priority was assigned to the NIC with an IP address.

The DM version installed with the v10.0 installer was taking a NIC which didn't had an IP address configured, resulting in having IP 127.0.0.1 configured for that Agent, instead of the IP address of the NIC, which is ignored during the upgrade process. This issue is resolved with RN29759 in a later DataMiner version.

Workaround for this was making sure that the correct NIC was used by specifying it's MAC in the NetworkAdapters section in the DataMiner xml file as mentioned in the help.

Jens Vandewalle [SLC] [DevOps Enabler] Selected answer as best 21st October 2021
1
2.71K 4 Comments

Do you see any errors in C:\Skyline DataMiner\Upgrades\Packages\<Your Upgrade package name>\progress.log?

What could also help is checking the Windows Event viewer (Application logs) for errors related to TaskbarUtility/Upgrading.

If you're upgrading to an internal (unreleased) build, could you share the build number? Then we can check if there were known issues in that build.

I'm assuming you're running 9.6.0 now (after installing) and will upgrade to 10.1.10 (the latest FR right now). Since this is quite a big jump, I'd recommend upgrading to 10.0.0 first, then to 10.1.0.0, then to 10.1.10.

Jens Vandewalle [SLC] [DevOps Enabler] Posted new comment 20th October 2021
Jens Vandewalle [SLC] [DevOps Enabler] commented

Hi Jens, no errors are mentioned in the progress.log file, nor in the Event Viewer. I’m upgrading to 10.1.9.0-10814
Gellynck Jens [SLC] commented

Then I think your best bet is to upgrade to the latest CU of the main release you installed, and then upgrade to 10.1.0 (latest CU)
Brent Alleweireldt [SLC] commented

One more point of investigation.
Upgrade control messages are done through SLNet (if SLNet is running) so the SLNet.txt logfiles are a good check as well to see what its last actions were or if there are any stuck threads etc.
Jens Vandewalle [SLC] [DevOps Enabler] commented

Hi Brent, I’ve updated my original post with a capture of the SLNet logging file. Besides lots of Upload Request messages, there is no relevant information.