[Sosa]

Greetings Folks,

I started running SETI again the other day after more than a year without completing a unit, just because I would like to reach 500 (I'm at 465 I think). Anyways, I'm using the client activated through terminal, running two in case one finishes and can't connect, which is exactly what has happened. Connection attempts time out, I must have an old address.

Should I download OS X cli again or is there some way for me to correct his through unix?

[reader50]

You are no doubt trying to run Classic SETI. They finally retired that project, and powered down the server that handled it.

To continue in SETI, you need to download the BOINC version. You're in luck, we just had a member post a tutorial/installation/optimization guide for this.

[Sosa]

Well it took me about an hour, but I finally installed the Boinc client for G4, got it running and it downloaded a unit and began work. I then followed instructions to delete the Seti Worker File given by Berkley setiathome_4.18_powerpc-apple-darwin and dropped in the seti@home-G4-a5 and app_info.xml files as per instructions. Now when I try to run BOINC I get this:

Starting BOINC client version 4.44 for powerpc-apple-darwin
2006-04-14 20:47:19 [---] Data directory: /SETI
2006-04-14 20:47:19 [SETI@home] Found app_info.xml; using anonymous platform
2006-04-14 20:47:19 [SETI@home] Computer ID: 2351330; location: ; project prefs: default
2006-04-14 20:47:19 [---] No general preferences found - using BOINC defaults
2006-04-14 20:47:19 [SETI@home] Deferring communication with project for 3 minutes and 50 seconds
2006-04-14 20:47:19 [SETI@home] Deferring communication with project for 3 minutes and 50 seconds
2006-04-14 20:47:19 [---] Insufficient work; requesting more
2006-04-14 20:47:19 [---] schedule_cpus: must schedule
2006-04-14 20:51:10 [SETI@home] Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2006-04-14 20:51:11 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2006-04-14 20:51:11 [SETI@home] New host venue: home
2006-04-14 20:51:12 [SETI@home] Started download of 10ja99ab.22286.13075.820176.1.43
2006-04-14 20:51:19 [SETI@home] Finished download of 10ja99ab.22286.13075.820176.1.43
2006-04-14 20:51:19 [SETI@home] Throughput 78414 bytes/sec
2006-04-14 20:51:19 [---] request_reschedule_cpus: files downloaded
2006-04-14 20:51:19 [---] schedule_cpus: must schedule
2006-04-14 20:51:19 [SETI@home] Starting result 10ja99ab.22286.13075.820176.1.43_2 using setiathome version 4.18
2006-04-14 20:51:20 [SETI@home] Unrecoverable error for result 10ja99ab.22286.13075.820176.1.43_2 (process got signal 5)
2006-04-14 20:51:20 [SETI@home] Unrecoverable error for result 10ja99ab.22286.13075.820176.1.43_2 (process got signal 5)
2006-04-14 20:51:20 [---] request_reschedule_cpus: process exited
2006-04-14 20:51:20 [SETI@home] Deferring communication with project for 9 minutes and 56 seconds
2006-04-14 20:51:20 [SETI@home] Deferring communication with project for 9 minutes and 56 seconds
2006-04-14 20:51:20 [SETI@home] Computation for result 10ja99ab.22286.13075.820176.1.43_2 finished
2006-04-14 20:51:20 [---] schedule_cpus: must schedule

Can anyone diagnose what is happening?

[Knightrider]

If you had some wu's already, then when you put in the new worker they will usually fail. Just let it run untill they clear. You may also see the occasional wu fail and be re done. Keep a small watch on your results as you may also see the occasional invalid result. It could also be that when this was happening the project server was down.

K.