| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Lock-up/Memory Problems |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 22
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Anyone had 'weird' problems on the SN2S project with unknown problems?
Since the re-release of SN2S I have had all my machines on the same project. All the ones here are on 24/7 and the two lappys run only BOINC, no other 'uses' are made of them. The desktop is used for 'normal' PC activities including games. Yesterday the oldest lappy had a message indication I should close BOINC to recover memory - I re-booted - Specs below (Windows 7). This morning the newest lappy (Windows 8) was even more screwed. When I tried to return completed WU's it said "Communicating with client", which it has never said before, as was totally locked up, could not exit boinc, could not re-start/shutdown by command, I had to powerdown manually, even task manager would not run. I was wondering if others had seen the same recently? Architecture: GenuineIntel Celeron(R) Dual-Core CPU T3500 @ 2.10GHz [Family 6 Model 23 Stepping 10] OS Details: Microsoft Windows 7 Home Premium x64 Edition, Service Pack 1, (06.01.7601.00) Number of CPU's: 2 Created: Sat, 27 Aug 11 12:14:37 -0400 Timezone: GMT +1 Floating Point Speed: 2,180.91 million ops/sec Integer Speed: 4,501.34 million ops/sec Memory Bandwidth: 500Mbit/sec Ram: 2.87Gb Cache: 1,024.00Kb Swap: 2.87Gb Disk Total: 116.21Gb Disk Free: 81.14Gb Architecture: AuthenticAMD AMD A8-4500M APU with Radeon(tm) HD Graphics [Family 21 Model 16 Stepping 1] OS Details: Microsoft Windows 8 x64 Edition, (06.02.9200.00) Number of CPU's: 4 Created: Fri, 25 Jan 13 09:14:19 -0500 Timezone: GMT +1 Floating Point Speed: 1,673.08 million ops/sec Integer Speed: 6,470.49 million ops/sec Memory Bandwidth: 250Mbit/sec Ram: 7.47Gb Cache: 2.00Mb Swap: 7.47Gb Disk Total: 679.01Gb Disk Free: 644.79Gb Ave Upload Rate: 66.19 Kb/sec Ave Download Rate: 26.00 Kb/sec Ave Turnaround:(tbf) 144,027.87 |
||
|
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3295 Status: Offline Project Badges: 
|
Could it be that you have a too high buffer which is downloading loads of tasks and making the client unresponsive?
----------------------------------------AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W AMD Ryzen 7 7730U 8C/16T 3.0 GHz |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I am set at 1 day + 1 day on all machines....
 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
.....and I re-iterate, only happened on the new SN2S. On the weeks prior when set on FAAH only it never occured!
 |
||
|
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3295 Status: Offline Project Badges:
|
No idea then. I doubt it's a hardware problem for obvious reasons.
----------------------------------------Maybe it is a bug. AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W AMD Ryzen 7 7730U 8C/16T 3.0 GHz |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I am switching back to FAAH to see if it happens on that project.....
|
||
|
|
cjslman
Master Cruncher Mexico Joined: Nov 23, 2004 Post Count: 2082 Status: Offline Project Badges: 
|
No lockup problems so far, but yesterday night I did get a "down for maintenance" msg on one of my laptops, but assumed that the WCG servers were actually down for maintenance. This morning everything seems to be fine.
----------------------------------------CJSL Crunching for a better future... |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7664 Status: Offline Project Badges: 
|
If it is only the laptops, have you investigated a heat issue ? Still does not explain why FAAH would run without a problem. I have had the "communicating with client " problem, but never on windows, only Linux. It seemed to be related to a wireless communication issue which would use system resources and cause all kinds of havoc with BOINC. So far for me SNS2 runs almost flawlessly.
----------------------------------------Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I think I can rule heat out as it is much cooler here following our heat wave and there was not a problem during it
|
||
|
|
depriens
Senior Cruncher The Netherlands Joined: Jul 29, 2005 Post Count: 350 Status: Offline Project Badges: 
|
Yup, I've had the same with a laptop. I'll try to describe it below.
----------------------------------------For me these problems were remarkable as I've been running WCG for quite some years on all of my desktops, laptops and now even android devices. None of the projects ever caused problems like S2NS caused over the past week. My guess is that it's due to high memory use of some S2NS batches . The laptop having troubles is running 8 threads on an i7-2720QM with 4GB of RAM. Last week I noticed that from one point the system was lagging extremely and almost didn't respond at all. Some reboots didn't fix the problem and a virusscan didn't show any problems either. Then I noticed that the S2NS workunits used up to 500MB of RAM each. So 8 units fill up the complete RAM causing it to swap constantly. I left the computer overnight and the day after the system was responding normally again. RAM use also dropped dramatically. I figured it was an incident until today I had the exact same problem. System didn't respond whatsoever and BOINC constantly "communicating with client". Subject units are the S2NS_4AOE_0000191 batch. Memory was filled up completely. To verify I cancelled all units of that batch and all problems disappeared immediately. I checked another system with an i7-920 and 6GB of RAM and the same batch of 8 workunits together chew up close to 4GB of RAM. This system is responding normally because more memory is installed (85% used at the moment).   |
||
|
|
|