Opened 10 years ago

Closed 9 years ago

#799 closed defect (invalid)

IZ3261: Job submission fails with "no suitable queues" when requesting SGE complexes

Reported by: benmwebb Owned by:
Priority: normal Milestone:
Component: sge Version: 6.1u3
Severity: minor Keywords: PC Linux drmaa
Cc:

Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=3261]

        Issue #:      3261             Platform:     PC       Reporter: benmwebb (benmwebb)
       Component:     gridengine          OS:        Linux
     Subcomponent:    drmaa            Version:      6.1u3       CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    dagru (dagru)
      QA Contact:     templedf
          URL:
       * Summary:     Job submission fails with "no suitable queues" when requesting SGE complexes
   Status whiteboard:
      Attachments:
                      Date/filename:                               Description:              Submitted by:
                      Tue Apr 13 22:50:00 -0700 2010: drmaa_test.c drmaa_test.c (text/plain) benmwebb

     Issue 3261 blocks:
   Votes for issue 3261:


   Opened: Tue Apr 13 22:49:00 -0700 2010 
------------------------


drmaa_run_job fails reporting "no suitable queues" whenever we try to run a job that requests an SGE complex, i.e. if

1. We set drmaa_native_specification to '-b no' and add '#$ -l mem_free=1G' to the remote_command shell script.
or
2. We set drmaa_native_specification to '-l mem_free=1G'.
or
3. We add 'testcomplex -l mem_free=1G' to ~/.qtask and set drmaa_job_category to 'testcomplex'.

The same scripts work without any problems with qsub, and DRMAA submission works fine once we remove any '-l' options.

I'm attaching a test program for (2) above. It's basically the simple job submission example from the DRMAA tutorial, with a simple addition
to set native_specification. When built and run, it yields the following on our systems:

% gcc -Wall drmaa_test.c  -I /home/sge61/include -ldrmaa -L /home/sge61/lib/lx24-amd64/
% LD_LIBRARY_PATH=/home/sge61/lib/lx24-amd64/ ./a.out
Could not submit job: error: no suitable queues

   ------- Additional comments from benmwebb Tue Apr 13 22:50:04 -0700 2010 -------
Created an attachment (id=202)
drmaa_test.c

   ------- Additional comments from benmwebb Wed Apr 14 13:02:45 -0700 2010 -------
On digging around in the code, I see this particular error code originates from deep within qmaster, thus it should not be DRMAA-specific.
And indeed, if I submit an equivalent script (option 1 in my original report) with qsub and add the '-w v' option, it also fails with the
same error. So I guess job verification is turned on by default for DRMAA for some reason. Adding '-w n' to my DRMAA native specification
makes things work for me. Is this a known bug in the 6.1u3 qmaster?

Attachments (1)

202 (2.5 KB) - added by dlove 9 years ago.

Download all attachments as: .zip

Change History (2)

Changed 9 years ago by dlove

comment:1 Changed 9 years ago by dlove

  • Resolution set to invalid
  • Severity set to minor
  • Status changed from new to closed

-w n is the default for DRMAA.

Note: See TracTickets for help on using tickets.