Folding Forum

Server 130.237.232.141 has been trying to issue me the same -bigadv work unit (Project: 6900 (Run 32, Clone 7, Gen 7)) for more than 30 minutes.
This doesn't happen very often with -bigadv servers but it is commonplace on the GPU servers and something that needs immediate attention for a resolution.
It is wasting time, money, and effort.

B

Please post your log showing the problem.

bruce wrote:Please post your log showing the problem.

The log has been dumped as part of the normal process of TRYING to clear the problem.
Anyone who's been folding long enough knows that's got to be part of the routine or it WILL keep happening.
So, sorry, no, I don't have a log to post but I can assure you it does not reveal anything I haven't already said.
The servers aren't keeping track of what they're doing in an effective interactive manner!!

I very rarely come here to post anything because every time it proves to be an exercise in frustration.
This one is no exception........ sadly. Anyway I finally got a different work unit (from server 22) and am
almost happy again. I say almost because almost 40 minutes of folding time and my own personal time
was flushed down the .......... trying to fix what the servers should NOT being doing in the first place.

But, when it starts happening with the GPU servers again I will post it all en-mass, and with 24 GPU's it's a mess

Windows keeps deleted files in the trash and it can easily be recovered from there.

If it's no longer a problem for you, we will have to consider the issue closed unless you can post the log. If you're still having the problem, the new log will be sufficient to debug the issue.

bruce wrote:Windows keeps deleted files in the trash and it can easily be recovered from there.

If it's no longer a problem for you, we will have to consider the issue closed unless you can post the log. If you're still having the problem, the new log will be sufficient to debug the issue.

I'm sure you've already written this one off anyway. You people spend more time skirting around the problems brought before you than doing anything positive that is immediately obvious. The same problems
that have demonized the project's server farm persist and you all just can't get a handle on it.

I'm not a dummy windows weenie. I also keep a clean house which means taking out the trash often. I run the 64-bit windoze XP kernel in a Solaris VM shell so it isn't quite as simple as you seem to automatically assume it is.
Your assumptions that everyone who comes here with a problem is less knowledgeable than yourself (and others) is quite insulting and thus I won't be back. Scratch one PhD engineer. Please inactivate my account at this forum.

B

1. Server side assignments have nothing to do with wu assignments.
2. If the AS tries to send the wu to you and you dump it, you get it back by design to prevent dumping.
3. If you folded so long you would know about 2, and know the log files would be asked to ensure this wasn't a case of dumping/cherry picking which
4. isn't allowed...

This is not about Bruce's attitude, it's about yours. You, being PhD no less, should know there are procedures to follow which include asking the basic questions first and starting with basis information with a minimum of assumptions.

Even if the #1 folder comes here with an issue, I would still start by asking the same questions, just to rule them out as being involved. It does not imply I do not respect that person's knowledge, it's following procedure which is good since I seen very knowledgeable persons skip a simple step by oversight or just lack of concentration etc. It happens to the best of us.