Posts by Walt V

1) Message boards : Questions and problems : BOINC Hangs when th Communicating popup pops up (Message 26717)
Posted 21 Aug 2009 by Walt V
Post:
Another possibility is that you have a projet that is producing 0 sized results that won't upload to the servers. This <edit> might cause </edit> the Core Client to hang and you get the "Communicating with client" popup, and then the BOINC Manager shows nothing. If you run task manager, do you have an instance of Boinc.exe running? If not, you could try running Boinc.exe in a cmd window and see if it errors out.

Walt
2) Message boards : The Lounge : The last to post at a secret date and time, wins (Message 26654)
Posted 17 Aug 2009 by Walt V
Post:
I have to agree with Jay...I live in Maryland, and it is near 90F today. Cold beer sounds good.

Walt
3) Message boards : Projects : DrugDiscovery@Home (Message 26597)
Posted 14 Aug 2009 by Walt V
Post:
Any idea when this project will start accepting new members...I imagine after the db recovery effort has run its course.

Walt
4) Message boards : BOINC Manager : BOINC Manager Won't Connect to Localhost (Message 26563)
Posted 10 Aug 2009 by Walt V
Post:
I'll give it a try...I'm sure the message log will be easeir to read than running the client manually in a CMD window and pausing the app to capture the error as it occurs.

The lattice project had another WU that produced a 0 byte output file, which of course the servers "choked" on. During the numerous restarts of the client, I think it also precipitated a "computation error" with CPDN.

Walt
5) Message boards : BOINC Manager : Another "Not Connected to a Client" Issue (Message 26475)
Posted 4 Aug 2009 by Walt V
Post:
Gweedz,
From the looks of your error, it may be/have been (if you are still experiencing it) bad WUs from Einstein@Home. I encountered a similar error with Lattice Project WUs this morning, and after manually deleting the WUs, BOINC Manager connected to the clinet (localhost) no problem. After that I just reset the project to make sure that there was no straggler data from it that might cause the problem to resurface.

Walt
6) Message boards : BOINC Manager : BOINC Manager Won't Connect to Localhost (Message 26472)
Posted 4 Aug 2009 by Walt V
Post:
I think the problem was with the attached Lattice Project...they had some WUs that were generating errors.

After I manually deleted all the WU data for the project, and restarted the BOINC Manager, Boinc.exe started up and nestat shows it sitting on TCP port 31416. I also reset the project and for now, things appear to be stable.

Walt
7) Message boards : BOINC Manager : BOINC Manager Won't Connect to Localhost (Message 26471)
Posted 4 Aug 2009 by Walt V
Post:
I installed 6.6.38, and while watching apps running in Task Manager, Boinc.exe ran for a bit then dropped out. I opened a command line window, and restarted Boinc.exe and it again ran for a while then crashed. By having the command window open I was able to see that it encountered an "unhandled exception: Access Violation (0xc0000005) at address 0x004350ED read attempt to address 0x00001CF0"...Then it does a debug dump and exits.

I checked the TCP ports, while BOINC was running, and saw nothing on port 31416.

Is there any output file that BOINC generates that may point to the culprit?

Walt
8) Message boards : BOINC Manager : BOINC Manager Won't Connect to Localhost (Message 26461)
Posted 4 Aug 2009 by Walt V
Post:
I am running the test version (6.6.76) that Ageless compiled and have run in to an issue where I can't connect to the localhost and have it run the applications. On occasion Spinhenge will launch the graphics display, but all other apps appear to not function. Any suggestions as to what may be the culprit? Are there settings I need to add to my cc_config.xml to capture what's happening?

Walt
9) Message boards : The Lounge : Check your bank-records... (Message 26155)
Posted 20 Jul 2009 by Walt V
Post:
Not just the tanker, but the oilfield as well, pehaps even the employees and equipment.



Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.