[
https://issues.apache.org/jira/browse/AIRAVATA-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eroma closed AIRAVATA-3363.
---------------------------
> mod_wsgi: Truncated or oversized response headers received from daemon process
> ------------------------------------------------------------------------------
>
> Key: AIRAVATA-3363
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3363
> Project: Airavata
> Issue Type: Bug
> Components: Django Portal
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Priority: Major
>
> mod_wsgi errors for the Django Portal when integrated with Custos:
> {code}
> [Tue Aug 11 18:59:24.552801 2020] [wsgi:error] [pid 8643] [client
> 68.51.122.242:51536] Timeout when reading response headers from daemon
> process 'aci.general.scigap.org':
> /var/www/portals/django-airavata-custos-integration/airavata-django-portal/django_airavata/wsgi.py,
> referer: https://aci.general.scigap.org/admin/users/
> ...
> [Tue Aug 11 19:03:29.714533 2020] [wsgi:error] [pid 7967] [client
> 68.51.122.242:52587] Truncated or oversized response headers received from
> daemon process 'aci.general.scigap.org':
> /var/www/portals/django-airavata-custos-integration/airavata-django-portal/django_airavata/wsgi.py,
> referer: https://aci.general.scigap.org/
> ...
> {code}
> Turns out the problem is probably related to running C extensions in some
> Python modules. Just a guess but it might be the grpc libraries since those
> are new with the Custos integration.
> https://serverfault.com/questions/844761/wsgi-truncated-or-oversized-response-headers-received-from-daemon-process/844786#844786
> The fix was to add
> {code}
> WSGIApplicationGroup %{GLOBAL}
> {code}
> to the virtual conf file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)