status=413 Request Entity Too Large

Attempting to transfer a mailbox between two Zimbra servers and receiving a message

Code:

---

status=413 Request Entity Too Large

---

I believe this to be a NGINX problem and from another post I have increased the zimbraFileUploadMaxSize parameter and restarted NGINX but the problem persists; the same if I restart the mailboxd process :(

Does this thread help: http://www.zimbra.com/forums/migrati...x-resturl.html

Hi Bill, that is what I had already tried :( Was working fine until I installed the front-end proxy :(

Code:

---

zmprov gs `zmhostname` zimbraFileUploadMaxSize
# name zimbra01.xxxxxxx.xxxxxxxxx
zimbraFileUploadMaxSize: 2097152000

---

Have even tried updating the front-end proxy and that makes no difference at all. Really stuck now as should be migrating mailbox tomorrow :( What I don't understand is that the exported mailbox is not that big; it fact its mine so I know that :)

Code:

---

[zimbra@zimbra01 ~]$ ls -l /download/import/pd.tgz
-rw-r--r-- 1 root root 16223685 Feb 16 04:59 /download/import/pd.tgz
[zimbra@zimbra01 ~]$ zmmailbox -z -m pd@domain.com postRestURL "//?fmt=tgz" /download/import/pd.tgz
ERROR: service.FAILURE (system failure: POST failed, status=413 Request Entity Too Large)
[zimbra@zimbra01 ~]$ zmprov gs `zmhostname` zimbraFileUploadMaxSize
# name zimbra01.domain.com
zimbraFileUploadMaxSize: 209715200

---

So how can 16.2Mb not fit into 200Mb ? If I check /opt/zimbra/conf/nginx/includes/nginx.conf.web.http(s) they do contain

Code:

---

client_max_body_size    200m

---

Any ideas please :confused:

I have taken a different approach to test and created a dummy mailbox with not content at all. I exported it from the source server and then attempted a import on the target and this is what I get

Code:

---

mmailbox -z -m test@domain.com postRestURL "//?fmt=tgz" /download/import/test.tgz
[] INFO: Redirect requested but followRedirects is disabled
ERROR: service.FAILURE (system failure: POST failed, status=302 Moved Temporarily)

---

This was all fine before I enabled NGINX.

I believe I have fixed the problem

Code:

---

su - zimbra
zmprov md domain.com -zimbraPublicServiceHostname smtp01.domain.com

---

when running zmmailbox with debug I noticed in the SOAP responses that it was directing HTTP traffic to the front-end proxy. Temporarily disabling the public service hostname allowed the import to work okay.

The question is whether this should be the correct action :confused:

Bug 44639 - zmmailbox fails on postRest when using public service hostname