 |
|
|
21)
Questions and Answers :
Windows :
Boinc v4.09 conflict w/ Climate Prediction
(Message 5106)
Posted 6 Oct 2004 by  old_user733
Post: By any chance do you have a dual processor or HT machine? There is an existing problem with BOINC GUI 4.09 and multi-processor machines when there is not enough work for both processors. I myself am locked out today after having lost 220 hours of work on one CPDN WU, and erroring out of about 3 more new WU's in an attempt to fix it. Apparently the fix (until a new BOINC GUI comes out) is to set your GENERAL prefs to use only 1 processor. This may or may not work, since upon rebooting or restarting BOINC, it hangs right away, before you can attempt to update. If you kill the BOINC GUI process, then the two HADSM processes (in that order), no harm is done to the WU's (however, the problem remains, and when you start up BOINC again it will hang). If you kill the HADSM processes first, the BOINC GUI will dump them claiming a processing error. If you have a lot of time invested in a WU, you will lose it. However, this seems to be the only way to get the client to attempt an update. |
|
22)
Questions and Answers :
Windows :
Problems with BOINC 4.09 on Windows XP
(Message 4894)
Posted 1 Oct 2004 by old_user733
Post: > > I would suggest updating your project preferences ( > http://climateapps2.oucs.ox.ac.uk/cpdnboinc/prefs.php?subset=global and > http://climateapps2.oucs.ox.ac.uk/cpdnboinc/prefs.php?subset=project ), > reinstalling BOINC 4.09, running the benchmarks, and doing a project update > for all the attached projects on the machine. > > My guess is the problem has nothing to do with you hardware or OS. > > Are there any suspect messages listed in the messages tab of the boinc_gui > application? > > Further info: This machine was attached to CPDN, Seti@Home, and Predictor. Predictor is obviously not giving any work lately, and Seti had run out. There was only one CPDN WU on this HT machine. So, since things were working again under 4.05, I could see that Seti had stopped giving me work because of the client version. I again tried upgrading to 4.09 (completely shutting BOINC down before upgrading), but, again, it got into this state (and it was NOT running the benchmarks). I then tried this -- I backed off again to 4.05, had it running again, then attached to LHC@home and got some work. I upgraded again to 4.09 and everything is now working. Could it have something to do with only having work for one of two processors? How come I can't get another WU from CPDN? So far, out of four machines, two being duals, one being HT, and one being a single, only one of the duals has two WU's from CPDN. Prefs are the same. (I know, a different problem.) |
|
23)
Questions and Answers :
Windows :
Problems with BOINC 4.09 on Windows XP
(Message 4759)
Posted 28 Sep 2004 by old_user733
Post: OK, more details. Setting size to zero didn't help. I also noticed there was NO Seti process running as it had run out of work, and S@H isn't responding. Going to try reinstalling 4.05. Also, I'm running 4.09 on three other machines with no problem. One is a P4 (non-HT) and two are PIII duals. ------- Edit-- Back up and running with 4.05... |
|
24)
Questions and Answers :
Windows :
Problems with BOINC 4.09 on Windows XP
(Message 4758)
Posted 28 Sep 2004 by old_user733
Post: This is not an answer, but more details... I just switched to BOINC 4.09, am running WinXP Pro, SP2. CPU is a 3.2GHz P4 HT. I didn't get to see the screensaver part -- when I turned the monitor on this morning, the screen was black, the machine unresponsive to mouse wiggles. I was able to do a Ctl-Alt-Del to get control, and rebooted. On reboot, BOINC started up but when I clicked the icon in the systray, nothing happened. I checked running processes, saw hadsm3um_4.03_w (50%), hadsm3_4.03_win (0%), boinc_gui (12%). My virus scanner was taking up the remaining time scanning client_state.xml as it was being rewritten constantly. I looked at client_state.xml and there is an odd line in it which may be a symptom. Here are the first few lines in the section up to the odd one: {project} {master_url}http://climateprediction.net/{/master_url} {project_name}climateprediction.net{/project_name} {share_size}0.000000{/share_size} {size}-7307860.000000{/size} I noticed that in properly working installations, the "size" is 0.000000. I'm going to try just changing that one line to see what happens. |
©2024 climateprediction.net