Hi,

I installed BOINC 4.25/4.26 instead of the 4.19 CC (after uninstalling 4.19).

If I start the BOINC Manager a blank GUI appears - all projects are "gone" no work units are shown in the GUI.

If I try to attach to a project nothing happens. There are only some messages written to different log files.

I'm using WinXP SP2.

stderrdae.txt
2005-03-13 20:17:29 [---] GUI RPC bind failed: -1
gstate.init() failed: -180

stdoutdae.txt
To pause/resume tasks hit CTRL-C, to exit hit CTRL-BREAK
2005-03-13 20:17:29 [---] Starting BOINC client version 4.26 for windows_intelx86
2005-03-13 20:17:29 [Einstein@Home] Using your default project prefs
2005-03-13 20:17:29 [ProteinPredictorAtHome] Using your default project prefs
2005-03-13 20:17:29 [SETI@home] Using your default project prefs
2005-03-13 20:17:29 [---] Version Change Detected (4.19 -> 4.26); running CPU benchmarks
2005-03-13 20:17:29 [Einstein@Home] Host ID is 73215
2005-03-13 20:17:29 [ProteinPredictorAtHome] Host ID is 73454
2005-03-13 20:17:29 [SETI@home] Host ID is 641600
2005-03-13 20:17:29 [---] General prefs: from SETI@home (last modified 2004-10-21 22:50:48)
2005-03-13 20:17:29 [---] General prefs: using separate prefs for home
2005-03-13 20:17:29 [---] GUI RPC bind failed: -1

stdoutgui.txt
Windows Socket Error '10061'
Error: Failed to display HTML document in utf-8 encoding
Error: Failed to display HTML document in utf-8 encoding
Error: Failed to display HTML document in utf-8 encoding
Error: Failed to display HTML document in utf-8 encoding
Error: Failed to display HTML document in utf-8 encoding
Windows Socket Error '10061'
Ermittlung des BOINC-Systemstatus. Bitte etwas Geduld ...
Windows Socket Error '10061'
Ermittlung der BOINC-Rechner-Informationen. Bitte etwas Geduld ...
Windows Socket Error '10061'

Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Error: Failed to display HTML document in utf-8 encoding
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Windows Socket Error '10061'
Error: Failed to display HTML document in utf-8 encoding


Can anybody explain what happens and how I can solve the problem.
Uninstalling the client doesn't have any affect.

Thanks for your help.

Greetings
Stefan

---

<img src="http://www.boincstats.com/stats/banner.php?cpid=710c1e51b47b1aa3c4b24b13251cb271"> <img src="http://www.boincstats.com/stats/teambanner.php?teamname=armageddon">

I'm not an expert.


that said, it sounds like the boinc gui can't access your network.

I use Mcafee firewall. When I installed Boinc CC Versions 4.60, 4.20 through 4.26 I get prompted twice by Mcafee when launching the manager for the first time. Once to allow the manager access to the network and then again by the service.

Did you give both of these access?

tony

---

Ports have changed. It's 1043 now days instead of 31xxx or something like that.
And client is called boinc.exe nowdays so if you have application firewall you have to update that rule as well.

Other than that you need to start boinc with -allow_remote_rpc_gui command

---

I had the same problem in one machine. In my case it solved after I rebooted.

---

> I had the same problem in one machine. In my case it solved after I rebooted.

I've got the problems again.
The situation is as described next:

1.) Using my Laptop in a company LAN, installing BOINCmngr, runs fine
2.) Restart in company LAN, runs fine
3.) Using the Laptop without any connection:
The boincmanager tells me that it's disconnected!
All units dissapear, nothing happens, no boinc.exe-task is running
Error messages as written above
4.) Using the laptop with a DSL connection (other home network):
The boincmanager tells me that it's disconnected!
All units dissapear, nothing happens, no boinc.exe-task is running
Error messages as written above
5.) Using my Laptop in a company LAN, installing BOINCmngr, runs fine

Installing client 4.19 solves the problem. The old client runs with all units available.

