Can't get RPC to work

Questions and Answers : Unix/Linux : Can't get RPC to work
Message board moderation

To post messages, you must log in.

AuthorMessage
Pete Davis
Volunteer tester

Send message
Joined: 22 Jun 00
Posts: 6
Credit: 58,544
RAC: 0
United States
Message 141438 - Posted: 23 Jul 2005, 14:59:35 UTC

I'm trying to run boinc with the -allow_remote_gui_rpc

I assume the Windows BOINC manager will be able to control it.

I've tried with and without a gui_rpc_auth.cfg file and with and without a remote_hosts.cfg file.

In the gui_rpc_auth.cfg all I had was the plain text password. I assume that's correct.

I've tried placing the gui_rpc_auth.cfg in the directory with the binary. I've tried placing it in the directory that the app is run from.

Anyway, regardless, with or without a password, with or without the remote_hosts.cfg, every time I try to connect with BOINC Manager, I get a message:

"The password you have provided is incorrect, please try again."

What am I doing wrong?

Thanks


ID: 141438 · Report as offensive
Michael R. Rogers, II

Send message
Joined: 8 Jul 05
Posts: 3
Credit: 1,006
RAC: 0
United States
Message 142137 - Posted: 24 Jul 2005, 17:12:12 UTC

I had the same issue too. Follow the following steps:

1) Turn off your firewall by running "/etc/init.d/iptables stop". We need to figure out what port BOINCMGR uses so we can add that to our rules to permit the manager to communicate to the server.

2) SELINUX: If, after you turn off your firewall and you still cannot connect, then SELINUX might be blocking the request. Ensure that RPC is enabled.

Note: There is no password, but I would love to figure out how to set it.

So, the questions are thus:

1) What port and protocol does the manager use to communicate to remote servers/clients?
2) How do you set a password?

BR,
Michael

ID: 142137 · Report as offensive
Pete Davis
Volunteer tester

Send message
Joined: 22 Jun 00
Posts: 6
Credit: 58,544
RAC: 0
United States
Message 142199 - Posted: 24 Jul 2005, 18:52:01 UTC - in response to Message 142137.  
Last modified: 24 Jul 2005, 18:55:33 UTC

I'm not doubting you, and I will try as you suggested when I get a chance, but my firewall rules don't disallow any communications between machines inside the network.

The Linux box is my router, so it is running iptables, but as I said, my internal firewall rules don't prevent any communications between the linux box and windows machines. I use samba, telnet, webmin, and a bunch of other network tools to communicate with the linux box and have never had to configure the firewall specifically for any app before.

It doesn't even block icmp packets. In addition, I log any dropped packets and in a quick test, no packets were showing up as being dropped.

As I said, I will try what you suggest when I get a chance (the machine is currently busy performing some work for me for the next 4 or 5 hours). Since you had the same problem, I suspect you're probably right, but I'd be very curious as to how iptables could be blocking it.



Pete
ID: 142199 · Report as offensive
Profile Darryl Baker

Send message
Joined: 2 Oct 00
Posts: 1
Credit: 8,605,533
RAC: 3
United States
Message 147111 - Posted: 4 Aug 2005, 22:30:54 UTC - in response to Message 142137.  

I too have this problem, except I'm on a Solaris box. No iptables problem.

I downloaded the source, even though I'm not much of a c++ programer I was able to figure out some basics:

the primary GUI port is 1043
the alternate GUI port is 31416

the password is kept in a file called "gui_rpc_auth.cfg" one line just the password.
the allowed hosts are kept in a file called "remote_hosts.cfg" just the hostnames one to a line I think.

My problem is both the attempts to bind to the GUI ports fail with a -1 and no other message. Do I need an entry in services? If so what is the service name?
ID: 147111 · Report as offensive
Michael R. Rogers, II

Send message
Joined: 8 Jul 05
Posts: 3
Credit: 1,006
RAC: 0
United States
Message 147675 - Posted: 6 Aug 2005, 0:00:37 UTC

Here's what I did to get it to work from my Fedora Core 4 box:

1) Enable ports 1043 TCP and 31416 TCP in your iptables configuration.
2) Restart iptables.
3) Connect to the IP address, but DO NOT enter a password.

BR,
Michael
ID: 147675 · Report as offensive

Questions and Answers : Unix/Linux : Can't get RPC to work


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