Finished work not reported
31 Dec 2006 7:52:09 UTC
Topic 192256
(moderation:
I have two (2) complete pieces of work that are not being reported. So far as I can tell the program has not even tried to report either complete work.
The Einstein system claims to be "running".
Wasup?
Finished work not reported
)
Ok for some reason the communication was defered 110 hrs. 1 min.
Took care of that but now the host and user cedits are unequal. We are one. Resistance was futile. The uniqueness of our scoes should be one in perfection.
Oh well, one assimalation at a time!
Yes, there was an outage a
)
Yes, there was an outage a few days back, which caused many systems to go into a long deffered communication mode. Only way to fix that is update. It's not recommended to use the update key, except in situations like this, as it causes a lot of database stress.
RE: Yes, there was an
)
Cool, I'll try it. It has been over 24 hrs sence the problem was fixed and my work has still not been reportrd.
RE: I have two (2) complete
)
OK, so, They have removed the man. report option. I guess I ain't the only one with this problem.
RE: RE: I have two (2)
)
You like Myst? Uru Live returns! www.urulive.com
Let's get the facts
)
Let's get the facts straight:
1.) You can override the long comm deferral for contacting the scheduler on all BOINC clients by selecting the project and clicking update on the Projects Tab. If you are in the deferral state, update, and you can't hit the scheduler, the public release and older versions will go back to the full 604800 second deferral. You will then have to override it again or wait until it times out.
2.) Manually updating the project does not put an undue excess load on the project servers, unless you are sitting there punching the update button constantly. However, if you revert to a Development version or one of the third party versions which restore the Report Results Immediately Diagnostic/Debug functionality and enable it, you override BOINC's normal habit of trying to consolidate as many reports as possible into one big DB session. This is what causes unnecessary extra load on the DB servers when they have to handle the constant stream of "solo" reports if everybody started doing it that way.
Alinator
I have 3 Einstein@home
)
I have 3 Einstein@home reports ready to transmit since the end of last year. But all I hear is that the server is down and will take a few days to correct. At first it started as communications deferral of some sort and then the report has not been sent and I have not received anything new. These reports deadline is Jan 15th.
What is the status on this server problem and why has the report not been uploaded if the problem has been fixed?
Thank you,
DS Russell
RE: I have 3 Einstein@home
)
Open BOINC Manager and go to the Transfers tab. Any results trying to upload will be listed there. Select each one in turn and hit the "Retry now" button and you will find that they will quickly disappear. When all three are uploaded, go to the Projects tab, select the EAH project and click the update button. Your outstanding results will be reported all in one go.
Alternatively, you could be patient and let BOINC sort this out for you. The only thing you have to worry about is if BOINC is stuck in the long (up to one week) deferral mode. In this case just use the update button to kick it back into life again.
All of this is because of the main fileserver instabilities which have been occurring over the last couple of weeks and hopefully are now solved for the time being at least :).
Cheers,
Gary.
Thank you for your response.
)
Thank you for your response. There is nothing in the transfers box - it is empty. The 3 reports are listed in the tasks box with a status of "Ready to Report" This has been the status for nearly a week. It started out as a Communication deferral but then changed to the current status about a week ago.
I just looked at the Projects tab. The status there is "Scheduler request pending, communication deferred". Apparently there still is a problem with the server since the upload would occur when the server is fixed. wouldn't it? The update button just updates your records - completed taks, credits, preferences, receive more tasks. It doesn't send the reports themselves, does it?
DS Russell
RE: I just looked at the
)
The "communications deferred" is probably the time left from a previous 1 week deferral that was entered into when BOINC failed to get a response from the scheduler on 3 successive occasions while the fileserver was down. So there was a request pending that couldn't be serviced on 3 successive retries so the request is still pending but BOINC has decided to go into a coma for up to a week. BOINC will NOT try to contact the server again until either (1) you click the Update button or (2) the deferral period expires - whichever is the sooner. So it's your call :).
The update button clears any deferrals currently in existence and allows communications to be attempted again. That's exactly what you need to do.
EDIT: I hadn't noticed previously that you only joined the EAH project on Jan 01 2007. Welcome to your baptism of fire :). The EAH project is normally very reliable but has had major server issues for over a month now. You just happened to join at a small interlude between two multi-day outages so you have really only experienced the most recent outage. If you read the terse messages on the front page news and read between the lines you will get the impression that the project staff have reacted magnificently but haven't yet discovered the root cause of the problems. Hopefully the temporary fileserver now in place will give them breathing space and will allow them the time needed to finally nail the source of the actual problem with the normal server once and for all.
Cheers,
Gary.