Errors

Original a few months back I tried to help out with the SETI project. I gave up and left after all my GPU tasks would immediately error.

I have come back again and it must be the combination of a new Boinc and new nvidia drivers because it is working pretty good. I am excited to be a part and help out with seti@home.

For the most part it is working good now. But I have I believe 7 errors right now in my task list. If anyone can look at these errors in my task list and help me it would be much appreciated. Five of the errors look like the same problem and the other two are each different.

The -12 error is found triplets twice, it is a fairly common error and shouldn't be much to worry about. The -5 error, can't open file, happens occasionally possibly because of the server problem with Bruno we are having right now. The rest of the errors were-177s, max time exceeded, that were probably the server thinking you should finish the tasks faster than it actually took. It takes the servers awhile to learn your machine and it makes mistakes at first. It looks like you are good to go now so welcome back and happy crunching.
____________


PROUD MEMBER OF Team Starfire World BOINC

Error -5 is an (Seti science) application error. Nothing to do with the project servers. "Can't open file" is usually caused by a file being locked by another program. Think about an anti-virus scanner locking client_state.xml due to scanning. Then BOINC can't write its state to it, thus ending in error -5.

Error -177 is a BOINC error. Also nothing to do with the project servers.
"Maximum elapsed time exceeded" can happen when the value of <rsc_fpops_est> on the running task is exceeded. BOINC will then stop the science application and give the task back to the project with error -177.

This can happen when the project doesn't allow for enough of a guestimate on the value of fpops that the task will take on this piece of hardware; when using optimized apps (not the case here), it can happen when the user adds a <flops> value to his app_info.xml file that's too small for his GPU.
____________
Jord

- BOINC FAQ Service
- BOINC User Wiki

Real is just a matter of perception.

Cool thanks guys it sounds like the -12 and -5 error are nothing to worry too much about. I only got one of each.

I guess I am more concerned with the -177 error that has happened five times. Its must be happening because one of my GPU stops crunching, but BOINC thinks it still is working. Then it either exceeds the maximum time and errors or I have to suspend and restart the task to get the GPU crunching again.

I really hope I can figure this out. It is discouraging getting errors and losing out on a lot of processing that could be getting done.

I'm sorry, I didn't notice you were running an AMD. Some of them have been known to do that. As far as I know, about the only thing you can do to cure this is use Lunatic's optimized app. You can find more information on it in the numbers crunching forum. Do know though, if you decide to install it you must keep up with the forums for updates to it. Lunatic's are always improving it but you have to install any updates yourself. It may also cause the temperature to rise some so keep an eye out for that too.
____________


PROUD MEMBER OF Team Starfire World BOINC

Thank you for the info. Yeah I think I might go buy a 2600K, 1155 board, and some DDR3. I want to run Intel so I can stop using SLIPatch on this AMD. I'm quite positive a processor upgrade would be really nice too.

On this same subject, the last 5 Astropulse tasks I've gotten have errored, the most recent one after only around 6 hours. Over Christmas break my laptop got through at least 3 Astropulse tasks, then it started erroring, and so far my laptop has errored on 3 (including one today) and my desktop computer has errored at least 2 (maybe 3). What is going on? As far as I know, none of the normal tasks I've gotten have errored.

"boinc_graphics_make_shmem failed"
maybe you use the screensaver? (set it to (none))


____________



- ALF - "Find out what you don't do well ..... then don't do it!" :)