missing credit for several wu's [Proj's 86nn & 137nn]

[6-o-9]

Mod: Copied pertinent WU info from another post, credit not received for these WU's - j

Project: 8679 (Run 78, Clone 3, Gen 81)
Project: 8676 (Run 81, Clone 0, Gen 38)
Project: 8675 (Run 92, Clone 1, Gen 19)
Project: 8632 (Run 0, Clone 2, Gen 84)
Project: 8650 (Run 390, Clone 0, Gen 18)

[JeansOn]

Joe announced, the persons are aware for the problem. No more examples are needed ...

But the problem is going on.
I'll still wait until correction. I hope, the uploaded material is not lost. That's more important for me, than ppd.

So I'll look up to this thread in near future. Pls give us an information, if the problem is corrected. Thank you.

[Joe_H]

They have checked the servers and found one problem, but correcting that was not the problem keeping the stats from being updated. But they were able to see the WU's being uploaded, so they are not lost. The problem has been escalated, hopefully the cause for the stats database not being updated will be identified soon.

[tug27224]

Based on the error messages we have received, we have increased the limit on file descriptors on our server(s) in hopes that this will solve the problem.
Please let me know if the problem still persists, and if so I'll continue to work on it.
Very sorry for the inconvenience.

[goodyca]

Since 6:00 UTC this morning I have successfully uploaded 10 WU's to servers 155.247.166.219 and 155.247.166.220 without credit being issued. Here is a listing of the problem WU's.

Project: 8637 (Run 5, Clone 1, Gen 90) 155.247.166.219
Project: 8659 (Run 502, Clone 0, Gen 16) 155.247.166.220
Project: 8630 (Run 0, Clone 722, Gen 44) 155.247.166.219
Project: 8677 (Run 29, Clone 1, Gen 70) 155.247.166.219
Project: 8646 (Run 365, Clone 0, Gen 11) 155.247.166.220
Project: 8658 (Run 501, Clone 0, Gen 9) 155.247.166.220
Project: 8621 (Run 12, Clone 3, Gen 18) 155.247.166.220
Project: 8679 (Run 45, Clone 4, Gen 78) 155.247.166.219
Project: 8637 (Run 5, Clone 85, Gen 44) 155.247.166.219
Project: 8699 (Run 0, Clone 16, Gen 112) 155.247.166.220

[Joe_H]

I can confirm that I also am not receiving credit for recent WU's returned to these WS's.

[tug27224]

I'm sorry to hear that. We'll continue to work on it to get things fixed as soon as possible.

[ViTe]

To be honest, it more looks like nobody cares about this problem. Two weeks passed but problem still not fixed and it looks like our points are lost. I think I'm not the only one who disappointed with this situation and I dont understand why we still getting an assignments to servers with problems: shut down and fix it. Its easy to break people's trust with disparagement.

[6-o-9]

To be honest, it more looks like nobody cares about this problem. Two weeks passed but problem still not fixed and it looks like our points are lost. I think I'm not the only one who disappointed with this situation and I dont understand why we still getting an assignments to servers with problems: shut down and fix it. Its easy to break people's trust with disparagement.

I agree completely. Especially as a brand new user and since roughly one third of of my WUs assignments are coming from 86nn this is really disheartening. I still want to help, but it seems there would be no shortage of WUs available, so I don't understand why these are still being assigned if there is obviously a problem with them. I'm definitely glad to hear the data is not lost because that is way more important than internet points, but let's be honest, getting internet points for your team is the "reward" for doing this for a lot of people (aside from the obvious purpose). This creates an accounting problem for points for the entire operation and this server should really be taken offline or at least stop assigning out WUs until it is fixed. You're going to lose trust and support from people who are less understanding than I am.

[tug27224]

I'm really sorry for the delay. I've been working on this since the issue arose, as there were several errors occurring at that time.
It turns out that there had been an update to the firewall ruleset for these two work servers so the points that had been earned could not be relayed to the appropriate servers.
This issue has been fixed.
In addition, the log of points earned during this downtime has remained intact since the WUs were successfully returned and accounted for.

[orion456]

Got a nice boost today!!

Thanks for your hard work in finding and fixing this glitch.

[SteveWillis]

I'm really sorry for the delay. I've been working on this since the issue arose, as there were several errors occurring at that time.
It turns out that there had been an update to the firewall ruleset for these two work servers so the points that had been earned could not be relayed to the appropriate servers.
This issue has been fixed.
In addition, the log of points earned during this downtime has remained intact since the WUs were successfully returned and accounted for.

Try and not let the negative comments get to you. I know from experience that as software/systems get more complicated so do the problems that crop up. Not to disparage bricklayers but I once had a manager who, when asked for precise time estimates, would say "We're not laying brick here". That is, sometimes it just takes what it takes.

[klasseng]

@ tug27224

Thank You for your work! I had been wondering about my erratic performance, but just chalking it up to the variations that occur when different types of WU's are assigned. Nice to see a 54WU/300K bonus show up!

peace,
Grant