All my uploads and downloads have finally cleared. And a 20% RAC jump to go with it... since I was lucky enough to be able to report a AP task with the rest.

---

- Luke.

Or.....

I had 39 WU's stuck in download for a couple of hours giving a mixture of these reports even though the network traffic seemed to be dropping off. A restart of BM caused them all to download immediately without any problem.

Same here.
Had a whole group of downloads allocated, but all of them were "Download Pending". Selected a few & did the "Retry now", but they timed out after a couple of seconds. After that time out, after the next attempt at downloading they rejoined all the others with "Download Pending" status.
I checked the project properties, and there were no deferal times there. Tried the "Do nework communication" option, still all "Download Pending".
Exited & restarted BOINC and after about 4-6 "Wrong file size" error messages, they all downloaded one ofter the other as fast as they ever have.

May be a bug with the manager? My present one is
v6.6.41
Running the AKv8 optimised app. No CUDA. No projects other than Seti.

---

Grant
Darwin NT

Or.....

I had 39 WU's stuck in download for a couple of hours giving a mixture of these reports even though the network traffic seemed to be dropping off. A restart of BM caused them all to download immediately without any problem.

Same here.
Had a whole group of downloads allocated, but all of them were "Download Pending". Selected a few & did the "Retry now", but they timed out after a couple of seconds. After that time out, after the next attempt at downloading they rejoined all the others with "Download Pending" status.
I checked the project properties, and there were no deferal times there. Tried the "Do nework communication" option, still all "Download Pending".
Exited & restarted BOINC and after about 4-6 "Wrong file size" error messages, they all downloaded one ofter the other as fast as they ever have.

May be a bug with the manager? My present one is
v6.6.41
Running the AKv8 optimised app. No CUDA. No projects other than Seti.

There are a few new features and changes related to the Transfers tab (UL's/DL's) in Boinc 6.10.18.

Perhaps it's worth a shot upgrading...

---

- Luke.

There are a few new features and changes related to the Transfers tab (UL's/DL's) in Boinc 6.10.18.

You must have different info than all the rest of us. ;-)

There were changes made in the project-wide upload and download back-off code. But these happened in 6.6.38 and 6.6.39

Grant is using 6.6.41, so he's well covered.

---

There are a few new features and changes related to the Transfers tab (UL's/DL's) in Boinc 6.10.18.

You must have different info than all the rest of us. ;-)

There were changes made in the project-wide upload and download back-off code. But these happened in 6.6.38 and 6.6.39

Grant is using 6.6.41, so he's well covered.

Oops, read the 6.10.18 thread wrong then. My mistake...

---

- Luke.

Must wait as the Force says the Turkeys, Er servers, are busy gobbling. :D

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I guess there is something wrong in Berkeley with the new network switch.

I made a 'reboot' of my DSL router (OFF/ON), for to be sure.
Before I made a reboot of the PC, no joy.

After reboot of DSL router at my home and second reboot of the PC, BOINC DLed ~ 50 WUs. Then again wrong DL size errors.
Again a reboot of the PC, again some WUs DLed. Again, wrong DL size errors.
Again reboot, no joy.. only wrong DL size errors.

Is there now with the new network switch in Berkeley a 'jumping' DL IP ?

I use BOINC V6.6.37 and never saw this in past.

---

I guess there is something wrong in Berkeley with the new network switch.

I made a 'reboot' of my DSL router (OFF/ON), for to be sure.
Before I made a reboot of the PC, no joy.

After reboot of DSL router at my home and second reboot of the PC, BOINC DLed ~ 50 WUs. Then again wrong DL size errors.
Again a reboot of the PC, again some WUs DLed. Again, wrong DL size errors.
Again reboot, no joy.. only wrong DL size errors.

Is there now with the new network switch in Berkeley a 'jumping' DL IP ?

I use BOINC V6.6.37 and never saw this in past.

