Posts by Milos Jakubicek

1) Message boards : Questions and problems : What do I do to configure my firewall? (Message 26710)
Posted 20 Aug 2009 by Milos Jakubicek
Post:
Hello bridgemaker,

I'm the Fedora package maintainer of BOINC. I'm not aware there should be any outstanding problems regarding firewall/SELinux/anything that should prevent BOINC to work out of the box at this time on Fedora 10/11/rawhide.

It would be helpful if you'd turn on all the debug flags in cc_config.xml as Kathryn suggested and post the results here so that we could see precisely at what point the communications breaks.

Regards,
Milos
2) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 19840)
Posted 30 Aug 2008 by Milos Jakubicek
Post:

But I think something about the problems the NetworkManager is causing should be written in the WIKI and/or the next version of BOINC for f9 should do something to avoid this problem to make it easier for new linux users to use BOINC with startup during boot with f9.


Please keep in mind that as far you're the only one experiencing such problems and that we still do not know very much about why it takes so long to bring up your network (...have you at least already test the DHCP response as I suggested?). And that the very reason of this problem is on BOINC side being not capable to use newly available connections, hopefully _this_ will be fixed soon (6.4).
3) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 19581)
Posted 19 Aug 2008 by Milos Jakubicek
Post:
[code][mex@localhost ~]$ time /sbin/ifup eth0
Benutzer können dieses Gerät nicht steuern.

real 0m0.080s
user 0m0.012s
sys 0m0.014s
[mex@localhost ~]$ su
Passwort:
[root@localhost mex]# time /sbin/ifup eth0

IP-Informationen werden für eth0 bestimmt...dhclient(2177) is already running - exiting.


Of course you have to bring the network down first if it is already running. First type "/sbin/ifdown eth0" and then "time /sbin/ifup eth0" -- as root, naturally.
4) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 19373)
Posted 9 Aug 2008 by Milos Jakubicek
Post:
[mex@localhost ~]$ time ifup eth0
bash: ifup: command not found


Ifup is placed under /sbin which is by default not included in $PATH (hence you have to type "/sbin/ifup").


PS: I am sure the problem originates from some ugly patch f9 has applied to itself during installation on my V5535 :rollingeyes:


I doubt this will be the reason as it would affect more users, not only you as it seems to be as far.
5) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 19288)
Posted 7 Aug 2008 by Milos Jakubicek
Post:

Currently I need at least "sleep 12" for boinc-client, which is ~ the time f9 needs to finish boot and I need to login & start boinc-manager.


OK, but maybe we could narrow the problem a bit if you'd try whether it's really caused by slow DHCP response or not. FYI I'm using V3550 and I can't remember about waiting for DHCP longer than 3 seconds on ethernet (wifi takes usually longer -- about 3 seconds to associate and next 3 waiting for DHCP response).
6) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 19179)
Posted 5 Aug 2008 by Milos Jakubicek
Post:
Mex, please, could you try changing the following line in the *original* init script:

# Required-Start: $network

into

# Required-Start: $network $named


This is ugly as normally desktops don't run DNS server.


I'm unsure whether this facility indicates running a named (e.g. bind). In the LSB specification one can read:

$network: basic networking support is available. Example: a server program could listen on a socket.

$named: IP name-to-address translation, using the interfaces described in this specification, are available to the level the system normally provides them. Example: if a DNS query daemon normally provides this facility, then that daemon has been started.

Hence $named indicates rather resolution-ready system than running named daemon, doesn't it?


Rather than straight sleeping for 12 seconds, one could implement a search for default route to appear. With optional max delay, such as this:


Of course this is possible, but I still think there should be a more clean solution -- the very cleanest is to fix this ugly bug in the boinc client, but this doesn't seem to happen soon :(
Mex's problem still has a more-or-less acceptable solution, as opposed to the situation when the network is really not available at the boot and appears later (laptop & wireless)...


Mex, I wonder if you're using static IP addresses or DHCP assigned ones? I've seen quite long network startup times when DHCP was in play ... sometimes DHCP servers just take some time to respond.


I assume it to be so (slow DHCP response) -- but 12-15 seconds are too many in any case.
7) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 19167)
Posted 4 Aug 2008 by Milos Jakubicek
Post:
Back to the Mac problem...


PS: "power-pc-linux-gnu" doesn't look right !
( I would expect ppc instead of pc or powerpc without -pc )
Can it be that there is a faulty platform name in the RPM ?


That's definitely not correct, it should be "powerpc-linux-gnu" according to what Kathryn told me (and what is on http://boinc.berkeley.edu/trac/wiki/BoincPlatforms) -- seems that the config.guess doesn't recognize the platform correctly. I've rebuilt boinc (still 5.10.45) with --with-boinc-platform=powerpc-linux-gnu and ppc64-linux-gnu respectively, please try the new RPM from:

http://koji.fedoraproject.org/koji/buildinfo?buildID=58570

Besides that, please read http://boinc.berkeley.edu/trac/wiki/BuildMacApp (however I don't know how much the information there is up to date).
8) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 19156)
Posted 4 Aug 2008 by Milos Jakubicek
Post:
Mex, please, could you try changing the following line in the *original* init script:

# Required-Start: $network

into

# Required-Start: $network $named

I'm pretty curious whether this could solve your problem (without needing any further delays etc.)

Anyway its really strange to me that your network takes so long to come up. Did you measure how long does it take indeed (the best way is probably to boot up without networking and then type "time ifup eth0" -- assuming you're using the eth0 interface of course)?
9) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 19075)
Posted 2 Aug 2008 by Milos Jakubicek
Post:

So not the client needs to be modified, only the RPM for f9 needs to be modified in a way that makes sure that boinc is started as a demon AFTER the access to the www has been initialized ... or the wiki needs a new instruction how to start the client during startup as a demon if the user has the same problems with a delay of the initialisation of the network.


Once again: the client indeed NEEDS to be modified. It's a known issue that it cannot use newly available connections after its start. I've just got a message from Frank S. Thomas (who is the maintainer of the debian packages of boinc) that this should be fixed by the asynchronous GUI RPC in BOINC 6.4.

As a workaround for now I'll modify the init script to wait for the network or named facility -- this should solve the issue in your case but it cannot solve the problem generally (the most troubles regarding this come from laptop users migrating all the time between various wireless connections while not restarting their machines often but using suspend to ram/disk instead of it).

I'll release new package together with new BOINC 6...hopefully soon, I'm just waiting for the 6.2.15 bugfix release.
10) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 18926)
Posted 29 Jul 2008 by Milos Jakubicek
Post:

What happens if you choose "Retry communication" from the menu after booting up *without* restarting the client? Does it work then? If the main problem is really that your network is not ready when starting the service, this should help. Otherwise I'm afraid it must be caused by something else.


Hm, I just have to correct myself: it SHOULD, but DOESN'T!
See http://lists.alioth.debian.org/pipermail/pkg-boinc-devel/2007-November/001063.html

I couldn't find the relevant ticket in BOINC trac although from the debian report I assume that it has been reported upstream. Has this ever been solved?
(I can still reproduce it on my machine with 5.10.45)
Actually I think that rather than hacking with any delays in boinc init script we should ensure that the client uses the connection (even after some delay) when it is available, hm?
11) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 18924)
Posted 29 Jul 2008 by Milos Jakubicek
Post:

As the client cant find a application for my PPC64 with Linux, it is possible that the name of the platform for which the client is requesting a application is not correct. Please check this on another PPC64 hardware with Linux (for example a old Macintosh with PPC64 and Fedora9).

Ah yes, I agree this could be the case (I already had to deal with a similar problem for i386), however I don't have access to any PPC machine.
What's the content of the line starting with:
"Starting BOINC client version 5.10.45 for"
on your PPC/PPC64 machine?
(it is e.g. i686-pc-linux-gnu on an i386 machine)

Next time I boot my notebook, I will type "chkconfig --list" and post the output BEFORE I restart the client, as the current output is after a restart when the client is able to connect to the projects servers.

This doesn't matter: chkconfig --list prints out the settings of installed daemons for all runlevels (whether they should be enabled (Ein) or disabled (Aus) at the specified runlevel)

What happens if you choose "Retry communication" from the menu after booting up *without* restarting the client? Does it work then? If the main problem is really that your network is not ready when starting the service, this should help. Otherwise I'm afraid it must be caused by something else.
12) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 18890)
Posted 28 Jul 2008 by Milos Jakubicek
Post:
PS: How do I upgrade to a 6.x version of the client, and will i have to upgrade the manager too if I do this ?

If you want to stick with the package from Fedora, you'll have to wait for Milos to get a new package put together and pushed out to the repositories.


BOINC 6 is still under development, isn't it? I'll upgrade the package as soon as it will become an official stable branch.
13) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 18889)
Posted 28 Jul 2008 by Milos Jakubicek
Post:

I found only one supporting Linux/PowerPC64 (not counting the proprietary? Yoyo or PS3grid which support the PS3 with Cell platforms).
Seems that I will have to contact http://boinc.berkeley.edu/alpha/, join SETI alpha or will have to compile my own client for my PS3 :(

MfG, MEX


You've the client, but you don't have any PPC work units, if I'm right (Kathryn, Eric?) -- so this is solved for me:)

Regarding the other problem (not being able to connect to the network), I'm pretty sure that this is just because networking is not up when the boinc daemon is started. Please type "chkconfig --list" and post the output.
14) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 18803)
Posted 24 Jul 2008 by Milos Jakubicek
Post:

