LHC@home

Hi everyone. For some reason I can't connect to my server which is running Mandrake 10 with BOINC 4.25 or BOINC View 1.03a. I have BOINC 4.19 installed on Mandrake 10, and the IP for this system is allowed in the IP config. BOINC keeps reporting that it cannot connect to the server, and BOINC View keeps saying that there isn't a BOINC client behind the port 1043.

Firewall on both systems is off, as I have a hardware firewall (router). This system is running Windows XP Pro.

Any ideas?

---

There are a few possible solutions. The problem is probably that 1043 was in use when BOINC started. You can try to restart BOINC, this sometimes helps. You can try a reboot. With 4.32 and later, BOINC uses either 1043 or 31416.

---

BOINC WIKI

> There are a few possible solutions. The problem is probably that 1043 was in
> use when BOINC started. You can try to restart BOINC, this sometimes helps.
> You can try a reboot. With 4.32 and later, BOINC uses either 1043 or 31416.
>

I've restarted BOINC and the system many times, which hasn't seemed to have worked. If I used the port 31416 on BOINC View, it doesn't give me an error saying there isn't a BOINC client under the port but it also doesn't show the BOINC information.

---

try:

# netstat -pl | grep -i boinc

This should list listening ports, and only print one line if boinc is running and listening.
The 4th column of the output should show '*:nnnn' where nnnn is the port on which boinc is listening, either 1043 or 31416.

That will help you determine if BOINC is running and listening for connections.

If it looks good, then take a look at your remote_hosts.cfg file in the boinc directory (on the linux box) and check that it is also okay and allows access from the XP client. If you make any changes to that file, then you must stop and start BOINC before they will take effect.

That's usually all that is needed to manage BOINC remotely.

Post an update if you're still stuck.

> try:
>
> # netstat -pl | grep -i boinc
>
> This should list listening ports, and only print one line if boinc is running
> and listening.
> The 4th column of the output should show '*:nnnn' where nnnn is the port on
> which boinc is listening, either 1043 or 31416.
>
> That will help you determine if BOINC is running and listening for
> connections.
>
> If it looks good, then take a look at your remote_hosts.cfg file in the boinc
> directory (on the linux box) and check that it is also okay and allows access
> from the XP client. If you make any changes to that file, then you must stop
> and start BOINC before they will take effect.
>
> That's usually all that is needed to manage BOINC remotely.
>
> Post an update if you're still stuck.
>

I put that command into konsole while BOINC was running, it didn't show any lines and it didn't give any error messages (it just went to another command line). Does this mean BOINC isn't listening for connections?

---

> I put that command into konsole while BOINC was running, it didn't show any
> lines and it didn't give any error messages (it just went to another command
> line). Does this mean BOINC isn't listening for connections?

Yes, it looks like it's not listening, and as jm7 noted, the reason is probably because something else was holding the port when BOINC started.

Try these to see what is listed:
# netstat -pl (will list all listening ports) (or an error if netstat can't be found)
# netstat -pl | grep -i 31416 (will list what is listening on port 31416)

BOINC 4.19 uses port 31416 IIRC...

> > I put that command into konsole while BOINC was running, it didn't show
> any
> > lines and it didn't give any error messages (it just went to another
> command
> > line). Does this mean BOINC isn't listening for connections?
>
> Yes, it looks like it's not listening, and as jm7 noted, the reason is
> probably because something else was holding the port when BOINC started.
>
> Try these to see what is listed:
> # netstat -pl (will list all listening ports) (or an error if netstat
> can't be found)
> # netstat -pl | grep -i 31416 (will list what is listening on port
> 31416)
>
> BOINC 4.19 uses port 31416 IIRC...
>

Nothing comes up for either of those commands. No error, no port, nothing.

EDIT: Problem solved. My router was playing up, wouldn't accept the connection and crashed about an hour ago reseting everything. The IP on this system changed to 192.168.1.4, and now I can see the BOINC information.

Thanks for all your help!

---