I have RNA Star jobs running for 24 pairs, 22 OK and 2 running, but this has been the case for 2 days. Is there an issue with the data or the server? What can I do?
Welcome @apeinasuit
It sounds like you just ran a larger batch of mapping jobs. Those will be split up between the clusters into smaller batches (automatically) but this might be difficult to visualize from the top level of the collection folder.
Some of those executed, then completed, then next set executed and completed, and now the last batch is still executing. Try to leave those jobs executing to get the result!
Next time, you can consider using a workflow to speed things up. A workflow queues all the jobs in an analysis project at the same time. This means that the next tool can start to process for some samples, whenever they are ready, even while other samples are still completing that initial step. When there are many higher computation tools all run in a series, or when there are many samples, or both, this “streaming through tools” can considerably speed things up!
In short: my guess is that the jobs that are executing now were only queued before, not actually running, but as the other jobs completed, the last few jobs are now actually running. If this doesn’t clear up after a day or so, you are welcome to post back a link to the history and we can help to confirm that this is all proceeding as expected.
Hope this helps! 
XRef →
For many more examples, please see queued-gray-datasets
And, the general process is here: