Hi Terry,
I have assumed the system time is always UTC synchronised using chronyd. The
servers user code is running under the GMT timezone. I was wondering if the
tweaking of the time by chronyd could cause this issue, but I would have
thought this situation would have been handled by crond if this could happen
and I have seen this issue about 4 times in a year, so it is not a totally
sporadic event.
grep-ing my /var/log/messages brings up entries like
Apr 5 08:16:43 localhost chronyd[900]: System clock wrong by 1.516625 seconds,
adjustment started
Apr 5 08:16:43 localhost chronyd[900]: System clock was stepped by 1.516625
seconds
Maybe you have some similar adjustements or bigger on the system?
One second off hitting exactly the moment your crontab scripts start could be
an explanation to 'double starts', although it seems rather improbable to have
that happen that often.
If you still have some logs around from the last time it happened, maybe you
can check if there is a connection between such adjustemnts and the
double-starters.
Otherwise, checking if such adjustements are happening often per day or just
once in weeks might be a next step to do in order to track down the issue.
Best regards,
Iosif
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
