The SETI project downloaded a new version of the client on my Mac (PMac Dual G5 2.5 GHz; BOINC Manager version 5.8.17). All WUs using the 5.21 version of the client keep failing while the ones using the 5.18 version of the client are running fine. I have copied the relevant messages below:

Wed Jul 18 19:36:53 2007|SETI@home|Restarting task 08ap00aa.2371.26913.11088.3.249_1 using setiathome_enhanced version 521
Wed Jul 18 19:36:53 2007|SETI@home|Restarting task 05jn00aa.15102.2993.692336.3.166_1 using setiathome_enhanced version 521
Wed Jul 18 19:36:54 2007|SETI@home|Task 05jn00aa.15102.2993.692336.3.166_1 exited with zero status but no 'finished' file
Wed Jul 18 19:36:54 2007|SETI@home|If this happens repeatedly you may need to reset the project.
Wed Jul 18 19:36:54 2007|SETI@home|Restarting task 05jn00aa.15102.2993.692336.3.166_1 using setiathome_enhanced version 521
Wed Jul 18 19:36:55 2007|SETI@home|Task 05jn00aa.15102.2993.692336.3.166_1 exited with zero status but no 'finished' file
Wed Jul 18 19:36:55 2007|SETI@home|If this happens repeatedly you may need to reset the project.
Wed Jul 18 19:36:55 2007|SETI@home|Restarting task 05jn00aa.15102.2993.692336.3.166_1 using setiathome_enhanced version 521
Wed Jul 18 19:36:56 2007|SETI@home|Task 05jn00aa.15102.2993.692336.3.166_1 exited with zero status but no 'finished' file
Wed Jul 18 19:36:56 2007|SETI@home|If this happens repeatedly you may need to reset the project.
Wed Jul 18 19:36:56 2007|SETI@home|Restarting task 05jn00aa.15102.2993.692336.3.166_1 using setiathome_enhanced version 521
Wed Jul 18 19:36:57 2007|SETI@home|Task 05jn00aa.15102.2993.692336.3.166_1 exited with zero status but no 'finished' file
Wed Jul 18 19:36:57 2007|SETI@home|If this happens repeatedly you may need to reset the project.
Wed Jul 18 19:36:57 2007|SETI@home|Restarting task 05jn00aa.15102.2993.692336.3.166_1 using setiathome_enhanced version 521
Wed Jul 18 19:36:58 2007|SETI@home|Task 05jn00aa.15102.2993.692336.3.166_1 exited with zero status but no 'finished' file
Wed Jul 18 19:36:58 2007|SETI@home|If this happens repeatedly you may need to reset the project.
Wed Jul 18 19:36:58 2007|SETI@home|Restarting task 05jn00aa.15102.2993.692336.3.166_1 using setiathome_enhanced version 521
Wed Jul 18 19:36:59 2007|SETI@home|Task 05jn00aa.15102.2993.692336.3.166_1 exited with zero status but no 'finished' file
Wed Jul 18 19:36:59 2007|SETI@home|If this happens repeatedly you may need to reset the project.
Wed Jul 18 19:36:59 2007|SETI@home|Restarting task 05jn00aa.15102.2993.692336.3.166_1 using setiathome_enhanced version 521
Wed Jul 18 19:37:00 2007|SETI@home|Task 05jn00aa.15102.2993.692336.3.166_1 exited with zero status but no 'finished' file
Wed Jul 18 19:37:00 2007|SETI@home|If this happens repeatedly you may need to reset the project.
Wed Jul 18 19:37:00 2007|SETI@home|Restarting task 05jn00aa.15102.2993.692336.3.166_1 using setiathome_enhanced version 521
Wed Jul 18 19:37:01 2007|SETI@home|Task 05jn00aa.15102.2993.692336.3.166_1 exited with zero status but no 'finished' file
Wed Jul 18 19:37:01 2007|SETI@home|If this happens repeatedly you may need to reset the project.
Wed Jul 18 19:37:01 2007|SETI@home|Restarting task 05jn00aa.15102.2993.692336.3.166_1 using setiathome_enhanced version 521
Wed Jul 18 19:37:02 2007|SETI@home|Task 05jn00aa.15102.2993.692336.3.166_1 exited with zero status but no 'finished' file
Wed Jul 18 19:37:02 2007|SETI@home|If this happens repeatedly you may need to reset the project.
Wed Jul 18 19:37:02 2007|SETI@home|Restarting task 05jn00aa.15102.2993.692336.3.166_1 using setiathome_enhanced version 521
Wed Jul 18 19:37:03 2007|SETI@home|Task 05jn00aa.15102.2993.692336.3.166_1 exited with zero status but no 'finished' file
Wed Jul 18 19:37:03 2007|SETI@home|If this happens repeatedly you may need to reset the project.
Wed Jul 18 19:37:03 2007|SETI@home|Restarting task 05jn00aa.15102.2993.692336.3.166_1 using setiathome_enhanced version 521
Wed Jul 18 19:37:05 2007|SETI@home|Task 05jn00aa.15102.2993.692336.3.166_1 exited with zero status but no 'finished' file
Wed Jul 18 19:37:05 2007|SETI@home|If this happens repeatedly you may need to reset the project.


Any ideas why this is happening? Any workarounds other than resetting the project? Thanks.

Yep... This is my new problem too... ;)


I found this in the error log in my slots folder:

Process creation (../../projects/setiathome.berkeley.edu/setiathome-5.21_AUTHORS) failed: errno=8

I found this in the error log in my boinc data folder:

Restarting task 08ap00aa.2371.16753.417318.3.248_2 using setiathome_enhanced version 521
Task 08ap00aa.2371.16753.417318.3.248_2 exited with zero status but no 'finished' file
If this happens repeatedly you may need to reset the project.

