No outgoing rpc on openSuse11.2 64bit, error -102 from handler

Message boards : Questions and problems : No outgoing rpc on openSuse11.2 64bit, error -102 from handler
Message board moderation

To post messages, you must log in.

AuthorMessage
Urs Echternacht

Send message
Joined: 15 Dec 05
Posts: 15
Germany
Message 30429 - Posted: 4 Jan 2010, 21:56:04 UTC

Mo 04 Jan 2010 19:13:48 CET [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_messages> <seqno>92</seqno></get_messages></boinc_gui_rpc_request>'
Mo 04 Jan 2010 19:13:48 CET [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><msgs><msg> <project></pro'
Mo 04 Jan 2010 19:13:48 CET [guirpc_debug] got new GUI RPC connection
Mo 04 Jan 2010 19:13:48 CET [guirpc_debug] error -102 from handler, closing socket
Mo 04 Jan 2010 19:13:49 CET [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><auth1/></boinc_gui_rpc_request>'

Using BOINC 6.10.17 (also with 6.10.19 or 6.10.24) installed in my home directory, i get the above error when opening the "Advanced"->"Select Computer..." dialog in Manager.
The upper field in this dialog is greyed out.

There is a remote_hosts.cfg file setup and a custom password set in gui_rpc_auth.cfg .
Several other hosts are reachable via LAN.
From every other host BOINC is able to connect to this host (Windows, Linux or OSX).

Boinc is started through the "run_client" script that came with the installer script.
The problem persists when starting the client with --allow_remote_gui_rpc .
No firewalls or blocked ports are in the way.
This setup has worked ok on several other Linux hosts before.

Who can give me a hint what to lookup beyond the wiki descriptions ? And what problem is the error message pointing at ?
_\|/_
Urs
ID: 30429 · Report as offensive
ziegenmelker

Send message
Joined: 24 Sep 05
Posts: 10
Germany
Message 30442 - Posted: 6 Jan 2010, 22:34:38 UTC - in response to Message 30429.  

Got exactly the same problem.

OpenSuse 11.2 32-bit after a fresh install. Worked fine with 11.0. No chance to enter an url or ip in the host-field. The computer is accessible for rpc connections from my other hosts.

cu,
Michael
ID: 30442 · Report as offensive
Urs Echternacht

Send message
Joined: 15 Dec 05
Posts: 15
Germany
Message 30465 - Posted: 8 Jan 2010, 22:38:14 UTC - in response to Message 30451.  


It looks like this problem has stumped all of us who try to help with problems. Maybe Ageless can ask Rom to have a look at it.


Thanks for at least having a thought about the problem.
Don't wanted to irritate anybody here.

Maybe one additional bit of information from the wiki / code : error -102 means ERR_READ.

My guess is, if interpreting the debug output i posted before, that the handler is not able to read something.

_\|/_
Urs
ID: 30465 · Report as offensive
ziegenmelker

Send message
Joined: 24 Sep 05
Posts: 10
Germany
Message 30474 - Posted: 9 Jan 2010, 13:00:16 UTC - in response to Message 30465.  

I re-checked all permissions - no problems found.

I start the client through a self-made init-script as user boinc, member of group boinc in /usr/local/boinc/BOINC.

The init script is used on all my other hosts too.

Boinc-Manager is startet from me (micha:users) in the BOINC directory.

I belong to the group boinc too.

Remote hosts are configured in the file '~/.BOINC Manager' and of cause the manager has access to this file.

Afaik the boincmgr is an independent programm without the need of an installed or running boinc client. Usually you can start the manager in any directory and contact a different host with url/pwd or ip/pwd.

So I think it's not a file access problem. Is it possible that some api call changed in KDE 4?

Last thing I could do is to compile my own client and manager on that host.

cu,
Michael
ID: 30474 · Report as offensive
Urs Echternacht

Send message
Joined: 15 Dec 05
Posts: 15
Germany
Message 30499 - Posted: 12 Jan 2010, 15:45:35 UTC

Had a look at the sources to find out what BOINC tries to read and can't. The error ERR_READ is thrown when the rpc handler wants to read from "sock" (possibly the network socket). Will check, if its permissions have changed compared to previous versions of OpenSuse11.
_\|/_
Urs
ID: 30499 · Report as offensive
Urs Echternacht

Send message
Joined: 15 Dec 05
Posts: 15
Germany
Message 30504 - Posted: 12 Jan 2010, 21:22:56 UTC

This is from systems /dev/stderr logfile:

X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x38006d2
12-Jan-2010 22:13:51 [---] [guirpc_debug] error -102 from handler, closing socket

It seems connected, always if i try with <guirpc_debug> set in cc_config.xml to call the menu "Advanced -> Select Computer ..." i can find this X Error neighbouring in the log.

Still don't know what the problem is and keep searching...
_\|/_
Urs
ID: 30504 · Report as offensive
Urs Echternacht

Send message
Joined: 15 Dec 05
Posts: 15
Germany
Message 30629 - Posted: 23 Jan 2010, 14:36:28 UTC

In this other thread the [ComputerMRU] list was the solution to the question/problem.
Looks like in the case here this also solves the problem : On New Install BOINC did not create the [ComputerMRU] list inside of .BOINC Manager file.
Adding this section to the file manually solved the problem.
Selecting other hosts running BOINC now works.

The possible bug :
Why did BOINC not create this section of that .BOINC Manager file ?
_\|/_
Urs
ID: 30629 · Report as offensive
ziegenmelker

Send message
Joined: 24 Sep 05
Posts: 10
Germany
Message 30674 - Posted: 25 Jan 2010, 12:56:35 UTC - in response to Message 30629.  
Last modified: 25 Jan 2010, 12:58:18 UTC

I can confirm this solves the problem. I use the same boinc version(6.10.17) on all my hosts, but the one with the problem is the only one with a fresh install. All other hosts were upgraded or the manager is not used, so I don't know with which version the problem occurred.

cu,
Michael

[edit] All other hosts run a different OpenSuse version too.
ID: 30674 · Report as offensive

Message boards : Questions and problems : No outgoing rpc on openSuse11.2 64bit, error -102 from handler

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.