There seems to be a scheduler problem over at Albert, a couple of us haven't been able to get work for at least a week,
And the formatting of the posting of the Event Log from Linux hosts goes to cock when previewed or posted:
Fri 10 Mar 2017 09:50:17 GMT | Albert@Home | [sched_op] Starting scheduler request Fri 10 Mar 2017 09:50:17 GMT | Albert@Home | Sending scheduler request: To fetch work. Fri 10 Mar 2017 09:50:17 GMT | Albert@Home | Requesting new tasks for CPU Fri 10 Mar 2017 09:50:17 GMT | Albert@Home | [sched_op] CPU work request: 345600.00 seconds; 2.00 devices Fri 10 Mar 2017 09:50:19 GMT | Albert@Home | Scheduler request completed: got 0 new tasks Fri 10 Mar 2017 09:50:19 GMT | Albert@Home | [sched_op] Server version 611 Fri 10 Mar 2017 09:50:19 GMT | Albert@Home | Another scheduler instance is running for this host Fri 10 Mar 2017 09:50:19 GMT | Albert@Home | Project requested delay of 60 seconds Fri 10 Mar 2017 09:50:19 GMT | Albert@Home | [sched_op] Deferring communication for 00:01:00 Fri 10 Mar 2017 09:50:19 GMT | Albert@Home | [sched_op] Reason: requested by project
Claggy
Copyright © 2024 Einstein@Home. All rights reserved.
Thanks, we'll look into it...
)
Thanks, we'll look into it...
Einstein@Home Project
There were actually two
)
There were actually two issues which are remnants from the migration to the new server. I fixed both the scheduler locking issue and the scheduler log issue. Thanks for reporting. Albert currently is out of work but I plan to do some more scheduler testing next week where I'm going to create work for BRP4 and/or BRP4G again.
I tried to download BPR4G
)
I tried to download BPR4G work, but keep getting Download Failed / Error while downloading for all hosts. Communication with Einstein and web is working fine at the same time.
app_version download error: couldn't get input files:
Hi Richie, BPR4G ended some
)
Hi Richie, BPR4G ended some time ago. If you still got some old tasks left, just cancel them.
Thanks,
Oliver
PS: nice rig by the way
Einstein@Home Project
This was an issue on
)
This was an issue on Albert@Home. It's fixed now. Please report further problems directly on Albert.