Still the same as in http://boinc.berkeley.edu/dev/forum_thread.php?id=2896&nowrap=true#18725:
"...Scheduler request failed: Couldn't resolve host name"


Ah, sorry, I missed that.

Anyway it seems to be a networking problem. What's the output of "host orbit.psi.edu", for example?

What about the iptables and SELinux? Try stopping iptables ("service iptables stop"), setting SELinux to permissive (as I've already mentioned).

I've also found this thread:
http://setiathome.berkeley.edu/forum_thread.php?id=47663
where someone had similar problem which has been "solved" by setting more verbose debugging output. Could you try the same (see http://boinc.berkeley.edu/trac/wiki/ClientMessages for details how to set other debugging messages) and post the output again?


15) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 18773)
Posted 23 Jul 2008 by Milos Jakubicek
Post:

But then the problem is that this client can't connect to the www and is unable to communicate with projects, download WU or upload results.


What are the error messages? I.e. if you try to attach to a project (e.g. via the manager), what is the output on the messages tab?
16) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 18763)
Posted 23 Jul 2008 by Milos Jakubicek
Post:

I think that link was created by the installer but I'm not sure, it's been a long time since I installed BOINC, maybe I created that link.


The link is created by the package.


I just stumbled across some old notes I made. Those notes mention it's necessary to enable port 31416 to allow remote hosts to connect to the client. Sorry for all the confusion. It's been so long since I installed it and since it's worked trouble free I've never had to review the topic to make repairs.


One thing is the RPC connection, another then the connection to the project website.
17) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 18762)
Posted 23 Jul 2008 by Milos Jakubicek
Post:

To RESTART the client I still have to use su to become root, and even worse: when the client is started at boot it isnt able to connect to the www unless I manually RESTART the client as root :(

MfG, MEX


What project? Isn't it World Community Grid?
18) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 18746)
Posted 22 Jul 2008 by Milos Jakubicek
Post:
Ah, I finally see what's the point, I'm replying to your e-mail on-thread:


I can only start the boinc demon as root !


That's correct -- as for any other daemon.
If you want BOINC to be started automatically at boot, type "chkconfig boinc-client on".


(reading http://fedoraproject.org/wiki/User:Mjakubicek/HowToUseBoinc someone may think that his user rights are good enough for starting boinc)


Hm, I'd have never thought that it can lead to such presumption, but anyway I'll edit the wiki accordingly.


[mex@localhost ~]$ service boinc-client start
bash: service: command not found

Correct, /sbin is not in $PATH on Fedora for regular users.


[mex@localhost ~]$ /sbin/service boinc-client start
Starting BOINC client as a daemon: /etc/init.d/boinc-client: line 165: /var/log/boincerr.log: Keine Berechtigung

Correct too, the only odd thing I see right now is that it should return 4 instead of 0 (which is confusing -- I'll fix that of course and release an update occasionally).
19) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 18744)
Posted 22 Jul 2008 by Milos Jakubicek
Post:
PS: How do I reactivate SELINUX after the test ?

Perhaps "setenforce 1"? Only a guess, since I'm out of unix for over ten years.


Although you're out of unix for such a long time, you still have good expectations;)
20) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ? (Message 18737)
Posted 22 Jul 2008 by Milos Jakubicek
Post:
Hi, sorry for late answer, I didn't set getting e-mail from this forum unfortunately.

>Doesn't deleting gui_rpc_auth.cfg have the same effect?

No, BOINC will create a new one with randomly generated password. The only way is to insert just a newline.

>I hope Eric or Milos will comment here because I'm stumped. I'll be
>installing F9 and BOINC in a few days. Hope I can offer more and better
>advice then but I have a feeling I'm going to run up against the same problem
>MEX is running into.

I'm a bit out of the time now and do not understand what's currently the issue actually:

- The GUI RPC auth problem is hopefully clearly explained on both the wikis (we agreed on merge but I completely forgot about -- will solve this next week).

- I'm not aware of any Upstart related issues and can hardly imagine there are some concerning the BOINC init script which is really simple. Moreover if there would be some, I should experience problems on all the F9 boxes where I've BOINC installed which is not the case.

- What concerns SELinux, a quick way how to check whether SELinux is a reason of any troubles is setting it to permissive mode by typing "setenforce 0" as root and trying whether it works. If still not, then it is SElinux-unrelated for sure.

- Seeing all the hacks you tried I suggest you do a clean install of BOINC again before trying anything else. The package installs all what is needed, creates user & group correctly, sets correct permissions etc. Just remove all boinc packages, install them again, start the service, start the manager and log in using the password from /var/lib/boinc/gui_rpc_auth.cfg.

If problems still persist, post on this thread again what's going on.

Thanks,
Milos


Next 20

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