Can anyone tell me why over the last month or so any time I reboot my system I have to manually reconnect BOINC to localhost? Been crunching since something like '99 and this is the first time I have run in to this issue.

Thanks in advance.

Can anyone tell me why over the last month or so any time I reboot my system I have to manually reconnect BOINC to localhost? Been crunching since something like '99 and this is the first time I have run in to this issue.

Thanks in advance.

If you have two userids and one of them starts up Boinc and then you start Boinc in the other userid, it will complain about re-connecting to the local host.

Plan B is run the repair function by starting up the Boinc install.
Plan C is run your tasks till your dry, then uninstall Boinc, cold boot and reinstall Boinc.

X <- fingers

Tom

---

A proud member of the OFA (Old Farts Association).

How does plan C help? Uninstalling BOINC merely removes the executable files from the install directory. It does not clear up the registry, nor clean up/out the data directory. The file used to make the connection between the client and manager lives in the data directory.

No, I don't have the answer either, but can tell that plan C won't do anything.

---

I only have one ID so that theory is is not it. I can try a repair but I would really love to know the root cause before I go with any nuclear option. Like I said I have been crunching for years and this only cropped up in the last month or so.

Thanks.

---

What you can try is exit BOINC completely, then navigate to the BOINC data directory, remove gui_rpc_auth.cfg and restart BOINC (Manager).
That will put a new empty gui_rpc_auth.cfg file into the data directory.

Another thing you can try is to actually add a password into the file. Can be anything.
Just don't end with a carriage return (Enter). Just fill in a password on the first line and save the file.

Then in BOINC Manager do File->Select computer, fill in localhost and the password, click OK.
If all's well, this should be done only once.

One last thing you can check is whether there have been any changes to the (Windows) firewall. It may be necessary to set inbound and outbound rules for boinc.exe and boincmgr.exe (and where asked, use tcp port 31416)

---

What you can try is exit BOINC completely, then navigate to the BOINC data directory, remove gui_rpc_auth.cfg and restart BOINC (Manager).
That will put a new empty gui_rpc_auth.cfg file into the data directory.

Another thing you can try is to actually add a password into the file. Can be anything.
Just don't end with a carriage return (Enter). Just fill in a password on the first line and save the file.

Then in BOINC Manager do File->Select computer, fill in localhost and the password, click OK.
If all's well, this should be done only once.

One last thing you can check is whether there have been any changes to the (Windows) firewall. It may be necessary to set inbound and outbound rules for boinc.exe and boincmgr.exe (and where asked, use tcp port 31416)

Ok, I deleted the cfg file and when I restart BOINC it will still not connect until I do File>Select computer>localhost. Once I do that it connects and it creates a new cfg file with what looks like one line of random characters not an empty cfg. I still have to select localhost every time I restart BOINC. Oh well, at least I only have to do it once with each restart.

Thanks

---

As always, please help the OP work out whether the problem is

- client running, but connection failing
- client not starting

I suspect the latter.

Does surprise me a little that no one seems to have an answer for this issue. I would think that it would be an easy one but I guess not.

---

Seems Not.........

I have almost the same problem..........anytime I exit BOINC or reboot the PC in question - I have to manually
reconnect to the local host. This PC has been running BOINC for a long time (since 2014). This problem has
popped up since upgrading to BOINC 7.14.2

My other 3 PCs run fine with no problem. Nothing added to the PC (hardware wise) in about 2 years and no
changes made to the firewall in that time...............

Tried removing and reinstalling - no luck

Not a show stopper but annoying

---

Bueller? Bueller? Bueller?

I can not believe that no one has a fix for this issue.

---

Some months ago one of my PCs went through a period of being very reluctant in re-connecting the BOINC manager with the BOINC client after reboots. Strangely this vanished after one of the hard disks failed, and it wasn't the boot or main data disk, but a small one that I used for data transfer for another job with no obvious links to BOINC or SETI other than being part of the same computer. The only thing I can think is that the failing hard disk was clogging one of the buses with transfer requests and blocking the manager and the client from talking to each other correctly.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

But please check - using task manager or similar - whether the CLIENT (boinc.exe) is running or not. That makes a huge difference to the answer to your question.

But please check - using task manager or similar - whether the CLIENT (boinc.exe) is running or not. That makes a huge difference to the answer to your question.

I restarted the system and checked in task manager. I found that boinctray.exe and boincmgr.exe were running but not boinc.exec. The manager reported that it was "disconnected" I then did a "select computer" in manager and put in localhost. I then closed the manager screen and boinc.exe suddenly appeared in the task manager. Hope that helps.

---

I take it there is no hope in resolving this issue? It is annoying to have to keep reconnecting after every reboot of the system.

---

You've identified the problem. It isn't re-CONNECTING to the client, it's re-STARTING the client - which you are implicitly doing by going through the 'connect to computer' menu. That's designed to happen: if you invoke that menu, and you're connecting to localhost, the Manager automatically starts the client if it isn't running already.

What you need to work out, and what others here might be able to help you with, is why the client isn't starting automatically when you start the machine.

What nobody has mentioned in this thread so far is: Windows 10, BOINC v7.14.2

One more to check off: once you have the machine running, go to the 'Options' menu in Advanced view, and choose 'Other options...'. In the dialog that opens. is the middle checkbox - 'Run the client?' - checked? It needs to be.

You've identified the problem. It isn't re-CONNECTING to the client, it's re-STARTING the client - which you are implicitly doing by going through the 'connect to computer' menu. That's designed to happen: if you invoke that menu, and you're connecting to localhost, the Manager automatically starts the client if it isn't running already.

What you need to work out, and what others here might be able to help you with, is why the client isn't starting automatically when you start the machine.

What nobody has mentioned in this thread so far is: Windows 10, BOINC v7.14.2

One more to check off: once you have the machine running, go to the 'Options' menu in Advanced view, and choose 'Other options...'. In the dialog that opens. is the middle checkbox - 'Run the client?' - checked? It needs to be.

Hi Richard,

Shouldn't that be done automatically upon installing BOINC? I never had to go into it and check to make sure of that. Not on Winders 7 or 10 or Linux either.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Yes, it should. But since Kwalk is having a problem that might be related, it's worth checking.

One more to check off: once you have the machine running, go to the 'Options' menu in Advanced view, and choose 'Other options...'. In the dialog that opens. is the middle checkbox - 'Run the client?' - checked? It needs to be.

DING! DING! DING! And we have a winner. The box was NOT checked. I am not even going to ask how it ever got unchecked after running just fine since 1999. I would have never thought to check that setting as in all the years of running BOINC I have never had to touch that setting. Richard, I owe you at least one virtual beer.

P.S. Just noticed the Union Jack. Make that at least one virtual pint.

---