Message boards :
Number crunching :
Boinc Mngr losing client connection
Message board moderation
Author | Message |
---|---|
Phil Burden Send message Joined: 26 Oct 00 Posts: 264 Credit: 22,303,899 RAC: 0 |
This has happened three times in the last 3 days, I open Boinc manager to check the tasks (it's usually on NNT, so I need to check regularly), and as it opens, all the tasks dissappear, for no apparent reason. I have to exit the manager, restart it, and it'll take 10-15 secs to reconnect to the client. After that, all is well, until the next day ;-) P. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14653 Credit: 200,643,578 RAC: 874 |
That sounds like the client has stopped running in the background, so there's nothing for the manager to connect to. Next time, open the Windows Task Manager, and see if boinc.exe is listed in the running processes. And yes, I mean specifically boinc.exe, not boincmgr.exe or any of the others like that. Once we know if that's the problem, we can think about why it's happening, and then decide what to do about it. |
Phil Burden Send message Joined: 26 Oct 00 Posts: 264 Credit: 22,303,899 RAC: 0 |
ok, slightly different scenario, BoincMgr seems normal, except nothing happening, tasks doing nothing. Event log is blank, weird. Task msansger shows Boinc.exe, boinctray.exe & boincmgr.exe as running processes. P. |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
I get that regularly on my notebook. For me it only occurs when I am using wireless and does not matter if I am connecting local or remote to BOINC. When I am on the wired NIC no problem. I don't have this issue with a desktop that is on a wireless connection on the other side of my place. So I am thinking perhaps a NIC/driver lag issue with BOINC. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
Terror Australis Send message Joined: 14 Feb 04 Posts: 1817 Credit: 262,693,308 RAC: 44 |
What version of BOINC and OS are you using ? IIRC there was a problem a couple of years ago with the v6.10.xx BOINC clients where this would happen on a regular basis. At the time, it would happen to me regularly on 4 different machines. Then it just stopped. I can't recall what the cause was or what the fix was. T.A. |
Phil Burden Send message Joined: 26 Oct 00 Posts: 264 Credit: 22,303,899 RAC: 0 |
I'm using 7.2.42 with Wiv7/64. Something Hal9000 said hit a chord. I recently installed a wireless dongle for some tests, and the issue started after that. So I disabled the dongle aqnd the problem hasn't reared its ugly head since ;-) P. |
tbret Send message Joined: 28 May 99 Posts: 3380 Credit: 296,162,071 RAC: 40 |
I'm using 7.2.42 with Wiv7/64. Something Hal9000 said hit a chord. I recently installed a wireless dongle for some tests, and the issue started after that. So I disabled the dongle aqnd the problem hasn't reared its ugly head since ;-) I don't know that this has anything to-do with anything, but a recent Windows update seemed to kill the onbaord LAN on two of my computers (different motherboards, but maybe the same LAN IC ) and only a restart would fix it. Other identical motherboards were not affected. I'm guessing something "grabbed" an IRQ the LAN wanted, but it's only a guess. |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
I'm using 7.2.42 with Wiv7/64. Something Hal9000 said hit a chord. I recently installed a wireless dongle for some tests, and the issue started after that. So I disabled the dongle aqnd the problem hasn't reared its ugly head since ;-) Out of curiosity who makes that dongle you bought? My two wireless machines that I don't have an issue with are using an Intel wireless NIC and a Cisco wireless bridge. The newer notebook that does have the issues uses an Atheros wireless NIC. Which I have been considering replacing with an Intel one. The throughput with the Atheros is a bit rubbish for me maxing out at around 3MB when connected via N. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
Phil Burden Send message Joined: 26 Oct 00 Posts: 264 Credit: 22,303,899 RAC: 0 |
It is a TP-Link dongle. P. |
jason_gee Send message Joined: 24 Nov 06 Posts: 7489 Credit: 91,093,184 RAC: 0 |
I use a TPLink PCIe card for Wireless-N, and it's an Atheros chip too. Not saying this is likely the issue, but worth some quick checks. The vendor drivers from either TP-link, Atheros themselves, or Microsoft Update are prone to Very high DPC latency spikes (at least on Win7 x64). As Boinc comms is through the TCPip stack, these stalls can cause these symptoms. To verify if this is the case on yours, disable the adaptor and see if the local Boinc client-manager symptoms are gone. If so, reenabling will see the symptoms return at some point. You can also see the extended DPC latency spikes using 'DPC Latency Checker'. I solved this for my host by using custom drivers available from laptopvideo2go. These drivers reveal all the hidden wifi options for the adaptor. The key setting that mitigated most of the latency problems was called "pcieaspm" set to "L0s On, L1 On" , I assume if it's a USB dongle the setting may be called something else, and is not visible in the device manager properties with 'normal' drivers. Also possibly watch DPC latencies while having web browsers open. I switched to chrome and disabled hardware acceleration. I can search for some links if you have a great deal of issues finding the atheros custom driver via laptopvideo2go, and/or need DPC latency checker. Most likely when I eventually replace my current PCIe Wireless card, I'll be looking for something with better quality low latency drivers. "Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions. |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
I use a TPLink PCIe card for Wireless-N, and it's an Atheros chip too. Good info. I am feeling that much more inclined to spend the $25 on an Intel wireless NIC for my notebook now. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.