Hi guys,

since I switched from 6.3.10 to 6.3.14 this weekend I get some strange behaviour: the BOINC manager says "disconnected" and I find that the BOINC client quit itself and all apps. The last entry in the log is always a file transfer, but that does not necessarily have to mean anything.

My CPU is overclocked, but the GPU is not and there has not been a single error in the last 1000 QMC units. The machine is freshly rebootet. I had these quits 3 times within 3 days now and have never seen such behaviour from BOINC before, so I tend to blame the new client (not 100% sure though).

I'm going to downgrade to 6.3.10 and see if it happens again. Any other suggestions?

MrS

---

Scanning for our furry friends since Jan 2002

Well, actually I did play a bit with the GPU clocks.. but the error still happened when I went back to standard clocks. You can see an example here. Note the message "No heartbeat from core client for 30 sec - exiting". Shortly after the WU was finished the error happened again, which should be visible in the output from the next WU.. coming soon ;)

MrS

---

Scanning for our furry friends since Jan 2002

Some of our team mates have also made a downgrade to 6.3.10. They had too much problems with the scheduler, if they use ncpus=5. PS3Grid was then on "waiting to run" and 5 CPU-tasks are running. This don't happened in the 6.3.10.

---

Had the same prob on one of my Linux-rigs: BOINC would run normal until it started to 'phone home': then the app would quit completely. When setting it to 'don't contact server' or deinstalling the LAN-cable it would run without problems...until I had to connect again to submit results...
So I had to switch back to 6.3.10...
Got no idea what could be the reason for this behaviour...

Thanks for reporting! I think I'll run 6.3.10 for some time (to see if it's still as stable as before) and if I switch back to 6.3.14 or a later version I'll investigate if I get the same behaviour as you do (and the quits are directly related to file transfers).

MrS

---

Scanning for our furry friends since Jan 2002

I beleive the disconnected issue has been resloved. We have to wait for the next release to see. Stick with 6.3.10 if you have this issue for now.

That's good to hear, thanks for the information.

MrS

---

Scanning for our furry friends since Jan 2002

New try...and new surprise... ;)

Made a fresh installation of 6.3.14 on an recently updated Linux-rig (Q9550 @ 3,96GHz, Kernel 2.6.24-21, NVIDIA-driver 177.80) and everything was fine as long as Milkyway was running solo. Then I attached to PS3GRID, downloaded 4 WUs...and the next time BOINC connected to the server the app stopped...
Haven't tried yet what's happening when I choose PS3GRID to install as first one...

New try...and new surprise... ;)

Made a fresh installation of 6.3.14 on an recently updated Linux-rig (Q9550 @ 3,96GHz, Kernel 2.6.24-21, NVIDIA-driver 177.80) and everything was fine as long as Milkyway was running solo. Then I attached to PS3GRID, downloaded 4 WUs...and the next time BOINC connected to the server the app stopped...
Haven't tried yet what's happening when I choose PS3GRID to install as first one...

6.3.14 has bugs in the scheduler that prevent it from making the correct decisons on what to run. It runs CPU only jobs fine, but when you combine CPU with CPU/GPU jobs it can get confused, sometimes hovever it will do OK. I found it does better with less CPU work on standby, I've set connect to 0.04 and additional work to 0.08 so as to keep less CPU work ready, it seems to be doing better, but not always.

Everyone should stay with 6.3.10 until a new version has been tested. Fixes are under way, so I do not know when it will be avaialable.

Keith staying with 6.3.10 would be fine however when adding a new Q9550 today I could not find it anywhere.They have yanked the links from Boinc and here. The only available client is 6.3.14 .

@JR - try here......http://boinc.berkeley.edu/dl/?C=M;O=D

P.