| Summary: | sci-misc/boinc-6.12.26-r1 crashes randomly | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Greg Trigg <trigggl> |
| Component: | Current packages | Assignee: | Gentoo Science Related Packages <sci> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | trogdog |
| Priority: | Normal | ||
| Version: | 2008.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Greg Trigg
2011-06-09 17:11:54 UTC
How does boinc crash? Do you have any output from the daemons? (In reply to comment #1) > How does boinc crash? Do you have any output from the daemons? Not sure where the best place is to get that information. I did a quick check of my logs, but didn't find anything that would be useful. All I can say is that all processes owned by boinc stop running, but when I try to start it, it says it's already running. When this occurs, I give the command to stop it and it throws out the "!!" message instead of "[OK]". Then it will start. I haven't noticed it in the past couple of days, so if and when it happens again, I'll see if I can find something a little more specific. (In reply to comment #2) >... When this occurs, I give the command to stop it and > it throws out the "!!" message instead of "[OK]". Then it will start... ...when I give the command, that is. Sounds like bug #320747? There is not much we as Gentoo could do. The boinc code is somehow not particulary clean thus it is more for upstream to fix. Had another one die while I was away for the weekend. (In reply to comment #4) > Sounds like bug #320747? That's from a year ago, is a different version (older than the one that I didn't have a problem with, and not the problem I currently have. I have no problems attaching to projects at all. (In reply to comment #5) > There is not much we as Gentoo could do. > > The boinc code is somehow not particulary clean thus it is more for upstream to > fix. Fair enough. It would be good, though, to know if other Gentoo users are having the same problem. Perhaps we can get boinc-6.10.58 placed back in portage as an alternate to 6.12.26? I bumped the version to 6.12.33 could you try that one? Also i can't restore the 6.10 version as the init scripts were rewritten and thus they wont probably work. If you want you can restore everything from cvs attic (http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sci-misc/boinc/) just browse dead files and history for the scripts/configs. (In reply to comment #7) > I bumped the version to 6.12.33 could you try that one? > Also i can't restore the 6.10 version as the init scripts were rewritten and > thus they wont probably work. > > If you want you can restore everything from cvs attic > (http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sci-misc/boinc/) just > browse dead files and history for the scripts/configs. OK, I tried it on one of my ppc64's and one of my amd64's. It's been running until now, but has just crashed on the ppc64. The amd64 is still going, so far. I have wrote myself a cron job which is pretty effective at restarting boinc when it crashes. Of course, it will restart boinc if it's stopped even if it wasn't because of a crash. I'll post it if anyone wants it. I do request that in the future the old version be left in portage when a new one comes out. Give users the ability to upgrade in their own time. 6.10 to 6.12 is a good example, though the move to baselayout-2 may have prevented it in this case. Seems to be fixed from the comments. |
