Project

General

Profile

Bug #8229

cn.creates failing with "413: Request Entity Too Large" thrown from apache

Added by Rob Nahf over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
d1_cn_buildout
Target version:
Start date:
2017-12-18
Due date:
% Done:

100%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

Description

While running sync from cn-orc-1, 18 cn.creates failed with the following exception. It turns out that the apache configuration was not controlled, and only cn-ucsb-1 had increased the SSL renegotiation size. The solution is to add the configuration to cn-ssl.conf in dataone-cn-os-core.

An actual error message:

[ERROR] 2017-12-18 20:30:12,542 (V2TransferObjectTask:call:269) Task-urn:node:CLOEBIRD-EOD_CLO_2016.eml - UnrecoverableException: EOD_CLO_2016.eml cn.createObject failed - ServiceFailure - 413: Request Entity Too Large: parser for deserializing HTML not written yet. Providing message body:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

413 Request Entity Too Large

Request Entity Too Large
The requested resource/cn/v2/object
does not allow request data with POST requests, or the amount of data provided in
the request exceeds the capacity limit.

Apache/2.4.7 (Ubuntu) Server at cn-orc-1.dataone.org Port 443


Related issues

Related to Infrastructure - Task #8091: Mysterious sync failure of an eml object from the GOA node In Progress 2017-05-05

Associated revisions

Revision 19052
Added by Rob Nahf over 4 years ago

fixes #8229: increased SSLRenegBufferSize to handle dataone-sized POSTS up to 10Mb.

Revision 19052
Added by Rob Nahf over 4 years ago

fixes #8229: increased SSLRenegBufferSize to handle dataone-sized POSTS up to 10Mb.

History

#1 Updated by Rob Nahf over 4 years ago

  • Tracker changed from Task to Bug

will commit the following to cn-ssl.conf in trunk:
(The SSLRenegBufferSize is the new line)



SSLVerifyClient optional

SSLRenegBufferSize 10000000

#2 Updated by Rob Nahf over 4 years ago

  • Related to Task #8091: Mysterious sync failure of an eml object from the GOA node added

#3 Updated by Rob Nahf over 4 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 30 to 100

Applied in changeset java-client:d1client|r19052.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)