Bug #8229
cn.creates failing with "413: Request Entity Too Large" thrown from apache
100%
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
Associated revisions
fixes #8229: increased SSLRenegBufferSize to handle dataone-sized POSTS up to 10Mb.
fixes #8229: increased SSLRenegBufferSize to handle dataone-sized POSTS up to 10Mb.
History
#1 Updated by Rob Nahf almost 7 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 almost 7 years ago
- Related to Task #8091: Mysterious sync failure of an eml object from the GOA node added
#3 Updated by Rob Nahf almost 7 years ago
- Status changed from In Progress to Closed
- % Done changed from 30 to 100
Applied in changeset java-client:d1client|r19052.
