Project 16525 not uploading

[muziqaz]

What is you username in FAH?

[PaulTV]

Uploading 16525 does work fine for me, so it's not failing for everyone. So the question is: what's different, that it fails for some, but not for others.

So, let's see if we can pinpoint a bit... I'm running v7 clients only right now. Both my Windows machines and my Ubuntu server have processed (and uploaded) 16525. Located in the Netherlands. What version of the client are you running, on which OS, and where are you located?

[bollix47]

Check your MTU .... it should be 1500

The internet's transmission control protocol (TCP) uses the MTU to determine the maximum size of each packet in any transmission. MTU is usually associated with the Ethernet protocol, where a 1500-byte packet is the largest allowed.

p.s. the upload of that project works fine here on v8.4.9

[ViTe]

IS there a way to prevent 16525 from being downloaded by the client?

You can block outgoing connections to work server IP 128.104.69.82 in you firewall and you never receive 16525 again.

[calxalot]

Does blocking the work server prevent the assignment server from giving you an assignment for the undesirable server?

[ViTe]

No its not. But you never get the the work unit from undesirable server and after couple of attempts assignment server just give you the work unit from another work server. It may be even next attempt so it works really good.
We don't have any ways to influence the decision of the assignment server but we can refuse to accept the assignment. At V8.4 we have a "Dump" button and able to dump any work unit that we don't like. Bloking the work server is just the automation.

[calxalot]

Doesn't a dump hurt your quick return bonus eligibility?

[muziqaz]

Doesn't a dump hurt your quick return bonus eligibility?

It does indeed, but 100% return rate is thing of the past with GLIBC issues nuking everything left and right anyways. So what's another dumped unit would do?
P.S. I'm still waiting for user's FAH username, that I can tell researcher simply to blacklist that user, that way they will not get that project. Simple

[calxalot]

I don't think you should be glib about it (glibc).
Is ViTe even using Linux?

[muziqaz]

I don't think you should be glib about it (glibc).
Is ViTe even using Linux?

I mention GLIBC because in grand scheme of things that is the biggest issue we have. Dumping one WU compared to 1000s dumped by others because of fahcore issue, is nothing

[calxalot]

Agreed. But isn't that only a problem for GPU WUs on linux?

[muziqaz]

Agreed. But isn't that only a problem for GPU WUs on linux?

Yes, which is massive chunk of the total production

[calxalot]

It looks like 3 people here having problems with 16525.

[muziqaz]

It looks like 3 people here having problems with 16525.

16525 is not entire Linux userbase
For the amount of traffic we get in forum, 3 people is a lot
Besides we were blacklisting user after user few months earlier because of 100s of thousands of WUs dumped due to fahcore issues

[ViTe]

I think bloking the work server is much better then dumping the unit cos actually you never getting the unit so no dumping required.