How long should 'Configuring update packages' take when upgrading the primary netwitness server? I'm attempting to upgrade from 11.3.2 to 11.4.1 and this is the first upgrade we have done. It's been stuck on this status for over 2 hours.
Maybe ~10-15 minutes at most. It's likely your stack has encountered an error and is now stuck. I recommend opening a support case to find whatever the issue is and fix it.
Will do, thanks!
Well I agree with Josh, BUT, it all depends on your download speed. If you did everything from the UI, meaning you went to the Admin -> Hosts page, selected the NW server and from the Update menu, selected "Check for Updates", then when it said new updates are available you selected the 11.4.1 update version and the selected the NW server and then from the update menu, selected "Update Host", it could take some time. In some cases depending on the network latency and download speeds, it may even fail after a long period of time. See, when you ran the "Check for Updates", all that was downloaded was the latest repo manifest file, the actual repo files have not been downloaded yet. If you decide to use the automated download, when you run the "Update Host" on the NW server, the first thing it has to do is download the repo(s), in your case it will download the 184.108.40.206 repo, then realize it that the 220.127.116.11 repo is also needed, so will then download it also, these are 4.6 GB and 6.5 GB respectively, as the 18.104.22.168 is a dependency of the 22.214.171.124 repo, when it is trying to "configure" the 126.96.36.199, it has to download the 188.8.131.52 to do so. So the question is, how long will it take to download 11.1 GB on your network?
The workaround for this is to download the netwitness-184.108.40.206.zip file from my.rsa.com, and the netwitness-220.127.116.11.zip from RSA-Link ahead of time, the place them BOTH in the /var/netwitness/common/update-stage directory on the NW server (note: don't unzip them), then go to the Hosts page and run the "check for updates" and it will pop up a window stating that 18.104.22.168 is available and would you like to initialize it?, say yes, and the two repos 22.214.171.124 and 126.96.36.199 will be created from the zip files. THEN start your update of the NW server and it will kick off immediately.
Presumably the 'Download update packages' status is where the download is occurring, my upgrade progressed past this fairly quickly and got stuck on 'Configuring update packages' which is where some sort of error occurred. I have spoken with support and they have suggested (as you have) an offline install which I will attempt today.
Retrieving data ...