Unrecoverable error code 99 (0x63)
28 Feb 2005 14:42:45 UTC
Topic 188131
(moderation:
Hi
I've got errors doing Einstein@home workunits.
It lasts for about 5 days on my 2 machines.
2005-02-28 03:12:33|Einstein@Home|Unrecoverable error for result H1_0103.4__0103.6_0.1_T29_Test02_0 ( - exit code 99 (0x63))
That's record from Celeron processor:
4.56
- exit code 99 (0x63)
Required user-variable `IFO` has not been specified!
Level 0: $Id: ComputeFStatistic.c,v 1.232 2005/02/11 17:03:16 ballen Exp $
Function call `LALUserVarReadAllInput(stat,argc,argv)' failed.
file ComputeFStatistic.c, line 436
Level 1: $Id: UserInput.c,v 1.21 2004/11/29 18:38:59 reinhard Exp $
Status code -1: Recursive error
function LALUserVarReadAllInput, file UserInput.c, line 701
Level 2: $Id: UserInput.c,v 1.21 2004/11/29 18:38:59 reinhard Exp $
Status code 8: Required user-variable was not set
function LALUserVarCheckRequired, file UserInput.c, line 758
BOINC_ERR_EXIT: now calling boinc_finish()
And that from AMD:
4.56
- exit code 99 (0x63)
Required user-variable `IFO` has not been specified!
Level 0: $Id: ComputeFStatistic.c,v 1.232 2005/02/11 17:03:16 ballen Exp $
Function call `LALUserVarReadAllInput(stat,argc,argv)' failed.
file ComputeFStatistic.c, line 436
Level 1: $Id: UserInput.c,v 1.21 2004/11/29 18:38:59 reinhard Exp $
Status code -1: Recursive error
function LALUserVarReadAllInput, file UserInput.c, line 701
Level 2: $Id: UserInput.c,v 1.21 2004/11/29 18:38:59 reinhard Exp $
Status code 8: Required user-variable was not set
function LALUserVarCheckRequired, file UserInput.c, line 758
BOINC_ERR_EXIT: now calling boinc_finish()
It looks like Boinc 4.56 Core is causing those errors , but there were no such errors earlier on that client.
I participate in more projects and there were no errors there. It's with Einstein's only.
Application version 4,79
First 7 workunits were crunched correctly with this version.
Regards
rudylis
Unrecoverable error code 99 (0x63)
)
Problem solved , by upgrading to Boinc 4.66
There is a bug in E@H client in my opinion , because
- only that client is causing errors
- there were no problems with Boinc 4.56 version earlier.
- what has E@H client to boinc core client ? :)
Thats my thoughts only
regards
rudylis
> Problem solved , by
)
> Problem solved , by upgrading to Boinc 4.66
> There is a bug in E@H client in my opinion , because
> - only that client is causing errors
> - there were no problems with Boinc 4.56 version earlier.
> - what has E@H client to boinc core client ? :)
>
>
> Thats my thoughts only
The BOINC 4.56 client had at least two errors which affected E@H badly. They had less effect on other projects because the other projects don't have long command lines, and the other projects don't re-use data files.
Cheers,
Bruce
Director, Einstein@Home
> The BOINC 4.56 client had
)
> The BOINC 4.56 client had at least two errors which affected E@H badly. They
> had less effect on other projects because the other projects don't have long
> command lines, and the other projects don't re-use data files.
>
> Cheers,
> Bruce
>
Thanks for explanation
I'm always interested in reasons of faults
rudylis