Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 4
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi!
I am running the UD Agent on my machine and use several cache slot with UD Mon. Today I had results of HPF in two cache slots. When I sent the results I got WU #4664298 as new WU in both slots. As I find it not very smart to do the same WU twice, I switched to one of the slots, killed WCGRID_ROSETTA.EXE so that the agent downloads a new WU. And again it gets the same WU #4664298 again. What's going on here? Best regards Thorsten |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It is statistically unlikely that you will get the same WU twice, although it did happen to me once before. To get the same WU 3 times goes beyond coincidence - perhaps one of the techies would like to look at the server logs . . . .
|
||
|
Alther
Former World Community Grid Tech United States of America Joined: Sep 30, 2004 Post Count: 414 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Today I had results of HPF in two cache slots. When I sent the results I got WU #4664298 as new WU in both slots. I don't know where UD Monitor gets/calculates those numbers, but those #s don't correspond to our workunit IDs. You should also know that you use UD Monitor at your own risk and we don't support or recommend using it. I understand most users have no problems with it, but there are no guarantees.
Rick Alther
Former World Community Grid Developer |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I don't know where UD Monitor gets/calculates those numbers, but those #s don't correspond to our workunit IDs. As far as I could analyse it UD Monitor gets the number from the filename of the WU in the agent's directory. In my case there is a file UD_4664298. If this is not your WU#, it is at least generated by the UD Agent. You should also know that you use UD Monitor at your own risk and we don't support or recommend using it. I am totally aware of this. Meanwhile other slots finished work and got new HPF WUs with other #s than the above. So at least for these slots the problem is not reoccuring. I will keep an eye on the slot with the duplicates. Best regards Thorsten |
||
|
|
![]() |