SOLiD server always put the jon in Q instead of run

[nath223]

hello!

For the color space data, I submitted a job on lifescope server. Our server contains 4 nodes. The job shows no error message when I checked on the lifescope server. However, when I check the status of jobs using qstat it shows the following:

Job ID Name User Time Use S Queue
------------------------- ---------------- --------------- -------- - -----
67971.scyld ...tor_lifescope auswertung 0 C ls_primary
67972.scyld ...tor_lifescope auswertung 0 C ls_primary
67973.scyld ...age_lifescope auswertung 0 C ls_primary
67974.scyld ...nts_lifescope auswertung 0 C ls_primary
67975.scyld ...age_lifescope auswertung 0 C ls_primary
67976.scyld ...nts_lifescope auswertung 0 C ls_primary
67977.scyld ...age_lifescope auswertung 0 Q ls_primary
67978.scyld ...nts_lifescope auswertung 0 Q ls_primary

The example file that I am running is should take only 3 hours to complete but in this case it run for 24 hours whithout any progress. I am new to understand the queued process of the server. Any suggestion for this problem?

[westerman]

Talk to one of your system admins not to us.

[colindaven]

In my experience the workers in the SOLiD cluster we had tend to go down a lot. Perhaps check they are running ? Like Rick said, talking to those responsible locally sounds like a good idea.