s_dchakr (Customer) asked a question.

February 6, 2025 at 12:15 AM
RSA Update to AM 8.7 SP 1 fails due to file integrity. Is there any workaround?

I keep getting the following error despite downloading the update iso from my.rsa.com

/opt/rsa/am/utils/bin/appliance/verifyPatch.sh: line 8: /tmp/rsa_update/checksums/new: Permission denied

xargs: sha256sum: terminated by signal 13

sort: open failed: /tmp/rsa_update/checksums/original: Permission denied

diff: /tmp/rsa_update/checksums/original: No such file or directory

  • 1 answer
  • 218 views

  • EricaChalfin (RSA)

    @s_dchakr (Customer)​ ,

     

    Thank you for the question!

     

    I have a few questions for you:

    • At what version of Authentication Manager is this server currently running?
    • If you open the Operations Console and navigate to Maintenance > Update and Rollback, what is the earliest version listed in the table? You may need to scroll down to see it.
    • Are you upgrading a hardware appliance or a virtual server?
    • Is this a primary server or replica?
    • If this is a replicated environment, which server was upgraded first?
    • How are you applying Authentication Manager 8.7 SP1?
    • What do you have set for a configured update source (browser, NFS share, Windows share)?
    • Have you tried changing the update source?
    • If you are using a Windows share, try changing the Windows user name from domain\username to username, as follows:
    • What are the file and directory permissions for that file? If you change them to 755 or 777 does that resolve the error? The Windows equivalent for 755 are: Owner: Read, Write, Execute/Group: Read, Execute/Everyone else: Read, Execute. For the corresponding value of 777, set permissions to Group: Read, Write, Execute/Everyone else: Read, Write, Execute.
    • Please login to my.rsa.com and confirm that the checksum value listed there matches what you see when you run sha256sum on the file you are installing.
    • Have you tried downloading the file from a different machine or network, perhaps on/off your VPN?

     

    If these options do not resolve the issue, navigate to Administration > Download Troubleshooting Files in the Operations Console to capture the complete update logs so that you can open a case with RSA Technical Support. Attach the logs to your case so that an technical support engineer can review them and provide a more detailed analysis. A review of the file named  /opt/rsa/am/server/logs/update-8.7.1.0-build<number>-<datestamp>.log would be helpful.

    Expand Post

Don't see what you're looking for?