Error I haven't seen before...

[rogerdugans]

Anyone seen this:

unexpected end of data set. connection closed.


Two of my linux rigs were displaying that when I checked just now: 1 rig is oc'd (900@1096) but the other is a 400mhz duallie that doesn't oc at all- and the other client was running fine!

Any ideas?

[Cy]

I just got that on one of my linux boxen a day or so ago. I just restarted the client and it grabbed a new unit from SETIQueue and started crunching again. Not sure what was going on. :(

That box as a single Xeon at 400 stock.

Cy

[Godfodda]

Think it's from a dropped connection while downloading a new WU from Berkeley?

[Sir-Epix]

I would have to say a dropped connection, but I haven't had any of those in the last two days. I finally got my production back up above 20...(Thank the Seti Gods). I then changed my sig, and will have to change it again rather soon because I am adding 10 P4 1.7GHz to my farm. HEHEHEHE.

[Cy]

All my machines run off of a SETIQueue local cache...so I'm not sure what it means.

Cy

[TC]

Would this be indicative of a corrupt work unit?

[Yodums]

Originally posted by TC
Would this be indicative of a corrupt work unit?

My thoughts exactly.

Yodums

[rogerdugans]

Those are the thoughts I had: corrupt or connection.
I'm leaning towards connection since the 400 dual has always been bulletproof, unless the wus are getting corrupted on the way from Berkeley.
Usually I think of corrupt wus being caused by an unstable oc, as that has happened to me once or twice in the past.

Thanks for the replies.