You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Geoffrey Corey (JIRA)" <ji...@apache.org> on 2016/03/10 17:46:40 UTC

[jira] [Closed] (INFRA-9642) Monitor git:// on git.apache.org

     [ https://issues.apache.org/jira/browse/INFRA-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey Corey closed INFRA-9642.
---------------------------------
    Resolution: Fixed

There is at least a self monitoring script for the git daemon on git.a.o that will restart the daemon and clear out stale connections if there is an error in git interactions over git://

> Monitor git:// on git.apache.org
> --------------------------------
>
>                 Key: INFRA-9642
>                 URL: https://issues.apache.org/jira/browse/INFRA-9642
>             Project: Infrastructure
>          Issue Type: Planned Work
>      Security Level: public(Regular issues) 
>            Reporter: Geoffrey Corey
>            Assignee: Geoffrey Corey
>            Priority: Minor
>
> It seems that after a while, using the git:// protocol on git.apache.org is unusable.
> 2 things:
> 1. Create a monitoring check for git:// on git.apache.org
> 2. Figure out how to clear out the stale git-daemon processes (sending them a SIGHUP seems to help) to keep the service up.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)