Here is the last part of the stdoutdae file for when Boinc disappeared. Hopes this helps as this seems to cause Boinctasks to go into a loop also. Have posted this problem on both sites.


18-Nov-2011 17:29:17 [---] failed to rename xfer history file: Error 5
18-Nov-2011 17:29:26 [Server for testing Bolpex] Scheduler request completed
18-Nov-2011 17:30:11 [EDGI Demo Project] Sending scheduler request: Requested by project.
18-Nov-2011 17:30:11 [EDGI Demo Project] Not reporting or requesting tasks
18-Nov-2011 17:30:14 [EDGI Demo Project] Scheduler request completed
18-Nov-2011 17:30:14 [---] Can't rename current state file to previous state file; The process cannot access the file because it is being used by another process. (0x20)
18-Nov-2011 17:30:14 [---] rename error: Access is denied. (0x5)
18-Nov-2011 17:30:14 [---] Couldn't write state file: rename() failed; giving up

Did you really mean this version number, which dates back to early February and is long superseded. Could you be referring to the current test build v6.13.12?

MacBook Pro 8,2, Mac OSX 10.7.2 v.v6.13.12 quits processing units but doesn't quit. Restart it and it runs for a few hours and then stops processing units. The "real" version client (6.12.35) runs fine. I couldn't fine any logs or error messages in the beta to share.

powerpc G4
boinc version: 6.12.35
wxWidgets version: 2.8.10

Boinc no longer can connect with milkyway@home site to report complet3ed work or fetch new. I cannot connect to http://milkyway.cs.rpi.edu/milkyway/ via firefox or safari either. Internet connection is fine.

please advise

powerpc G4
boinc version: 6.12.35
wxWidgets version: 2.8.10

Boinc no longer can connect with milkyway@home site to report complet3ed work or fetch new. I cannot connect to http://milkyway.cs.rpi.edu/milkyway/ via firefox or safari either. Internet connection is fine.

please advise

What has that got to do with this thread? you're not running Boinc 6.12.13 or even 6.13.12.

Milkyway@home is down, have read of the News on Project Outages thread for further info, when it becomes available.

Claggy

What has that got to do with this thread? you're not running Boinc 6.12.13 or even 6.13.12.

Milkyway@home is down, have read of the News on Project Outages thread for further info, when it becomes available.

Claggy

excuse me. thank you for the link to the correct thread.

I am running Boinc 6.12.13 and it often disconnects from the client, what ever that is and then I can't access any of my projects or see my tasks. Boinc screen saver will say that "Boinc is not running." The only way to get it started again is to restart the computer.

It's an app problem, not a firewall issue. If the firewall were the issue Boinc would not be able to connect at all. I am tired of this problem and if it continues I may drop out of Boinc altogether.

This evening it was acting up so I ran the 6.12.13 installer and got an option to repair the installation, so I tried it. Of course I made sure Boinc Manager was quit and out of Task Manager before I ran the installer. After a few seconds it finished and I got Boinc Manager up and it was reconnected to the client and all the projects were showing and everything was fine. I hope that's the fix.

---

Wish the mods would edit the OP title to say it's 6.13.12 (if that's what it is). Then we'll know up front what [alpha] version is being discussed.

--//--

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

First of all the version number is 6.13.12. It also happens with 7.0.2, but only if Boinctasks is running at a very high cpu usage (98). So belive this to be a Boinctasks problem only. As long as the usage for Boinctasks stays low there is no problem. I presently only run Boinctasks for short periods to see how my network is doing and what computers have problems. Thanks for all your input, but believe this to be a Boinctasks problem only.

First of all the version number is 6.13.12.

If you edit your post again, you, as OP, can change the thread title.

Gruß,
Gundolf

Have upgraded to 6.12.34 and 7.0.7. The problem does not seem to exist any more. Many thanks for the assistance.