You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2015/10/14 21:21:06 UTC

[jira] [Updated] (INFRA-9962) status.a.o does not monitor SVN replication

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

Sebb updated INFRA-9962:
------------------------
    Status: Waiting for Infra  (was: Closed)

It's trivial to check the current Last Changed Rev in SVN and the last changed date.

All one needs to do is to compare them, and if there is a large discrepancy, report an error. The code would need to allow for small differences in the revision number, but there should not be a large difference in the date.

This could be installed as a service on a host somewhere.

Similar checks can be done for svnpubsub; all the TLP sites (apart from httpd) have a .revision file which should agree with the source in SVN.

> status.a.o does not monitor SVN replication
> -------------------------------------------
>
>                 Key: INFRA-9962
>                 URL: https://issues.apache.org/jira/browse/INFRA-9962
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>            Reporter: Sebb
>            Assignee: Daniel Gruno
>
> It appears that status monitoring does not include svn replication.
> See my recent email to infra [1] - the US repo was 
> Last Changed Date: 2015-07-08 22:46:04 +0100 (Wed, 08 Jul 2015)
> and EU was
> Last Changed Date: 2015-07-07 17:46:07 +0100 (Tue, 07 Jul 2015)
> i.e. over a day out of date.
> Seems to me that this ought to have been picked up by monitoring.
> [I noticed it by purely by accident]
> [1]https://mail-search.apache.org/members/private-arch/infrastructure/201507.mbox/%3cCAOGo0VYRSaWs-3ax8H2jcmrO-p9S7_6cdCAz33tZiaV4+ymbqg@mail.gmail.com%3e



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