146.94.192.82 Collection Server, still waiting

[Knish]

On Apr 27, *.82 got used as a CS for an assignment from the linus1 WS. Asside from the logs reporting an estimation of base points after uploading, there were no issues. (I stil got my QRB despite what the log said)

On May 9, *.82 was used again for the linus1 and I just made a note of the WU (P16425 R949 C1 G66) bc the estimation of base points had caught my eye in the logs.

Code: Select all

19:02:18:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:16425 run:949 clon...
19:03:21:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 168.245.198.125:80: Connection timed out
19:03:21:WU00:FS00:Trying to send results to collection server
19:03:21:WU00:FS00:Uploading 1.49MiB to 146.94.192.82
19:03:21:WU00:FS00:Connecting to 146.94.192.82:8080
19:03:22:WU00:FS00:Upload complete
19:03:22:WU00:FS00:Server responded WORK_ACK (400)
19:03:22:WU00:FS00:Final credit estimate, 719.00 points

Previously I noted how sometimes it took 27 days for data to catch up and get reported - viewtopic.php?f=16&t=34414
so I just waited until later. It's around 51 days later now and someone has completed the WU on May 11, but I don't see myself on that list. The WU was completed in 2hrs 51min so it can't be an expiration thing. I know WUs are never lost, but is this maybe a case of since there was already a success on May 11, the "CS" data is ignored?

[bruce]

From the serverstat app, I see that 146.94.192.82 is off-line. I'm not sure how long it has been that way. I think it's a new CS, so I'll check and see if it's, in fact, configured as part of the server interconnections It does look like your WU uploaded so it MIGHT be a simple setting missing on the server.

[dlucent]

Sorry about that, it should be working correctly now. Please let me know if this machine continues to misbehave. Thanks!