KWSN Orbiting Fortress Forum Index KWSN Orbiting Fortress
KWSN Distributed Computing Teams forum
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Won't connect to localhost - I'm about out of ideas

 
Post new topic   Reply to topic    KWSN Orbiting Fortress Forum Index -> Ye Olde Help Scrolls
View previous topic :: View next topic  
Author Message
Lloyd M.
Prince
Prince


Joined: 02 Mar 2007
Posts: 521

PostPosted: Mon Sep 24, 2007 5:38 pm    Post subject: Won't connect to localhost - I'm about out of ideas Reply with quote

Everyone,
I can't get BOINC to start on my (by far) best shrubber, and I've tried nearly everything I can think of. My apologies to the extent that I'm fuzzy on specifics.

Windoze XP Home (SP2, I think), was operating very, very sluggishly, and I couldn't get it to do a soft restart, so I hit the hard reset. It took a couple of power-off resets to get it to stop complaining about NTLDR being missing, then it finally did a chkdsk, and said something about restoring the registry when it finally booted back up.

Then BOINC wouldn't connect to local host (even with multiple tries), so I did several soft restarts, with no luck.

IE is working fine on the Internet, so I presume my TCP/IP stack is fine.

I downloaded the latest version (5.10.2-something, if I recall correctly) and installed it. It came up with an error message about BOINC something .DLL failing to unregister. I dismissed the error dialog, and installation seemed to proceed normally.

Well, despite a number of tries (just as above), I can't get it to connect to localhost. It keeps timing out. There were some events in my firewall log (the NVIDIA firewall built into the mobo) that had the faint possibility of being related, so I even turned it off.

No luck.

