Project

General

Profile

Bug #11515

AWS probe time lock too strict

Added by Kevin Retzke about 3 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Start date:
01/27/2016
Due date:
% Done:

0%

Estimated time:
Duration:

Description

01:00:01 CST Gratia: ERROR: probe was run less than one hour ago, please wait 2 s

The probe checks if it previously ran within the last 3599 seconds, and refuses to start if so.
Cron jobs aren't guaranteed to start up at exactly the time requested, there needs to be some margin.

One minute is probably reasonable.

History

#1 Updated by Kevin Retzke about 3 years ago

  • Status changed from New to Resolved

Set check to 3540s.

probes|00549116

#2 Updated by Joe Boyd about 1 year ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF