I don't have enforce_projects set to true, I'm trying to phase projects in
and this problem is stalling it.

The only difference with the output of `qstat -j` is the line "project".
Apart from that, they're the same (including the hard_q line).

If I `qstat -u "*"`, the jobs show, even `qstat` but as soon as I introduce
the `-q` flag, all jobs with projects disappear (even with `q- "*"`.

What SGE are you using?  I'm on 6.2u5.



Regards,
Joseph David Borġ
http://www.jdborg.com


On 3 May 2012 14:44, Reuti <[email protected]> wrote:

> Am 02.05.2012 um 11:14 schrieb Joe Borġ:
>
> >Yes but I have enforce_project set to true which means I have to
> >specify a project.
> >I can queue a job for a specific cluster queue and it won't show up if
> >I do qstat -q on that
> >cluster queue.
>
> Where is this configured then?  I'm happy with the qw to show in the list
> and I'm usually more interested in that than I am with the actual job
> running, but I can't see the qw + project jobs, which I also need to see.
> Once a job with a project starts, I can see the job in qstat.
>
>
> I tried to reproduce this by setting enforce_project to TRUE too and
> assigning a project which is attached to a queue like before. I still get a
> proper ouptut. Can you spot anything in `qstat -j <jobid>` while
> "schedd_job_info TRUE" is set in the scheduler configuration.
>
> Does the behavior change if you request the options "-s r" resp. "-s p" in
> addition to the "-q all.q" option?
>
> -- Reuti
>
> PS: Limited service, I'm on vacation and the Internet is pretty unsteady
> here.
>
>
> Regards,
> Joseph David Borġ
> http://www.jdborg.com
>
>
> On 2 May 2012 09:50, William Hay <[email protected]> wrote:
>
>> On 2 May 2012 09:40, Joe Borġ <[email protected]> wrote:
>> > Are you sure?
>> >
>> Yes but I have enforce_project set to true which means I have to
>> specify a project.
>> I can queue a job for a specific cluster queue and it won't show up if
>> I do qstat -q on that
>> cluster queue.
>>
>> William
>> > $ qmod -d jb.q
>> > joe.borg@host_a changed state of "jb.q@host_a" (disabled)
>> >
>> > $ qsub -q jb.q test.sh
>> >
>> > $ qstat -q jb.q
>> > job-ID  prior   name       user         state submit/start at
>> > queue                          slots ja-task-ID
>> >
>> -----------------------------------------------------------------------------------------------------------------
>> >   14150 0.00000 test.sh    joe.borg     qw    05/02/2012
>> > 09:36:18                                    1
>> >
>> > Regards,
>> > Joseph David Borġ
>> > http://www.jdborg.com
>> >
>> >
>> > On 2 May 2012 09:19, William Hay <[email protected]> wrote:
>> >>
>> >> On 1 May 2012 22:37, Reuti <[email protected]> wrote:
>> >> > Hi,
>> >> >
>> >> > Am 01.05.2012 um 14:57 schrieb Joe Borġ:
>> >> >
>> >> > Hi all,
>> >> >
>> >> > I'm trying to submit a job with a project assigned to a queue.
>> Without
>> >> > the
>> >> > project, running `qstat -q example.q` shows the job whilst it's
>> queued.
>> >> > As
>> >> > soon as I use the -P flag with qsub, I can't see the job using the -q
>> >> > flag
>> >> > with qstat until the job starts.
>> >> >
>> >> > Why is this?  The hard_q_list is still set to example.q, so it should
>> >> > still
>> >> > show.
>> >> >
>> >> >
>> >> > I can't confirm this. Do you have anything in addition in your
>> >> > ~/.sge-qstat
>> >> > to limit the output? Which version are you using?
>> >> I can reproduce this here in so far as all our jobs have a project
>> >> associated with them
>> >> and qstat -q only shows jobs actually running in the queue not queued
>> >> jobs eligible to
>> >> run in the queue.
>> >>
>> >> >
>> >> > -- Reuti
>> >> >
>> >> >
>> >> > Regards,
>> >> > Joseph David Borġ
>> >> > http://www.jdborg.com
>> >> >
>> >> > _______________________________________________
>> >> > users mailing list
>> >> > [email protected]
>> >> > https://gridengine.org/mailman/listinfo/users
>> >> >
>> >> >
>> >
>> >
>>
>
>
>
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users

Reply via email to