I followed your instructions and this is the result: (Computer number - 3200494 | Timezone (IST) - GMT + 5.30hrs )
Quote:
Tue Aug 10 10:09:54 2010 Einstein@Home work fetch suspended by user
Tue Aug 10 10:10:02 2010 Einstein@Home update requested by user
Tue Aug 10 10:10:06 2010 Einstein@Home Sending scheduler request: Requested by user.
Tue Aug 10 10:10:06 2010 Einstein@Home Reporting 1 completed tasks, not requesting new tasks
Tue Aug 10 10:10:12 2010 Einstein@Home Scheduler request completed
Tue Aug 10 10:10:12 2010 Einstein@Home Message from server: Completed result h1_0788.35_S5R4__29_S5GC1a_0 refused: result already reported as success
Tue Aug 10 10:10:12 2010 Einstein@Home Message from server: Resent lost task h1_0788.35_S5R4__189_S5GC1a_2
Also, this is not the host that is reporting no disk space. I'll fix the disk space issue later today...
I'm still not sure what is happening there, it looks like the scheduler crashed or at least doesn't properly finish the reply after it wrote the time it ran in the log. Definitely not an ordinary crash, and also definitely related to the new scheduler. I'll try to revert to an older, more stable version.
We have isolated some (Einstein@home customization) code that seems responsible for the weird scheduler behavior and built a scheduler without it that is now running. We still don't know what's wrong with that code, but at least the scheduler should be fine now.
For the sake of debugging this problem could you re-enable GPU tasks, issue one work request (update project) and make the sched_request_einstein.phys.uwm.edu.xml available to me (post it here, put somewhere to download or send via PM)?
Excuse me please, I don't view this thread after august, 7.
Gundolf, I followed your
)
Gundolf,
I followed your instructions and this is the result: (Computer number - 3200494 | Timezone (IST) - GMT + 5.30hrs )
Also, this is not the host that is reporting no disk space. I'll fix the disk space issue later today...
I'm still not sure what is
)
I'm still not sure what is happening there, it looks like the scheduler crashed or at least doesn't properly finish the reply after it wrote the time it ran in the log. Definitely not an ordinary crash, and also definitely related to the new scheduler. I'll try to revert to an older, more stable version.
BM
BM
RE: Gundolf, I followed
)
Fine that you got your result reported. Now don't forget to allow new tasks again.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
We have isolated some
)
We have isolated some (Einstein@home customization) code that seems responsible for the weird scheduler behavior and built a scheduler without it that is now running. We still don't know what's wrong with that code, but at least the scheduler should be fine now.
BM
BM
Bernd, Thanks for the
)
Bernd,
Thanks for the update. It seems to be working fine on my machines.
Gundolf, of course it's running once again! Crunching numbers away!
Regards,
Susheel
RE: For the sake of
)
Excuse me please, I don't view this thread after august, 7.
If sheduler reply need: