Description of problem: Can't start boinc-client as a background service: [root@hp ~]# 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. [root@hp ~]# systemctl status boinc-client.service boinc-client.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) [root@hp ~]# dmesg shows nothing. I can't find anything related to Boinc in /var/log/ The error message given by systemd is uninformative, because it does not tell *which* file or directory is missing. I can start boinc-client with the following command: sudo -u boinc /usr/bin/boinc_client --dir /var/lib/boinc Version-Release number of selected component (if applicable): boinc-client-6.12.43-1.r25218svn.fc17.i686 systemd-44-4.fc17.i686 How reproducible: Always. Steps to Reproduce: 1.# service boinc-client start Actual results: Boinc does not start. Systemd gives uninformative error message No such file or directory. Expected results: Boinc starts as a background process. Additional info:
I preupgraded from F16 to F17 yesterday and also have this problem. I discovered that after renaming: /usr/lib/systemd/system/boinc-client to /usr/lib/systemd/system/boinc-client.service then BOINC started to work again: $ sudo systemctl start boinc-client.service $ systemctl status boinc-client.service boinc-client.service - Berkeley Open Infrastructure Network Computing Client Loaded: loaded (/usr/lib/systemd/system/boinc-client.service; disabled) Active: active (running) since Tue, 15 May 2012 14:09:08 -0300; 2s ago Process: 11646 ExecStartPre=/bin/sleep 1 (code=exited, status=0/SUCCESS) Main PID: 11648 (boinc_client) CGroup: name=systemd:/system/boinc-client.service ├ 11648 /usr/bin/boinc_client --dir /var/lib/boinc └ 11654 ../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.88_x86_64-pc-... I concluded that there should be an issue with the spec file in the transition from SysV to systemd.
Created attachment 586878 [details] Patch to rename the systemd service file This patch to the spec file renames the systemd service file with .service extension
Pay attention,because mv /usr/lib/systemd/system/boinc-client{,.service} is not sufficient, because in this way boinc start, but does'nt works. You must apply the patch that is in this page to the .spec file, and rebuild the rpm files. Further there is a second bug: even if boinc-client is enabled, the service does not start at boot, and you must start it (every boot) with systemctl start boinc-client.service To solve this problem, in the file /usr/lib/systemd/system/boinc-client.service, change After=network.target graphical.target in After=network.target See http://www.mathhelp.eu/software/boinc/boinc.html for the full patch.
(In reply to comment #1) > I preupgraded from F16 to F17 yesterday and also have this problem. > > I discovered that after renaming: > > /usr/lib/systemd/system/boinc-client > > to > > /usr/lib/systemd/system/boinc-client.service > > then BOINC started to work again: When simply renaming the file, the boinc service can work but the boincmgr can not connect to it. It's better to use a symbolic link: ln -s /usr/lib/systemd/system/boinc-client /usr/lib/systemd/system/boinc-client.service
2 days ago I contacted the package mantainer, he is working on it, soon we will get a patch
>To solve this problem, in the file > /usr/lib/systemd/system/boinc-client.service, change > After=network.target graphical.target > in > After=network.target > > See http://www.mathhelp.eu/software/boinc/boinc.html for the full patch. The aim of the graphical.target was to enable the gpu computing : https://bugzilla.redhat.com/show_bug.cgi?id=754600 Nevertheless, even if it has been working at the beginning, the service now starts but die immediately. If somebody has an idea, please tell me. I can do some tests if needed. Thanks
(In reply to comment #6) > >To solve this problem, in the file > > /usr/lib/systemd/system/boinc-client.service, change > > After=network.target graphical.target > > in > > After=network.target > > > > See http://www.mathhelp.eu/software/boinc/boinc.html for the full patch. > > The aim of the graphical.target was to enable the gpu computing : > https://bugzilla.redhat.com/show_bug.cgi?id=754600 > > Nevertheless, even if it has been working at the beginning, the service now > starts but die immediately. If somebody has an idea, please tell me. I can > do some tests if needed. > Thanks For me it is the opposite. With "graphical.target" in /usr/lib/systemd/system/boinc-client.service boinc-client, although enabled, doesn't start at boot. Without "graphical.target" boinc.client starts at boot, if enabled. It can depend on grub options in the kernel line? But I tried it on a desktop with akmod nvidia and on a notebook with ati free driver, and it is the same. N.B. I tried ln -s /usr/lib/systemd/system/boinc-client /usr/lib/systemd/system/boinc-client.service, but it does not work. It is better to apply the path and rebuild the rpm files.
> to apply the path Excuse me, "to apply the patch"
Hope an official fix will be relased as soon as possible
PING?
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
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).
It is not possible to permanently enable the service by doing systemctl enable boinc-client.service
(In reply to comment #13) > It is not possible to permanently enable the service by doing > systemctl enable boinc-client.service As I wrote, in /usr/lib/systemd/system/boinc-client.service change "After=network.target graphical.target" in "After=network.target"
(In reply to comment #14) > (In reply to comment #13) > > It is not possible to permanently enable the service by doing > > systemctl enable boinc-client.service > > As I wrote, in /usr/lib/systemd/system/boinc-client.service change > "After=network.target graphical.target" in "After=network.target" I was speaking about the patch in Fedora system
(In reply to comment #13) > It is not possible to permanently enable the service by doing > systemctl enable boinc-client.service This also happens to me. The service is enabled according to systemd, but it doesn't start when I boot my pc.
I found this ("dmesg --level=err,warn"): [ 6.640318] systemd[1]: Found ordering cycle on graphical.target/start [ 6.640333] systemd[1]: Breaking ordering cycle by deleting job boinc-client.service/start
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.