I keep getting server down for maintenance or http errors for quite some time on a few boxes...almost a day.....any idea if it will allow reporting before they go down to switch? Getting quite a backlog...
The "maintenance" message looks like a pure protection mechanism since it gives a 1 hour backoff. There is no guarantee that the work can be reported before server shutdown. This is not really an issue if you intend to be crunching next week as the new server will quite happily accept the reports then. If you are wanting to report final work before shutting down your machine and you wont be around next week, you can try the "update" button every few minutes or so. On the law of averages you will get lucky every so often and the stuff will go through. I've been able to do that quite a few times for machines that are going off permanently.
Thanks for the quick reply Gary....Since some hosts were reporting I started flushing dns caches in my modem and routers and worked! Got through to a server ,reported,and d/l more work.... a possible hint for those with the same problem?
At this moment I have on my two systems running Einstein 11 and 23 requests that have the status ready to report. Every time Boinc tries to report I got the message that the projec is down for maintenance or a http error. The strange thing is that in the task list this task are mark as completed. This means that the reports are accepted, but the conformation is not send back to my systems. Thies lead to the situation that this reporting will be repeaed over and over. I believe that this can akso stress the servers.
... The strange thing is that in the task list this task are mark as completed. This means that the reports are accepted, but the conformation is not send back to my systems.
That is exactly correct - the work has been accepted by the server but the confirmation back to the client has not made it through. The client therefore retains the results and will try to report them again (and again) since it can't know that the server wasn't able to get its response back successfully. When a subsequent attempt to report is eventually successful, the results will finally disappear from the client and there will be a message from the server saying that the results are being ignored this time because they were previously successfully received. It will call it an "attempt to submit a duplicate results" or something like that. There is nothing to worry about as all will be handled correctly.
If you want to vastly improve the chances of any particular attempt to report being completed successfully, make sure your host is not asking for work (ie set NNT for the project) at the same time as reporting completed tasks. The reporting of tasks will succeed more frequently if no new tasks are simultaneously being requested.
RE: RE: I keep getting
)
Thanks for the quick reply Gary....Since some hosts were reporting I started flushing dns caches in my modem and routers and worked! Got through to a server ,reported,and d/l more work.... a possible hint for those with the same problem?
At this moment I have on my
)
At this moment I have on my two systems running Einstein 11 and 23 requests that have the status ready to report. Every time Boinc tries to report I got the message that the projec is down for maintenance or a http error. The strange thing is that in the task list this task are mark as completed. This means that the reports are accepted, but the conformation is not send back to my systems. Thies lead to the situation that this reporting will be repeaed over and over. I believe that this can akso stress the servers.
RE: ... The strange thing
)
That is exactly correct - the work has been accepted by the server but the confirmation back to the client has not made it through. The client therefore retains the results and will try to report them again (and again) since it can't know that the server wasn't able to get its response back successfully. When a subsequent attempt to report is eventually successful, the results will finally disappear from the client and there will be a message from the server saying that the results are being ignored this time because they were previously successfully received. It will call it an "attempt to submit a duplicate results" or something like that. There is nothing to worry about as all will be handled correctly.
If you want to vastly improve the chances of any particular attempt to report being completed successfully, make sure your host is not asking for work (ie set NNT for the project) at the same time as reporting completed tasks. The reporting of tasks will succeed more frequently if no new tasks are simultaneously being requested.
Cheers,
Gary.