Another OGR Question

[MaxCrunch]

Frequently when I try to flush the buffer, I connect to a Dnet (or RR team TA) machine, but get a message that reads:

FlushOGR::Unable to assert acknowledgment validity

The client tries to flush a couple more times, sometimes actually sending a unit, sometimes not, but usually the above message repeats a couple of times then gives up and goes back to crunching. I've noticed this also happens sometimes when it tries to fetch work units, but seemingly not as often. Any insights?

Thanks,
MaxC

 

[Viztech]

Uhhh, almost sounds like a poor Internet connection, or possibly a winsock problem.
What OS are you using?
If Win 95, do you have the winsock2 update?
Do you have this trouble on all of your machines, or just one.

viz

 

[MaxCrunch]

I've noticed it happens most often on two WinNT machines that have to go through a proxy firewall. However, since they do work correctly some of the time, I would speculate that the client settings are correct. I've also seen it happen on a Linux box connected directly to the 'Net, so I don't think it's a firewall problem, at least not all the time.

MaxC

 

[Viztech]

Max-

I really wonder if it isn't an Internet or firewall problem.

Which keyserver are you dumping to? Try to ping or tracert to them.

Have you tried port 23 or 80? Mika listens on 2064 and 23 (I think) so try the port 80 round robin.

If all else, we can arrange to have you try to dump to my Pproxy when I can watch the console.

viz

 

[Viztech]

Bump

I'm wondering about this one....

viz

 

[BoberFett]

If it's sporadic, and does sometimes get a WU through, it sounds like a bad connection to me. If you can find one of the RR servers that you have a better ping to, try flushing directly to it rather than using the RR.

 

[MaxCrunch]

OK, here's what seemed to fix things. The problems started when I tried to set the client to flush and fetch to the RR proxies. It worked sporadically (but it DID work), but since I didn't have daily access to the machines I wanted something more bulletproof so I decided to go back to simply fetching and flushing through Dnet's servers. However, when I changed the client settings back to using the Dnet servers, the problems started. Welllllll, to make a long story short, when I changed the setting to use distributed.net keyservers, I never removed the info about using the TA proxies (that configuration choice disappears from the screen when you select "YES" to using the dnet keyservers, so I never thought to remove the TA proxy info, figuring it wouldn't be used!). Somehow that seems to have messed up the fetch/flush process. This morning, when I thought to configure the client as it was before I tried the TA RR proxies (by removing all mention of the TA proxies in the config file), BOOM, everything worked exactly as it should!

The config file(s) seem to be pretty sensitive to making sure that one doesn't have TOO MUCH info in them!

Thanks for your responses!
MaxC