Bug 1329332 - After upgrading to 24 from 23 boinc client doesn't start/work anymore
Summary: After upgrading to 24 from 23 boinc client doesn't start/work anymore
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: boinc-client
Version: 24
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
Assignee: Laurence Field
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-21 16:02 UTC by Ludovic Hirlimann [:Paul-muadib]
Modified: 2016-05-23 20:06 UTC (History)
7 users (show)

Fixed In Version: boinc-client-7.6.22-4.fc24
Clone Of:
Environment:
Last Closed: 2016-05-23 20:06:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ludovic Hirlimann [:Paul-muadib] 2016-04-21 16:02:32 UTC
Description of problem:

Boinc client doesn(t work anymore, doesn't start.

Version-Release number of selected component (if applicable):

[ludo@Oulanl ~]$ rpm -q boinc-client 
boinc-client-7.6.22-1.fc24.x86_64

[ludo@Oulanl ~]$ cat /etc/redhat-release 
Fedora release 24 (Twenty Four)


How reproducible:

Have boinc configured on 23 and upgrade to 24.



Actual results:


Expected results:

boinc continues running.

Additional info:
[ludo@Oulanl ~]$ sudo systemctl status boinc-client.service 
[sudo] password for ludo: 
● boinc-client.service - Berkeley Open Infrastructure Network Computing Client
   Loaded: loaded (/usr/lib/systemd/system/boinc-client.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since jeu. 2016-04-21 17:37:00 CEST; 22min ago
     Docs: man:boinc(1)
  Process: 20233 ExecStop=/usr/bin/boinccmd --quit (code=exited, status=1/FAILURE)
  Process: 20224 ExecStart=/usr/bin/boinc_client --daemon --start delay 1 (code=exited, status=0/SUCCESS)
 Main PID: 1211 (code=exited, status=1/FAILURE)

avril 21 17:37:00 Oulanl systemd[1]: Starting Berkeley Open Infrastructure Network Computing Client...
avril 21 17:37:00 Oulanl systemd[1]: boinc-client.service: Control process exited, code=exited status=1
avril 21 17:37:00 Oulanl systemd[1]: Failed to start Berkeley Open Infrastructure Network Computing Client.
avril 21 17:37:00 Oulanl systemd[1]: boinc-client.service: Unit entered failed state.
avril 21 17:37:00 Oulanl systemd[1]: boinc-client.service: Failed with result 'exit-code'.


[ludo@Oulanl ~]$ sudo systemctl start boinc-client.service 
Job for boinc-client.service failed because the control process exited with error code. See "systemctl status boinc-client.service" and "journalctl -xe" for details.
[ludo@Oulanl ~]$ journalctl -xe


vril 21 17:59:29 Oulanl polkitd[1169]: Registered Authentication Agent for unix-process:20719:3292269 (system bus n
avril 21 17:59:29 Oulanl systemd[1]: Starting Berkeley Open Infrastructure Network Computing Client...
-- Subject: Unit boinc-client.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit boinc-client.service has begun starting up.
avril 21 17:59:29 Oulanl boinc_client[20727]: 21-Apr-2016 17:59:29 BOINC is initializing...
avril 21 17:59:29 Oulanl boinccmd[20736]: can't connect to local host
avril 21 17:59:29 Oulanl systemd[1]: boinc-client.service: Control process exited, code=exited status=1
avril 21 17:59:29 Oulanl systemd[1]: Failed to start Berkeley Open Infrastructure Network Computing Client.
-- Subject: Unit boinc-client.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit boinc-client.service has failed.
-- 
-- The result is failed.
avril 21 17:59:29 Oulanl audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:i
avril 21 17:59:29 Oulanl systemd[1]: boinc-client.service: Unit entered failed state.
avril 21 17:59:29 Oulanl systemd[1]: boinc-client.service: Failed with result 'exit-code'.


what else can I add to make this bug actionable ?

Comment 1 Bob Tyler 2016-05-15 15:16:26 UTC
would a priority upgrade be possible? I have eight systems to test bata(f24) and boinc on.

Comment 2 Germano Massullo 2016-05-16 14:59:01 UTC
I am glad to announce that I fixed the bug. I wish publicly to thank the Debian BOINC mantainer, Gianfranco Costamagna, for his precious help.
I am doing a few tests and in 2-3 days I will release an official update.

Have a nice day

Comment 3 Ludovic Hirlimann [:Paul-muadib] 2016-05-16 15:53:25 UTC
(In reply to Germano Massullo from comment #2)
> I am glad to announce that I fixed the bug. I wish publicly to thank the
> Debian BOINC mantainer, Gianfranco Costamagna, for his precious help.
> I am doing a few tests and in 2-3 days I will release an official update.
> 
> Have a nice day

what needed fixing ? Also can you look into the boincmgr bug where it coredumps ?

Comment 4 Fedora Update System 2016-05-16 16:22:11 UTC
boinc-client-7.6.22-3.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-2479a25458

Comment 5 Fedora Update System 2016-05-16 18:50:35 UTC
boinc-client-7.6.22-4.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-2479a25458

Comment 6 Fedora Update System 2016-05-17 22:01:10 UTC
boinc-client-7.6.22-4.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-2479a25458

Comment 7 Fedora Update System 2016-05-23 20:05:52 UTC
boinc-client-7.6.22-4.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.