Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Migration

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 02-15-2010, 09:47 AM
Moderator
 
Posts: 7,929
Default 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
__________________
Reply With Quote
  #2 (permalink)  
Old 02-15-2010, 10:37 AM
Zimbra Consultant & Moderator
 
Posts: 20,319
Default

Does this thread help: ZCS-to-ZCS with zmmailbox and RestURL
__________________
Regards


Bill
Reply With Quote
  #3 (permalink)  
Old 02-15-2010, 11:38 AM
Moderator
 
Posts: 7,929
Default

Hi Bill, that is what I had already tried Was working fine until I installed the front-end proxy
__________________
Reply With Quote
  #4 (permalink)  
Old 02-15-2010, 11:40 AM
Moderator
 
Posts: 7,929
Default

Code:
zmprov gs `zmhostname` zimbraFileUploadMaxSize
# name zimbra01.xxxxxxx.xxxxxxxxx
zimbraFileUploadMaxSize: 2097152000
__________________
Reply With Quote
  #5 (permalink)  
Old 02-16-2010, 02:04 AM
Moderator
 
Posts: 7,929
Default

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
__________________
Reply With Quote
  #6 (permalink)  
Old 02-16-2010, 04:39 AM
Moderator
 
Posts: 7,929
Default

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.
__________________
Reply With Quote
  #7 (permalink)  
Old 02-16-2010, 05:52 AM
Moderator
 
Posts: 7,929
Default

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

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

Last edited by uxbod; 02-16-2010 at 06:01 AM..
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.