I am now getting another type of unrecoverable error as well as the original- both lead to client errors on the WU. The second error is: Unrecoverable error for result H1_1319.4__1319.9_0.1_T29_Test02_0 (One or more arguments are invalid (0x80000003) - exit code -2147483645 (0x80000003). Any ideas or should I just give up?
Nope. resetting the project didnt work. Here are the errors again:
4/5/2005 10:05:12 PM|Einstein@Home|Starting result H1_0858.9__0859.0_0.1_T23_Test02_3 using einstein version 4.79
4/5/2005 10:05:13 PM|Einstein@Home|Unrecoverable error for result H1_0858.9__0859.0_0.1_T23_Test02_3 (There are no child processes to wait for. (0x80) - exit code 128 (0x80))
I was originally, after installing bionic, getting a message that a problem occured that would prevent graphiics from displaying. i was under the impression, from what i read on the instructions, that if the program was installed in shared mode and not single user mode that this would occur. since i installed it in shared mode i figured this would be ok. does the E@H program even NEED to display graphics to run results or could this be the reason why this wont run? Beyond that i am at a loss as to what could explan this. not really knowing how the program is supposed to process and what it needs to do so i dont know what else to offer up as possible explainations. What services need to be running on my machine to make the program work? i have also turned quite a few services off on my server for security reasons and maybe one was turned off that E@H requires? BTW, resetting the project also did not help.
> I am now getting another type of unrecoverable error as well as the original-
> both lead to client errors on the WU. The second error is: Unrecoverable error
> for result H1_1319.4__1319.9_0.1_T29_Test02_0 (One or more arguments are
> invalid (0x80000003) - exit code -2147483645 (0x80000003). Any ideas or should
> I just give up?
Sounds bad. The exit code is quite unusual. Which client are you using? Maybe try an other version.
> > I am now getting another type of unrecoverable error as well as the
> original-
> > both lead to client errors on the WU. The second error is: Unrecoverable
> error
> > for result H1_1319.4__1319.9_0.1_T29_Test02_0 (One or more arguments are
> > invalid (0x80000003) - exit code -2147483645 (0x80000003). Any ideas or
> should
> > I just give up?
>
> Sounds bad. The exit code is quite unusual. Which client are you using? Maybe
> try an other version.
I never fully completed a E@H WU with boinc 4.25. I have gone back to 4.19 and everything is fine now. Seti and Predictor ran fine under 4.25 though E@H kept chucking everything out with errors.
OK, i have done the following to try to remedy this based on the suggestions i saw here plus some other steps i firgured might make a difference. I tried Bionic v4.19 but it also generated errors. reinstalled bionic 4.25 in shared user mode, not service mode as i had before (slight mistake when i said before it was shared user mode, i was wrong), still the same issue. Looks like maybe something on the E@H end with the client and maybe not the WU's. S@H seems to not care which version i use as it runs fine in all versions. guess for now unless someone else has any other ideas i can try i will simply not run E@H... 8-(
sorry for the delay, I have been trying to find another solution behind the scenes for people like you. The only advice I can give you right now is to suspend E@H for a few days until the rest of the current search has been performed. The 0859 WUs trigger a bug in our App that causes the client error, and due to various reasons whe haven't been able to fix it before the whole pool will consist of such WUs. It's purely our fault, not yours.
> Brian A,
>
> sorry for the delay, I have been trying to find another solution behind the
> scenes for people like you. The only advice I can give you right now is to
> suspend E@H for a few days until the rest of the current search has been
> performed. The 0859 WUs trigger a bug in our App that causes the client error,
> and due to various reasons whe haven't been able to fix it before the whole
> pool will consist of such WUs. It's purely our fault, not yours.
>
> BM
>
Kewl, thanks for the heads up. glad to know it wasnt just me going crazy. ;-)
If there is anything on my end you need to fix this, any info i can provide, let me know. i do tech support for a living and would be willing to help out in any way needed...
Thank you, but we actually understand the problem very well, we just ran out of time to fix it. Bruce will cancel these WUs asap so that they don't cause any more confusion.
> Thank you, but we actually understand the problem very well, we just ran out
> of time to fix it. Bruce will cancel these WUs asap so that they don't cause
> any more confusion.
>
> BM
>
Did the WU's ever get removed? i have tried over the last several days to see if E@H will work but still getting the same errors. Dont know what has changed but i am also now getting an application error popup when the app tries to process the WU. it gives the error as an application failure for E@H v4.79 if i look in event manager. I wasnt getting this popup before...
Resetting the project didn't
)
Resetting the project didn't fix it for me. Any other suggestions?
I am now getting another type
)
I am now getting another type of unrecoverable error as well as the original- both lead to client errors on the WU. The second error is: Unrecoverable error for result H1_1319.4__1319.9_0.1_T29_Test02_0 (One or more arguments are invalid (0x80000003) - exit code -2147483645 (0x80000003). Any ideas or should I just give up?
Nope. resetting the project
)
Nope. resetting the project didnt work. Here are the errors again:
4/5/2005 10:05:12 PM|Einstein@Home|Starting result H1_0858.9__0859.0_0.1_T23_Test02_3 using einstein version 4.79
4/5/2005 10:05:13 PM|Einstein@Home|Unrecoverable error for result H1_0858.9__0859.0_0.1_T23_Test02_3 (There are no child processes to wait for. (0x80) - exit code 128 (0x80))
I was originally, after installing bionic, getting a message that a problem occured that would prevent graphiics from displaying. i was under the impression, from what i read on the instructions, that if the program was installed in shared mode and not single user mode that this would occur. since i installed it in shared mode i figured this would be ok. does the E@H program even NEED to display graphics to run results or could this be the reason why this wont run? Beyond that i am at a loss as to what could explan this. not really knowing how the program is supposed to process and what it needs to do so i dont know what else to offer up as possible explainations. What services need to be running on my machine to make the program work? i have also turned quite a few services off on my server for security reasons and maybe one was turned off that E@H requires? BTW, resetting the project also did not help.
> I am now getting another
)
> I am now getting another type of unrecoverable error as well as the original-
> both lead to client errors on the WU. The second error is: Unrecoverable error
> for result H1_1319.4__1319.9_0.1_T29_Test02_0 (One or more arguments are
> invalid (0x80000003) - exit code -2147483645 (0x80000003). Any ideas or should
> I just give up?
Sounds bad. The exit code is quite unusual. Which client are you using? Maybe try an other version.
BM
BM
> > I am now getting another
)
> > I am now getting another type of unrecoverable error as well as the
> original-
> > both lead to client errors on the WU. The second error is: Unrecoverable
> error
> > for result H1_1319.4__1319.9_0.1_T29_Test02_0 (One or more arguments are
> > invalid (0x80000003) - exit code -2147483645 (0x80000003). Any ideas or
> should
> > I just give up?
>
> Sounds bad. The exit code is quite unusual. Which client are you using? Maybe
> try an other version.
I never fully completed a E@H WU with boinc 4.25. I have gone back to 4.19 and everything is fine now. Seti and Predictor ran fine under 4.25 though E@H kept chucking everything out with errors.
OK, i have done the following
)
OK, i have done the following to try to remedy this based on the suggestions i saw here plus some other steps i firgured might make a difference. I tried Bionic v4.19 but it also generated errors. reinstalled bionic 4.25 in shared user mode, not service mode as i had before (slight mistake when i said before it was shared user mode, i was wrong), still the same issue. Looks like maybe something on the E@H end with the client and maybe not the WU's. S@H seems to not care which version i use as it runs fine in all versions. guess for now unless someone else has any other ideas i can try i will simply not run E@H... 8-(
Brian A, sorry for the
)
Brian A,
sorry for the delay, I have been trying to find another solution behind the scenes for people like you. The only advice I can give you right now is to suspend E@H for a few days until the rest of the current search has been performed. The 0859 WUs trigger a bug in our App that causes the client error, and due to various reasons whe haven't been able to fix it before the whole pool will consist of such WUs. It's purely our fault, not yours.
BM
BM
> Brian A, > > sorry for the
)
> Brian A,
>
> sorry for the delay, I have been trying to find another solution behind the
> scenes for people like you. The only advice I can give you right now is to
> suspend E@H for a few days until the rest of the current search has been
> performed. The 0859 WUs trigger a bug in our App that causes the client error,
> and due to various reasons whe haven't been able to fix it before the whole
> pool will consist of such WUs. It's purely our fault, not yours.
>
> BM
>
Kewl, thanks for the heads up. glad to know it wasnt just me going crazy. ;-)
If there is anything on my end you need to fix this, any info i can provide, let me know. i do tech support for a living and would be willing to help out in any way needed...
Thank you, but we actually
)
Thank you, but we actually understand the problem very well, we just ran out of time to fix it. Bruce will cancel these WUs asap so that they don't cause any more confusion.
BM
BM
> Thank you, but we actually
)
> Thank you, but we actually understand the problem very well, we just ran out
> of time to fix it. Bruce will cancel these WUs asap so that they don't cause
> any more confusion.
>
> BM
>
Did the WU's ever get removed? i have tried over the last several days to see if E@H will work but still getting the same errors. Dont know what has changed but i am also now getting an application error popup when the app tries to process the WU. it gives the error as an application failure for E@H v4.79 if i look in event manager. I wasnt getting this popup before...