Uninstall the webtier then reinstall it to resolve the issue. If you do not want to uninstall and reinstall, please refer to the second solution below.
- SSH to the primary RSA Authentication Manager server as the rsaadmin user then run the following commands:
login as: rsaadmin
Using keyboard-interactive authentication.
Password: <enter operating system password>
Last login: Fri Jan 10 12:33:27 2020 from jumphost.vcloud.local
RSA Authentication Manager Installation Directory: /opt/rsa/am
rsaadmin@am82p:~> cd /opt/rsa/am/utils/etc/
rsaadmin@am82p:~> ls -alh systemfields.properties
-rw------- 1 rsaadmin rsaadmin 11K Jan 15 16:22 systemfields.properties
rsaadmin@am82p:~> cp systemfields.properties /tmp/
- Use WinSCP or another program to connect to the primary RSA Authentication Manager server as the rsaadmin user.
- Download the systemfields.properties file you just copied to /tmp to your local PC then disconnect from WinSCP.
- SSH into the Linux or Windows webtier server.
- Run sudo to the root user (Linux) or administrator (Windows). Use the same password you used for rsaadmin when entering the command below:
rsaadmin@am82p:~> sudo su -
- Upload the systemfields.properties file to /tmp on the Linux webtier servers.
- Via SSH on the webtier, type the following commands (make adjustments if your install location is different from the default):
mv systemfields.properties systemfields.properties.orig
cp /tmp/systemfields.properties ./
- Now that the file has been copied, set the correct permissions on the file. First run the following command to check permissions on both of the systemfields.properties files:
ls -alh systemfields.properties*
-rw-------. 1 root root 11K Jan 21 08:42 systemfields.properties
-rw-------. 1 webtier webtier 0 Jan 4 05:36 systemfields.properties.orig
- In this case, when the webtier was installed, the user defined during the install was called webtier and if we look at the file permissions for the original systemfields.properties file we can see the owner and group are both webtier. We need to make sure permissions on the new systemfields.properties file match the one we renamed. The user and group will be different than what is in this example, so use that as opposed to what is shown here. The commands below set the new file permissions and owner/group to match the original file.
chmod 600 systemfields.properties
chown webtier:webtier systemfields.properties
- Run the following command to update the systemfields.properties file for the webtier server OS and hardware. Until now we have been doing everything as root, but you need to switch to the webtier user to run this last command. Again the user you picked during install will be different than the example user.
sudo su - webtier
Invalid argument. Multiple CLU's starting with 'manage-sec' found:
When you run the above command you will see an error, take note of the patch level of your webtier in the Operations Console. In the example below, we are on SP1 patch 10, so you want to use the same manage-secrets version via the following command.
./rsautil manage-secrets-184.108.40.206.0 -a recover
Please enter OC Administrator username: <enter name of Operations Console admin user>
Please enter OC Administrator password: <enter password for Operations Console admin user>
Machine fingerprint restored successfully.
The above command requires the Operations Console username and password from the primary Authentication Manager server from which you copied the systemfields.properties file.
If all commands have been run without issue, you can now start the webtier services via the following command:
You will get a green status, then in about five minutes the server will show up as online again in the Operations Console.