Hi all. I keep getting the above message and the current project resets and starts again. What might be the cause and how can I actually produce some finished work?

Hope you can help.

Doug.

Hi all. I keep getting the above message and the current project resets and starts again. What might be the cause and how can I actually produce some finished work?

Hope you can help.

Doug.

The first step would be to unhide your Mac so that we can take a look at the error output. You can do this by going to Your Account>Seti@Home Preferences on this web site. As asn example of what might be visible to other users, you can click on my name to see my computer info.

Also since you use a Mac you might get a better response in the Mac forum

From the Boinc FAQ Service...
Here is what Error 154 might be...

ERR_FCNTL -154

BOINC wasn't able to get a file's attributes. In general this has to do with socket-connections.

Applies only to non-Windows-systems or versions of Windows without WINSOCK-functionality.

---

Hi all. I keep getting the above message and the current project resets and starts again. What might be the cause and how can I actually produce some finished work?

Hope you can help.

Doug.

The first step would be to unhide your Mac so that we can take a look at the error output. You can do this by going to Your Account>Seti@Home Preferences on this web site. As asn example of what might be visible to other users, you can click on my name to see my computer info.

Also since you use a Mac you might get a better response in the Mac forum

From the Boinc FAQ Service...
Here is what Error 154 might be...

ERR_FCNTL -154

BOINC wasn't able to get a file's attributes. In general this has to do with socket-connections.

Applies only to non-Windows-systems or versions of Windows without WINSOCK-functionality.

Thanks for that, I did not realise there was a Mac forum (!) but now, of course, I know.
Will unhide my Mac and thanks for the feedback. Hope it helps, since I'm not contributing much at the minute.

I keep getting similar errors and I am running i686 and amd64 arch. messages logs across 10 servers, 2 of which are amd64 arch show errors like this cut from a log but of course with different process numbers:


2007-07-08 14:17:55 [SETI@home] Restarting task 03mr00aa.283.26096.453402.3.232_2 using setiathome_enhanced version 512
2007-07-08 14:17:56 [---] [error] Process 12789 not found
2007-07-08 14:20:49 [---] Restarting 11jn00aa.26574.13665.909646.3.50_2 - message timeout

this repeats about every 2 to 3 minutes. i find that production across all machines is severely affected.

this only began within the past month or two. could it be from a bad upgrade version?

both arch are running boinc 5.8.15. i have tried reinstalling, even fresh installs but it still happens.

---

I keep getting similar errors and I am running i686 and amd64 arch. messages logs across 10 servers, 2 of which are amd64 arch show errors like this cut from a log but of course with different process numbers:


2007-07-08 14:17:55 [SETI@home] Restarting task 03mr00aa.283.26096.453402.3.232_2 using setiathome_enhanced version 512
2007-07-08 14:17:56 [---] [error] Process 12789 not found
2007-07-08 14:20:49 [---] Restarting 11jn00aa.26574.13665.909646.3.50_2 - message timeout

this repeats about every 2 to 3 minutes. i find that production across all machines is severely affected.

this only began within the past month or two. could it be from a bad upgrade version?

both arch are running boinc 5.8.15. i have tried reinstalling, even fresh installs but it still happens.

There is a fix for at least one cause of this on windows machines that has been checked into the source. I have no idea when it will appear in a production version.

---

BOINC WIKI

I keep getting similar errors and I am running i686 and amd64 arch. messages logs across 10 servers, 2 of which are amd64 arch show errors like this cut from a log but of course with different process numbers:


2007-07-08 14:17:55 [SETI@home] Restarting task 03mr00aa.283.26096.453402.3.232_2 using setiathome_enhanced version 512
2007-07-08 14:17:56 [---] [error] Process 12789 not found
2007-07-08 14:20:49 [---] Restarting 11jn00aa.26574.13665.909646.3.50_2 - message timeout

this repeats about every 2 to 3 minutes. i find that production across all machines is severely affected.

this only began within the past month or two. could it be from a bad upgrade version?

both arch are running boinc 5.8.15. i have tried reinstalling, even fresh installs but it still happens.

There is a fix for at least one cause of this on windows machines that has been checked into the source. I have no idea when it will appear in a production version.

everything i run is linux. is there still some fix available?

---

I keep getting similar errors and I am running i686 and amd64 arch. messages logs across 10 servers, 2 of which are amd64 arch show errors like this cut from a log but of course with different process numbers:


2007-07-08 14:17:55 [SETI@home] Restarting task 03mr00aa.283.26096.453402.3.232_2 using setiathome_enhanced version 512
2007-07-08 14:17:56 [---] [error] Process 12789 not found
2007-07-08 14:20:49 [---] Restarting 11jn00aa.26574.13665.909646.3.50_2 - message timeout

this repeats about every 2 to 3 minutes. i find that production across all machines is severely affected.

this only began within the past month or two. could it be from a bad upgrade version?

both arch are running boinc 5.8.15. i have tried reinstalling, even fresh installs but it still happens.

There is a fix for at least one cause of this on windows machines that has been checked into the source. I have no idea when it will appear in a production version.

everything i run is linux. is there still some fix available?

it appears downgrading from 5.8.15 to 5.4.11 cured the problem on all servers. i will remain with this version until i discover this problem is fixed.

---

I keep getting similar errors and I am running i686 and amd64 arch. messages logs across 10 servers, 2 of which are amd64 arch show errors like this cut from a log but of course with different process numbers:


2007-07-08 14:17:55 [SETI@home] Restarting task 03mr00aa.283.26096.453402.3.232_2 using setiathome_enhanced version 512
2007-07-08 14:17:56 [---] [error] Process 12789 not found
2007-07-08 14:20:49 [---] Restarting 11jn00aa.26574.13665.909646.3.50_2 - message timeout

this repeats about every 2 to 3 minutes. i find that production across all machines is severely affected.

this only began within the past month or two. could it be from a bad upgrade version?

both arch are running boinc 5.8.15. i have tried reinstalling, even fresh installs but it still happens.

There is a fix for at least one cause of this on windows machines that has been checked into the source. I have no idea when it will appear in a production version.

everything i run is linux. is there still some fix available?

Not for *nix, no. The same bit of code may be the culprit, but I cannot tell as my *nix programming is a bit on the weak (last time I programmed unix was more than 2 decades ago).

---

BOINC WIKI

I keep getting similar errors and I am running i686 and amd64 arch. messages logs across 10 servers, 2 of which are amd64 arch show errors like this cut from a log but of course with different process numbers:


2007-07-08 14:17:55 [SETI@home] Restarting task 03mr00aa.283.26096.453402.3.232_2 using setiathome_enhanced version 512
2007-07-08 14:17:56 [---] [error] Process 12789 not found
2007-07-08 14:20:49 [---] Restarting 11jn00aa.26574.13665.909646.3.50_2 - message timeout

this repeats about every 2 to 3 minutes. i find that production across all machines is severely affected.

this only began within the past month or two. could it be from a bad upgrade version?

both arch are running boinc 5.8.15. i have tried reinstalling, even fresh installs but it still happens.

There is a fix for at least one cause of this on windows machines that has been checked into the source. I have no idea when it will appear in a production version.

everything i run is linux. is there still some fix available?

Not for *nix, no. The same bit of code may be the culprit, but I cannot tell as my *nix programming is a bit on the weak (last time I programmed unix was more than 2 decades ago).

no prob. since they know of the bug, and i have a workable older version running, i'll just wait for the fix to come down the line.

---