Hi when I start up run_manager fm the console I get a "connection refused" and then a "get_socket_error(0: 111" error.

My Linux is fully connected and I have no outbound sockets blocked in my firewall. Any suggestion of what is wrong? I can not download any new work now, now that I have to use the BOINC interfaces.
The manager Gui reports that the connection is deferred.... and it keeps trying every 10 mins or so.

Thnx
Frank Kuypers ( fkuypers@caiw.nl)

Can you please try to start the boinc client with the parameter "-allow_remote_gui_rpc" and then try to connect with boinc manager.
If you have not entered a password in "gui_rpc_auth.cfg" the boinc manager setup one automaticly. With change it to a single "Return" in the file, the boinc manager could connect without a password. Also you can enter a password + a return sign, to use this password to connect to the boinc client.

---

Can you please try to start the boinc client with the parameter "-allow_remote_gui_rpc" and then try to connect with boinc manager.
If you have not entered a password in "gui_rpc_auth.cfg" the boinc manager setup one automaticly. With change it to a single "Return" in the file, the boinc manager could connect without a password. Also you can enter a password + a return sign, to use this password to connect to the boinc client.

Hi, I did what you wrote; start the boinc client with the parameter "-allow_remote_gui_rpc" and then try to connect with boinc manager.

and the client seems to be running ok now.

the manager though, can connect as it says "Connect :Operation now in progress", but the initpoll still gives me : "get_socket_error ():11 " and the gui still can not connect...

Pls let me know.
Thnx

Hi, I did what you wrote; start the boinc client with the parameter "-allow_remote_gui_rpc" and then try to connect with boinc manager.

and the client seems to be running ok now.

the manager though, can connect as it says "Connect :Operation now in progress", but the initpoll still gives me : "get_socket_error ():11 " and the gui still can not connect...

Which version of boinc manager and boinc client do you have ?
Have you started the boinc client before the boinc manager ?

Looks strange. If you have entered a single enter or a password and a return after your password, it should normaly work...

Your firewall should allow port 1043 and port 31416 inbound and outbound to localhost.

If this don't help, you could attach manualy to the project with "boinc_client -attach_project http://setiathome.berkeley.edu $ACCOUNT_KEY". - So boinc will attach to the project, and download the seti app. After the seti app was downloaded, the boinc client downloads WUs from the project servers and starts crunching.

---

Hi, I did what you wrote; start the boinc client with the parameter "-allow_remote_gui_rpc" and then try to connect with boinc manager.

and the client seems to be running ok now.

the manager though, can connect as it says "Connect :Operation now in progress", but the initpoll still gives me : "get_socket_error ():11 " and the gui still can not connect...

Which version of boinc manager and boinc client do you have ?
Have you started the boinc client before the boinc manager ?

Looks strange. If you have entered a single enter or a password and a return after your password, it should normaly work...

Your firewall should allow port 1043 and port 31416 inbound and outbound to localhost.

If this don't help, you could attach manualy to the project with "boinc_client -attach_project http://setiathome.berkeley.edu $ACCOUNT_KEY". - So boinc will attach to the project, and download the seti app. After the seti app was downloaded, the boinc client downloads WUs from the project servers and starts crunching.

Hi, I downloaded the latest Linux version this morning ( CET) so I have the most recent one.
The gui_rpc_auth.cfg file only contains one line, with a large alphanumeric string, no further commands or line.

I have started run_client as you said with -allow_remote_gui_rpc as you said and it does talk to the server at the other end...so that seems to be working....in some sort ;-)

Funny thing is there is nowhere where I had to fill in or enter my account name at all...., although it seems to be chatting with my settings on the Seti site....

the socket error stays, but when I say update fm the Gui, the console of the run_client, seems to respond as well,as I can see it did pick up my new settings...

But again...no where did I enter my accountname or key....

---

The gui_rpc_auth.cfg file only contains one line, with a large alphanumeric string, no further commands or line.

You must remove this string in the file and enter here a password followed by a return, or add a single return in this file for no password access from the gui to the client - like I described in my other posts.

I have started run_client as you said with -allow_remote_gui_rpc as you said and it does talk to the server at the other end...so that seems to be working....in some sort ;-)

It is command line only.
The boinc client do the scheduling of the computing, and connects to the project (seti) servers. This is command line only.
From the boinc_client you can attach to each project with "-attach_project". But this is also posible via the boinc manager gui.

But the command line client has a interface which is accessable via the network. You enable this with "boinc_client -allow_remote_gui_rpc". The GUI (boinc manager) has to be started after the command line client, and connects to the boinc manager.

Funny thing is there is nowhere where I had to fill in or enter my account name at all...., although it seems to be chatting with my settings on the Seti site....

Your stats show one computer, which has downloaded one WU. Looks like your system is crunching now.

the socket error stays, but when I say update fm the Gui, the console of the run_client, seems to respond as well,as I can see it did pick up my new settings...

It is caused by the string in gui_rpc_auth.cfg !

But again...no where did I enter my accountname or key....

You have already registerd at the project. It was done with the "boinc_client -attach_project ....".



So you have now following steps to do :
- change the file gui_rpc_auth.cfg, like I suggested you.
- stop and start the boinc client with "boinc_client -allow_remote_gui_rpc"
- start the boinc manager from a other shell
-> now the boinc manager should be able to connect to the boinc_client, and you see, that you are attached to the project, and see in the work tab, that you have a WU in progress.

---

The gui_rpc_auth.cfg file only contains one line, with a large alphanumeric string, no further commands or line.

You must remove this string in the file and enter here a password followed by a return, or add a single return in this file for no password access from the gui to the client - like I described in my other posts.

I have started run_client as you said with -allow_remote_gui_rpc as you said and it does talk to the server at the other end...so that seems to be working....in some sort ;-)

It is command line only.
The boinc client do the scheduling of the computing, and connects to the project (seti) servers. This is command line only.
From the boinc_client you can attach to each project with "-attach_project". But this is also posible via the boinc manager gui.

But the command line client has a interface which is accessable via the network. You enable this with "boinc_client -allow_remote_gui_rpc". The GUI (boinc manager) has to be started after the command line client, and connects to the boinc manager.

Funny thing is there is nowhere where I had to fill in or enter my account name at all...., although it seems to be chatting with my settings on the Seti site....

Your stats show one computer, which has downloaded one WU. Looks like your system is crunching now.

the socket error stays, but when I say update fm the Gui, the console of the run_client, seems to respond as well,as I can see it did pick up my new settings...

It is caused by the string in gui_rpc_auth.cfg !

But again...no where did I enter my accountname or key....

You have already registerd at the project. It was done with the "boinc_client -attach_project ....".



So you have now following steps to do :
- change the file gui_rpc_auth.cfg, like I suggested you.
- stop and start the boinc client with "boinc_client -allow_remote_gui_rpc"
- start the boinc manager from a other shell
-> now the boinc manager should be able to connect to the boinc_client, and you see, that you are attached to the project, and see in the work tab, that you have a WU in progress.

YEP I am fine now, things work as "expected" now.
Thanks a lot for your great help !
Regards fm The Netherlands
Frank Kuypers