Open link in a new tab

Content

Expand project menu

Work Package attachment upload fails (RESOLVED)

Trying to upload attachments to a work package. Smaller files work fine, but files over 8MB failing.

From /var/log/httpd/error_log
[Fri Feb 24 11:21:08.072851 2017] [proxy:error] [pid 13451] (104)Connection reset by peer: [client 206.180.45.25:15004] AH01084: pass request body failed to 127.0.0.1:6000 (127.0.0.1), referer: https://project.rentsys.com/projects/new-product-development/work_packages/445/activity
[Fri Feb 24 11:21:08.073030 2017] [proxy_http:error] [pid 13451] [client 206.180.45.25:15004] AH01097: pass request body failed to 127.0.0.1:6000 (127.0.0.1) from 206.180.45.25 (), referer: https://project.rentsys.com/projects/new-product-development/work_packages/445/activity

Message actions

Hi John,

this sounds like an issue with your KeepAliveTimeout configuration of Apache due to the way it fails after a specific content length is exceeded.

Please see https://httpd.apache.org/docs/2.4/en/mod/core.html#keepalivetimeout for more information.

Best,
Oliver

Message actions

Already tried that. I did find this in messages log

openproject-web-1.service: E, [2017-02-27T09:21:37.700210 SAAS-7] ERROR — : worker=0 PID:12631 timeout (16s > 15s), killing
openproject-web-1.service: E, [2017-02-27T09:21:37.752442 SAAS-7] ERROR — : reaped #<Process::Status: pid 12631 SIGKILL (signal 9)> worker=0
openproject-web-1.service: I, [2017-02-27T09:21:37.814538 #12729] INFO — : worker=0 ready

Openproject-web-1 service is apparently killing the upload process after 15 seconds.
Where is the setting to make it stop doing that?

Message actions

Turns out this tracks back to /opt/openproject/config/unicorn.rb

timeout Integer(ENV['WEB_TIMEOUT'] || 300)

I commented this line out and replaced with
timeout Integer(300)

This solves my problem, however I would rather set the environment variable correctly.
Where do I do this?

Message actions

Never mind.

openproject config:set WEB_TIMEOUT=300

Message actions

Hi John,

great to hear you found it out yourself until I could check back. Yes, that was the other server that could have timed out. Did not think about that.

Best,
Oliver