| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Not connected to a client |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 10
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I get the following error all of a sudden after more than 10 years of running BOINC.
World Community Grid - BOINC Manager - Connection Failed World Community Grid - BOINC Manager is unable to connect to a World Community Grid client. I was unable to find any help till now on how to resolve it. It is a windows machine. |
||
|
|
pcwr
Ace Cruncher England Joined: Sep 17, 2005 Post Count: 10903 Status: Offline Project Badges: 
|
Probably due to the current server maintainance currently going on.
----------------------------------------Report back if you still have problems after this has completed. Patrick  |
||
|
|
vepaul
Senior Cruncher Belgium Joined: Nov 17, 2004 Post Count: 261 Status: Offline Project Badges:
|
Yes, I have the same problem: started at 3.30h this morning and is expected to be the same for maximum 13 hours, so says the forum.
Paul |
||
|
|
Dieter Matuschek
Advanced Cruncher Germany Joined: Aug 13, 2005 Post Count: 142 Status: Offline Project Badges: 
|
Sometimes a reboot will do some wonder.
----------------------------------------  Ask not what the world can do for you - ask what you can do for the world. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thank you all for your help in this regard. I have rebooted the system as well. But I still face the same problem and it comes with a message box asking to connect to a client. When I click ok it still tries and fails. Appreciate if someone who faced it earlier offers a solution.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hasn't happened to me for a while now but the last time it happened something else had allocated the port (31416 IIRC). While having the problem, have you checked:
1. That a process named boinc.exe is running (this is the client process) 2. That port 31416 is not allocated to another process (IIRC netstat will tell you) 3. Is 31416 being blocked by firewall software If #2 is the issue a reboot normally fixes that problem as the conflicting process will allocate another port at startup freeing 31416 for the boinc.exe process. If the other items are the problem, a reboot probably won't do much good. That's all I remember at the moment.... Hope it helps |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thank you for your response. The boinc.exe process is not running. I only see boincmgr.exe and boinctray.exe processes running. Also there is no issue with port 31416 when I checked using netstat and port 31416 was not firewall blocked
|
||
|
|
KLiK
Master Cruncher Croatia Joined: Nov 13, 2006 Post Count: 3108 Status: Offline Project Badges:
|
Deinstall
----------------------------------------Reboot Install And it will fix it! Use WCG version of BOINC |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
That's the problem, no client running to communicate with. You can look in the DATA directory of your BOINC installation and see if there might be messages in the stderrdae.txt or stdoutdae.txt log files indicating why the client process isn't running.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thank you for your response. The boinc.exe process is not running. I only see boincmgr.exe and boinctray.exe processes running. Also there is no issue with port 31416 when I checked using netstat and port 31416 was not firewall blocked Is boinc.exe truly not running? If installed as service, you will not see the process in Task Manager unless you hit the 'Show processes for all users' |
||
|
|
|