Client Detatched errors!!
18 Dec 2008 12:20:04 UTC
Topic 194091
(moderation:
Wow, I just noticed 4 client detatched errors listed where both me and the other person crunching the workunit have them listed. However, I'm still crunching those workunits and I've already uploaded and reported one of them. Here they are:
http://einsteinathome.org/workunit/45789654
http://einsteinathome.org/workunit/45794556
http://einsteinathome.org/workunit/45790510
http://einsteinathome.org/workunit/45805046
Is anyone else having this problem?? Until this issue is resolved I'm going to stick my computers on the primegrid challenge instead.
edit: and it looks like it's getting ready to happen again: http://einsteinathome.org/workunit/45998823
~It only takes one bottle cap moving at 23,000 mph to ruin your whole day~
Client Detatched errors!!
)
Could you publish the hostid of your machine this happens with?
BM
BM
RE: Could you publish the
)
It would seem to be 1754825
Edit - peered with 1682194, 1631677, and 1669839
Too bad they don't even show
)
Too bad they don't even show the Core Client versions in this case. Mary, which version are you using?
BM
BM
RE: Too bad they don't even
)
1631677 was using v5.8.16 before and after the detaches, under Linux 2.6.9-55.ELxenU.
I'm thinking Mary tried to
)
I'm thinking Mary tried to upgrade either to 6.4.5 or ended up there after another version try, and the install got corrupted. Maybe the tasks didn't migrate to the Data folder or something along those lines.
Her latest task has a Breakpoint Encountered (0x80000003) error now as well though, so AV could also be a possible cause, (especially if it's Norton), from what I believe I've seen in another thread.
RE: I'm thinking Mary tried
)
Yep. I've switched over to 6.4.5, but the installation doesn't seem to be having any corruption issues. In fact, it fixed the screensaver issues on my computers and is running great with all my other projects. I aborted all the Einstein tasks, hence the breaks now. Those client detatched errors occured on the server while I was still actively crunching the units. I hadn't communicated with the server until I uploaded that one WU and noticed that it said the client was detatched. By the way, this computer started out with 6.4.5. It's not an update since the computer is brand new. I found it strange that my wingmen on the WU's received the error too, so it apparently isn't my computer itself that's causing the problem.
It very well could be 6.4.5 itself. I've just upgraded my other computer which has never had any of these errors pop up. I'll try out an Einstein WU on it here in a sec to see if the error pops up again. If it does, then it would indicate that the project isn't settling well with 6.4.5. Just be aware that it takes about 21 hours for that old thing to finish an Einstein task.
[edit] Okay, I've got a task up and running on my other computer (id = 1363329). It has no communication with the internet, so if any errors pop up on this WU: http://einsteinathome.org/workunit/45937225 in the next, oh say 20 hours, then it is happening on the server. If something happens when I try to upload the task, then it would indicate issues with 6.4.5. If nothing happens then who knows. On another note, I wish we could get ahold of my wingmen for those other tasks and find out what version they're running...
~It only takes one bottle cap moving at 23,000 mph to ruin your whole day~
RE: On another note, I wish
)
The ones I looked into are GRID accounts. For them it's quite normal to detach the client from the project before they run out of processing time.
BM
BM
Hmm.. Well I just returned a
)
Hmm.. Well I just returned a new task from the same computer that encountered all those client detatched errors and this one went through just fine. Neither person crunching it hit a client detatched error. I haven't changed a thing on my computer since before I hit those errors and my other computer is crunching along just fine. Maybe the 'computer gods' were just in a bad mood that day. Anyway, I'll be over at primegrid for the challenge once my other computer finishes up its last Einstein WU sometime tonight. See you guys again in January.
~It only takes one bottle cap moving at 23,000 mph to ruin your whole day~
RE: Her latest task has a
)
Where is the proof that Norton is the cause of or associated with 0x80000003 errors? I do not know if a causal relationship exists, but if it doesn't you are perpetuating already too common myths that Norton is an inferior product. I personally have not experienced any problems with any version of NIS on Windows. I recently experienced this particular error but a simple reboot of windows and restart of BOINC solved the problem.
RE: RE: Her latest task
)
You would be quite correct in this case. That error was not caused by Norton as I don't even have Norton on either of my computers. That error was caused by me physically hitting 'abort task'. I would figure that you'd see it a lot more often with people just aborting tasks than with any sort of virus scanning software issue.
~It only takes one bottle cap moving at 23,000 mph to ruin your whole day~