Thread '"[error] GUI RPC bind failed: 99" under Debian Etch'

Author	Message
thackert Send message Joined: 23 May 07 Posts: 4	Message 10437 - Posted: 23 May 2007, 17:41:01 UTC I get the above error under Debian Etch (tested with boinc_5.8.16_i686 and also with boinc_5.9.11). With 5.8.16 it is nearly impossible to stop the client, whereas with 5.9.11 it stops automatically with "[error] GUI RPC bind failed: 99" ... :( The only site with the same problem was in Polish (which I can not read nor speak. And after an online translation it was still nearly unintelligible ... :( ). Could someone help me to get my boinc client running again? TIA Thomas. ID: 10437 ·

Metod, S56RKO Send message Joined: 9 Sep 05 Posts: 128	Message 10439 - Posted: 23 May 2007, 18:39:34 UTC - in response to Message 10437. I get the above error under Debian Etch (tested with boinc_5.8.16_i686 and also with boinc_5.9.11). With 5.8.16 it is nearly impossible to stop the client, whereas with 5.9.11 it stops automatically with "[error] GUI RPC bind failed: 99" ... :( Can you check if there's perhaps another programme already using port that BOINC is trying to bind to? Use command netstat -ap as root and check if there's something binding port number 31416. It would be listed in column Local Address and programme using that port would be stated in last column - PID/Program name. Some services are listed using port names rather than numbers. Mapping between number and name is taken from file /etc/services, so you may want to check if there's mapping for port 31416 ... *Metod ...* ID: 10439 ·

thackert Send message Joined: 23 May 07 Posts: 4	Message 10454 - Posted: 24 May 2007, 6:51:13 UTC - in response to Message 10439. Hello Metod, S56RKO, I get the above error under Debian Etch (tested with boinc_5.8.16_i686 and also with boinc_5.9.11). With 5.8.16 it is nearly impossible to stop the client, whereas with 5.9.11 it stops automatically with "[error] GUI RPC bind failed: 99" ... :( Can you check if there's perhaps another programme already using port that BOINC is trying to bind to? Use command netstat -ap as root and check if there's something binding port number 31416. I have tried it (this was one of the things I could read on the Polish page, which I found with $searchengine ... ;) ), but could not find anything ... :( It would be listed in column Local Address and programme using that port would be stated in last column - PID/Program name. Some services are listed using port names rather than numbers. Mapping between number and name is taken from file /etc/services, so you may want to check if there's mapping for port 31416 ... I have not found this port there either ... :( Do you have any other ideas? ID: 10454 ·

Metod, S56RKO Send message Joined: 9 Sep 05 Posts: 128	Message 10470 - Posted: 25 May 2007, 7:46:42 UTC - in response to Message 10454. Last modified: 25 May 2007, 7:48:44 UTC Do you have any other ideas? Huh, I ran out of them :( It's puzzling me as I have several boxes here running Sarge and Etch and I don't any problems whatsoever. Just got one ;) ... You could try to run boinc as root - temporarily of course. If it doesn't complain about the same error, then this would mean that you have something installed that prevents normal users to start certain applications. Not that I'm aware of any such thing that would prevent from user's app to use port 31416, but anyhow. [edit] To run boinc as root, change working directory to the one you have installed boinc into. Then you have two possibilities: use sudo: sudo ./boinc become root using command su and then run boinc as ./boinc You'll get all the logging to terminal window ... *Metod ...* ID: 10470 ·

thackert Send message Joined: 23 May 07 Posts: 4	Message 10491 - Posted: 26 May 2007, 2:46:48 UTC - in response to Message 10470. Last modified: 26 May 2007, 2:49:43 UTC Do you have any other ideas? Huh, I ran out of them :( It's puzzling me as I have several boxes here running Sarge and Etch and I don't any problems whatsoever. I have done a dist-upgrade to SID afterwards, but it does not change anything ... :( Just got one ;) ... You could try to run boinc as root That is really bad ... ;) - temporarily of course. If it doesn't complain about the same error, then this would mean that you have something installed that prevents normal users to start certain applications. Not that I'm aware of any such thing that would prevent from user's app to use port 31416, but anyhow. I have tried it, but I get the same error message ... :( [edit] To run boinc as root, change working directory to the one you have installed boinc into. Then you have two possibilities: use sudo: sudo ./boinc become root using command su and then run boinc as ./boinc Or you can use sux to run graphical progams too ... ;) You'll get all the logging to terminal window ... Yes, but with the same error message and nothing more ... :( It seems that I have to learn iptables to find out if there is filter blocking this port ... :( Many thanks so far Thomas. ID: 10491 ·

thackert Send message Joined: 23 May 07 Posts: 4	Message 10494 - Posted: 26 May 2007, 8:50:58 UTC - in response to Message 10491. Big snip You'll get all the logging to terminal window ... Yes, but with the same error message and nothing more ... :( It seems that I have to learn iptables to find out if there is filter blocking this port ... :( I have to reply to myself, sorry ... :( After loads of hacking, trial&error and searching the boinc sites (where the trouble shooting sites are out of date, I think ... ;) ) it works now ... :) But only, if I use the --no_gui_rpc parameter, for whatever reason ... :( Does it has a special/needed functionality, which I need for whatever reason? Thanks for your helping and happy crunching :) Thomas. P.S.: I am using my old account again, means: As Noize terroR it is running ... ;) ID: 10494 ·

Metod, S56RKO Send message Joined: 9 Sep 05 Posts: 128	Message 10509 - Posted: 27 May 2007, 10:24:51 UTC - in response to Message 10494. Last modified: 27 May 2007, 10:26:25 UTC You'll get all the logging to terminal window ... Yes, but with the same error message and nothing more ... :( It seems that I have to learn iptables to find out if there is filter blocking this port ... :( Actually iptables doesn't prevent a progamme to bind (eg. use) a port. It just blocks access to that particular port from disallowed foreign address. The fact you can not successfully start BOINC even if run as root means that either there's another application running that already bound to that port or you have some other security mechanism preventing BOINC from binding to that port. According to what you wrote earlier there's no application using the port in question and I don't have any experience with security enhancement tools, so I can't help you here ... After loads of hacking, trial&error and searching the boinc sites (where the trouble shooting sites are out of date, I think ... ;) ) it works now ... :) But only, if I use the --no_gui_rpc parameter, for whatever reason ... :( Does it has a special/needed functionality, which I need for whatever reason? Running BOINC using --no_gui_rpc cures symptom but not cause. Running BOINC without being bound to it's GUI RPC port means you can not administer your BOINC remotely - it can be done using BOINC manager or some third party software (eg. BoincView) running on another machine. Other than this BOINC doesn't need this port as it behaves just like any other application that needs net access from time to time (such as Web browser or e-mail client). *Metod ...* ID: 10509 ·

Copyright © 2025 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.