EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #10250

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] Hi, i want ask

Hi Jokoe,

I think it is highly unlikely that LimitRequestBody is you issue and I deliberately did not mention it in my initial reply.  As pre Apache 2.4.53 it was unlimited and since then the limit has been 1073741824 bytes = 1 GiB.  So unless, you or a colleague has explicitly set the value much lower than its default then not being able to upload files of a few megabytes is not going to be caused by LimitRequestBody.  However, it would be useful to know what version of Apache and the name and version of your operating system (e.g. Ubuntu 24.04).

You initial description suggested it just stopped working and you had not changed anything.  Had you rebooted the server or restarted Apache between when you were able to upload larger files and not?  Having not knowingly changed anything, suggests a package upgrade by the operating system or something off-server like "Agung PW" suggests.  However, firewalling to limit file upload would need to be something done by a Web Application Firewall (WAF) for that to be the case you EPrints instance running on Apache would need to be being proxied by another server or you would have needed to set up some WAF-like integration with Apache (e.g. mod_security2).  I would assume you would be aware if either of these scenarios were the case?

Overall, this does not sound like an EPrints issue, it could be a file permissions issue.  In particularly for Apache's tmp directory, as this buffers all but the smallest files during upload.  As you don't look to have explicitly set this in EPrints configuration.  It could be under /tmp/systemd-private-HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH-httpd.service-XXXXXX/tmp/ (this is where it is for RHEL and it various associated Linux OS).  For this path the Hs are a long hexadecimal number and the Xs are base-64 letters, (e.g. systemd-private-52165418fd404aeaa8b8b93816dcfd02-httpd.service-SxqmgN/tmp/).  It is worth checking to see if there are any files in this directory.  They will have randomly generated filenames (e.g. 0kM1yT2BIS).  However if you can generate an md5sums for these files and the newest file in this directory has a md5sum matching the file you have just tried to upload, then this confirms the files are uploading but there is some permissions issue stopping them being copied into place in the archive's documents directory.

Regards

David Newman

On 14/09/2025 5:40 am, jokoe soesilo wrote:
CAUTION: This e-mail originated outside the University of Southampton.
CAUTION: This e-mail originated outside the University of Southampton.
Hi Gunnar
when i grep -ri LimitRequestBody /etc/apache2 nothing find this configuration,then what i should to do 

On Sun, Sep 14, 2025 at 11:15 AM Gunnar Wolf <gwolf@gwolf.org> wrote:
CAUTION: This e-mail originated outside the University of Southampton.

CAUTION: This e-mail originated outside the University of Southampton.

jokoe soesilo dijo [Sun, Sep 14, 2025 at 10:43:58AM +0700]:
>Hi,
>where i can setting LimitRequetBody on Apache2 ubuntu server

Check the Apache2 configuration, it would typically be in
/etc/apache2/apache2.conf, but it's worth checking if it appears in any
other file in that directory. To that end, you can run:

     $ grep -ri LimitRequestBody /etc/apache2
*** Options: https://wiki.eprints.org/w/Eprints-tech_Mailing_List
*** Archive: https://www.eprints.org/tech.php/
*** EPrints community wiki: https://wiki.eprints.org/


*** Options: https://wiki.eprints.org/w/Eprints-tech_Mailing_List
*** Archive: https://www.eprints.org/tech.php/
*** EPrints community wiki: https://wiki.eprints.org/