Error 413 -- Request Entity Too Large

[ReggieFisher]

Hello, I'm attempting to upgrade from 8.3 SP5 to 8.4. The update file for 8.4 is really huge (3 gigs)... When I attempt to upload the update file via local browser, I get the following error:

Error 413 -- Request Entity Too Large

From RFC 2068 Hypertext Transfer Protocol -- HTP/1.1:

10.4.14 413 Request Entity Too Large

The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server may close the connection to prevent the client from continuing the request.

Is there a setting I need to change on the RSA instance to be able to get this update installed?  Thank you!

[JayGuillette]

Because the 8.4 update is larger than 2GB, the update install script modifies the /opt/rsa/am/server/config/config.xml, (before the rsaadmin password is even requested), in order that the update can be uploaded through the browser.
However, if this fails, the config.xml is not reverted back to the original version; rather, it is left in an inconsistent state with incorrect pointers to the 8.3.0.4.0 files instead of the 8.3.0.5.0 version you are running, if the system is ever restarted after this occurs, it may not start.

You can either wait for patch 6 or revert to patch 4.
If you cannot get services started, call Support to open a case, There are some fixes for this situation.

[ReggieFisher]

I'm not having an issue getting services started. I'm currently running 8.3.0.5.0 with no issue. I'm trying to run the update for 8.4.0.0.0

[JayGuillette · Accepted solution]

Your options are;

1. update to AM 8.4 from an NFS or Windows Share, not from your browser

2. roll-back your current AM 8.3 P5 to AM 8.3 P4 (or roll back to some earlier version then patch to AM 8.3 P4) and update to AM 8.4 through your browser

3. wait for AM 8.3 Patch 6, update to AM 8.3 Patch 6, then update to AM 8.4 through browser

You've run into a problem with updating AM 8.3 P5 to AM 8.4 through the browser, so it's probably not going to work for you.

[ReggieFisher]

The Windows Share option worked... I appreciate your assistance, Jay!

[JayGuillette]

Glad to hear it worked.

[YanivNess1]

I also received the same error and what worked for me was doing a restart of the services and trying again.