You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by "Daniel Gruno (Jira)" <ji...@apache.org> on 2020/08/23 12:11:00 UTC
[jira] [Commented] (COMDEV-381) gunicorn failing on projects-vm3
[ https://issues.apache.org/jira/browse/COMDEV-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182674#comment-17182674 ]
Daniel Gruno commented on COMDEV-381:
-------------------------------------
It is due to internal NAT'ing that goes wrong in the DC it's in.
The fix is to modify /etc/hosts to point projects.apache.org at its internal LAN IP instead, which I have now done.
> gunicorn failing on projects-vm3
> --------------------------------
>
> Key: COMDEV-381
> URL: https://issues.apache.org/jira/browse/COMDEV-381
> Project: Community Development
> Issue Type: Bug
> Reporter: Sebb
> Priority: Major
>
> Since the move to vm3, gunicorn has not been running properly.
> I have fixed the restarting error, which was due to gunicorn not being on the path for the cron job.
> Gunicorn now starts, but fails almost immediately with:
> urllib.error.URLError: <urlopen error [Errno 111] Connection refused>
> This is invoked from:
> File "/var/www/reporter.apache.org/scripts/pdata.py", line 92, in <module>
> charters = loadJson(DESCRIPTIONS)
> File "/var/www/reporter.apache.org/scripts/pdata.py", line 84, in loadJson
> resp = uc.get(url, name=None, encoding='utf-8', errors=None)
> However I have been unable to determine why the request is failing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org