Running upgrade using CLI on the NetWitness Admin Server results in a similar error as below:
[2020-02-28T23:11:21+00:00] <98045> (ERROR) Command line upgrade can only be executed on the NW Server (please re-run from the NW Server).
Missing /var/netwitness/common/repo/ folder - no repo files
Running orchestration-cli update-admin-node on the NetWitness Admin server fails with errors.
nwsetup-tui was run by mistake on the NetWitness Admin node
Usually happens when user has the habit of doing ssh from the head unit connecting to the other hosts. Sometimes thinking they are already ssh'd to the target host, and run nwsetup-tui to initiate the node configuration.
On the NetWitness Admin server (nw-node-zero):
Re-create the repo folders, and copy/unzip the update files.
Re-create /etc/netwitness/platform/resolv.dnsmasq file with correct DNS server.
Edit the /etc/netwitness/platform/nw-node-type to show 'node-zero'.
Ensure in mongo db that the nw-node-zero host UUID has the parameter - "node-zero" : true.
Run orchestration-cli-client --update-admin-node until there are no errors and it completes successfully.
To re-create the repo folder and files:
Download the corresponding NetWitness update packages, for example, netwitness-184.108.40.206.zip, netwitness-220.127.116.11.zip from RSA Link.
Up to and depending on your current version
SCP/Copy the zip files to a temp directory on your NetWitness Admin with enough filesystem disk space
Unzip the NetWitness update packages to their corresponding repository directories.
Restore the file from backup, depends if you have taken a backup previously. It should be in /var/netwitness/backup/files/etc/netwitness/platform/resolv.dnsmasq.tgz. tar -xvzf /var/netwitness/backup/files/etc/netwitness/platform/resolv.dnsmasq.tgz -C /etc/netwitness/platform/
Or just re-create the file again using vi, /etc/netwitness/platform/resolv.dnsmasq with the correct DNS entries.
Using vi, edit the /etc/netwitness/platform/nw-node-type file to show 'node-zero' instead of 'node-x'
Ensure in mongo db that the nw-node-zero host UUID has the parameter - "node-zero" : true Sample: