Custom Query – Son of Grid Engine

Description

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

        Issue #:      2058             Platform:     Sun      Reporter: roland (roland)
       Component:     gridengine          OS:        All
     Subcomponent:    man              Version:      6.0         CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     andreas
          URL:
       * Summary:     shell_start_mode should be documentated to be only used for batch jobs
   Status whiteboard:
      Attachments:

     Issue 2058 blocks:
   Votes for issue 2058:


   Opened: Mon May 22 01:24:00 -0700 2006 
------------------------


The shell_start_mode in described queue_conf(5) but the man page. From the man
page a user could think the option affects all jobs but that's not true. The
shell_start_mode is only used for batch jobs submitted by qsub and is not used
for interactive jobs submitted by qrsh/qsh/qlogin.

Description

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

        Issue #:      2059             Platform:     All      Reporter: andreas (andreas)
       Component:     gridengine          OS:        All
     Subcomponent:    drmaa            Version:      6.0         CC:    None defined
        Status:       STARTED          Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    templedf (templedf)
      QA Contact:     templedf
          URL:        http://gridengine.sunsource.net/servlets/BrowseList?list=dev&by=thread&from=12304
       * Summary:     shared library name DT_SONAME not set with libdrmaa.so
   Status whiteboard:
      Attachments:

     Issue 2059 blocks:
   Votes for issue 2059:


   Opened: Tue May 23 07:57:00 -0700 2006 
------------------------


DESCRIPTION:
Under Linux there is a ld(1) option

-soname=name
  When creating an ELF shared  object,  set  the  internal
  DT_SONAME field  to  the specified name.  When an executable is linked
  with a shared object which has a DT_SONAME field, then when the
  executable is  run  the  dynamic linker will attempt to load the shared
  object specified by the DT_SONAME field rather than  the  using  the
  file name given to the linker.

for setting a shared libraries DT_SONAME.

An application linked with a shared library with DT_SONAME
can detect at deployment time, if the library in LD_LIBRARY_PATH
has the right version. Without DT_SONAME being set it can occur
the application starts though, but shows strange error behaviour
during run-time.

COMMENTS:
Until now (6.0u8) libdrmaa.so delivered with N1GE is of version 0.95.
It is planned though to deliver in future releases a DRMAA 1.0 library
*plus* the old 0.95 compliant one.

WORKAROUND:
As workaround the application shall use drmaa_version() to ensure
LD_LIBRARY_PATH libdrmaa.so has the correct version.

   ------- Additional comments from andreas Tue May 23 08:20:43 -0700 2006 -------
There is a related problem with libdrmaa.so 0.95/1.0:

I just encountered libdrmaa.0.95.so (maintrunk) even had linking
symbols

   int drmaa_get_num_attr_names(drmaa_attr_names_t* values, int *size);
   int drmaa_get_num_attr_values(drmaa_attr_values_t* values, int *size);
   int drmaa_get_num_job_ids(drmaa_job_ids_t* values, int *size);

even though these functions actually are DRMAA 1.0 specific. I fixed
it (maintrunk). Now at least DRMAA 1.0 applications will fail with a
more reasonable error message, in case LD_LIBRARY_PATH libdrmaa is 0.95.


   ------- Additional comments from andreas Tue May 23 09:03:20 -0700 2006 -------
Added URL to thread with details on how to solve the -soname issue.

   ------- Additional comments from andreas Mon May 29 00:28:05 -0700 2006 -------
Fixed for in Maintrunk and S2-branch for Solaris and Linux

Description

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

        Issue #:      2060             Platform:     Sun      Reporter: ovid (ovid)
       Component:     gridengine          OS:        All
     Subcomponent:    clients          Version:      6.0u4       CC:    None defined
        Status:       NEW              Priority:     P4
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    roland (roland)
      QA Contact:     roland
          URL:
       * Summary:     qstat -pri -xml reports data imcompletely
   Status whiteboard:
      Attachments:

     Issue 2060 blocks:
   Votes for issue 2060:


   Opened: Tue May 23 15:06:00 -0700 2006 
------------------------


Plain output of qstat -pri looks like this:


sgetest@dt218-123# qstat -pri
job-ID  prior   nurg    npprior ntckts   ppri name       user         state
submit/start at     queue                          slots ja-task-ID
----------------------------------------------------------------------------------------------------------------------------------------------------
   6794 0.50500 0.00000 0.50000 0.50000     0 SEQUENTIAL sgetest      r
05/23/2006 13:51:28 all.q@dt218-123                    1
   6795 0.50500 0.00000 0.50000 0.50000     0 ARRAY      sgetest      r
05/23/2006 13:51:28 all.q@dt218-123                    1 3
   6799 0.45617 0.00000 0.45117 0.50000  -100 PENDING    sgetest      r
05/23/2006 13:51:28 all.q@dt218-123                    1 1
   6799 0.45617 0.00000 0.45117 0.50000  -100 PENDING    sgetest      r
05/23/2006 13:51:28 all.q@dt218-123                    1 4


The same output in XML format looks like this:

sgetest@dt218-123# qstat -pri -xml
<?xml version='1.0'?>
<job_info  xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <queue_info>
    <job_list state="running">
      <JB_job_number>6794</JB_job_number>
      <JAT_prio>0.50500</JAT_prio>
      <JB_nppri>0.50000</JB_nppri>
      <JB_priority>0</JB_priority>
      <JB_name>SEQUENTIAL</JB_name>
      <JB_owner>sgetest</JB_owner>
      <state>r</state>
      <JAT_start_time>05/23/2006 13:51:28</JAT_start_time>
      <queue_name>all.q@dt218-123</queue_name>
      <slots>1</slots>
    </job_list>
    <job_list state="running">
      <JB_job_number>6795</JB_job_number>
      <JAT_prio>0.50500</JAT_prio>
      <JB_nppri>0.50000</JB_nppri>
      <JB_priority>0</JB_priority>
      <JB_name>ARRAY</JB_name>
      <JB_owner>sgetest</JB_owner>
      <state>r</state>
      <JAT_start_time>05/23/2006 13:51:28</JAT_start_time>
      <queue_name>all.q@dt218-123</queue_name>
      <slots>1</slots>
      <tasks>3</tasks>
    </job_list>


Note that the XML output lacks the nurg and ntckts columns!

SGE

Context Navigation

Custom Query (431 matches)

Results (94 - 96 of 431)

Download in other formats:

