- Joined
- Feb 7, 2005
- Location
- Folding in Maryland!!
This is from one of my single core instances running on the Pentium D...
Any ideas as to what's causing it?
Any ideas as to what's causing it?
-
Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!
Unable to transmit unit to work server?
- Thread starter traldan
- Start date
- Joined
- Jan 9, 2006
Looks like the returned data is incomplete. I'd leave it alone, and when it cycles through to another autosend period, it should try to resend the WU again. Like the log file says, it might just be a transmission loss.
If it works, great, if not, then I'd check the work directory and see if you have files that got tore up by a HD or FAH error.
If you do, just run check disk, and see that the HD is okay, and delete that unit from your queue with the delete flag. (Which is just " -delete N", where N is the number of the WU in the queue, iirc).
Good luck.
If it works, great, if not, then I'd check the work directory and see if you have files that got tore up by a HD or FAH error.
If you do, just run check disk, and see that the HD is okay, and delete that unit from your queue with the delete flag. (Which is just " -delete N", where N is the number of the WU in the queue, iirc).
Good luck.
you might also want to check any issues posted over at FC ... check the standard core forum and the server one.
without the project and server ip it is hard for us to check for 'known' issues.
The log snippet almost looks like the symptoms on smp when you don't specify bigpackets before you get your fisrt wu. Resloution to that one required using qfix.
without the project and server ip it is hard for us to check for 'known' issues.
The log snippet almost looks like the symptoms on smp when you don't specify bigpackets before you get your fisrt wu. Resloution to that one required using qfix.
