I found a strange error with my jails (ezjails) producing double status emails.
The apparent error is similar to the one mentioned here.
As I investigated further I found out that "sometimes" the ezjail runs the cronjob twice - so creating a race condition with two save-entropy jobs trying to move and alter the files concurrently. Or sending out a status email twice...
/etc/crontab looks normal, so no double entries or so.
/var/log/cron shows the duplicate starts of the jobs.
What can cause such a behaviour? As cron is triggered via timestamps, could it be possible that under high load (define high here) time is "too slow"?
The apparent error is similar to the one mentioned here.
As I investigated further I found out that "sometimes" the ezjail runs the cronjob twice - so creating a race condition with two save-entropy jobs trying to move and alter the files concurrently. Or sending out a status email twice...
/etc/crontab looks normal, so no double entries or so.
/var/log/cron shows the duplicate starts of the jobs.
What can cause such a behaviour? As cron is triggered via timestamps, could it be possible that under high load (define high here) time is "too slow"?