Ticket	Resolution	Summary	Owner	Reporter
#357	fixed	IZ2058: shell_start_mode should be documentated to be only used for batch jobs		roland
Description	[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2058] Issue #: 2058 Platform: Sun Reporter: roland (roland) Component: gridengine OS: All Subcomponent: man Version: 6.0 CC: None defined Status: NEW Priority: P3 Resolution: Issue type: DEFECT Target milestone: --- Assigned to: andreas (andreas) QA Contact: andreas URL: * Summary: shell_start_mode should be documentated to be only used for batch jobs Status whiteboard: Attachments: Issue 2058 blocks: Votes for issue 2058: Opened: Mon May 22 01:24:00 -0700 2006 ------------------------ The shell_start_mode in described queue_conf(5) but the man page. From the man page a user could think the option affects all jobs but that's not true. The shell_start_mode is only used for batch jobs submitted by qsub and is not used for interactive jobs submitted by qrsh/qsh/qlogin.
#358	fixed	IZ2059: shared library name DT_SONAME not set with libdrmaa.so		andreas
Description	[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2059] Issue #: 2059 Platform: All Reporter: andreas (andreas) Component: gridengine OS: All Subcomponent: drmaa Version: 6.0 CC: None defined Status: STARTED Priority: P3 Resolution: Issue type: DEFECT Target milestone: --- Assigned to: templedf (templedf) QA Contact: templedf URL: http://gridengine.sunsource.net/servlets/BrowseList?list=dev&by=thread&from=12304 * Summary: shared library name DT_SONAME not set with libdrmaa.so Status whiteboard: Attachments: Issue 2059 blocks: Votes for issue 2059: Opened: Tue May 23 07:57:00 -0700 2006 ------------------------ DESCRIPTION: Under Linux there is a ld(1) option -soname=name When creating an ELF shared object, set the internal DT_SONAME field to the specified name. When an executable is linked with a shared object which has a DT_SONAME field, then when the executable is run the dynamic linker will attempt to load the shared object specified by the DT_SONAME field rather than the using the file name given to the linker. for setting a shared libraries DT_SONAME. An application linked with a shared library with DT_SONAME can detect at deployment time, if the library in LD_LIBRARY_PATH has the right version. Without DT_SONAME being set it can occur the application starts though, but shows strange error behaviour during run-time. COMMENTS: Until now (6.0u8) libdrmaa.so delivered with N1GE is of version 0.95. It is planned though to deliver in future releases a DRMAA 1.0 library plus the old 0.95 compliant one. WORKAROUND: As workaround the application shall use drmaa_version() to ensure LD_LIBRARY_PATH libdrmaa.so has the correct version. ------- Additional comments from andreas Tue May 23 08:20:43 -0700 2006 ------- There is a related problem with libdrmaa.so 0.95/1.0: I just encountered libdrmaa.0.95.so (maintrunk) even had linking symbols int drmaa_get_num_attr_names(drmaa_attr_names_t* values, int size); int drmaa_get_num_attr_values(drmaa_attr_values_t values, int size); int drmaa_get_num_job_ids(drmaa_job_ids_t values, int *size); even though these functions actually are DRMAA 1.0 specific. I fixed it (maintrunk). Now at least DRMAA 1.0 applications will fail with a more reasonable error message, in case LD_LIBRARY_PATH libdrmaa is 0.95. ------- Additional comments from andreas Tue May 23 09:03:20 -0700 2006 ------- Added URL to thread with details on how to solve the -soname issue. ------- Additional comments from andreas Mon May 29 00:28:05 -0700 2006 ------- Fixed for in Maintrunk and S2-branch for Solaris and Linux
#359	fixed	IZ2060: qstat -pri -xml reports data imcompletely	Dave Love <d.love@…>	ovid
Description	[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2060] Issue #: 2060 Platform: Sun Reporter: ovid (ovid) Component: gridengine OS: All Subcomponent: clients Version: 6.0u4 CC: None defined Status: NEW Priority: P4 Resolution: Issue type: DEFECT Target milestone: --- Assigned to: roland (roland) QA Contact: roland URL: * Summary: qstat -pri -xml reports data imcompletely Status whiteboard: Attachments: Issue 2060 blocks: Votes for issue 2060: Opened: Tue May 23 15:06:00 -0700 2006 ------------------------ Plain output of qstat -pri looks like this: sgetest@dt218-123# qstat -pri job-ID prior nurg npprior ntckts ppri name user state submit/start at queue slots ja-task-ID ---------------------------------------------------------------------------------------------------------------------------------------------------- 6794 0.50500 0.00000 0.50000 0.50000 0 SEQUENTIAL sgetest r 05/23/2006 13:51:28 all.q@dt218-123 1 6795 0.50500 0.00000 0.50000 0.50000 0 ARRAY sgetest r 05/23/2006 13:51:28 all.q@dt218-123 1 3 6799 0.45617 0.00000 0.45117 0.50000 -100 PENDING sgetest r 05/23/2006 13:51:28 all.q@dt218-123 1 1 6799 0.45617 0.00000 0.45117 0.50000 -100 PENDING sgetest r 05/23/2006 13:51:28 all.q@dt218-123 1 4 The same output in XML format looks like this: sgetest@dt218-123# qstat -pri -xml <?xml version='1.0'?> <job_info xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <queue_info> <job_list state="running"> <JB_job_number>6794</JB_job_number> <JAT_prio>0.50500</JAT_prio> <JB_nppri>0.50000</JB_nppri> <JB_priority>0</JB_priority> <JB_name>SEQUENTIAL</JB_name> <JB_owner>sgetest</JB_owner> <state>r</state> <JAT_start_time>05/23/2006 13:51:28</JAT_start_time> <queue_name>all.q@dt218-123</queue_name> <slots>1</slots> </job_list> <job_list state="running"> <JB_job_number>6795</JB_job_number> <JAT_prio>0.50500</JAT_prio> <JB_nppri>0.50000</JB_nppri> <JB_priority>0</JB_priority> <JB_name>ARRAY</JB_name> <JB_owner>sgetest</JB_owner> <state>r</state> <JAT_start_time>05/23/2006 13:51:28</JAT_start_time> <queue_name>all.q@dt218-123</queue_name> <slots>1</slots> <tasks>3</tasks> </job_list> Note that the XML output lacks the nurg and ntckts columns!