Questions and Answers :
Macintosh :
computational error
Message board moderation
Author | Message |
---|---|
Rastaman Send message Joined: 7 Oct 00 Posts: 5 Credit: 1,480,686 RAC: 0 |
Since several days ago this happen: lun 25 jun 17:34:26 2007|SETI@home|[file_xfer] Started download of file 13ap99aa.11495.4208.97162.3.159 lun 25 jun 17:34:34 2007|SETI@home|[file_xfer] Finished download of file 13ap99aa.11495.4208.97162.3.159 lun 25 jun 17:34:34 2007|SETI@home|[file_xfer] Throughput 55461 bytes/sec lun 25 jun 17:34:35 2007|SETI@home|Starting 13ap99aa.11495.4208.97162.3.159_0 lun 25 jun 17:34:35 2007|SETI@home|Starting task 13ap99aa.11495.4208.97162.3.159_0 using setiathome_enhanced version 518 lun 25 jun 17:34:47 2007|SETI@home|Deferring communication for 1 min 0 sec lun 25 jun 17:34:47 2007|SETI@home|Reason: Unrecoverable error for result 13ap99aa.11495.4208.97162.3.159_0 (process exited with code 131 (0x83, -125)) lun 25 jun 17:34:47 2007|SETI@home|Computation for task 13ap99aa.11495.4208.97162.3.159_0 finished Anyone can say me what is this and what i can do to fix? B&W G3 MacOS X 10.4.9 1Gb RAM 1.1 Ghz (Processor Upgrade) BOINC 5.10.7 |
Dotsch Send message Joined: 9 Jun 99 Posts: 2422 Credit: 919,393 RAC: 0 |
All results from this system fail. It could be, that this is a hardware problem (CPU, Memory, Cache). Could you please let a hardware diagnostic tool running to verify, if everything is OK with your system. Could you please stop the BOINC client on the affected system, till the problem is solved. |
Guy LOEBL Send message Joined: 29 Mar 00 Posts: 2 Credit: 3,592,586 RAC: 13 |
Hi Folks. I'm experiencing excatly the same problems. OK to stop the BOINC client, but how will we know the problem is fixed? Hear you soon. |
Jeffrey Send message Joined: 21 Nov 03 Posts: 4793 Credit: 26,029 RAC: 0 |
computational error 5.10.7 did me in... All was fine 'til the upgrade, so this is not a hardware problem... I noticed it is no longer the recommended client for windows machines... I'm going back to 5.8.17, for now... ;) It may not be 1984 but George Orwell sure did see the future . . . |
Jeffrey Send message Joined: 21 Nov 03 Posts: 4793 Credit: 26,029 RAC: 0 |
I'm going back to 5.8.17, for now... After completely removing the new and reverting back to the old, still no dice... hmmm... ;) It may not be 1984 but George Orwell sure did see the future . . . |
Pat McGee Send message Joined: 22 Oct 00 Posts: 6 Credit: 120,423 RAC: 0 |
I'm running S@H on two different Macs, both with G3 processors. Both stopped generating good results sometime in the past several days. At about the same time, I upgraded both systems from 10.4.9 to 10.4.10. I suspect, but can't prove that the OS upgrade killed the S@H client. I hope to have some free time soon so I can downgrade one of the machines back to 10.4.9 and see if that fixes things. Or, maybe something else I did broke both of them. I can't think of anything else I changed in common, though - I use them for very different tasks. On one system, I get error code 131. On the other, that part of the log message is clipped off and I can't read it. I haven't changed versions of BOINC or S@H in a while - probably at least 3-4 months, but I'm not really sure. I run the menu bar client on one, the full client on the other. Maybe what this is telling me is that I should upgrade my hardware. Somehow I doubt that it's worth anyone's time to debug this problem if it affects only G3 processors - they're too slow to contribute too much, and there probably aren't all that many left anyway. Pat |
Jeffrey Send message Joined: 21 Nov 03 Posts: 4793 Credit: 26,029 RAC: 0 |
At about the same time, I upgraded both systems from 10.4.9 to 10.4.10. I suspect, but can't prove that the OS upgrade killed the S@H client. I can prove that it didn't... I don't use Tiger on my crunchin machine... ;) It may not be 1984 but George Orwell sure did see the future . . . |
Jeffrey Send message Joined: 21 Nov 03 Posts: 4793 Credit: 26,029 RAC: 0 |
Well, I've tried 5.10.7 and 5.8.17 and even 5.4.9, they all give me computation error code 131... Methinks that it's the new seti app 5.18, so I'm dead in the waters of lake ET... ;) It may not be 1984 but George Orwell sure did see the future . . . |
Gill's Send message Joined: 2 Aug 05 Posts: 2 Credit: 1,000,619 RAC: 0 |
I am having the same problem, "the process exited with code 131 (0x83, -125))" error! Boinc itself is not crashing, just Seti@Home. This has been happening for the past several days. My other projects are returning good results. This appears a mac specific issue, because my windows pc is working fine for Seti. If a solution cannot be found, I guess I will detach from this project! I have contributed over 10,000 work units to this project with my G3. Maybe Seti@Home doesn't need our help anymore. There are other Projects. |
Dotsch Send message Joined: 9 Jun 99 Posts: 2422 Credit: 919,393 RAC: 0 |
If a solution cannot be found, I guess I will detach from this project! I have contributed over 10,000 work units to this project with my G3. Maybe Seti@Home doesn't need our help anymore. There are other Projects. Please be patitent. This is looks a application problem. The error output of the failed results on all Macs look very simliar. So it could be, that this is a application problem, but I am not shure. I will forward this problem to the SETI devs. |
Dotsch Send message Joined: 9 Jun 99 Posts: 2422 Credit: 919,393 RAC: 0 |
Well, I've tried 5.10.7 and 5.8.17 and even 5.4.9, they all give me computation error code 131... I think, that this is not a BOINC related problem. |
C Send message Joined: 3 Apr 99 Posts: 240 Credit: 7,716,977 RAC: 0 |
Since several days ago this happen: Two suggestions: Boot the computer from your CD-ROM boot disk and repair disk permissions using the Disk Utility App on the CD; and try running Alex Kan's optimized SETI client - available here: http://setiathome.berkeley.edu/forum_thread.php?id=31810 Just scroll to the bottom, then begin scrolling back up until you find the appropriate version. No guarantees, but it might work, and if it does, it runs twice as fast as the standard client. C Join Team MacNN |
Jeffrey Send message Joined: 21 Nov 03 Posts: 4793 Credit: 26,029 RAC: 0 |
Boot the computer from your CD-ROM boot disk and repair disk permissions using the Disk Utility App on the CD 1st thing I tried... This only repairs 'system related' permissions anyway... ;) It may not be 1984 but George Orwell sure did see the future . . . |
Paul Cripe Send message Joined: 19 Jan 04 Posts: 1 Credit: 1,700,765 RAC: 0 |
I have same problem. Installed OS update 10.4.10 yesterday AM. Since then noted all comps taking 16-17 seconds with computational error. Suspended SETI comp until problem resolved. |
Dotsch Send message Joined: 9 Jun 99 Posts: 2422 Credit: 919,393 RAC: 0 |
The SETI develeopers are woring on the problem. Eric has written that is it a G3 issue. Edit : It is better to suspend SETI at the PPC G3 systems, if your system is affected from this problem. |
Ian Wilson Send message Joined: 23 Jun 99 Posts: 1 Credit: 84,060 RAC: 0 |
Hi - I have the same kind of issue, example below. I'm using a G3 Pismo Powerbook running 10.3.9 Look forward to some sort of a fix - this has been going on for a few days now so I'll disable Boinc until there is a fix Ian Fri Jun 29 09:53:42 2007|SETI@home|[file_xfer] Started download of file 24no99aa.27926.17377.229830.3.200 Fri Jun 29 09:53:46 2007|SETI@home|[file_xfer] Finished download of file 24no99aa.27926.17377.229830.3.200 Fri Jun 29 09:53:46 2007|SETI@home|[file_xfer] Throughput 93698 bytes/sec Fri Jun 29 09:53:47 2007|SETI@home|Starting 24no99aa.27926.17377.229830.3.200_2 Fri Jun 29 09:53:48 2007|SETI@home|Starting task 24no99aa.27926.17377.229830.3.200_2 using setiathome_enhanced version 518 Fri Jun 29 09:54:31 2007|SETI@home|Deferring communication for 1 min 0 sec Fri Jun 29 09:54:31 2007|SETI@home|Reason: Unrecoverable error for result 24no99aa.27926.17377.229830.3.200_2 (process exited with code 131 (0x83)) Fri Jun 29 09:54:31 2007|SETI@home|Computation for task 24no99aa.27926.17377.229830.3.200_2 finished |
Jeffrey Send message Joined: 21 Nov 03 Posts: 4793 Credit: 26,029 RAC: 0 |
The SETI develeopers are woring on the problem. Please keep us informed... In the meantime, look out Rosetta, here I come... ;) It may not be 1984 but George Orwell sure did see the future . . . |
NGCamacho Send message Joined: 18 Nov 02 Posts: 3 Credit: 783,333 RAC: 0 |
This problem is being discussed in the Number Crunching Board. From what I read it seems to affect only G3's. Work around was suggested. Here's the link to the thread "computation error" on several computers Good Luck, Nora |
hikerbiker Send message Joined: 24 May 99 Posts: 10 Credit: 95,454 RAC: 0 |
Any idea as to when the "computation error" will be fixed ? thanks |
The Gonif Send message Joined: 20 May 99 Posts: 17 Credit: 972,837 RAC: 0 |
Hi, For what it's worth, I too have a G3/1.1 GHz and have been bitten with the "Unrecoverable error for result" issue after a SETI update. I tried placing the new XML file in place, but I had already done a "reset_project", which apparently removes the setiathome application from the system. And since I had already tried to upload a corrupt result set, the SETI server has deferred communication for 19 hours, so when Seti@home started up with the new XML file it downloaded everything except the new Seti@home application and now I think I'll have to wait for 19 hours to see what happens. Hopefully the development team is working on this... I've got 35,000 classic Seti hours and 57,000 credits (although I still don't know what a credit is) and I'd love to keep working on it. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.