I suppose that doing a complete uninstall/reinstall of BOINC might help, though I really want to make sure I do that right (and I'm not certain of what that is), so I don't lose my work in progress.
_________________
Back to top
View user's profile Send private message
ohiomike
Prince
Prince


Joined: 20 May 2007
Posts: 858
Location: Sometimes

PostPosted: Mon Sep 24, 2007 6:59 pm    Post subject: Re: Won't connect to localhost - I'm about out of ideas Reply with quote

Lloyd M. wrote:
Everyone,
I can't get BOINC to start on my (by far) best shrubber, and I've tried nearly everything I can think of. My apologies to the extent that I'm fuzzy on specifics.

Windoze XP Home (SP2, I think), was operating very, very sluggishly, and I couldn't get it to do a soft restart, so I hit the hard reset. It took a couple of power-off resets to get it to stop complaining about NTLDR being missing, then it finally did a chkdsk, and said something about restoring the registry when it finally booted back up.

Then BOINC wouldn't connect to local host (even with multiple tries), so I did several soft restarts, with no luck.

IE is working fine on the Internet, so I presume my TCP/IP stack is fine.

I downloaded the latest version (5.10.2-something, if I recall correctly) and installed it. It came up with an error message about BOINC something .DLL failing to unregister. I dismissed the error dialog, and installation seemed to proceed normally.

Well, despite a number of tries (just as above), I can't get it to connect to localhost. It keeps timing out. There were some events in my firewall log (the NVIDIA firewall built into the mobo) that had the faint possibility of being related, so I even turned it off.

No luck.

I suppose that doing a complete uninstall/reinstall of BOINC might help, though I really want to make sure I do that right (and I'm not certain of what that is), so I don't lose my work in progress.


The good new is an un-install/re-install shouldn't kill your work. The un-install removes the Boinc programs, but not the project data. The new version should pick up where you left off (in theory).
_________________

Resident Linux fan and credit ho >My Shrubbers<
Proud member of the "Fry a CPU for breakfast club"
Back to top
View user's profile Send private message Visit poster's website
Lloyd M.
Prince
Prince


Joined: 02 Mar 2007
Posts: 521

PostPosted: Mon Sep 24, 2007 7:46 pm    Post subject: Re: Won't connect to localhost - I'm about out of ideas Reply with quote

ohiomike wrote:


The good new is an un-install/re-install shouldn't kill your work. The un-install removes the Boinc programs, but not the project data. The new version should pick up where you left off (in theory).


So I tried the uninstall/reinstall, and I'm still getting the same symptoms.

Now I'm really out of ideas.
_________________
Back to top
View user's profile Send private message
Eaving
Prince
Prince


Joined: 23 Feb 2003
Posts: 694
Location: Portland, Or.

PostPosted: Mon Sep 24, 2007 7:57 pm    Post subject: Reply with quote

Is BOINC running but failing to communicate, or simply failing to run at all?

Boinc has some pretty basic trouble shooting suggestions. Sounds like you may have already tried them, but for the sake of pointing you towards their suggestions

http://boinc.berkeley.edu/trac/wiki/TroubleshootClient
_________________


Last edited by Eaving on Mon Sep 24, 2007 8:03 pm; edited 1 time in total
Back to top
View user's profile Send private message Send e-mail Visit poster's website
JerWA
Prince
Prince


Joined: 01 Jan 2007
Posts: 1497
Location: WA, USA

PostPosted: Mon Sep 24, 2007 7:58 pm    Post subject: Reply with quote

Try connecting remotely. Create two plain text files (no wordpad).

gui_rpc_auth.cfg with a password in it...
remote_hosts.cfg with 127.0.0.1 in it.

Shut down BOINC (all the way) and restart it. See if it will connect to localhost. If not, see if it will connect to 127.0.0.1 (same thing but different approach).

If it still won't work, open a command prompt and run:
Code:
netstat -an -p TCP | find "31416"

You should have a listener on 127.0.0.1:31416. If you don't then BOINC isn't being allowed to open a port, check for firewall stuff. If you do, but there are no connections (timing out or whatever), then the listener is up but something isn't allowing connections to it.

With the command waiting, try opening the manager and connection, and then immediately re-run the netstat command. You should see connection attempts, and if you don't then something is still blocking them/not allowing the listener to actually accept connections.
_________________

Stats: [BOINC Synergy] - [Free-DC] - [MundayWeb] - [Netsoft] - [All Project Stats]
Back to top
View user's profile Send private message Yahoo Messenger MSN Messenger
Lloyd M.
Prince
Prince


Joined: 02 Mar 2007
Posts: 521

PostPosted: Mon Sep 24, 2007 10:13 pm    Post subject: Reply with quote

Thanks to everyone for pitching in to try and help. This is pretty weird, since this computer is working fine otherwise, never had serious problems with BOINC before, and was running BOINC just fine before the error recovery this morning.

JerWA wrote:
If it still won't work, open a command prompt and run:
Code:
netstat -an -p TCP | find "31416"

You should have a listener on 127.0.0.1:31416. If you don't then BOINC isn't being allowed to open a port, check for firewall stuff. If you do, but there are no connections (timing out or whatever), then the listener is up but something isn't allowing connections to it.


Believe it or not, I actually know something about this, though (obviously), not nearly as much as you. I can't make sense of what is going on here, and it didn't help to disable my NVIDIA firewall again. I even checked to make sure that the Windoze firewall was still disabled.

Here it is (certain details obscured for security reasons)

Code:

C:\Documents and Settings\******>netstat -an -p TCP | find "31416"
  TCP    127.0.0.1:2528         127.0.0.1:31416        SYN_SENT

C:\Documents and Settings\******>netstat -an -p TCP | find "31416"
  TCP    127.0.0.1:2529         127.0.0.1:31416        SYN_SENT

C:\Documents and Settings\******>netstat -an -p TCP | find "31416"
  TCP    127.0.0.1:2530         127.0.0.1:31416        SYN_SENT

C:\Documents and Settings\******>netstat -an -p TCP | find "31416"
  TCP    127.0.0.1:2531         127.0.0.1:31416        SYN_SENT

C:\Documents and Settings\******>netstat -an -p TCP | find "31416"
  TCP    127.0.0.1:2532         127.0.0.1:31416        SYN_SENT

C:\Documents and Settings\******>netstat -an -p TCP | find "31416"

C:\Documents and Settings\******>netstat -an -p TCP | find "31416"

C:\Documents and Settings\******>netstat -an -p TCP

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3476           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1028         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1034         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1938         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:3476         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5354         0.0.0.0:0              LISTENING
  TCP    ***.**.**.**:139       0.0.0.0:0              LISTENING
  TCP    ***.**.**.**:2168      17.254.2.129:80        FIN_WAIT_2
  TCP    ***.**.**.**:2171      17.254.2.129:80        FIN_WAIT_2
  TCP    ***.**.**.**:2176      17.254.2.129:80        FIN_WAIT_2
  TCP    ***.**.**.**:2311      204.0.3.66:80          CLOSE_WAIT

C:\Documents and Settings\******>netstat -an -p TCP

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3476           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1028         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1034         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1938         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:2535         127.0.0.1:31416        SYN_SENT
  TCP    127.0.0.1:3476         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5354         0.0.0.0:0              LISTENING
  TCP    ***.**.**.**:139       0.0.0.0:0              LISTENING
  TCP    ***.**.**.**:2168      17.254.2.129:80        FIN_WAIT_2
  TCP    ***.**.**.**:2171      17.254.2.129:80        FIN_WAIT_2
  TCP    ***.**.**.**:2176      17.254.2.129:80        FIN_WAIT_2
  TCP    ***.**.**.**:2311      204.0.3.66:80          CLOSE_WAIT

C:\Documents and Settings\******>netstat -an -p TCP

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3476           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1028         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1034         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1938         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:3476         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5354         0.0.0.0:0              LISTENING
  TCP    ***.**.**.**:139       0.0.0.0:0              LISTENING
  TCP    ***.**.**.**:2168      17.254.2.129:80        FIN_WAIT_2
  TCP    ***.**.**.**:2171      17.254.2.129:80        FIN_WAIT_2
  TCP    ***.**.**.**:2176      17.254.2.129:80        FIN_WAIT_2
  TCP    ***.**.**.**:2311      204.0.3.66:80          CLOSE_WAIT

C:\Documents and Settings\******>

_________________
Back to top
View user's profile Send private message
Lloyd M.
Prince
Prince


Joined: 02 Mar 2007
Posts: 521

PostPosted: Mon Sep 24, 2007 10:16 pm    Post subject: Reply with quote

Eaving wrote:
Is BOINC running but failing to communicate, or simply failing to run at all?


The client won't connect to localhost (or even 127.0.0.1 per Sir Jerwa's suggestion). I don't think it's actually running. Boincmgr.exe is in my processes.

[edit] Thanks for the link to the wiki. That MicroSoft installer cleanup utility didn't actually find any evidence of the old BOINC Client installation[/edit]
_________________
Back to top
View user's profile Send private message
JerWA
Prince
Prince


Joined: 01 Jan 2007
Posts: 1497
Location: WA, USA

PostPosted: Tue Sep 25, 2007 1:44 am    Post subject: Reply with quote

The lack of a listener means the BOINC Manager is not being allowed to open a port (unless you've changed the port it's listening on, which I don't even know how to do). The SYN_SENT message you're getting shows a connection attempt, but the lack of a listener means it isn't possible for that attempt to succeed.

If you look at my own output you will see a 31416 listener, and 2 connections (I assume one is the manager and one is BoincView), the 3 other connections are to systems on the network I monitor.
Code:
netstat -an -p TCP | find "31416"
  TCP    127.0.0.1:1044         127.0.0.1:31416        ESTABLISHED
  TCP    127.0.0.1:3076         127.0.0.1:31416        ESTABLISHED
  TCP    127.0.0.1:31416        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:31416        127.0.0.1:1044         ESTABLISHED
  TCP    127.0.0.1:31416        127.0.0.1:3076         ESTABLISHED
  TCP    192.168.1.200:3074     192.168.1.202:31416    ESTABLISHED
  TCP    192.168.1.200:3075     192.168.1.101:31416    ESTABLISHED
  TCP    192.168.1.200:3077     192.168.1.100:31416    ESTABLISHED


Look in your /program files/BOINC directory for the stderr*.txt files and see if there's anything pertinent in there. If there's too much, close BOINC, clear the files, and open it again then check to see if anything new and interesting showed up.

Other than firewall software, I'm at a loss as to what would prevent BOINC from at least opening a listener. That usually requires a more robust firewall like Comodo, Zone Alarm, etc, that monitors applications and stops them before they can even try.
_________________

Stats: [BOINC Synergy] - [Free-DC] - [MundayWeb] - [Netsoft] - [All Project Stats]
Back to top
View user's profile Send private message Yahoo Messenger MSN Messenger
Lloyd M.
Prince
Prince


Joined: 02 Mar 2007
Posts: 521

PostPosted: Tue Sep 25, 2007 10:16 pm    Post subject: Reply with quote

JerWA wrote:

Look in your /program files/BOINC directory for the stderr*.txt files and see if there's anything pertinent in there. If there's too much, close BOINC, clear the files, and open it again then check to see if anything new and interesting showed up.


Quite a few of these:
Code:

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x004141B3 write attempt to address 0x00C7D000

Engaging BOINC Windows Runtime Debugger...


and these:
Code:

[09/25/07 20:59:40] TRACE [1920]: RPC_CLIENT::init_poll sock = 384

[09/25/07 20:59:40] TRACE [1920]: RPC_CLIENT::init_poll attempting connect

[09/25/07 20:59:40] TRACE [1920]: RPC_CLIENT::init_poll sock = 38



JerWA wrote:

Other than firewall software, I'm at a loss as to what would prevent BOINC from at least opening a listener. That usually requires a more robust firewall like Comodo, Zone Alarm, etc, that monitors applications and stops them before they can even try.


I thought the whole idea of a firewall built into the chipset was that it would be more robust than ZoneAlarm, et al.
_________________
Back to top
View user's profile Send private message
Lloyd M.
Prince
Prince


Joined: 02 Mar 2007
Posts: 521

PostPosted: Wed Sep 26, 2007 1:06 am    Post subject: Got some additional help, and got this figured out! Reply with quote

Well, I set up Skype so I could IM chat with a help volunteer at BOINC. It was a decent hour for him because he was in Australia.

At his suggestion, I tried restore points (none of which worked). The next approach was to reinstall BOINC in a different directory.

That seemed OK, so I tried attaching a project that I haven't attached on this machine yet. Probably not a good move, but it seems to have more or less worked out.

To move over your work in progress, you copy the projects directory (or, in my case, the rest of the old subdirectories in the projects directory, so I wouldn't blow away the project I just attached), the slots directory, and all the XML files in the root BOINC directory.

For some reason, my SETI chicken app went goofy, and the only one I could download was non-graphics. Sigh. They're busy working on something that will be compatible with Vista, first.

Well, at least the BOINC manager isn't complaining any more, and it's a newer version of the SETI app. BOINC IS running fine, and I finally had an excuse to upgrade to the 5.10 client!

We'll see if this hoses up my CPUids
_________________
Back to top
View user's profile Send private message
Sir Papa Smurph
Cries like a little girl
Prince


Joined: 18 Jul 2006
Posts: 4430
Location: Michigan

PostPosted: Wed Sep 26, 2007 3:28 pm    Post subject: Reply with quote

I am not a IT guy but I think you should check your services. I believe that you need rpc Remote Procedure Call to be enabled for boinc to run correctly. I don't know how but one time that caused me the same problem. If you have messed around with your services or had an infection you should check to see if they are all set correctly.
_________________
a.k.a. Licentious of Borg.........Resistance Really is Futile.......
and a Really Hoopy Frood who always knows where his Towel is...
Back to top
View user's profile Send private message
Michelle
Moistened Bint
Prince


Joined: 28 Oct 2004
Posts: 10232
Location: At my desk

PostPosted: Sun Oct 23, 2011 12:43 am    Post subject: Reply with quote

Hi Honeys, I'm home. lol

I was googling 'Boinc won't connect to localhost" and look what I found! #ni-1

I've got Mandriva 10 running on my old machine that I re-inherited from little missy when she got her laptop. Installed boinc and now have the connection problem. Rolling Eyes I'm off to find Remote Procedure Call (whatever that is).
_________________
My brain hurts.
Jammy's Brain Donor.



[img]http://www.katrinashome.com/KWSN_Michelle_counter.php[/img]
Back to top
View user's profile Send private message
Sir Papa Smurph
Cries like a little girl
Prince


Joined: 18 Jul 2006
Posts: 4430
Location: Michigan

PostPosted: Sun Oct 23, 2011 7:45 am    Post subject: Reply with quote

rpc is a windows service. several other services depend on it. You must have it running to run boinc, and a bunch of other stuff
_________________
a.k.a. Licentious of Borg.........Resistance Really is Futile.......
and a Really Hoopy Frood who always knows where his Towel is...
Back to top
View user's profile Send private message
Michelle
Moistened Bint
Prince


Joined: 28 Oct 2004
Posts: 10232
Location: At my desk

PostPosted: Sun Oct 23, 2011 9:29 am    Post subject: Reply with quote

Yep, realised later that it was a windows service. I've uninstalled and reinstalled about 4 times now. Maybe it just doesn't like Mandriva for some reason. I think I've had boinc running in Ubuntu but I really wasn't impressed with it last time I used it.

Tim installed it on the Eee pc he gave me but I've taken it off and put the original operating system back on. Seems okay to use and the webcam worked to take FB pics. lol
_________________
My brain hurts.
Jammy's Brain Donor.



[img]http://www.katrinashome.com/KWSN_Michelle_counter.php[/img]
Back to top
View user's profile Send private message
Sir Papa Smurph
Cries like a little girl
Prince


Joined: 18 Jul 2006
Posts: 4430
Location: Michigan

PostPosted: Sun Oct 23, 2011 2:30 pm    Post subject: Reply with quote

I would be using Ubuntu accept I just can't get the video drivers to install for GPU computing. It is most likely my fault but I can't find the directions to install them that I can understand...

Why somebody doesn't write an installer program is beyond me....
_________________
a.k.a. Licentious of Borg.........Resistance Really is Futile.......
and a Really Hoopy Frood who always knows where his Towel is...
Back to top
View user's profile Send private message
Michelle
Moistened Bint
Prince


Joined: 28 Oct 2004
Posts: 10232
Location: At my desk

PostPosted: Sun Oct 23, 2011 6:10 pm    Post subject: Reply with quote

Haven't got a clue about installing anything on linux myself. Instructions are like a foreign language. I always just download through the software channels because they extract and install.

Downloaded a more up-to-date boinc from Berkeley but couldn't work out how to install. Tim had a go and it didn't work for him either, and he knows a heck of a lot more about linux than I do. I think he's tried every 'flavour'. lol He's using opensuse at the moment and trying to set up a mail server and web server on his computer.

I liked Ubuntu, but not the latest release, so that's why I've got Mandriva on the other computer. It's nice! Mandriva 11 is not as nice as 10 so I've put 10 back on. Might try Fedora again and see how that is now. Mint wasn't bad either. I've tried 8 and 9.
_________________
My brain hurts.
Jammy's Brain Donor.



[img]http://www.katrinashome.com/KWSN_Michelle_counter.php[/img]
Back to top
View user's profile Send private message
Michelle
Moistened Bint
Prince


Joined: 28 Oct 2004
Posts: 10232
Location: At my desk

PostPosted: Sat Oct 29, 2011 6:50 am    Post subject: Reply with quote

Installed openSUSE as I could not get BOINC to connect to localhost in Mandriva. Installing BOINC now so I'll keep fingers crossed and see what happens. It would be nice to get it working on this machine as well as the windows machine. I know I have had it working in linux but it may have been Ubuntu or Mint.
_________________
My brain hurts.
Jammy's Brain Donor.



[img]http://www.katrinashome.com/KWSN_Michelle_counter.php[/img]
Back to top
View user's profile Send private message
Michelle
Moistened Bint
Prince


Joined: 28 Oct 2004
Posts: 10232
Location: At my desk

PostPosted: Sun Oct 30, 2011 5:48 am    Post subject: Reply with quote

Finally got it working in a round-a-bout way. Gave up on openSUSE and decided to try Fedora before trying Ubuntu again.
Wouldn't connect to localhost when opened through the applications menu, but will open when the little cog icon is clicked after going through the maze-like file system to find the right folder.
The little cog icon is now residing on the the task bar, and I've attached to some projects.

I remember the days when KDE desktop was a pain in comparison to the ease and simplicity of Gnome. I guess there's been a huge reversal because KDE Plasma is very nice and Gnome is dreadful and way more difficult to configure (for me anyway).
_________________
My brain hurts.
Jammy's Brain Donor.



[img]http://www.katrinashome.com/KWSN_Michelle_counter.php[/img]
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    KWSN Orbiting Fortress Forum Index -> Ye Olde Help Scrolls All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group
Optimized Seti@Home App | BOINC Stats