[beadman]

Has anyone been successfully running Einstein@home on a PowerBook G4 while also subscribed to CPDN and SETI? I can't get E@H to pause and let the other two clients have the CPU. I switch between clients every two hours; when it comes time for CPDN to switch, it pauses nicely, as does SETI. But E@H says it is pausing (I'm in terminal mode), but actually does not pause. When I look at Activity Monitor, it shows E@H and the other client both using the CPU. I've got 1 GB RAM, lots of disk space available, etc.

beadman

[Shaktai]

Originally posted by beadman:
Has anyone been successfully running Einstein@home on a PowerBook G4 while also subscribed to CPDN and SETI? I can't get E@H to pause and let the other two clients have the CPU. I switch between clients every two hours; when it comes time for CPDN to switch, it pauses nicely, as does SETI. But E@H says it is pausing (I'm in terminal mode), but actually does not pause. When I look at Activity Monitor, it shows E@H and the other client both using the CPU. I've got 1 GB RAM, lots of disk space available, etc.

beadman

This has also been reported in the Einstein forums. It would be best to report it there as well, so that the project team is fully aware of the problem. Be sure to include which client version you are using. I don't have any boxes running that combination for sharing, but at intitial glance, it appears to be any combination of Einstein with CPDN and a third project.

[beadman]

Thanks, Shaktai - I have already reported it on the E@H <a href="http://einstein.phys.uwm.edu/forum_thread.php?id=543">forums</a>. My userID there is "C"


I just thought I'd see if anyone here at MacNN had been able to run it all successfully.
beadman

[Shaktai]

Originally posted by beadman:
Thanks, Shaktai - I have already reported it on the E@H <a href="http://einstein.phys.uwm.edu/forum_thread.php?id=543">forums</a>. My userID there is "C"


I just thought I'd see if anyone here at MacNN had been able to run it all successfully.
beadman

Well I haven't had any problems running 2 projects but haven't really had a chance to test it recently since the 4.19 BOINC CC, or the latest aps. Tell you what, I still have about a week before I have to tear the farm down for relocation. I'll tack on SETI to my G5 to see what happens. On my G3 iBook I'll add in Einstein to run with predictor. Maybe we can see if it is a BOINC client problem or something else.

[fillmeup]

I'm running Seti 50/ Einstein 49/ Predictor 1 with no switching, or "dueling projects" problems so far.
G4 700mhz 7450 iMac 10.3.7 - running mikkyo's optimized client.
Leave applications in memory while preempted? - yes
Switch between applications every - 1680 minutes. I know that's more than the recommended 60, but I'm trying to give Einstein time to complete it's average 27 hour work unit.

[Shaktai]

I tried to duplicate it on my G5 but couldn't. (but not runnning CPDN) This is starting to look like a conflict between the Einstein & CPDN apps. It doesn't occur consistently but from what I am seeing seems to occur when CPDN is one of the program running with Einstein. Not enough info to say for sure.

[beadman]

On my Mac, it has happened both ways: E@H not pausing when SETI resumes, and E@H not pausing when CPDN resumes. Twice now, SETI restarted instead of resuming when E@H didn't pause. I'm running all three, and had sharing set to 100 for each. This is the only time in several months that SETI has restarted instead of resuming. I've had zero conflicts between SETI and CPDN when just the two were running.

beadman

[Shaktai]

Originally posted by beadman:
On my Mac, it has happened both ways: E@H not pausing when SETI resumes, and E@H not pausing when CPDN resumes. Twice now, SETI restarted instead of resuming when E@H didn't pause. I'm running all three, and had sharing set to 100 for each. This is the only time in several months that SETI has restarted instead of resuming. I've had zero conflicts between SETI and CPDN when just the two were running.

beadman

I had no problem with SETI and Einstein, and it didn't make any difference on whether the app was in memory or not.

[fillmeup]

Cancel what I said above.

Just had the problem with both Einstein and Seti running at the same time. Einstein said it was pausing.

Console reported some problems with the projects, but I have no idea whether they are related to this problem.

2005-02-18 17:10:31 [Einstein@Home] Requesting 25534 seconds of work
2005-02-18 17:10:31 [Einstein@Home] Sending request to scheduler: http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
2005-02-18 17:10:38 [Einstein@Home] Scheduler RPC to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
2005-02-18 17:10:38 [Einstein@Home] Project prefs: using separate prefs for home
2005-02-18 17:10:38 [Einstein@Home] Pausing result H1_0129.4__0129.6_0.1_T09_Test02_1 (left in memory)

2005-02-18 17:10:38 [SETI@home] Starting result 01ja05aa.400.9136.978420.214_3 using setiathome version 4.30
2005-02-18 17:11:46 [SETI@home] Result 01ja05aa.400.9136.978420.214_3 exited with zero status but no 'finished' file
2005-02-18 17:11:46 [SETI@home] If this happens repeatedly you may need to reset the project.

2005-02-18 17:11:46 [SETI@home] Restarting result 01ja05aa.400.9136.978420.214_3 using setiathome version 4.30
2005-02-18 17:12:01 [SETI@home] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-02-18 17:12:01 [SETI@home] No schedulers responded
2005-02-18 17:12:01 [SETI@home] Deferring communication with project for 1 minutes and 0 seconds

I'm still using javalizards Seti worker. Seemed to work for some of the prior work units. Has it been determined that this worker can be used with the new 4.19, and optimized 4.19 client? I'm, of course referring to "note: SETI workers are not currently
included because they need rebuilding" on the optimized 4.19 page.

[reader50]

Check permissions on the folder the SETI "finished" file is supposed to be written to. If you upgraded the client recently, with a fresh SETI folder, the client may be failing to write out the file.

[fillmeup]

Originally posted by reader50:
Check permissions on the folder the SETI "finished" file is supposed to be written to.

Done.

Thanks reader50.

Now, if Seti was only UP.