| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Boinc Manager connection failures |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 9
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello all,
For the past 2 days my Boinc client gets the following errors and exits. Anyone know what is going on? Thanks Mark =========== start error message ============ SIGSEGV: segmentation violation Stack trace (8 frames): ./boinc[0x80938af] [0xffffe400] ./boinc[0x80675e7] ./boinc[0x805d878] ./boinc[0x80831e2] ./boinc[0x80833d2] /lib/libc.so.6(__libc_start_main+0xe5)[0xb7e2f5f5] ./boinc(__gxx_personality_v0+0x165)[0x804bc21] Exiting... ========== end error message ============ |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Some more information would be nice.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Simply put, my machine runs boinc connected to WCG 24x7. It has not been doing anything else for the past week. I have added no new programmes and I don't recall downloading new fixes this past week. So, I dunno. Perhaps I ought to re-boot and see what happens over the next few days?
Mark |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Seems 6c1452.mine.nu is having the same problem. Hummmm.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
From the vanishingly little you have told me, it appears that his problem is entirely different to yours.
OS version, BOINC version, recent changes to your system - give me something to work with, please. You've been around a while, you know what we need to know. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Sorry. There is a lot of data including memory dumps. I don't know where to begin. So, to answer your questions:
"OS version": Linux 2.6.25.18-0.2-pae i686 System: openSUSE 11.0 (i586) KDE: 4.0.4 (KDE 4.0.4 >= 20080505) "release 15.2" "BOINC version": BOINC client version 5.10.45 for i686-pc-linux-gnu "Recent changes to your system" - no changes in the past few months apart from some auto updates. I've re-booted the system. I will wait until there is a further failure before I re-post, unless you suggest more information to post. Perhaps re-booting is all I need. Else I'll swap out my memory to ensure there is no such defect. A pain. Thanks for the help so far. Sorry for the short answers. I am not sure which info to focus on at the moment. Mark |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
So, this crash doesn't happen instantly? In fact, it happens at indeterminate times?
In that case, I would very much like to match up your crash reports with your message log at the time of each crash. "apart from some auto updates" - Never underestimate the destructive power of a trivial update. Some extra questions: is your computer overclocked? Do you have any reason to suspect a hardware issue? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi Didactylos,
I understand what you say about updates - I tend to let yast apply all updates. That could be a source of the problem, I suppose. I don't expect a hardware problem, but you can never tell when a memory fault appears. I've re-booted and if boinc crashes again, II'll swap out the memory and see if that helps. And I'll save the message log too. I don't change the clock speed so there is no worry there (but someday I would like to have a dual processor quad core Xeon 3ghz system running maxed out, but until I win the lotto.....!) ;) I'll update the forum once I have some more news. Thanks for the help so far. Mark |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi Didactylos,
I re-booted my machine and after a number of days, no problems. I suspect there may have been some problem that the re-boot cured. I also blew out the dust from the fans and CPU heatsink. Dust (ie heat) may have been a contributing force. At any rate, thanks for the patience and wise questions. As always, your wisdom is very much appreciated. Kind regards, Mark |
||
|
|
|