Ah, didn't think of that, of course the obvious explanation. Thanks for looking into that!
Is there a way for me to find that out myself, e.g. using qstat? I had a look at the qstat man-page, but judging by the descriptions it looks like something I'd have to fiddle around with if/when a job gets queued for a long time at some point in the future to figure out how to do. Regards, Morten On 5 December 2012 07:11, Merlissimo <m...@toolserver.org> wrote: > Server sql-s1-rr was unavailable during the night. So resource sql-s1-rr > was 0. > > Because i am not a ts admin i could not check that you requested this > resource for this jobs. But just now nosy had a look and confirmed my > suspicion. The job was started after resource sql-s1-rr was available again. > > Merlissimo > > Am 04.12.2012 16:44, schrieb Morten Wang: > > Looks like the issue got resolved around 09:00UTC, as from the qacct >> output: >> >> jobname opentasks >> jobnumber 873860 >> [...] >> qsub_time Mon Dec 3 22:19:03 2012 >> start_time Tue Dec 4 09:06:32 2012 >> end_time Tue Dec 4 09:21:18 2012 >> >> If you want to look into it more closely, this job was submitted by me >> (user: nettrom) through my crontab on the submit servers. >> >> >> Cheers, >> Morten >> >> > _______________________________________________ > Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) > https://lists.wikimedia.org/mailman/listinfo/toolserver-l > Posting guidelines for this list: > https://wiki.toolserver.org/view/Mailing_list_etiquette >
_______________________________________________ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
