No, I don't. Like I said, it happened on the server side! My host didn't even succeed in making a scheduler request. This is the second time it happened. I'm not the only one this happened to; there were other users reporting the same thing.

What version of BOINC?
Which OS & version?

EDIT- ie, were they the same as yours or different?
____________
Grant
Darwin NT.

No, I don't. Like I said, it happened on the server side! My host didn't even succeed in making a scheduler request. This is the second time it happened. I'm not the only one this happened to; there were other users reporting the same thing.

What version of BOINC?
Which OS & version?

EDIT- ie, were they the same as yours or different?

Linux/x64, BOINC 7.0.39
Others have had it happen on Windows (don't know about BOINC version, most definitely not 7.0.39).
I don't think it's client's fault but server's - I assume it receives a malformed request (due to networking problems) and thinks project was reset.
Client wasn't even notified about that and continued to crunch already abandoned tasks so I had to manually abort them (ok, I accidentaly aborted a few more tasks that weren't "abandoned"). I had to use proxy for that otherwise that computer on that ISP rarely manages to contact scheduler without timing out.
____________

Frank, I've been having a lot of this too and all my desktops with Nvidia GTX 550 ti graphics processors have been slowly running out of work. I have used the No new tasks option and then update followed by the allow new tasks and update a few minutes later after tasks upload routine again and again over the last week or so with gradually decreasing success. As of about 6 a.m. this morning I was out of all work on both desktops. I've switched over to my old standby's gpugrid, world community grid, and a few other cosmology projects. Some of us believe the problem is with the scheduler not being able to keep track of tasks completed and sending out way to many tasks. Many of us have many dozens and many hundreds of ghost processes in the system. There also seems to be an association between Astro Pulse work being split and sent out which may be fouling the rest of the scheduling work. The internet bandwidth of the 100 meg line from the lab to BOINC seems to be far beyond capacity. Some of us have noticed this big problem of getting work and reporting work after a maintenance downtime about 3 or 4 weeks ago. I noticed that the system seemed to come out of that maintenance fine and all my computers were happily send working out and getting new work without time outs or failures. My recollection is that it (Seti at Home) stopped running well after just a few hours.

My notebooks, even one with an Nvidia 525m graphics processor and an i7 2670 qm core processor is still getting some work and reporting out, but having dozens and dozens of reporting failures and time outs every day. My i3 notebook with intel integrated graphics is doing fine. My little core duo notebook whose Radeon 2600 series processor doesn't qualify to run jobs is working fine too. As I wrote earlier, I am gradually switching over to alternative projects with my desktops beginning today.

I have never seen it this bad in my year here and am rethinking my priorities. Right now I am thinking a new project mix will be 2 parts medical discovery and disease fighting projects along with some Seti at Home work with my notebooks. I have fought this kind of chronic frustration at work before and it is too stressful for many people to handle well. The low limits on work per cpu and graphics processor are already hitting my desktops even though they were both down to just a few dozen short work units each. The limits will not help with the problem at all according to what I have read here. From my point of view, the download/upload issue became much more severe after that maintenance downtime around 4 weeks ago. I remember it all happened not too long after my wife and I got back from a memorial service for a close family member around mid October. We had just returned from visiting our families for an extended period and were building RAC up again slowly. Momentum stopped. Sorry, I don't have enough data to track it back to an exact date. I hope the Seti folks address this very, very soon. They are way understaffed, but I know they have the project's interests at heart. I know too that there are times when a project just has to step back and solve serious issues that may negatively affect project morale if left without at least a partial or interim solution. Brother Frank on Seti at Home.

No, I don't. Like I said, it happened on the server side! My host didn't even succeed in making a scheduler request. This is the second time it happened. I'm not the only one this happened to; there were other users reporting the same thing.

What version of BOINC?
Which OS & version?

EDIT- ie, were they the same as yours or different?

Linux/x64, BOINC 7.0.39
Others have had it happen on Windows (don't know about BOINC version, most definitely not 7.0.39).
I don't think it's client's fault but server's - I assume it receives a malformed request (due to networking problems) and thinks project was reset.
Client wasn't even notified about that and continued to crunch already abandoned tasks so I had to manually abort them (ok, I accidentaly aborted a few more tasks that weren't "abandoned"). I had to use proxy for that otherwise that computer on that ISP rarely manages to contact scheduler without timing out.

Are you using a proxy- guess what? I just got my first abandoned tasks, 200 of them.
Only occurred since using a proxy.
____________
Grant
Darwin NT.

Are you using a proxy- guess what? I just got my first abandoned tasks, 200 of them.
Only occurred since using a proxy.

Welcome to the club. :-)
I didn't use any proxy when it happened.

Meh... just another not so set-and-forget thing that could happen at S@H. If you don't notice that all tasks were abandoned, boinc will just continue to crunch them into oblivion, wasting time and power. Looks like it's best to have a minimum cache or check your tasks every day.
It really got my goat when I saw my 100 AP tasks nuked...
____________

I have been running just fine since I fixed my networking, have as much work as the project will send me. And reporting is going though just about always on the first shot. Downloads have still been a little slow but moving along.

Now I just need to replace one of my nvidia cards that is no longer working right on my old crunch box.

This is what I keep getting. Any word as to when this all may be rectified??

You should try using a proxy. It seems that the scheduller is not having issues doing its work, but it fails to comunicate with the clients when its contacted directly. When a proxy is used the comunications fail a lot less... Not a confirmed theory, but everyone using a proxy is now getting work regularly.
____________

You should try using a proxy. It seems that the scheduller is not having issues doing its work, but it fails to comunicate with the clients when its contacted directly. When a proxy is used the comunications fail a lot less... Not a confirmed theory, but everyone using a proxy is now getting work regularly.

Ok. So where is the list of proxies? And how to configure it in Boinc?
____________

You should try using a proxy. It seems that the scheduller is not having issues doing its work, but it fails to comunicate with the clients when its contacted directly. When a proxy is used the comunications fail a lot less... Not a confirmed theory, but everyone using a proxy is now getting work regularly.

Ok. So where is the list of proxies? And how to configure it in Boinc?

To find a proxy you better use google, if we post a proxy address here and everybody start to use it, the admins of that proxy will block the SETI comunications due to the bandwith used...
Look for transparent or anonymous free proxies... not every proxy you will find works, so you will need to try different ones until one works for you.

To set it, in BOINC 6.xx, in advanced mode you need to go to the Tools menu, then "display and network options" and in the http proxy tab you should mark the "conect via http proxy" option and enter the address and the port of the proxy. I guess its not very different in BOINC 7.xx but Ive never used that version...
____________