And that's precisely why I didn't reset both of My routers. :D

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Just on the off chance, I rebooted my machine and the all of the pending downloads completed. I had already tried just stopping and restarting BOINC and SETI.

I just noticed others posting that it appears that things have cleared up. I guess that it was just coincidence that it cleared while I was rebooting.

---

http://boincstats.com/signature/-1/user/18390/sig.png

It wasn't really a 'reset' of the DSL router.
It was a 'reboot'.. I switched only OFF - waited one, two minutes and again - ON.

Because I didn't had joy..
I switched OFF again the DSL router, waited now ~ 10 minutes. Again ON.
Then reboot of PC.
BOINC DLed WUs, every 2nd DL wrong size error.
After ~ 30 WUs DLed, only DL wrong size errors.

It's not at my side.

I don't have time for to reboot after ~ 30 DLs.

---

There's a glitch of some type in the system- the number of results being returned is about half of what it would normally be & the network traffic dropped off way to quickly given the length of the outage.
And i've got another Work Unit ready to download, but it keeps timing out even after restarting BOINC.

---

Grant
Darwin NT

I updated both PCs with BOINC V6.10.18, but no joy.

Oh well..

---

There's a glitch of some type in the system- the number of results being returned is about half of what it would normally be & the network traffic dropped off way to quickly given the length of the outage.
And i've got another Work Unit ready to download, but it keeps timing out even after restarting BOINC.

The trick is:

Exit BOINC.
do ipconfig /flushdns
Wait a minute.
Restart BOINC.
Instead of Retry download, do Advanced->Do network communications.

Others rebooting their machine(s) is about the same thing as that.

---

There's a glitch of some type in the system- the number of results being returned is about half of what it would normally be & the network traffic dropped off way to quickly given the length of the outage.
And i've got another Work Unit ready to download, but it keeps timing out even after restarting BOINC.

The trick is:

.....

That did it.
Hopefully they'll have it sorted before i need to do it.
:-)

---

Grant
Darwin NT

There's a glitch of some type in the system- the number of results being returned is about half of what it would normally be & the network traffic dropped off way to quickly given the length of the outage.
And i've got another Work Unit ready to download, but it keeps timing out even after restarting BOINC.

The trick is:

.....

That did it.
Hopefully they'll have it sorted before i need to do it.
:-)

Ditto and Good Night all. (yawns)

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Ohh.. well..

What help it if I need to do it after every ~ 30 DLs?
My GPU cruncher make ~ 600 'normal' AR WUs/day.
He idle since days..

So 20x reboot or flush/day?
The hardware (if reboot) will be happy about.

Maybe it's time for to switch OFF some days.. maybe to Wednesday/Thursday next week..

Ohh.. nice weekend.

---

Exit BOINC.
do ipconfig /flushdns
Wait a minute.
Restart BOINC.
Instead of Retry download, do Advanced->Do network communications.

Well that did the trick just there :P
Drinking koffie now and everything seems fine.

---

Exit BOINC.
do ipconfig /flushdns
Wait a minute.
Restart BOINC.
Instead of Retry download, do Advanced->Do network communications.

Well that did the trick just there :P
Drinking koffie now and everything seems fine.

Well, that did not the trick here... on both machines :(

---

Exit BOINC.
do ipconfig /flushdns
Wait a minute.
Restart BOINC.
Instead of Retry download, do Advanced->Do network communications.

Well that did the trick just there :P
Drinking koffie now and everything seems fine.

Well, that did not the trick here... on both machines :(

In addition to the above trick, on my main machine I had to make a hosts file entry ( located in \windows\system32\drivers\etc ). My secondary machine already had such an entry (leftover & forgotten from last time...), so didn't have the problems downloading. The entry I added was:

208.68.240.18 boinc2.ssl.berkeley.edu

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Does that mean Vader is on the fritz again? Has anybody checked exactly which comms are failing? (I'm away from my main machines at the moment, and this little P4 has got plenty of work).

See 911175 and thereabouts.