sleep can be interrupted by signals. Maybe your code (or some (C) library it uses) doesn't handle an incoming signal in a good way and the process ends that way?

Can you structure your process in a way that it can be easily restarted by a wrapping shell script or simply reimplement it as a cron job that is run every minute?

It seems to me that a signal would be possible only if the process would be expecting something, if we were in multithread. This is not the case. We wait 1 minute before checking new work to do. It a simple "polling". Yes it would be possible to wrap it in a main script, but I would like to understand.

Have you read the documentation link I provided?

May be interrupted if the process receives a signal such as SIGALRM .

So, if anything sends a signal to your process, such as SIGALRM, it might wake up or crash.

Good idea, but I do not know how to do that for a service ?

What if there is a log file error, Log module error, or disk full condition ?

Good idea, but the disk is not full and log4perl continues to work on another process...

In perldoc sleep, we read the following caveats:

May be interrupted if the process receives a signal such as "SIGALRM".

                   eval {
                       local $SIG{ALARM} = sub { die "Alarm!\n" };
                       sleep;
                   };
                   die $@ unless $@ eq "Alarm!\n";
[download]

You probably cannot mix "alarm" and "sleep" calls, because "sleep" is often implemented using "alarm."

Methinks that some or all of the foregoing will prove to have exceptional relevance to your present problem.   ...

In fact, I would wager that it consists of what has been described here:   “sleeps can be interrupted by a signal, and ‘un-caught signals’ generally mean ... (oopsie! hateitwhenthishappens!!) ... Death.”

However, not to be “snarky,” tell us more!   When your script runs into trouble, what does it do?   What does it log?   The more specific detail you can give, the more specifically we can help you ... and, after all, that’s why we’re all here.

Please see my answer above for alarms.
In fact I do not know what it does.
It is no more present, and I do not know how and why it stops. And I have displayed the log above. It starts sleep, then disappears without logging more...