> Sorry this was my fault. I was doing some work on the scheduler and forgot to
> restart it. So it was off for about 90 minutes.
>
> Bruce
Ahhh, signs of impending burnout here.... :).
You need a big buzzer on your desk linked to the server status page that goes off right under your coffe cup and splashes cold coffee in your face which is probably lying sideways on the desktop in an overwork induced stupor :)
On a more sensible note, it is extremely pleasing to see all your hard work and preparation paying off with what appears to us "outsiders" as a remarkably trouble free ramping up of users after you opened the floodgates. Hopefully this will continue and the project will go from strength to strength.
Also, while I've got your attention, put a very clear and obvious entry in the FAQ entitled What can I do to improve Validation Times for myself and others?. Put it right after the entry about "Pending for a week". Here is some suggested text which I'm sure you could correct and improve upon.
"Probably the singlemost important thing that each individual contributor could do would be to really think through how much work is kept on hand (ie cached). Please consider the seven day time limit carefully and your own ability to complete the work within that limit. Then set your "Connect to Network" interval under general preferences accordingly. A time limit of 1.0 days may be good in many cases for several reasons. Firstly you wont have work that is going "stale" all the time. Secondly you will be reporting results much closer to the time the work was issued. Thirdly, you wont be unnecessarily delaying others who have also completed the same work. Fourthly, everyone will be getting their recognition and due credit in a more timely fashion."
"As part of considering your "connect" interval, you have to consider the liklihood of server outages and plan accordingly. If you support multiple projects, you can let that support be its own extended cache. One project going down will not really affect you too much. Therefore you certainly don't need large caches for each project. In the case of Einstein@home, the most likely cause of a scheduler outage is Professor BA going to sleep at his desk from overwork and exhaustion. The buzzer under the coffee cup hardware mod will solve that problem in the future"
:). Keep up the good work. This is a fantastic project.
> I've been trying for several days, and it keeps saying the scheduler is not
> responding. Anyone else having this problem?
>
> Messages info:
> Einstein@Home - 2005-03-02 17:30:03 - Scheduler RPC to
> http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed
> Einstein@Home - 2005-03-02 17:30:03 - No schedulers responded
I don't know what's wrong. The last evidence of your machine contacting the scheduler was three days ago. Has anything changed in your networking that might prevent your machine from contacting the scheduler?
No, nothing has changed. I'm on 33.6k dial-up believe it or not.
To get it to connect, I go to the tab: Projects and right-click for Update.
Is this the proper procedure?
FYI - I just tried again, and got the same scheduler did not respond, but then I let it sit for the 1 minute timeframe, and then it connected correctly and a new job is being worked on. Strange.
Also, good question for you. In the Work tab, the Name column has what is being worked on. It always has Test02_(number) like this. Does this mean that these are Test runs, or are these the actual production searches that are supposed to be worked on?
Scheduler is Down?
)
Yes, I've been unable to get to it for 20-30 minutes now too.
Me too. None of my machines
)
Me too. None of my machines are connecting.
Jeff
Team CoBPA
There is a link on the front
)
There is a link on the front page of this site listed under the More Information heading that provides the status of all servers for this project.
Server Status
There's a fine line between fishing and standing on the shore looking like an idiot -- Steven Wright
Same problem and for the last
)
Same problem and for the last hour ie 23:47UTC on all machines.Please see 'Server Status' under "More Information" heading on Einstein@Home web page.
Sorry this was my fault. I
)
Sorry this was my fault. I was doing some work on the scheduler and forgot to restart it. So it was off for about 90 minutes.
Bruce
Director, Einstein@Home
> Sorry this was my fault. I
)
> Sorry this was my fault. I was doing some work on the scheduler and forgot to
> restart it. So it was off for about 90 minutes.
>
> Bruce
Ahhh, signs of impending burnout here.... :).
You need a big buzzer on your desk linked to the server status page that goes off right under your coffe cup and splashes cold coffee in your face which is probably lying sideways on the desktop in an overwork induced stupor :)
On a more sensible note, it is extremely pleasing to see all your hard work and preparation paying off with what appears to us "outsiders" as a remarkably trouble free ramping up of users after you opened the floodgates. Hopefully this will continue and the project will go from strength to strength.
Also, while I've got your attention, put a very clear and obvious entry in the FAQ entitled What can I do to improve Validation Times for myself and others?. Put it right after the entry about "Pending for a week". Here is some suggested text which I'm sure you could correct and improve upon.
"Probably the singlemost important thing that each individual contributor could do would be to really think through how much work is kept on hand (ie cached). Please consider the seven day time limit carefully and your own ability to complete the work within that limit. Then set your "Connect to Network" interval under general preferences accordingly. A time limit of 1.0 days may be good in many cases for several reasons. Firstly you wont have work that is going "stale" all the time. Secondly you will be reporting results much closer to the time the work was issued. Thirdly, you wont be unnecessarily delaying others who have also completed the same work. Fourthly, everyone will be getting their recognition and due credit in a more timely fashion."
"As part of considering your "connect" interval, you have to consider the liklihood of server outages and plan accordingly. If you support multiple projects, you can let that support be its own extended cache. One project going down will not really affect you too much. Therefore you certainly don't need large caches for each project. In the case of Einstein@home, the most likely cause of a scheduler outage is Professor BA going to sleep at his desk from overwork and exhaustion. The buzzer under the coffee cup hardware mod will solve that problem in the future"
:). Keep up the good work. This is a fantastic project.
Cheers,
Gary.
Hi: I see in the
)
Hi:
I see in the "server status" page that all is "running" but i can´t cocnect to it since my account creation.....?????
I've been trying for several
)
I've been trying for several days, and it keeps saying the scheduler is not responding. Anyone else having this problem?
Messages info:
Einstein@Home - 2005-03-02 17:30:03 - Scheduler RPC to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed
Einstein@Home - 2005-03-02 17:30:03 - No schedulers responded
> I've been trying for
)
> I've been trying for several days, and it keeps saying the scheduler is not
> responding. Anyone else having this problem?
>
> Messages info:
> Einstein@Home - 2005-03-02 17:30:03 - Scheduler RPC to
> http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed
> Einstein@Home - 2005-03-02 17:30:03 - No schedulers responded
I don't know what's wrong. The last evidence of your machine contacting the scheduler was three days ago. Has anything changed in your networking that might prevent your machine from contacting the scheduler?
Bruce
Director, Einstein@Home
No, nothing has changed. I'm
)
No, nothing has changed. I'm on 33.6k dial-up believe it or not.
To get it to connect, I go to the tab: Projects and right-click for Update.
Is this the proper procedure?
FYI - I just tried again, and got the same scheduler did not respond, but then I let it sit for the 1 minute timeframe, and then it connected correctly and a new job is being worked on. Strange.
Also, good question for you. In the Work tab, the Name column has what is being worked on. It always has Test02_(number) like this. Does this mean that these are Test runs, or are these the actual production searches that are supposed to be worked on?