No output

[airinanonna1112-spec]

I have been uploading my alignment file since yesterday in different methods but there is no output. Works from yesterday are still in queued for 15 hours. Can you please explain what could be the issue and how can I solve this ?

[spond]

Dear @airinanonna1112-spec,

Is that for Datamonkey? If so, we are in the process of migrating the service to a new (larger/faster) backend, and there were some issues with job scheduling. They should have been resolved. Would you mind trying again to see if the problem is gone?

Best,
Sergei

[stevenweaver]

Dear @airinanonna1112-spec,

Thank you for reporting. We've had a scheduling issue since yesterday and we're in the middle of trying to find an appropriate balance between Datamonkey jobs and institutional users in our college. I'll look into balancing things out more.

Best,
Steven

[airinanonna1112-spec]

Dear Sergei,
Thank you for the responses. I just run a job. Unfortunately, situation is still the same.

[airinanonna1112-spec]

Dear Steven,
Thank you for the response. Can you please tell me when can I work with Datamonkey again?

[stevenweaver]

Dear @airinanonna1112-spec,

Yes, I believe I've sorted the slurm partitions as I intended them to be set yesterday. It did come at the expense of clearing the current queue, unfortunately.

You can try submitting jobs again.

Dear @spond,

Summary of work:

• Expanded datamonkey partition from 3 to 16 nodes with OverSubscribe=FORCE:4 to allow node sharing.
• Removed hardcoded --nodes=1 flags from datamonkey job submission scripts (absrel, busted, fel, gard, meme, slac) that were preventing multiple jobs per node.
• Restarted datamonkey services and cleared queue. New jobs can now share nodes - expect max ~32 concurrent jobs (2 per node) when there are no other users on the system.

Best,
Steven

[tszaszgreen]

Hello all,

First, thank you for all of the work you do on Datamonkey. I wanted to let you know that on my end, I can now submit jobs to every tool except for RELAX. Regardless of which branches I select, the job automatically aborts. This continues even for files that previously ran fine through RELAX. It does not generate anything for the log file, and the error directs me to open an issue here. I assumed that these are related, but please let me know if you would like me to submit a separate ticket.

Thank you,
Taylor

[airinanonna1112-spec]

Hello Steven,

Thank you. Its working now.

[stevenweaver]

Dear @tszaszgreen,

Please try again.

Best,
Steven

[tszaszgreen]

Hello,

It is working again. Thank you so much!

Taylor

[doloacu]

Hi all, I hope you're doing well.
Anyone else can't run FUBAR? It's not been working today...

[stevenweaver]

Dear @doloacu,

FUBAR issue has been resolved.

Best,
Steven

[github-actions]

Stale issue message