Client Error - Compute Error

norm
norm
Joined: 9 Feb 05
Posts: 5
Credit: 288543
RAC: 0
Topic 191922

I've had two WU's crash in the last several days with the folowing error:

Quote:

_SSEgas.c
2006-10-07 22:03:57.7242 [CRITICAL]: At lowest level status code = 0, description: NO LAL ERROR REGISTERED

2006-10-07 22:03:57.7243 [CRITICAL]: APP DEBUG: Application caught signal 6.

2006-10-07 22:03:57.7243 [CRITICAL]: Stack trace of LAL functions in worker thread:
2006-10-07 22:03:57.7243 [CRITICAL]: TestLALDemod at line 80 of file /home/bema/einsteinathome/CFS/EaH_build_release_einstein_S5R1_4.17/extra_sources/lalapps-CVS/src/pulsar/FDS_isolated/CFSLALDemod_SSEgas.c
2006-10-07 22:03:57.7243 [CRITICAL]: At lowest level status code = 0, description: NO LAL ERROR REGISTERED

The above message is written to the error log over 100 times. See WU 15793803 & WU 15609125

Any ideas about what's causing this error?

I'm running an older version of Boinc (5.2.13). Do I need to upgrade?

Thanks,
Norm

Bernd Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4343
Credit: 252678742
RAC: 35578

Client Error - Compute Error

Apparently something on your machine keeps trying to terminate the App by sending it a signal 6 (SIGABRT). Might be the Core Client that thinks there's no other way to terminate the App, an upgrade might help, but I'm not fully sure.

BM

BM

norm
norm
Joined: 9 Feb 05
Posts: 5
Credit: 288543
RAC: 0

Two more WU's crashed before

Two more WU's crashed before I had the chance to upgrade to Boinc 5.4.9.

Since upgrading two have completed successfully. Hopefully that solved the problem.

Thanks for the reply.
Norm

Comment viewing options

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