. . I guess that explains the http error

. . Where was that report number setting again ??

Report number makes no difference to http connections - at that stage, you're talking to the networking bit of the operating system, and it doesn't yet know what you want to do with the connection when you get it.

Report number only comes into play if you see the internal server error bit too.

. . I guess that explains the http error

. . Where was that report number setting again ??

Report number makes no difference to http connections - at that stage, you're talking to the networking bit of the operating system, and it doesn't yet know what you want to do with the connection when you get it.

Report number only comes into play if you see the internal server error bit too.

. . That makes sense since it was set at 0 and changing it to 50 made no difference ... :(

Stephen

:(

Well, I am still getting HTTP errors when trying to report 50.

BAH!

---

Well, I am still getting HTTP errors when trying to report 50.

There are many different sorts of http error, and the action to be taken (if any) depends on which one it is. If it simply says 'transient http error', with no further enlightenment, you can get the rest of the gory details with http_debug logging. But most of them can't be resolved at our end of the line - they simply represent congestion and overcrowding in the server closet.

Well, I am still getting HTTP errors when trying to report 50.

BAH!

. . I have dropped mine to 25 but still get the internal server error ... :(

Stephen

? ?

All work reported, just can't get any new work.

---

All work reported, just can't get any new work.

Same here with the full reporting, and I've started to get just a dribble of replacements - the odd half dozen here and there. And the SSP has caught up, and seems to be telling us there is work in hand to be distributed.

So far, it seems to be heading in the right direction, although no signs yet of a miracle cure for the recent problems.

Just get the first set of new work:

Wed 04 Apr 2018 09:37:30 AM EST | SETI@home | Scheduler request completed: got 107 new tasks

---

04/04/2018 16:00:56 | | Project communication failed: attempting access to reference site
04/04/2018 16:00:58 | | Internet access OK - project servers may be temporarily down.

Got 5 earlier now only getting this.

Not too bad here. A full quota of WU, although I've noticed that the D/L speed has dropped (from about 500k about 50 mins ago to about 30k, 10 mins ago).

---

Don't take life too seriously, as you'll never come out of it alive!

.....And we are up and running again...all systems blazing...:-)

Except the splitter systems.............
We are about out of work RTS.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Late to the thread news. Didn't expect the project back so soon. See that the RTS has nothing in it. Doesn't matter since I still have over 3200 tasks still to report 50 at at time.

Anybody see any reorganizations in the server descriptions or functions. Front page just mentions they changed how the database accesses storage. I was expecting a lot more functional change.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Well well...some purging is starting to happen, my valids have shrunk by about one third :)

---

Humans may rule the world...but bacteria run it...

Late to the thread news. Didn't expect the project back so soon. See that the RTS has nothing in it. Doesn't matter since I still have over 3200 tasks still to report 50 at at time.

Anybody see any reorganizations in the server descriptions or functions. Front page just mentions they changed how the database accesses storage. I was expecting a lot more functional change.

I usually don't have any problems with reporting around 1000 at a time. It happens in about three Updates and automatically handles how many report at a time, I do nothing except hit the Update button. This morning though it wasn't working with just a few hundred, so, I used the old method of setting No New Tasks. That worked the first time and they all reported at once. If you're still having trouble you might try Updating with No new tasks set.

Thanks for the tip Tbar, I will give that a try the next connection.

[Edit] Hah! Worked. Set NNT and reported 933 tasks. But in reality it only reported a couple of hundred. Will see whether I can get any work now.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Results waiting for db purging	71	29,103	982,799

Finaly Good News!

---

[Edit] Hah! Worked. Set NNT and reported 933 tasks. But in reality it only reported a couple of hundred. Will see whether I can get any work now.

IIRC the max number of reported task on one report is 256, even if it shows a bigger number.
Eventualy after few updates all will clear.
What makes your host not receive new work is if you have some UL stalled.

---

Late to the thread news. Didn't expect the project back so soon. See that the RTS has nothing in it. Doesn't matter since I still have over 3200 tasks still to report 50 at at time.

Anybody see any reorganizations in the server descriptions or functions. Front page just mentions they changed how the database accesses storage. I was expecting a lot more functional change.

I usually don't have any problems with reporting around 1000 at a time. It happens in about three Updates and automatically handles how many report at a time, I do nothing except hit the Update button. This morning though it wasn't working with just a few hundred, so, I used the old method of setting No New Tasks. That worked the first time and they all reported at once. If you're still having trouble you might try Updating with No new tasks set.

. . That sounds like a good idea ...

Stephen

. .