[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] condor_q lists jobs, exits w/ 1?

I also see the same problem with condor 7.4.4 and quill.

I looked into the source code and program behaviour is correct (print the same 
output like without arguments), but program exits with wrong return value.

I prepared patch and I hope that people from condor project will accept it.

Lukas Slebodnik

On Wed, May 25, 2011 at 09:56:51PM -0400, Sam Gerstein wrote:
> On Wed, May 25, 2011 at 8:44 PM, Shahaan Ayyub <shahaan@xxxxxxxxx> wrote:
> > Sam,
> >   It seems that "-name my_schedd_hostname" was not resolved properly, and
> > the output was parsed for the default condor_q command which talks to the
> > local  schedd, which is same in your case. Try condor_q on another schedd in
> > your pool and see the return value.
> >
> > regards,
> >
> > Shahaan
> >
> That's a good idea, and I had started to look in that direction before -
> unfortunately that doesn't seem to be it.
> If I specify a wrong value for the schedd name it fails out without querying
> the local schedd; if I specify a different (unused) schedd in the pool, it
> succeeds with exit code 0;  if I go to that second machine and run my
> original -name with the correct name of the central manager, I get the same
> behavior as in my original test: valid output, exit code 1.
> You may suggest that I shouldn't care about this problem I've run into -
> just run condor_q without the -name, since there's only one active schedd..
>  Indeed, I wouldn't let it bother me, but I'm running CycleServer on top of
> my cluster, and that's how it generates its condor_q commands.  It took me a
> little while to figure out why it wasn't getting any job attributes..
> Sam
> On Thu, May 26, 2011 at 9:25 AM, Sam Gerstein <sgerstein@xxxxxxxxxxxxxxx>wrote:
> >
> >> I've searched around for an explanation of what might cause condor_q to
> >> give an exit code of 1 despite printing what appears to be normal complete
> >> output, but am at a loss - has anyone seen this before?
> >>
> >> What I've found is running "condor_q" and "condor_q -name
> >> my_schedd_hostname" produce the same output, but the latter returns exit
> >> code 1.
> >> I'm running 7.4.4, with quill, on ubuntu.  When I tested again just now I
> >> had about 200 jobs in my queue; I don't know whether behavior is different
> >> depending on queue depth.
> >>
> >> Thanks for any assistance you can provide-
> >> Sam