Reconnecting to localhost.

Message boards : Number crunching : Reconnecting to localhost.
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile kwalk

Send message
Joined: 2 Aug 99
Posts: 29
Credit: 16,535,464
RAC: 3
United States
Message 2001806 - Posted: 9 Jul 2019, 17:07:15 UTC

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.
ID: 2001806 · Report as offensive
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 2001853 - Posted: 10 Jul 2019, 0:15:10 UTC - in response to Message 2001806.  
Last modified: 10 Jul 2019, 0:19:23 UTC

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).
ID: 2001853 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 2001899 - Posted: 10 Jul 2019, 8:31:03 UTC - in response to Message 2001853.  

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.
ID: 2001899 · Report as offensive
Profile kwalk

Send message
Joined: 2 Aug 99
Posts: 29
Credit: 16,535,464
RAC: 3
United States
Message 2001929 - Posted: 10 Jul 2019, 13:27:22 UTC - in response to Message 2001853.  

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.
ID: 2001929 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 2001935 - Posted: 10 Jul 2019, 14:01:49 UTC

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)
ID: 2001935 · Report as offensive
Profile kwalk

Send message
Joined: 2 Aug 99
Posts: 29
Credit: 16,535,464
RAC: 3
United States
Message 2002039 - Posted: 11 Jul 2019, 0:37:20 UTC - in response to Message 2001935.  

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
ID: 2002039 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14655
Credit: 200,643,578
RAC: 874
United Kingdom
Message 2002081 - Posted: 11 Jul 2019, 12:02:05 UTC

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

- client running, but connection failing
- client not starting

I suspect the latter.
ID: 2002081 · Report as offensive
Profile kwalk

Send message
Joined: 2 Aug 99
Posts: 29
Credit: 16,535,464
RAC: 3
United States
Message 2003011 - Posted: 17 Jul 2019, 15:20:02 UTC - in response to Message 2002081.  

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.
ID: 2003011 · Report as offensive
Mithotar
Avatar

Send message
Joined: 11 Apr 01
Posts: 88
Credit: 66,037,385
RAC: 50
United States
Message 2003661 - Posted: 21 Jul 2019, 22:28:03 UTC - in response to Message 2003011.  

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
ID: 2003661 · Report as offensive
Profile kwalk

Send message
Joined: 2 Aug 99
Posts: 29
Credit: 16,535,464
RAC: 3
United States
Message 2004620 - Posted: 28 Jul 2019, 12:15:09 UTC - in response to Message 2003661.  

Bueller? Bueller? Bueller?

I can not believe that no one has a fix for this issue.
ID: 2004620 · Report as offensive
rob smith Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer moderator
Volunteer tester

Send message
Joined: 7 Mar 03
Posts: 22241
Credit: 416,307,556
RAC: 380
United Kingdom
Message 2004639 - Posted: 28 Jul 2019, 16:10:53 UTC

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?
ID: 2004639 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14655
Credit: 200,643,578
RAC: 874
United Kingdom
Message 2004640 - Posted: 28 Jul 2019, 16:17:57 UTC - in response to Message 2004620.  

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.
ID: 2004640 · Report as offensive
Profile kwalk

Send message
Joined: 2 Aug 99
Posts: 29
Credit: 16,535,464
RAC: 3
United States
Message 2005537 - Posted: 3 Aug 2019, 18:26:45 UTC - in response to Message 2004640.  

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.
ID: 2005537 · Report as offensive
Profile kwalk

Send message
Joined: 2 Aug 99
Posts: 29
Credit: 16,535,464
RAC: 3
United States
Message 2008779 - Posted: 22 Aug 2019, 13:40:43 UTC - in response to Message 2005537.  

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.
ID: 2008779 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14655
Credit: 200,643,578
RAC: 874
United Kingdom
Message 2008784 - Posted: 22 Aug 2019, 14:34:54 UTC - in response to Message 2008779.  

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.
ID: 2008784 · Report as offensive
Profile Siran d'Vel'nahr
Volunteer tester
Avatar

Send message
Joined: 23 May 99
Posts: 7379
Credit: 44,181,323
RAC: 238
United States
Message 2008788 - Posted: 22 Aug 2019, 15:12:44 UTC - in response to Message 2008784.  

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
ID: 2008788 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14655
Credit: 200,643,578
RAC: 874
United Kingdom
Message 2008798 - Posted: 22 Aug 2019, 16:16:57 UTC - in response to Message 2008788.  

Yes, it should. But since Kwalk is having a problem that might be related, it's worth checking.
ID: 2008798 · Report as offensive
Profile kwalk

Send message
Joined: 2 Aug 99
Posts: 29
Credit: 16,535,464
RAC: 3
United States
Message 2009019 - Posted: 24 Aug 2019, 1:30:47 UTC - in response to Message 2008784.  
Last modified: 24 Aug 2019, 1:35:17 UTC

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.
ID: 2009019 · Report as offensive

Message boards : Number crunching : Reconnecting to localhost.


 
©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.