HADDOCK2.4 Job Stuck in 'Queued' Status for Several Days - Seeking Assistance

HADDOCK
,
1

Dear HADDOCK Support Team and Community,

I am a Master’s student currently using the HADDOCK web server (specifically HADDOCK2.4) for my research on protein-glycan docking simulations.

I have been successfully utilizing the server for the past couple of weeks, accessing it through my university network. Previously, my jobs would typically run and provide results within a reasonable timeframe, usually 4-6 hours.

The Issue

  • Timeline: Starting approximately five days ago, all my submitted jobs have been permanently stuck with the status: “Status: Queued”.

  • Context: This is happening despite using the exact same network connection and computer that I used successfully before this issue arose.

  • Attempted Solutions: I have tried deleting and resubmitting the jobs multiple times, but the outcome remains the same—they immediately go into a prolonged ‘Queued’ state without ever starting the calculation.

Request for Help

  • What steps can I take to resolve this and allow my HADDOCK2.4 jobs to start running again?

Any guidance or information on the current server status would be highly appreciated. I am currently unable to utilize HADDOCK2.4 for my simulations.

Thank you very much for your time and assistance.

Best regards, wengh

The HADDOCK category is meant to discuss any HADDOCK-related issue. For general information about HADDOCK refer to HADDOCK – Bonvin Lab

2

I am having the same issue, and it started around the same time

3

Dear all

Because of unforeseen issues with the HTC infrastructure used to execute HADDOCK workloads, the server capacity is currently limited, which has caused a long queue of submissions. We hope the situation will revert to normal soon, but this is not something we have under our control.

4

I appreaciate the answer!

5

Apologies, I just saw this. Thank you very much for the update!

6

Has it returned to normal? I encountered the same problem and submitted the file around 23:00 on November 5th.

7

The situation has improved indeed - still some issues, but enough throughput for now.