infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-17719) Need check to detect when crontabs stop running
Date Wed, 20 Mar 2019 07:20:00 GMT

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

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

The issue is not about minotaur.

I happened to notice the error on minotaur, however it could happen on any host.

If a cronjob fails to run, there generally won't be an email; besides there could be an error
in email transmission (as happened with Whimsy lately).

i.e. passive monitoring won't detect such failures, there needs to be active monitoring, as
is done for other services.

It does not need to be done for every cronjob, but there are some that are more important
than others.

> Need check to detect when crontabs stop running
> -----------------------------------------------
>
>                 Key: INFRA-17719
>                 URL: https://issues.apache.org/jira/browse/INFRA-17719
>             Project: Infrastructure
>          Issue Type: Planned Work
>          Components: Infra Wishlist
>            Reporter: Sebb
>            Assignee: Chris Thistlethwaite
>            Priority: Major
>
> It looks like the minotaur crontabs have not been running for a few days.
> Some of these run vital services (e.g. setting up new mail archives) so there should
be a check to ensure that the jobs are running.
> If there is a log file that is updated when cronjobs are run, then its date could be
checked. There are no doubt other ways of checking.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message