Questions and Answers :
Windows :
Unable to connect to the core client
Message board moderation
Author | Message |
---|---|
Frank Tolentino Send message Joined: 16 Jul 14 Posts: 34 Credit: 211,343 RAC: 0 |
Hi I have an 'Unable to connect to the core client' message come up on my BOINC manager...No WUs are being received. Could it be i need to upgrade the BOINC manager? I don't upgrade when it notifies me. Could there be a more fundamental reason to do with connection that is on the SETI@Home end? Many thanks. |
Frank Tolentino Send message Joined: 16 Jul 14 Posts: 34 Credit: 211,343 RAC: 0 |
It's ok...Whatever it was it seems to have fixed itself. |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Could there be a more fundamental reason to do with connection that is on the SETI@Home end?The message about not being able to connect to the core client is done by BOINC Manager (the graphical user interface) when it can't make contact with the client that runs underneath. BOINC consist of: - a client called BOINC (boinc.exe) (which does all the communications with the projects, storing of tasks, scheduling when what task is being calculated upon, etc.) - a graphical user interface called BOINC Manager (boincmgr.exe) (which allows you to easily command and control the client, without having to resort to the command line) - a command line tool called BOINCCMD (boinccmd.exe) (which allows you to command and control the client from the command line, in case you cannot run BOINC Manager) - a screen saver called BOINC.scr (which runs the built in screen saver when the project has no graphics application of its own, or the project screen saver when the project does have a graphics app of its own) The message you had was that BOINC Manager could not connect to the client, which is usually caused by: - the client (boinc.exe) not running. It can happen that for some reason the client is killed (user killed it, or an overzealous anti-virus/anti-malware program) Of course when the client isn't running, the manager cannot make contact with it. -- Solution: exit BOINC Manager, wait up to 10 seconds, restart it. The manager should start the client. If it doesn't work, try a reboot of the system. - neither the client, nor the manager having been cleared through the firewall. These parts of BOINC communicate with each other via remote procedure call, via TCP port 31416. If this port is blocked in the firewall, it means the parts of BOINC when run cannot communicate with each other, and you get the message. -- Solution: add the client and manager to the firewall's inbound and outbound rules. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.