| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Connecting to localhost |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 13
|
|
| Author |
|
|
Mont
Cruncher Joined: Jun 3, 2007 Post Count: 20 Status: Offline Project Badges: 
|
My grid won't let me connect, it just sits there 'Connecting to localhost'.
I recently upgraded my gpu from ati to nvidia. A search would seem to indicate this is a problem. I have uninstalled the ati drivers and reinstalled wcg but it still hangs there. Unfortunately this is on my work pc so this could be the nail in the coffin for my wcg input. I can't run it at home (clashes with shadowprotect) and it will be a while before I do an upgrade at work. Thanks for your help. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi,
Sorry for a non-reply within the last 27 hours... at work, well I trust you got permission, lest you're the boss to run BOINC on a work PC. Things such as Firewall and AV software can interfere with the BOINC Manager connecting to the client. If the problem has not resolved, locate the BOINC data directory which contains the stdoutdae.txt file. Open it with a text editor [wordpad e.g.] Find the last occurrence of the following line, noting that your version could be different: 02-08-2011 09:05 Starting BOINC client version 6.10.60 for windows_intelx86 Copy everything down from there and post in your next reply. Then we can read what the core client is doing, provided that boinc.exe [the core client] is actually running [look is task manager, all user processes view]. If it's not running the BOINC Manager could not connect anyhow. ttyl --//-- P.S. With the boinccmd tool you can do many activities to find out what BOINC is doing. Here the wiki: http://boinc.berkeley.edu/wiki/Boinccmd_tool |
||
|
|
Mont
Cruncher Joined: Jun 3, 2007 Post Count: 20 Status: Offline Project Badges:
|
Hi Seke, thanks for the Reply.
----------------------------------------BOINC is not connecting. Here is the end of the log for you: 02-Aug-2011 12:00:35 [---] Starting BOINC client version 6.10.58 for windows_intelx86 02-Aug-2011 12:00:35 [---] log flags: file_xfer, sched_ops, task 02-Aug-2011 12:00:35 [---] Libraries: libcurl/7.19.7 OpenSSL/0.9.8l zlib/1.2.3 02-Aug-2011 12:00:35 [---] Data directory: E:\BOINC\Data 02-Aug-2011 12:00:35 [---] Running under account x 02-Aug-2011 12:00:35 [---] Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz [Family 6 Model 23 Stepping 10] 02-Aug-2011 12:00:35 [---] Processor: 6.00 MB cache 02-Aug-2011 12:00:35 [---] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 nx lm vmx smx tm2 pbe 02-Aug-2011 12:00:35 [---] OS: Microsoft Windows XP: Professional x86 Edition, Service Pack 3, (05.01.2600.00) 02-Aug-2011 12:00:35 [---] Memory: 3.50 GB physical, 7.34 GB virtual 02-Aug-2011 12:00:35 [---] Disk: 149.01 GB total, 116.93 GB free It's possible that someone changed the firewall settings but it's unlikely. Work stopped the same day I upgraded the gpu. Rgs [Edit 1 times, last edit by Mont at Aug 3, 2011 1:02:58 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello Mont,
Work stopped the same day I upgraded the gpu. But the section you posted does not say anything about a GPU. What happens after a reboot? Is there any Message about a GPU or does it freeze before that point?  Lawrence |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi Mont,
You don't tell where you got the log, but if through BOINC Manager, you've effectively told us that the ''connecting to localhost'' problem was overcome. There is this oddity with this some run into... Where did you get the 6.10.58 client... here at WCG's download page? See this thread, from this post: http://www.worldcommunitygrid.org/forums/wcg/...ead,30328_offset,0#303596 which tells that the Berkeley version of 6.10.58 overcomes the issue. Also, like Lawrence noted, the log is cut off a little short, need a bit more to where the client starts telling if there are projects attached and if there is a work fetch request that fails or succeeds. ttyl. --//-- |
||
|
|
Mont
Cruncher Joined: Jun 3, 2007 Post Count: 20 Status: Offline Project Badges:
|
That's it for the log. There's no cpu test, no tasks, no project list. I downloaded the latest version from the wcg home page.
Rgs |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Mont,
Plz follow the link in my previous post to the Berkeley 6.10.58 version, download, install, boot and tell us if the BOINC Manager still has connection problems. Was the log directly from the stdoutdae.txt file? The boinccmd tool, see me previous previous post you can do all sorts of activities, project attaching and whatnot. BOINC Manager is not needed to run BOINC. For the BM to connect it needs to have an open port 31416 via the 127.0.0.1 localhost IP [never leaves computer]. A new version of Firewall could be obtuse, so check in there if it's got rules for boinc.exe and boincmgr.exe. If so, delete them and watch if something pops up asking to grant and remember permission. --//-- |
||
|
|
Mont
Cruncher Joined: Jun 3, 2007 Post Count: 20 Status: Offline Project Badges:
|
uote]Plz follow the link in my previous post to the Berkeley 6.10.58 version, download, install, boot and tell us if the BOINC Manager still has connection problems. Was the log directly from the stdoutdae.txt file? --//-- Hi Rob et al. I went to http://www.worldcommunitygrid.org/forums/wcg/...ead,30328_offset,0#303596 as you suggested and I did install for all users anyway. Using another anti-virus so Norton would not seem to be an issue. Yes it was from the txt file. I will check tomorrow if there's anything worthwhile in the local firewall and even install on a test pc to make sure it's not the org's firewall. Failing that I suppose I will install Win7 in a couple of months so maybe a fresh registry will do the trick. Thanks for your help everyone. Rgs ---------------------------------------- [Edit 1 times, last edit by Mont at Aug 4, 2011 1:34:43 PM] |
||
|
|
Mont
Cruncher Joined: Jun 3, 2007 Post Count: 20 Status: Offline Project Badges:
|
Installs and communicates ok on another machine on network.
----------------------------------------Out of curiosity, what information do I need to provide under Advanced > Select Computer? [Edit 1 times, last edit by Mont at Aug 5, 2011 5:11:24 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Installs and communicates ok on another machine on network. Out of curiosity, what information do I need to provide under Advanced > Select Computer? For the BOINC Manager [boincmgr.exe] to connect to the Core Client [boinc.exe] you need not provide anything ... leave the host name / password fields blank and enter. Sometimes that does not seem to work, then type localhost in the host name fields, don't enter anything is the pw field and OK. The password can be changed and is stored in the gui_rpc_auth.cfg file. Default it holds a 32 character hex random value. Most users will change this password so they can remotely connect to a client. The password change requires the restart of the core client / stop start of the core client service. Depending on how installed and what version of client, BOINC Manager can start the core client, but when running as service, boinc.exe has to run prior for the boincmgr to be able to connect. [In 6.12 the boincmgr can start the service when the user has permission] As noted in a previous post, the boincmgr is not needed. Most actions can be done with the boinccmd tool in a terminal/cmd window, to include attaching the client to WCG, passing password and account number, etc. --//-- |
||
|
|
|