signal 27 stopping a workunit - jiffie problem?

knarf
knarf
Joined: 11 Mar 05
Posts: 4
Credit: 1389706
RAC: 0
Topic 190719

Hi,

sometimes I get the following output on stderr:

process got signal 27

e.g. see http://einsteinathome.org/task/17007257

According to signal.h that is SIGPROF and can be delivered at a overflow of the jiffies. This actually happens every ~5 days on an alpha and the client errors also happenon that scale. Could it be, that the code cannot handle an overflowing jiffie counter?

Frank

Michael Karlinsky
Michael Karlinsky
Joined: 22 Jan 05
Posts: 888
Credit: 23502182
RAC: 0

signal 27 stopping a workunit - jiffie problem?

Quote:

Hi,

sometimes I get the following output on stderr:

process got signal 27

e.g. see http://einsteinathome.org/task/17007257

According to signal.h that is SIGPROF and can be delivered at a overflow of the jiffies. This actually happens every ~5 days on an alpha and the client errors also happenon that scale. Could it be, that the code cannot handle an overflowing jiffie counter?

Frank

From 'man setitimer':

ITIMER_PROF
Decrements both in process virtual time and when the
system is running on behalf of the process. It is
designed to be used by interpreters in statistically
profiling the execution of interpreted programs. Each
time the ITIMER_PROF timer expires, the SIGPROF signal
is delivered. Because this signal may interrupt in-
progress functions, programs using this timer must be
prepared to restart interrupted functions.

The default action is to terminate the process if it receives SIGPROF. So
you need to install a signal handler to avoid this. But it might be used
by Albert/BOINC API to determine an error condition. Who knows?

Michael

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.