| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Cannot attach to Localhost |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 29
|
|
| Author |
|
|
MarshallW
Cruncher Joined: Nov 16, 2004 Post Count: 13 Status: Offline Project Badges: 
|
Just a quick update, and request for any further suggestions.
- I uninstalled and reinstalled the WCG software. No help - I uninstalled and totally removed the WCG / BOINC directory and reinstalled. No help. - I added rules to give the outbound BOINC software access to the required ports. No help. - I turned off the firewall. No help - I removed the only new application I know of on the system. No help. - I checked the date and time - they are fine. No help. That just leaves the possibility of a GPU driver problem. I will see if I can remove any / all old video/GPU drivers as per the links above. I am hoping this can fix the problem, and I am thinking it might since I did update my video drivers about the time this problem showed up. In the meantime, if anyone has any other ideas, please let me know. And thanks for all the suggestions! - |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello MarshallW.
With the said 4th-item left, please follow the steps as indicated there closely. Good luck! ; |
||
|
|
MarshallW
Cruncher Joined: Nov 16, 2004 Post Count: 13 Status: Offline Project Badges:
|
Frustrating...
I uninstalled my AMD / ATI drivers using the Control Panel. The system requested a reboot after removing them. Upon reboot, BOINC was able to connect to localhost. I booted into safe mode, and ran Driver Sweeper to remove all drivers and keys for ATI and AMD. This seemed to run ok. I rebooted out of safe mode and came up using the basic hardware video drivers again, and BOINC once again was able to start up and process tasks. I installed the latest drivers and control software for my video card. That appeared to run cleanly, and I rebooted. The video came back at full resolution, but once again I get a constant "Connecting to localhost." So it seems my video drivers are the culprit. Is there something I need to turn on / off somewhere to get the BOINC Manager to connect? Thanks as always for your help. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
You could try to add the <no_gpus>1</no_gpus> to the <options> section of cc_config.xml. The manual which has more gpu related options: http://boinc.berkeley.edu/wiki/Cc_config.xml
Oh yeah, there was a post about a version that would not connect to the daemon no matter what, then reverting to an earlier one made the problem go away... did you mention what BOINC *exact* version you run [which would not explain the fail out of the blue without changing the client. Try version 5.10.45] --//-- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
@MarshallW,
Sad to hear that the issue remained unsolved even after the last (the 4th) item was done. The good news is: we are now more confident about what particular area is involved in the issue: the video. Whether that is the only area involved may yet not be clear. @SekeRob, I've dealt with installing and uninstalling video hardware/drivers throughout my BOINC-participating life and I have never encountered anything similar to what MarshallW is having and with this, I was surprised that video has even anything to do with ensuring proper BOINC operation -- until I realized that because GPU-computing is relatively new, the current video drivers are still in that phase of swatting the bugs and imperfections attendant to the desire of AMD/nVidia (the two giants in the GPU world) to prepare/initialize their respective hardware for the coming full-blown GPU-computing world. The BOINC software is inevitably caught in this transition: unlike before, BOINC now has to deal with both the CPU and the GPU. ; |
||
|
|
kskjold
Senior Cruncher Norway Joined: May 20, 2008 Post Count: 469 Status: Offline Project Badges: 
|
I had the same problem http://www.worldcommunitygrid.org/forums/wcg/...ead,32309_offset,0#356507 . The result was reinstalling win7, update the amd driver and then installing BOINC. Now everything is working.....
---------------------------------------- |
||
|
|
MarshallW
Cruncher Joined: Nov 16, 2004 Post Count: 13 Status: Offline Project Badges:
|
@SekeRob: I am running BOINCManage 6.10.58 (I updated it this week.) I tried creating the cc_config.xml file as you suggested, and I could not get it to do anything. I tried some log options and the GPU option you suggested, and nothing seemed to happen, and no output file was created. I put it in my \BOINC directory where all of the other files reside. Nothing.
Then I decided to try some options in my AMD Catalyst Control Panel, only to find out it had not installed correctly. It seems to have some kind of problem with Microsoft .NET files even though I have what is supposed to be the latest and greatest levels of everything. The fix for that looked very daunting, so I took an incremental approach, and uninstalled the Catalyst software. This did not remove the video driver but did require a reboot. After the reboot, BOINC is running! Yay!! So whatever the problem is, it lies in the AMD Catalyst Control Center software that did not install correctly when I reapplied it yesterday. (It had apparently installed correctly last week or so I assume since I was able to use it.) I want to thank all of you for your assistance and pointers as to where to look. And @kskjold, I am SO happy to not have to reinstall Win7. No way do I want to try that! As long as it runs, I am happy :) |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Coincidentally someone over at the developers forum pointed yesterday at the ATI/Catalyst drivers & CC, something about 11.7/11.8 versions, 1 month after someone asked the question.
----------------------------------------There's always a connection... did the issue start when you upgraded to 6.10.58? You did write: The only thing that has changed on my system (that I am aware of) are normal Windows system updates (Running Win 7 65-bit). Software install orders are often crucial [with old libs overwriting new libs , v.v. too and such], to incl. booting, and BOINC recognizing the right drivers especially. The GPU part is far from fully mature... who wonders why WCG is being meticulous and not to race into launching one. The cc_config file has to be read in via the advanced menu of BM, but many option changes require a client restart before they take effect. Only then does BOINC do a system steady state assessment. Great you're up and running again after your tribulations. Crunch On. --//-- [Edit 1 times, last edit by Former Member at Feb 25, 2012 4:54:08 PM] |
||
|
|
MarshallW
Cruncher Joined: Nov 16, 2004 Post Count: 13 Status: Offline Project Badges:
|
It is hard for me to pinpoint exactly when the problem started, but I think it started when I had to load new video drivers for a gaming application I was beta testing. I went to the AMD website, and downloaded and installed the latest drivers and the latest version of the Catalyst Control Center. I blame that download. This occurred before the last set of Win7 updates.
Thanks again for all of your assistance. Happily crunching on... |
||
|
|
|