Description of problem: after the boinc-client package installation, it doesn't start at the next computer boot. Version-Release number of selected component (if applicable): All version of boinc-client package ( 7.0.36-2 , 7.0.28-1, 7.0.6-1 ) How reproducible: Steps to Reproduce: 1. Install boinc-client 2. Restart your computer 3. ps -e | grep 'boinc' 4. no boinc-client process running Workaround: modifiying the following line (number 27) of the /etc/init.d/boinc-client file like this : # Default-Start: 3 4 5 Validate the change with systemctl enable boinc-client.service
Assignee: bugsquad => mageiaSource RPM: (none) => boinc
Created attachment 3559 [details] It is the boinc-client-init-d file fixed in the boinc-client-7.0.28-1.mga2.src.rpm This file has been tested on the x86_64 architecture with no problem. Normally, this bug is resolved.
Attachment 3559 mime type: application/octet-stream => application/txt
Attachment 3559 mime type: application/txt => application/text-plain
Keywords: (none) => PATCH
The above patch works also perfectly with the 7.0.36-2 version of boinc-client package.
When will it be possible to close the bug ?
I will try to have a look ASAP. Sorry. For now, I'm working on updating BOINC to 7.0.55 in cauldron/3. Thanks for your reports and help!
Status: NEW => ASSIGNED
I would not hesitate to test the 7.0.55 version when it will be out.
I build Mageia 3 packages for the 7.0.56 version of BOINC client. You can look at it by following these links : [url=http://elmondo74.fr/boincrpms/boinc-client-7.0.56-1.mga3.x86_64.rpm]boinc-client-7.0.56-1.mga3.x86_64.rpm[/url] [url=http://elmondo74.fr/boincrpms/boinc-client-7.0.56-1.mga3.x86_64.rpm.digest]boinc-client-7.0.56-1.mga3.x86_64.rpm.digest[/url] [url=http://elmondo74.fr/boincrpms/boinc-manager-7.0.56-1.mga3.x86_64.rpm]boinc-manager-7.0.56-1.mga3.x86_64.rpm[/url] [url=http://elmondo74.fr/boincrpms/boinc-manager-7.0.56-1.mga3.x86_64.rpm.digest]boinc-manager-7.0.56-1.mga3.x86_64.rpm.digest[/url] [url=http://elmondo74.fr/boincrpms/boinc-client-7.0.56-1.mga3.src.rpm]boinc-client-7.0.56-1.mga3.src.rpm[/url] [url=http://elmondo74.fr/boincrpms/boinc-client-7.0.56-1.mga3.src.rpm.digest]boinc-client-7.0.56-1.mga3.src.rpm.digest[/url]
Sorry for the post above . I repost the links (digests are sha256). http://elmondo74.fr/boincrpms/boinc-client-7.0.56-1.mga3.x86_64.rpm http://elmondo74.fr/boincrpms/boinc-client-7.0.56-1.mga3.x86_64.rpm.digest http://elmondo74.fr/boincrpms/boinc-manager-7.0.56-1.mga3.x86_64.rpm http://elmondo74.fr/boincrpms/boinc-manager-7.0.56-1.mga3.x86_64.rpm.digest http://elmondo74.fr/boincrpms/boinc-client-7.0.56-1.mga3.src.rpm http://elmondo74.fr/boincrpms/boinc-client-7.0.56-1.mga3.src.rpm.digest
You can look at my packages by following this link : http://www.mageialinux-online.org/forum/topic-14891+boinc-paquetages.php
I published the lastest version ( 7.0.65 ) of BOINC packages ( http://www.mageialinux-online.org/forum/topic-14891+boinc-paquetages.php ) .
Thank you! I installed the 7.0.65-2 versions from Comment 9 on mga3 and it just works :) It took long time to communicate with bam.boincstats.com, first time timed out, but i do no tknow which end the problem is. My internet comnnection is good. First i tried the current cauldron official version, did not work and i could not quickly figure out where to put the file mentionned in Comment 1. First, after having installed the official repo version i noticed boinc-client was not check marked to run at start in the MCC > System > Start/stop... interface, so i enabled it there. So I cannot tell for sure if .65 does that. Minor problem, both versions: Alla other system tray icons show a menu when I right click them, but the boinc icon need me to keep holding the button and release it over the action i want.
CC: (none) => fri
Seems i was too happy too soon... After reboot i see CPUs get loaded fully, but later they are getting unused. I believe they are not given new jobs. boinc manager say it have contact with the boinc-client but it do not update any status, and despite i suspend or enable all, the load on cpus are not afffected. And boinc-manager do not show the loggin messages tab. If i exit boinc manager and start it again it say another instance is already running. Maybe some file ownership or group member problems?
Weird. I have gkrellm running so i can see each of the 8 virtual CPU in my i7. Only one was fully used for many minutes, while all other virtually resting. Suddenly all was used a couple second, then maybe 20 s virtually no load, then bang all to 100%. Bringing up boinc manager i see it is working, statuses updating etc. Strange lockup. I guess the last process finished and that triggered it to get sane... I will see if it still runs tomorrow.
Yes still 100% But after reboot and not starting boinc manager CPU, usage drops after a while. I can start manager, and client connection is alive, i see projects finish, next start, uploads, etc, but only running half load for half hour now. Remedy: Using the boinc manager menu Activity I suspended and after a few seconds let it run again, and i have 100% load. I spotted in the log that it resetted timers due to time change, see below. But *I* have not changed time... I see journalctl use the same time boinc initially run on, and then suddenly it experience time had backed two hours, which is CET and which rsyslog writes in the old style log. Maybe the time shift confuses it. Next question is why it changed time. And why journal use that 2 hours wrong time. boinc log, see time shift: mån 13 maj 2013 11:23:19 | World Community Grid | Not requesting tasks: project is not highest priority mån 13 maj 2013 11:23:20 | World Community Grid | Scheduler request failed: Couldn't resolve host name mån 13 maj 2013 11:23:40 | | System clock was turned backwards; clearing timeouts mån 13 maj 2013 09:23:41 | World Community Grid | Sending scheduler request: Requested by project. mån 13 maj 2013 09:23:41 | World Community Grid | Reporting 2 completed tasks mån 13 maj 2013 09:23:41 | World Community Grid | Not requesting tasks: project is not highest priority mån 13 maj 2013 09:23:42 | World Community Grid | Scheduler request failed: Couldn't resolve host name mån 13 maj 2013 10:35:58 | World Community Grid | Computation for task GFAM_x3NIE_loopsAmb1_PfMAP2K_w2WATs_0104597_0231_0 finished
I have no problems of CPU load. You may have to tweak your preferences in the boinc manager menu. Concerning permissions problems, you have to have your normal user account to boinc group. For the time problem, sorry but Ihave no idea.
Yes i am in boinc group. If i just leave it alone once it have been running a while (past a time when time shifts?) it seem to be able to run "forever" It seem its time get set wrong during every boot, and later corrected. I just passed another shift: mån 13 maj 2013 16:25:23 | World Community Grid | Reporting 4 completed tasks mån 13 maj 2013 16:25:23 | World Community Grid | Not requesting tasks: project is not highest priority mån 13 maj 2013 16:25:24 | World Community Grid | Scheduler request failed: Couldn't resolve host name mån 13 maj 2013 16:25:39 | | System clock was turned backwards; clearing timeouts mån 13 maj 2013 14:25:40 | World Community Grid | Sending scheduler request: Requested by project. mån 13 maj 2013 14:25:40 | World Community Grid | Reporting 4 completed tasks mån 13 maj 2013 14:25:40 | World Community Grid | Not requesting tasks: project is not highest priority mån 13 maj 2013 14:25:41 | World Community Grid | Scheduler request failed: Couldn't resolve host name World Community grid seem to have unusually bad connections. I am also having problems with BAM, edited resource share have not been updated to client for hours and boots. I also note at start of log, same session: mån 13 maj 2013 16:25:23 | | No config file found - using defaults Is it normal to not have config file? Also in beginning of log i see it knows it use UTC +2 hours initially: mån 13 maj 2013 16:25:23 | | Local time is UTC +2 hours But, in KDE i have time set to UTC exactly. Also syslog use UTC +2, but rsyslog UTC +0. Posted on forum: https://forums.mageia.org/en/viewtopic.php?p=34295 I keep running it and see if some idea comes up here, in forum, in my head or it just get a magical fix from another update.
7.0.65-2 runs great now. Jumping time i see no more, Bug 10122. Minor issues: § If windows have been open during KDE logout, they are restored but can not connect to client. If i close it, and start boinc manager again, it say another instance of BOINC manager is already running, and asks what client to connect to. When i enter the name of my machine it connects OK. So it seem the mechanixm for detecting if it is already running is not working, possibly because the running session paused by KDE could not be restored to running state. § boinc system tray icon need me to keep holding the right mouse button and not release it until i point on the action i want.
Please test boinc-client-7.2.39-1.mga3 from 3/core/updates_testing
Hardware: x86_64 => AllVersion: Cauldron => 3Depends on: (none) => 12129
(In reply to Damien Lallement from comment #17) > Please test boinc-client-7.2.39-1.mga3 from 3/core/updates_testing Thanks Damien. Everyone, please report your testing results on Bug 12129.
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: ASSIGNED => RESOLVEDResolution: (none) => OLD