Posts by Urs Echternacht

Info	Message
1) Message boards : Questions and problems : Why could "exceeded limit of 200 slot directories" happen on Linux ? Message 64882 Posted 14 Oct 2015 by Urs Echternacht	Thanks Jord. Will rebuild my Linux client from newer source to get rid of that bug.
2) Message boards : Questions and problems : Why could "exceeded limit of 200 slot directories" happen on Linux ? Message 64878 Posted 13 Oct 2015 by Urs Echternacht	On SL 7.1, 64 bit : How often does/should BOINC 7.6.6 clean up the slot directories / remove empty slots ? Empty slots should be reused somehow, shouldn't they ? Tue 13 Oct 2015 23:57:05 CEST \| SETI@home \| [error] exceeded limit of 200 slot directories Tue 13 Oct 2015 23:57:05 CEST \| SETI@home \| [error] Can't create task for 08jl11aa.22829.16120.438086664200.12.191_2 Tue 13 Oct 2015 23:57:05 CEST \| SETI@home \| [error] exceeded limit of 200 slot directories Tue 13 Oct 2015 23:57:05 CEST \| SETI@home \| [error] Can't create task for 12ja11ac.20991.17002.438086664202.12.211_0 Tue 13 Oct 2015 23:57:05 CEST \| SETI@home \| [error] exceeded limit of 200 slot directories Tue 13 Oct 2015 23:57:05 CEST \| SETI@home \| [error] Can't create task for 12ja11ac.20991.17002.438086664202.12.228_0 Tue 13 Oct 2015 23:57:05 CEST \| SETI@home \| [error] exceeded limit of 200 slot directories Tue 13 Oct 2015 23:57:05 CEST \| SETI@home \| [error] Can't create task for 12ja11ac.20991.17002.438086664202.12.202_0 Situation : 0 - 3 are empty slot directories. 4 - 6 are used slot directories. 7 - 202 are empty slot directories. After removing slots 7 - 202 , host has continued normally but did not reuse empty slot dirs 0 - 3, instead created new ones 7 - 10. Is that how BOINCs slot usage strategy should work ?
3) Message boards : Questions and problems : BOINC and CentOS x64 -how to run? Message 48739 Posted 21 Apr 2013 by Urs Echternacht	You missed the Wink. Claggy it's almost 4 AM and that damned BOINC doesn't run. So I'm not in corresponding state ;) Check http://boinc.berkeley.edu/dev/forum_thread.php?id=8307&postid=48717 for a hint.
4) Message boards : Questions and problems : boincmgr :: Fatal Error: Mismatch between the program and library build versions detected. Message 48717 Posted 20 Apr 2013 by Urs Echternacht	There is also an easier alternative (but i don't think it is recommended) : Download and install BOINC 6.10.58 for your linux version and copy the file "boincmgr" to a place where it is not getting overwritten, maybe you can rename to reflect its version. Now download and install any newer version of BOINC you want. Replace the new file "boincmgr" with the version from BOINC 6.10.58 that you saved before. The version from BOINC 6.10.58 was statically linked, so should work on any linux (with a new enough glibc), and as long as BOINCs old BOINC Manager interface is supported.
5) Message boards : Questions and problems : Two ATI cards on linux(centos6) x86_64,How to use its both? Message 40304 Posted 22 Sep 2011 by Urs Echternacht	For using two ATI/AMD GPU's i had to revert to Cat 11.6 (1.4.1417) driver version. Cat 11.7 or Cat 11.8 didn't detect my second GPU either.
6) Message boards : Questions and problems : No outgoing rpc on openSuse11.2 64bit, error -102 from handler Message 30629 Posted 23 Jan 2010 by Urs Echternacht	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 ?
7) Message boards : Questions and problems : No outgoing rpc on openSuse11.2 64bit, error -102 from handler Message 30504 Posted 12 Jan 2010 by Urs Echternacht	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...
8) Message boards : Questions and problems : No outgoing rpc on openSuse11.2 64bit, error -102 from handler Message 30499 Posted 12 Jan 2010 by Urs Echternacht	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.
9) Message boards : Questions and problems : No outgoing rpc on openSuse11.2 64bit, error -102 from handler Message 30465 Posted 8 Jan 2010 by Urs Echternacht	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.
10) Message boards : Questions and problems : No outgoing rpc on openSuse11.2 64bit, error -102 from handler Message 30429 Posted 4 Jan 2010 by Urs Echternacht	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 ?
11) Message boards : Questions and problems : BOINC 6.10 released to the public Message 28411 Posted 31 Oct 2009 by Urs Echternacht	Two quirks i have with recommended BOINC 6.10.17 on 32bit windows xp sp3 : 1) After network connection was going unwantedly down a "slowly blinking" (2 seconds) popup from system tray icon was going on my nerves ("Network status"). To resolve restarting the client helped. The hint from the popup to do "Advanced->Do network communication" did not work. 2) The option "Advanced->shutdown connected client" repeatable does restart the client on first try. A immediately following second attempt really shuts the client down. No idea why. These are no way showstoppers, but don't work as wanted i guess.
12) Message boards : BOINC Manager : Cannot connect to localhost since updating windows Message 2024 Posted 17 Dec 2005 by Urs Echternacht	Last night before I shut down I installed 5.2.14, did a reboot and everything worked fine. I did a reboot 10 minutes ago and the same problem appeared but in a different way. Instead of showing that manager is "disconnected" on the status bar as per usual, manager just shows that it is "connecting", basically it freezes. Reloading manager does not solve the problem but rebooting does (on occasion!). Just thought I would add this in, waiting patiently for 5.2.15... I've seen the same behaviour when giving 5.2.14 a try under W2KSP4+. It's just frozen and doing nothing. Reverted back to 5.2.13 without problems.
13) Message boards : BOINC Manager : BOINC doesn't work Message 1958 Posted 15 Dec 2005 by Urs Echternacht	The manager window is blank. When I try to attach to a project or to account manager, it replies the BOINC is not connected to a BOINC client, and tells me to use File Select Computer to connect, and mentions local host as an option, which is the only option. Which then says not able to connect to a BOINC client. It should be 'localhost' in one word. And there is a password option that has to be used. Open your BOINC folder (the one you installed BOINC into. It should contain boinc.exe, boincmgr.exe and other stuff.) in windows-explorer and search for a file named 'gui_rpc_auth.cfg'. Open it with a simple texteditor like notepad. What is in the file? There should be a long number with figures and letters in there. If so delete that number. Make sure that there is only one 'return' and nothing else in that file. Save the file and reboot your PC. Now try again. Is a connection to the BOINC Core Client now possible? edited for typos.
14) Message boards : BOINC Manager : BOINC doesn't work Message 1955 Posted 15 Dec 2005 by Urs Echternacht	Version 5.2.13. Win 98 SE. Cable broadband, always connected. As can be read in your previous posts you want to use SETI@home with BOINC. So at first you had to install BOINC. What options did you choose during the installation process: single, shared or service install? Single installation is recommended if you install on your own PC. Shared installation is recommended if you are not the only user of this PC. Service installation will keep BOINC in the background all the time. More options: did you enable or disable BOINC as your primary screensaver? Did you enable or disable BOINC to log on at startup of your machine? All these options were given during the installation procedure. I hope i havn't forgotten any. So during installation you will have to decide how you can use BOINC afterwards. the BOINC manager says it is not connected to a client There are many reasons that could cause this behaviour (shown in the status bar of BOINC-manager). First of all when running SETI@home with BOINC there are running two/three different programs side by side: BOINC-manager (boincmgr.exe), BOINC Core Client (boinc.exe) and the SETI@home application (setiathome_4.18). BOINC-manager is only the interface for the user to handle the Core Client. It can be shut down without shutting down the Core Client or the SETI@home application. BOINC Core Client is actually the program that connects to the servers of the applications like SETI@home. If it is not running then BOINC-manager will show the message it showed you. SETI@home application is at most like the classic client, but without the ability to connect with the SETI@home servers. It is doing the science-work and the screensaver. So check if the BOINC Core Client (boinc.exe) is running when the BOINC-manager shows that message. Maybe a helpfull link for the start: Installing the BOINC Client Software And Participating In A BOINC Powered Project edited for typos and more.
15) Message boards : BOINC Manager : BOINC doesn't work Message 1930 Posted 15 Dec 2005 by Urs Echternacht	If it can't connect to Seti, how the hell does it know how to run? I know I previously connected it to Seti, as it showed in the manager window for a time. Now nothing and no indication of what to do to fix it. I will try to help here, but be warned i do not have much experience in helping others to get BOINC run the way they want it to run. First i need some more information: What version of BOINC are you using (click on 'Help' and 'About BOINC Manager...')? What operating system are you using BOINC with (Windows .., Linux .., Mac.., others)? What kind of internet-connection are you using (DSL, Broadband, Dial-up, others)? edited for typos.

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.