Job still "In Progress" after 24 hours

Avatar
Anthony Wons

Hello. I submitted a job nearly 24 hrs ago and its status is still "In Progress". It seems odd as I only have 9 CPU hours left this month. Is there any way of finding out what stage it's at?  There are no output files of any sort so maybe it's waiting to be scheduled?

5 comments

  • Avatar
    Chloe Allison

    Hi Anthony, 

    Could you please provide the jobID, you can find this in the job status tab:

    Thanks,

    Chloe

    Comment actions Permalink
  • Avatar
    Anthony Wons

    Hi Chloe

    Thanks for replying. In the end I cancelled the job and reran it with slightly different memory settings. However, it would be good to know why it didn't finish, if it's possible to find out.

    The job ID was 426498ad-16d9-4f94-9d8a-63db5a937ac4

    Comment actions Permalink
  • Avatar
    Chloe Allison

    Hi Anthony,

    From the logs it looks like the job reached ~10% before it was cancelled. If it was taking longer than expected it could be due to a high number of frames requested in the output video? I would suggest lowering the number of frames to 10 and see if the runtime is closer to what is expected, sometimes generating a high frame rate video on the cloud slows down the runtime, an alternative would be to just save a snapshot at each frame and generate the video yourself in the post processor. 

    I hope this helps.

    Best Regards,

    Chloe

    Comment actions Permalink
  • Avatar
    Anthony Wons

    Hi Chloe

    Thanks for looking into it. I confess I still haven't quite got the hang of OnScale but the run that did work produced about 50 snapshots and the snapshot.flxdato file has a total size of about 11 GB. Is that likely to cause a problem? 

    I couldn't discover a way of finding out how far the run had got. I had to override the memory estimate and that seemed to make the progress in the job status window show as 100% right from the start so I couldn't tell how far it had actually got. After aborting the run there were no output or log files at all. Is there any way I could have found out what had happened?

    Thanks for your help

    Anthony

    Comment actions Permalink
  • Avatar
    Chloe Allison

    Hi Anthony,

    Apologies for the delayed reply. 11 GB is quite a large file, it may take some time to read that into the post processor, let me know if you have any issues with it, if the post processor is extremely slow, it can also be processed in a scripted Review file. 

    For your second point, our status reporting was broken for a few weeks there, which is why you saw 100% progress straight away. This should be fixed now. But if you provide me with the job ID I can find out what happened to that job for you. 

    Thanks,

    Chloe

    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post