What can I do/change to solve this problem?!

Greetings
Stefan

---

<img src="http://www.boincstats.com/stats/banner.php?cpid=710c1e51b47b1aa3c4b24b13251cb271"> <img src="http://www.boincstats.com/stats/teambanner.php?teamname=armageddon">

> Installing client 4.19 solves the problem. The old client runs with all units
> available.
>
> What can I do/change to solve this problem?!

It sounds to me like something is using the officially, IANA-assigned port that BOINC uses. When BOINC tries to load, something else has already bound (occupied) the port.

4.19 uses the old, unofficial 31416.

The official port is 1043.

---

> 4.19 uses the old, unofficial 31416.
>
> The official port is 1043.

Eventually I want to set up something so I can "FILE - Select Computer" on my laptop at work and check up on my crunchers at home. My son tells me I need to set up "Port Forwarding" or "Port Triggering" in my router at home. My router wants a beginning and ending port... is this the port I use for both of those values? I need to do some reading up on this...

Thanx, Skip

>
> > Installing client 4.19 solves the problem. The old client runs with all
> units
> > available.
> >
> > What can I do/change to solve this problem?!
>
> It sounds to me like something is using the officially, IANA-assigned port
> that BOINC uses. When BOINC tries to load, something else has already bound
> (occupied) the port.
>
> 4.19 uses the old, unofficial 31416.
>
> The official port is 1043.
>
ActiveSynch is notorious for this. It will grab every port that is not already used by some other program :(

---

BOINC WIKI

> > 4.19 uses the old, unofficial 31416.
> >
> > The official port is 1043.
>
> Eventually I want to set up something so I can "FILE - Select Computer" on my
> laptop at work and check up on my crunchers at home. My son tells me I need
> to set up "Port Forwarding" or "Port Triggering" in my router at home. My
> router wants a beginning and ending port... is this the port I use for both of
> those values? I need to do some reading up on this...
>
> Thanx, Skip

If you use 4.25 or later, the starting port is 1043 and the ending port is 1043.

Every time you open a port (port forwarding or port triggering) you expose your machines to the internet a little bit more.

I'd use the WAP statistics instead.

---

> If you use 4.25 or later, the starting port is 1043 and the ending port is
> 1043.
>
> Every time you open a port (port forwarding or port triggering) you expose
> your machines to the internet a little bit more.
>
> I'd use the WAP statistics instead.

Thanx for the answer.

What are "Wap Statistics"?

---

- da shu @ HeliOS,
"A child's exposure to technology should never be predicated on an ability to afford it."

> > If you use 4.25 or later, the starting port is 1043 and the ending port
> is
> > 1043.
> >
> > Every time you open a port (port forwarding or port triggering) you
> expose
> > your machines to the internet a little bit more.
> >
> > I'd use the WAP statistics instead.
>
> Thanx for the answer.
>
> What are "Wap Statistics"?

There is a link in your account that says "Stats on your cell phone" -- this is intended for a web-enabled cell phone.

If you don't have a web-enabled phone (or don't want to use your airtime) you can use this with a PC-based WAP browser (I found one at http://www.winwap.org) and query SETI.

There are two advantages:

1) you don't need to allow access to your machines from outside.

2) you don't need public IP addresses for your machines.

The other way to do this is to use something like OpenVPN to allow access to your network from outside -- then VPN in.

... but either way, you are going to have to reduce security, and it's something I'd avoid as much as possible.

---

> If you use 4.25 or later, the starting port is 1043 and the ending port is
> 1043.
>
> Every time you open a port (port forwarding or port triggering) you expose
> your machines to the internet a little bit more.

> One of my computers was in this state. I ended up uninstalling, wiping the
> BOINC directory and starting over, and that seemed to work.

Thank you for this advice.
But it also doesn't work.

I tried the following things:
- Uninstall, reboot, new installation --> Status disconnected
- start boinc.exe manually --> GUI RPC bind failed: -1
- check ports --> nothing on 1043, so boinc.exe should run
- disable firewall --> no affect

Maybe it will work when I'm in the company on monday but that's a little bit too much trial and error (now for about two weeks) :-(
So I will quit using BOINC CC 4.25 and go back to 4.19 as long as it is possible to work with that.

Hope that a new stable core client will solve such problems!!!

Thanx for your help & Greetings
Stefan

---

<img src="http://www.boincstats.com/stats/banner.php?cpid=710c1e51b47b1aa3c4b24b13251cb271"> <img src="http://www.boincstats.com/stats/teambanner.php?teamname=armageddon">

> Maybe it will work when I'm in the company on monday but that's a little bit
> too much trial and error (now for about two weeks) :-(
> So I will quit using BOINC CC 4.25 and go back to 4.19 as long as it is
> possible to work with that.
>
> Hope that a new stable core client will solve such problems!!!

Anything can follow from a false premise, and this is a great example.

Originally, BOINC chose a fairly random port, 31416 (okay, it's suspiciously PI-like). What they are supposed to do is ask the IANA for an official assignment, and they've been given that assignment: 1043.

Nothing else is supposed to use port 1043.

It certainly looks like some outlaw piece of software is using port 1043 on your machine.

You can use something like TCPview from http://www.sysinternals.com to see what programs are bound to what ports.

Your suggestion that this has something to do with an "unstable client" is of course false -- it is something else on your machine that is using the assigned BOINC port, and getting there before BOINC can grab it.

---

I used "Active Ports" that shows that 1043 isn't in use.
Not at home with DSL and not at work in the company network.
It's confusing... :-(

Greetings
Stefan

---

<img src="http://www.boincstats.com/stats/banner.php?cpid=710c1e51b47b1aa3c4b24b13251cb271"> <img src="http://www.boincstats.com/stats/teambanner.php?teamname=armageddon">

> I used "Active Ports" that shows that 1043 isn't in use.
> Not at home with DSL and not at work in the company network.
> It's confusing... :-(
>
> Greetings
> Stefan

What happens if you try to start the BOINC service?

Are there any lockfiles in your BOINC directory??

The error you are seeing says that something is preventing BOINC from using port 1043. When you switch to 4.19, it tries for port 31416 and gets it. You switch back to 1043, and you don't.

If it isn't firewall software of some sort, it may be that whatever had port 1043 is no longer using it when you check it with active ports.

---

> Are there any lockfiles in your BOINC directory??
>
> The error you are seeing says that something is preventing BOINC from using
> port 1043. When you switch to 4.19, it tries for port 31416 and gets it. You
> switch back to 1043, and you don't.
>
> If it isn't firewall software of some sort, it may be that whatever had port
> 1043 is no longer using it when you check it with active ports.

The error I have been chasing is:

"2005-02-19 16:28:33 [---] GUI RPC bind failed: -1
gstate.init() failed: -180"

Tracing I have done thru the code in gui_rpc_server.C, basically the cc opens the socket and then tried to bind the socket as per:

addr.sin_family = AF_INET;
addr.sin_port = htons(GUI_RPC_PORT);
addr.sin_addr.s_addr = htonl(INADDR_ANY);

int one = 1;
setsockopt(lsock, SOL_SOCKET, SO_REUSEADDR, (char*)&one, 4);

retval = bind(lsock, (const sockaddr*)(&addr), (socklen_t)sizeof(addr));
if (retval) {
msg_printf(NULL, MSG_ERROR, "GUI RPC bind failed: %dn", retval);
boinc_close_socket(lsock);
lsock = -1;
return ERR_BIND;
}

The bug is reported onn bbugs as per
http://bbugs.axpr.net/bug.php?op=show&bugid=145

The last entry states"

Posted by: link at loganinternational dot com
Date: 12:00 PM 03-18-2005
I have found that LSASS.EXE (local security authentication server) uses ports from 1039 and up. I've seen mine as high as 1045 but it would depend on how many people were logging on at that time.

Therefore, it is entirely possible that port 1043 could be in use or not depending on the time of day and how many people are logging (or logged) on.

This would meet my issues as the problem happens when the machine is starting and logging on.

---

73 de Peter VK3AVE

> Tracing I have done thru the code in gui_rpc_server.C, basically the cc opens
> the socket and then tried to bind the socket as per:
>
> addr.sin_family = AF_INET;
> addr.sin_port = htons(GUI_RPC_PORT);
> addr.sin_addr.s_addr = htonl(INADDR_ANY);
>
> int one = 1;
> setsockopt(lsock, SOL_SOCKET, SO_REUSEADDR, (char*)&one, 4);
>
> retval = bind(lsock, (const sockaddr*)(&addr),
> (socklen_t)sizeof(addr));
> if (retval) {
> msg_printf(NULL, MSG_ERROR, "GUI RPC bind failed: %dn", retval);
> boinc_close_socket(lsock);
> lsock = -1;
> return ERR_BIND;
> }
>
> The bug is reported onn bbugs as per
> http://bbugs.axpr.net/bug.php?op=show&bugid=145
>
> The last entry states"
>
> Posted by: link at loganinternational dot com
> Date: 12:00 PM 03-18-2005
> I have found that LSASS.EXE (local security authentication server) uses ports
> from 1039 and up. I've seen mine as high as 1045 but it would depend on how
> many people were logging on at that time.
>
> Therefore, it is entirely possible that port 1043 could be in use or not
> depending on the time of day and how many people are logging (or logged) on.
>
> This would meet my issues as the problem happens when the machine is starting
> and logging on.

So, I'm guessing that stopping and starting the BOINC service later would probably be a short-term workaround, assuming LSASS doesn't hold on to the port (as others have suggested).

... and a fix in BOINC might be to wait a minute or two and try to bind the port again later.

---

> > Are there any lockfiles in your BOINC directory??
> >
> > The error you are seeing says that something is preventing BOINC from
> using
> > port 1043. When you switch to 4.19, it tries for port 31416 and gets it.
> You
> > switch back to 1043, and you don't.
> >
> > If it isn't firewall software of some sort, it may be that whatever had
> port
> > 1043 is no longer using it when you check it with active ports.
>
> The error I have been chasing is:
>
> "2005-02-19 16:28:33 [---] GUI RPC bind failed: -1
> gstate.init() failed: -180"
>
> Tracing I have done thru the code in gui_rpc_server.C, basically the cc opens
> the socket and then tried to bind the socket as per:
>
> addr.sin_family = AF_INET;
> addr.sin_port = htons(GUI_RPC_PORT);
> addr.sin_addr.s_addr = htonl(INADDR_ANY);
>
> int one = 1;
> setsockopt(lsock, SOL_SOCKET, SO_REUSEADDR, (char*)&one, 4);
>
> retval = bind(lsock, (const sockaddr*)(&addr),
> (socklen_t)sizeof(addr));
> if (retval) {
> msg_printf(NULL, MSG_ERROR, "GUI RPC bind failed: %dn", retval);
> boinc_close_socket(lsock);
> lsock = -1;
> return ERR_BIND;
> }
>
> The bug is reported onn bbugs as per
> http://bbugs.axpr.net/bug.php?op=show&bugid=145
>
> The last entry states"
>
> Posted by: link at loganinternational dot com
> Date: 12:00 PM 03-18-2005
> I have found that LSASS.EXE (local security authentication server) uses ports
> from 1039 and up. I've seen mine as high as 1045 but it would depend on how
> many people were logging on at that time.
>
> Therefore, it is entirely possible that port 1043 could be in use or not
> depending on the time of day and how many people are logging (or logged) on.
>
> This would meet my issues as the problem happens when the machine is starting
> and logging on.
>

When I use TCPView from SysInternals it says that port 1043 is being used by "System:8" and it is listening. This is the system process with PID 8.

When I refresh BoincView and watch TCPView and capture it when BV comes up I get an additional line of;

"System:8 TCP :1539 :1043 SYN_SENT"

I had this problem last week and a reboot solved it. The reboot no longer works and now my Einstein work is late (2 units). I even tried to detach from Seti from the command line. There is nothing in my Event Logs (Win2K) other than Boinc ended.

If this helps anyone please let me know.

Thank you,
Doug

---

<a href="http://www.boinc.dk/index.php?page=user_statistics&amp;project=sah&amp;userid=12439"><img border="0" height="70" src="http://12439.sah.sig.boinc.dk?1"></a>&gt;

I found out, that the problem only occurs, if there is no physical connection to the network (network cable connected)!
Not sure why, but this solve the problem for me.

While I'm out of office I can't use the BOINC Mngr. without any network connection. :-(

Strange but true.

Greetings
Stefan

---

<img src="http://www.boincstats.com/stats/banner.php?cpid=710c1e51b47b1aa3c4b24b13251cb271"> <img src="http://www.boincstats.com/stats/teambanner.php?teamname=armageddon">

I get this bug too ...
and it seems to me it start to happen after latest security updates from Microsoft ...

there is nothing using port 1043, tried disable both Kerio PF and Windows Firewall and also create rules ... result is same ...

there is no virus, trojan, spyware, adware, malware on machine (tested with numerous products)

network is correctly connected ...

71 43.09013855 boincmgr.exe:110 84C03F90 IRP_MJ_CREATE TCP:0.0.0.0:0 Address Open
Address Open SUCCESS
72 43.09027209 boincmgr.exe:110 84C03F90 TDI_SET_EVENT_HANDLER TCP:0.0.0.0:1843 Error Event
73 43.09044390 boincmgr.exe:110 84C03F90 TDI_QUERY_INFORMATION TCP:0.0.0.0:1843 Query Address
Query Address SUCCESS
SUCCESS SUCCESS-74
75 43.09046010 boincmgr.exe:110 84C03F90 TDI_SET_EVENT_HANDLER TCP:0.0.0.0:1843 Disconnect Event
76 43.09058581 boincmgr.exe:110 84C03F90 TDI_QUERY_INFORMATION TCP:0.0.0.0:1843 Query Address
Query Address SUCCESS
SUCCESS SUCCESS-77
78 43.09059867 boincmgr.exe:110 84C03F90 TDI_SET_EVENT_HANDLER TCP:0.0.0.0:1843 Receive Event
79 43.09072298 boincmgr.exe:110 84C03F90 TDI_QUERY_INFORMATION TCP:0.0.0.0:1843 Query Address
Query Address SUCCESS
SUCCESS SUCCESS-80
81 43.09073583 boincmgr.exe:110 84C03F90 TDI_SET_EVENT_HANDLER TCP:0.0.0.0:1843 Expedited Receive Event
82 43.09085959 boincmgr.exe:110 84C03F90 TDI_QUERY_INFORMATION TCP:0.0.0.0:1843 Query Address
Query Address SUCCESS
SUCCESS SUCCESS-83
84 43.09087244 boincmgr.exe:110 84C03F90 TDI_SET_EVENT_HANDLER TCP:0.0.0.0:1843 Chained Receive Event
85 43.09099592 boincmgr.exe:110 84C03F90 TDI_QUERY_INFORMATION TCP:0.0.0.0:1843 Query Address
Query Address SUCCESS
SUCCESS SUCCESS-86
87 43.09100821 boincmgr.exe:110 84C03F90 TDI_QUERY_INFORMATION TCP:0.0.0.0:1843 Query Address
Query Address SUCCESS
88 43.09103839 boincmgr.exe:110 84C79558 IRP_MJ_CREATE TCP:Connection obj Context:0x84C7E268
Context:0x84C7E268 SUCCESS
89 43.09106213 boincmgr.exe:110 84C79558 TDI_ASSOCIATE_ADDRESS TCP:Connection obj TCP:0.0.0.0:1843
TCP:0.0.0.0:1843 SUCCESS
90 43.09125489 boincmgr.exe:110 84C79558 TDI_CONNECT TCP:0.0.0.0:1843 127.0.0.1:1043
127.0.0.1:1043 CONNECTION_REFUSED

---