Please click update again and then paste the logs from the message tab after you do that into a post here so we can see what's going on.
Tue Jan 16 23:36:29 2007|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
Tue Jan 16 23:36:29 2007|Einstein@Home|Reason: Requested by user
Tue Jan 16 23:36:29 2007|Einstein@Home|(not requesting new work or reporting completed tasks)
Tue Jan 16 23:36:34 2007|Einstein@Home|Scheduler request succeeded
Tue Jan 16 23:36:34 2007|Einstein@Home|Message from server: Project is temporarily shut down for maintenance
Tue Jan 16 23:36:34 2007|Einstein@Home|Project is down
I have deleted all three of your duplicate posts. Please understand that it is very bad form to hijack another person's thread like this so that is why I have deleted them.
If you have a genuine question that needs answering and you wish to illustrate that question with an example from your messages, please start your own topic, giving background information about your setup. It is highly unlikely that you would ever need to spam the boards by simply dumping literally hundreds of lines from your messages tab without even asking a question. It is up to you to select a small subset of lines which show the problem you want help with.
Please click update again and then paste the logs from the message tab after you do that into a post here so we can see what's going on.
Tue Jan 16 23:36:29 2007|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
Tue Jan 16 23:36:29 2007|Einstein@Home|Reason: Requested by user
Tue Jan 16 23:36:29 2007|Einstein@Home|(not requesting new work or reporting completed tasks)
Tue Jan 16 23:36:34 2007|Einstein@Home|Scheduler request succeeded
Tue Jan 16 23:36:34 2007|Einstein@Home|Message from server: Project is temporarily shut down for maintenance
Tue Jan 16 23:36:34 2007|Einstein@Home|Project is down
This log snippet is telling you that BOINC is of the opinion that the EAH project doesn't need work at the moment and doesn't have any work to report. There are quite a number of possible scenarios for this and without a lot more information about your setup, it's not possible to say what the most likely scenario is.
Almost as an aside, after the successful scheduler contact, your client was informed that the project was temporarily down anyway so that if work had actually been requested, it wouldn't have been supplied.
The scheduling server is under immense pressure at the moment due to the very high numbers of short duration results that are clogging the database. Even a casual glance at a number of recent threads will fill you in with a lot of the details. My impression is that the "Project is temporarily shut down for maintenance" message is simply a defence mechanism to kick out those requests that the server is simply unable to handle. As well there may be other database issues that are contributing to this, making it difficult for the server to recover from the overload.
Everybody is in the same boat and manual intervention by users (imagine even just 1% of users incessantly hammering on the "update" button) is likely simply to make things worse. Your best action is to leave your client alone to sort things out with the server in its own good time. I'm sure the Devs are doing their very utmost to alleviate the situation until the last of these "shorts" are finally dealt with. After the current work is finished and the new work gets underway, the load on the server should drop considerably, perhaps by a factor of five.
Does this also affect current WU's that I have finished but haven't been able to upload to the server ?
I hope these will upload properly when the server is up and running again.
Andy
Many people seem to be wondering about much the same sort of things that you are. Some are even asking if they should abort the stuck results in their caches. I've just done a quick check of a number of my boxes. Based on that check, I estimate that I have more than 1500 results ready to report. I have no fears that eventually every last one of those will be reported and will be of use to the project.
From the behaviour of my own boxes, it's interesting to note that the ONLY things that are NOT happening at the moment are (i) the downloading of new work and (ii) the reporting of uploaded results. The contact with the scheduler is happening so that my boxes are not going into the 1 week backoff that some have reported. The maximum backoff I'm seeing is 2-3 hours and often a lot less. As results are finished, they are being uploaded - the status is always "Ready to report". The results are on the server waiting to be reported. Why the hell would anyone want to kill any results in this condition?
The following comments are not directed at any particular person. They are made simply to make sure people understand some basic issues.
Consider what would happen if any person decides to abandon any stuck results on their system. Since the quorum is two and the initial issue is two, you would be immdeiately forcing your quorum partner into an extended wait. All the time and effort you have put into the original crunching would be wasted and you would force the server to reissue the work to a third party.
So please don't walk away from EAH with no chance for the work to be reported. By all means go and crunch another project if you wish but leave EAH attached and unsuspended so that BOINC can clean up for you when the server is able to accept the reporting of your completed results. If you really want to abandon EAH just set "no new work" and finally detach when all your results have eventually been reported.
Wed Jan 17 16:30:26 2007|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
Wed Jan 17 16:30:26 2007|Einstein@Home|Reason: Requested by user
Wed Jan 17 16:30:26 2007|Einstein@Home|(not requesting new work or reporting completed tasks)
Wed Jan 17 16:30:32 2007|Einstein@Home|Scheduler request succeeded
Wed Jan 17 16:30:32 2007|Einstein@Home|Message from server: Project is temporarily shut down for maintenance
Wed Jan 17 16:30:32 2007|Einstein@Home|Project is down
This has been going on for some time. I find it difficult to believe that the server has been incapable of doling out work or accepting results for this period of time. I am not sure when the last time was that I did either, but I estimate two weeks.
Does this also affect current WU's that I have finished but haven't been able to upload to the server ?
I hope these will upload properly when the server is up and running again.
Andy
Many people seem to be wondering about much the same sort of things that you are. Some are even asking if they should abort the stuck results in their caches. I've just done a quick check of a number of my boxes. Based on that check, I estimate that I have more than 1500 results ready to report. I have no fears that eventually every last one of those will be reported and will be of use to the project.
From the behaviour of my own boxes, it's interesting to note that the ONLY things that are NOT happening at the moment are (i) the downloading of new work and (ii) the reporting of uploaded results. The contact with the scheduler is happening so that my boxes are not going into the 1 week backoff that some have reported. The maximum backoff I'm seeing is 2-3 hours and often a lot less. As results are finished, they are being uploaded - the status is always "Ready to report". The results are on the server waiting to be reported. Why the hell would anyone want to kill any results in this condition?
The following comments are not directed at any particular person. They are made simply to make sure people understand some basic issues.
Consider what would happen if any person decides to abandon any stuck results on their system. Since the quorum is two and the initial issue is two, you would be immdeiately forcing your quorum partner into an extended wait. All the time and effort you have put into the original crunching would be wasted and you would force the server to reissue the work to a third party.
So please don't walk away from EAH with no chance for the work to be reported. By all means go and crunch another project if you wish but leave EAH attached and unsuspended so that BOINC can clean up for you when the server is able to accept the reporting of your completed results. If you really want to abandon EAH just set "no new work" and finally detach when all your results have eventually been reported.
Have not been receiving any work units
)
Please click update again and then paste the logs from the message tab after you do that into a post here so we can see what's going on.
Kathryn :o)
Einstein@Home Moderator
RE: Please click update
)
Tue Jan 16 23:36:29 2007|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
Tue Jan 16 23:36:29 2007|Einstein@Home|Reason: Requested by user
Tue Jan 16 23:36:29 2007|Einstein@Home|(not requesting new work or reporting completed tasks)
Tue Jan 16 23:36:34 2007|Einstein@Home|Scheduler request succeeded
Tue Jan 16 23:36:34 2007|Einstein@Home|Message from server: Project is temporarily shut down for maintenance
Tue Jan 16 23:36:34 2007|Einstein@Home|Project is down
@ Higgs Boson, I have
)
@ Higgs Boson,
I have deleted all three of your duplicate posts. Please understand that it is very bad form to hijack another person's thread like this so that is why I have deleted them.
If you have a genuine question that needs answering and you wish to illustrate that question with an example from your messages, please start your own topic, giving background information about your setup. It is highly unlikely that you would ever need to spam the boards by simply dumping literally hundreds of lines from your messages tab without even asking a question. It is up to you to select a small subset of lines which show the problem you want help with.
Cheers,
Gary.
For the record, I'm getting
)
For the record, I'm getting the exact same lines in my log as TheOuthouseMouse is (project down, down for maintenance, etc.).
RE: RE: Please click
)
This log snippet is telling you that BOINC is of the opinion that the EAH project doesn't need work at the moment and doesn't have any work to report. There are quite a number of possible scenarios for this and without a lot more information about your setup, it's not possible to say what the most likely scenario is.
Almost as an aside, after the successful scheduler contact, your client was informed that the project was temporarily down anyway so that if work had actually been requested, it wouldn't have been supplied.
The scheduling server is under immense pressure at the moment due to the very high numbers of short duration results that are clogging the database. Even a casual glance at a number of recent threads will fill you in with a lot of the details. My impression is that the "Project is temporarily shut down for maintenance" message is simply a defence mechanism to kick out those requests that the server is simply unable to handle. As well there may be other database issues that are contributing to this, making it difficult for the server to recover from the overload.
Everybody is in the same boat and manual intervention by users (imagine even just 1% of users incessantly hammering on the "update" button) is likely simply to make things worse. Your best action is to leave your client alone to sort things out with the server in its own good time. I'm sure the Devs are doing their very utmost to alleviate the situation until the last of these "shorts" are finally dealt with. After the current work is finished and the new work gets underway, the load on the server should drop considerably, perhaps by a factor of five.
Cheers,
Gary.
also see this thread from
)
also see this thread from Bernd.
Udo
RE: also see this thread
)
Does this also affect current WU's that I have finished but haven't been able to upload to the server ?
I hope these will upload properly when the server is up and running again.
Andy
RE: RE: also see this
)
Many people seem to be wondering about much the same sort of things that you are. Some are even asking if they should abort the stuck results in their caches. I've just done a quick check of a number of my boxes. Based on that check, I estimate that I have more than 1500 results ready to report. I have no fears that eventually every last one of those will be reported and will be of use to the project.
From the behaviour of my own boxes, it's interesting to note that the ONLY things that are NOT happening at the moment are (i) the downloading of new work and (ii) the reporting of uploaded results. The contact with the scheduler is happening so that my boxes are not going into the 1 week backoff that some have reported. The maximum backoff I'm seeing is 2-3 hours and often a lot less. As results are finished, they are being uploaded - the status is always "Ready to report". The results are on the server waiting to be reported. Why the hell would anyone want to kill any results in this condition?
The following comments are not directed at any particular person. They are made simply to make sure people understand some basic issues.
Consider what would happen if any person decides to abandon any stuck results on their system. Since the quorum is two and the initial issue is two, you would be immdeiately forcing your quorum partner into an extended wait. All the time and effort you have put into the original crunching would be wasted and you would force the server to reissue the work to a third party.
So please don't walk away from EAH with no chance for the work to be reported. By all means go and crunch another project if you wish but leave EAH attached and unsuspended so that BOINC can clean up for you when the server is able to accept the reporting of your completed results. If you really want to abandon EAH just set "no new work" and finally detach when all your results have eventually been reported.
Cheers,
Gary.
Incidentally, I am still
)
Incidentally, I am still getting these messages:
Wed Jan 17 16:30:26 2007|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
Wed Jan 17 16:30:26 2007|Einstein@Home|Reason: Requested by user
Wed Jan 17 16:30:26 2007|Einstein@Home|(not requesting new work or reporting completed tasks)
Wed Jan 17 16:30:32 2007|Einstein@Home|Scheduler request succeeded
Wed Jan 17 16:30:32 2007|Einstein@Home|Message from server: Project is temporarily shut down for maintenance
Wed Jan 17 16:30:32 2007|Einstein@Home|Project is down
This has been going on for some time. I find it difficult to believe that the server has been incapable of doling out work or accepting results for this period of time. I am not sure when the last time was that I did either, but I estimate two weeks.
Justin L.
RE: Wed Jan 17 16:30:26
)
In other cases, if this project did have any work at the moment (and it doesn't), you'd see this message when the following applies:
Check the Projects tab in BOINC Manager, check in the Status of the affected project that it doesn't say "Won't get new tasks" in its status.
If your project has this status, click on the project, then click on the "Allow new tasks" button on the left hand side menu.
Check if your Network connection is available. In the activity menu bar, check if Network activity isn't set to Suspended.