Bug 827912

I'm getting on 2 systems (one fresh install, one upgraded using preupgrade):

[root@ap ~]# service boinc-client start
Redirecting to /bin/systemctl  start boinc-client.service
Failed to issue method call: Unit boinc-client.service failed to load: No such file or directory. See system logs and 'systemctl status boinc-client.service' for details.

Nothing in /var/log/messages

[root@ap ~]# ls -l /usr/lib/systemd/system/boinc-client 
-rwxr-xr-x. 1 root root 345 Feb  8 16:14 /usr/lib/systemd/system/boinc-client

(I do not though know why it is executable)

When I restored the /etc/init.d/boinc-client from a back up, things started to work as expected (please see http://forums.fedoraforum.org/showthread.php?t=280933). I believe the rpm package for boinc-client is defective.

Please excuse the incorrect link in my previous comment. The correct link is http://forums.fedoraforum.org/showthread.php?t=280935. I am sorry for this mistake.

boinc-client-6.12.43-2.r25218svn.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/boinc-client-6.12.43-2.r25218svn.fc17

Same problem with this new verion (at least for me).

Are you saying that the following:

systemctl start boinc-client.service

still errors for you? I can't really believe that, also because of others that confirmed the issue is now fixed.

rpm -qa|grep boinc-client
boinc-client-6.12.43-1.r25218svn.fc17.x86_64

sudo systemctl start boinc-client.service
Failed to issue method call: Unit boinc-client.service failed to load: No such file or directory. See system logs and 'systemctl status boinc-client.service' for details.

May be something went wrong when upgrading... I'll try to force reinstall of the package...

Oh, dear, I didn't notice the 43-1 instead of 43-2 in version.
Has it been submitted to rawhide may be? I haven't it active right now...

Ok, I enable in gpk-application the testing repository and I didn't get the new version either.
I manually downloaded the rpm's and installed them. Now boinc-client starts, but I get a complain from SELinux:

--------------------------------------------------------

SELinux is preventing /usr/bin/boinc_client from read access on the lnk_file stdoutdae.txt.

*****  Plugin catchall (100. confidence) suggests  ***************************

If cree que de manera predeterminada, boinc_client debería permitir acceso read sobre  stdoutdae.txt lnk_file.     
Then debería reportar esto como un error.
Puede generar un módulo de política local para permitir este acceso.
Do
permita el acceso momentáneamente executando:
# grep boinc_client /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:boinc_t:s0
Target Context                system_u:object_r:boinc_var_lib_t:s0
Target Objects                stdoutdae.txt [ lnk_file ]
Source                        boinc_client
Source Path                   /usr/bin/boinc_client
Port                          <Desconocido>
Host                          mallorn.farre.nom
Source RPM Packages           boinc-client-6.12.43-2.r25218svn.fc17.x86_64
Target RPM Packages           
Policy RPM                    selinux-policy-3.10.0-132.fc17.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     mallorn.farre.nom
Platform                      Linux mallorn.farre.nom 3.4.3-1.local.fc17.x86_64
                              #1 SMP Sat Jun 23 20:41:17 CEST 2012 x86_64 x86_64
Alert Count                   5
First Seen                    dom 24 jun 2012 22:35:22 CEST
Last Seen                     dom 24 jun 2012 22:35:27 CEST
Local ID                      12a47b8a-ac14-4ba0-88ed-027d272e6372

Raw Audit Messages
type=AVC msg=audit(1340570127.980:379): avc:  denied  { read } for  pid=13073 comm="boinc_client" name="stdoutdae.txt" dev="md1" ino=125043310 scontext=system_u:system_r:boinc_t:s0 tcontext=system_u:object_r:boinc_var_lib_t:s0 tclass=lnk_file


type=SYSCALL msg=audit(1340570127.980:379): arch=x86_64 syscall=stat success=no exit=EACCES a0=7fc80eaf7e40 a1=7fffb84f94d0 a2=7fffb84f94d0 a3=63 items=0 ppid=1 pid=13073 auid=4294967295 uid=990 gid=983 euid=990 suid=990 fsuid=990 egid=983 sgid=983 fsgid=983 tty=(none) ses=4294967295 comm=boinc_client exe=/usr/bin/boinc_client subj=system_u:system_r:boinc_t:s0 key=(null)

Hash: boinc_client,boinc_t,boinc_var_lib_t,lnk_file,read

audit2allowunable to open /sys/fs/selinux/policy:  Permission denied


audit2allow -Runable to open /sys/fs/selinux/policy:  Permission denied

-------------------------------------------------------------------

Sorry for the parts in Spanish. If you need translation, feel free to ask for it.

Thanks. I'm aware of the SELinux issue, will be fixed today.

Package boinc-client-6.12.43-2.r25218svn.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing boinc-client-6.12.43-2.r25218svn.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-9859/boinc-client-6.12.43-2.r25218svn.fc17
then log in and leave karma (feedback).

I have been working with Kathryn at The BOINC FAQ Service on this problem.  She suggested that I report the bug here (Red Hat Bugzilla).  The problem at BOINC FAQ Service is titled "Disconnected boinc manager in fedora 17" and located here:  http://boinc.berkeley.edu/dev/forum_thread.php?id=7622

I now have BOINC working on my Fedora 17 machine with one notable exception.  I cannot autostart the client.  The command line "systemctl enable boinc-client.service" doesn't autostart boinc-client.  I have to manually start the client with "systemctl start boinc-client.service".

The Fedora 17 installation instructions (located here:  http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Fedora) are not completely accurate.  Also, the missing script indicated in the responses at BOINC FAQ Service was not needed in my case.  Renaming "boinc-client" as installed by yum (su -c 'yum install boinc-client boinc-manager') to "boinc-client.service" was needed however.

Should the boinc-client update indicated in comment 11 fix my autostart problem also?

It should fix starting the client manually, starting it automatically on boot will be fixed by the next update, you might try:

http://koji.fedoraproject.org/koji/taskinfo?taskID=4229099

boinc-client-7.0.29-1.r25790svn.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Client now autostarts after a reset.  The command string "pgrep -l boinc" returns "837 boinc" and "838 boinc_client".

However, there is still a bit of an issue.  When I run Manager after a restart, I get a "Could not connect to client" error window with the following message:

"The BOINC manager could not connect to BOINC client.  The client might not be running or your (sic) not allowed to connect to it.  Please refer to the documentation provided by the link below to learn how to setup the client."

The link is on "How to use BOINC on Fedora".

The message on the bottom right of the Manager window indicates the client is "disconnected".  Closing the error window results in Manager communicating with client.

Every time I start Manager, I get the same error window.  This error window occurs even if I already have Manager running and open a second interation.

RLK