Posts by ziegenmelker

Info	Message
1) Message boards : Questions and problems : Remote settings not written Message 33622 Posted 1 Jul 2010 by ziegenmelker	Installed BOINC 6.10.56(Linux 64 Bit) on my local host and on one remote host. Sadly I'm not able to change the settings(e.g. memory usage or cache) on the remote host with the local manager logged in. Also I need a remote_hosts.cfg, that I did not need before. This is not handy if one doesn't have a dyndns account, but changing ips. Of cause I start all clients with the option -allow_remote_gui_rpc. A different host is still running 6.10.17 without these problems. I can even successfully change settings with my local BOINC-Manager(6.10.56). All my BOINC clients are started through the same init-script and run under a dedicated user with all rights set up correct.
2) Message boards : Questions and problems : No outgoing rpc on openSuse11.2 64bit, error -102 from handler Message 30674 Posted 25 Jan 2010 by ziegenmelker	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.
3) Message boards : Questions and problems : BOINCmgr: Select Computer - Linux Message 30599 Posted 20 Jan 2010 by ziegenmelker	You find them in the (hidden) file ~/".BOINC Manager" in the section '[ComputerMRU]'. example line: 0=www.example.com cu, Michael
4) Message boards : Questions and problems : No outgoing rpc on openSuse11.2 64bit, error -102 from handler Message 30474 Posted 9 Jan 2010 by ziegenmelker	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
5) Message boards : Questions and problems : No outgoing rpc on openSuse11.2 64bit, error -102 from handler Message 30442 Posted 6 Jan 2010 by ziegenmelker	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
6) Message boards : BOINC client : Work not reported if quota reached Message 3829 Posted 10 Apr 2006 by ziegenmelker	BOINC is already up to version 5.2.13, with a new one before too much longer. You could try the latest and see; it's a lot different to the ones you have. Sorry for my typo. :( I meant v. 5.2.x and v. 5.3.x
7) Message boards : BOINC client : Work not reported if quota reached Message 3827 Posted 10 Apr 2006 by ziegenmelker	Hi, I hope this was not mentioned before. ;) With the new faster apps at e@h two of my hosts continuously reach the daily quota. The problem is, that the boinc client does not report finished work any more, so I have to do it manualy. This only happens, if the quota is reached. Uploading is working normally. I use boinc versions 4.2.x and 4.3.x. Is there any workaround or maybe a fix in the future? cu, Michael
8) Message boards : BOINC client : Internet connection: -100% Message 721 Posted 26 Oct 2005 by ziegenmelker	I would check the settings for network availability (make sure it's "always available" and not "based on preferences") and the setting on the web page for "connect every", making sure it's something reasonable (ie; less than 3, preferably less than 1). This sounds very much like a preferences-setting problem somewhere. I can't see any place where to change settings like "network availability". After changing the language of the boinc-client I see what you might mean: File-menue -> run always. But this should not make any difference, because my Windows-boxes all have the same settings (run based on preferences) and they upload there WUs as soon as they are finished. Anyway I will give this a try, i.e. I will change the startup scripts of the boinc client on the Linux-boxes and add the parameter "??". Oh, there isn't one, I can only use 'boinc_cmd --set_network_mode always'. Afair, during the Windows installation I was asked what kind of internet connection is available, under Linux this question never showed up. Finally, my "connect every" settings (0.l and 1.5) are shared between the different boxes. Therefore this can't have any influence.
9) Message boards : BOINC client : Internet connection: -100% Message 719 Posted 25 Oct 2005 by ziegenmelker	I wouldn't edit the client state file because of that value. The connected fraction is currently not used by the client or the server, and on Linux it's always -1, meaning 'unknown', as the value can't be determined on that OS. I already tried, but it didn't change anything but got reset to -1 after the next contact to the scheduler.
10) Message boards : BOINC client : Internet connection: -100% Message 710 Posted 22 Oct 2005 by ziegenmelker	Hi, my two linux-boxes don't upload finished workunits although the hosts are allways connected with the internet. The boinc clients are 4.72 and 5.2.2 and both are started with -return_results_immediately. But they both fetch new work when needed and then they also upload the finished workunits. This seems to be caused by the following, taken out of my 'computer-summary': While BOINC running, % of time host has an Internet connection: -100% Anyone any idea how to get rid of that? cu, Michael

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.