---

It may not be 1984 but George Orwell sure did see the future . . .

Version 5.21 is supose to fix a problem with 5.18 that caused it to crash on PPC G3 cpus.
It looks like 5.21 crashes on the PPC G4. Mine just loops like the message above, until the daily work unit limit is reached.

added: The Test version of 5.21 that I downloaded worked fine on my G3, but when I just re-started Boinc Manager(menubar), and it downloaded the new 5.21 release, it crashed also, or maybe differently. The log showed a computational error and I think it exited with status x08, uploading the result.
On the G4's, the work is restarted.

I restarted the Test version in the Terminal window, and it is working fine again.

---

I have the same problem:

Please read here.

---

I'm having the same problem and have suspended Seti until this is resolved. It causes the BOINC Manager to "hang" and the Rosetta project is not getting a look-in.

Running on a PPC dual G5, MacOSX 10.4.10, Setiathome 5.21.

Geoff

---

Dual 1.8 GHz PowerPC G5 Mac, 3 GB Ram, MacOSX 10.4.10

I'm having the same problem and have also suspended Seti until this is resolved.

PPC G4, MacOSX 10.3.9

---

I have the same problem with the application 5.21 for MAC

SETI@home|Restarting task 05jn00aa.15102.9281.1003414.3.87_2 using setiathome_enhanced version 521
SETI@home|Task 05jn00aa.15102.9281.1003414.3.87_2 exited with zero status but no 'finished' file
SETI@home|If this happens repeatedly you may need to reset the project.

Version 5.21 is supose to fix a problem with 5.18 that caused it to crash on PPC G3 cpus.
It looks like 5.21 crashes on the PPC G4. Mine just loops like the message above, until the daily work unit limit is reached.

added: The Test version of 5.21 that I downloaded worked fine on my G3, but when I just re-started Boinc Manager(menubar), and it downloaded the new 5.21 release, it crashed also, or maybe differently. The log showed a computational error and I think it exited with status x08, uploading the result.
On the G4's, the work is restarted.

I restarted the Test version in the Terminal window, and it is working fine again.

I'm going to speak for all Beta Testers here in that we apologize this problem is happening now but we hope you will understand that we only have about 11000 beta testers and only a small percentage (app. 3%) are running Macs. So we can't test every possible combination of computer/os/BOINC version/configuration setting/operating style/etc. I'm sure the developers are hard at work trying to figure out what is happening, so please be patient.

Reporting your errors and giving as many details as possible about your setup will help them narrow the problem down and get it fixed.

---

Jim

Some people plan their life out and look back at the wealth they've had.
Others live life day by day and look back at the wealth of experiences and enjoyment they've had.

I restarted the Test version in the Terminal window, and it is working fine again.

I dropped the test version into boinc and it didn't work there... ;)

---

It may not be 1984 but George Orwell sure did see the future . . .

There was a problem with the file permissions on the 5.21 that went into the main project. Resetting the project will get you version 5.22, which shouldn't have that problem.

Eric

---

@SETIEric@qoto.org (Mastodon)

Resetting the project will get you version 5.22, which shouldn't have that problem.

So far so good... ;)

---

It may not be 1984 but George Orwell sure did see the future . . .

There was a problem with the file permissions on the 5.21 that went into the main project. Resetting the project will get you version 5.22, which shouldn't have that problem.

Eric

Thanks for the update.
:-)

I reset the project and started using the new 5.22 version of Seti. I have since had two crashes so have suspended Seti again.

Crash info:

Command: setiathome-5.22.powerpc-apple-darwin
Path: ../../projects/setiathome.berkeley.edu/setiathome-5.22.powerpc-apple-darwin
Parent: boinc [312]

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x7c3e0b78

Both crashes have the same info.

Running on a PPC G5 dual Mac, MacOSX 10.4.10.

Geoff

---

Dual 1.8 GHz PowerPC G5 Mac, 3 GB Ram, MacOSX 10.4.10

Same here on 2 PPC Macs - one dual CPU Cube and one iMac G5 rev 3, both with OS X 10.4.10. Similar message log as raghu.

---

5.22 crashes here, too.
eMac G4@1,42GHz and Mac OS X 10.4.10.
I can provide the crash reports if you need them.

---

As well as running OSX 10.4.10, it is worth making sure you are running the latest version of BOINC Manager. That is 5.10.7 (or even 5.10.10), which are downloadable from the SETI@home website (shown in the menu on BOINC Manager Projects or Tasks pages when an active item is selected)

Keith

As well as running OSX 10.4.10, it is worth making sure you are running the latest version of BOINC Manager. That is 5.10.7 (or even 5.10.10), which are downloadable from the SETI@home website (shown in the menu on BOINC Manager Projects or Tasks pages when an active item is selected)

I'm sorry I forgot to mention I'm using the 5.10.7 command line BOINC version.

---

There was a problem with the file permissions on the 5.21 that went into the main project. Resetting the project will get you version 5.22, which shouldn't have that problem.

Eric

============================================

Eric

It is easy to overcome the permissions problem by selecting the folder "setiathome.berkeley.edu", then go to menu:
File/GetInfo?Ownership&Permissions/Details/ApplyToEnclosed
Then all should be OK. No further reset necessary.

Keith

Is anything happening with this crashing problem? I have Seti suspended for two weeks now and would like to start running it again soon.

Geoff

---

Dual 1.8 GHz PowerPC G5 Mac, 3 GB Ram, MacOSX 10.4.10

If you need proof that 5.23 works, look at my work units. It has been running well from the day it was released.

---