Custom Query (431 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (22 - 24 of 431)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Ticket Resolution Summary Owner Reporter
#369 fixed IZ2075: help output for qstat -explain should mention only usable for queue instance Dave Love <d.love@…> ovid
Description

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

        Issue #:      2075             Platform:     Sun      Reporter: ovid (ovid)
       Component:     gridengine          OS:        All
     Subcomponent:    clients          Version:      6.0u4       CC:    None defined
        Status:       NEW              Priority:     P5
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    roland (roland)
      QA Contact:     roland
          URL:
       * Summary:     help output for qstat -explain should mention only usable for queue instance
   Status whiteboard:
      Attachments:

     Issue 2075 blocks:
   Votes for issue 2075:


   Opened: Thu Jun 15 15:50:00 -0700 2006 
------------------------


qstat -explain E broken

Here's the plain output:


sgetest@dt218-130# qstat -explain E
queuename                      qtype used/tot. load_avg arch          states
----------------------------------------------------------------------------
all.q@dt218-130                BIPC  1/20      0.05     lx24-x86
   1378 0.50617 PENDING    sgetest      r     06/15/2004 15:39:03     1 2
----------------------------------------------------------------------------
all.q@dt218-141                BIPC  2/40      0.02     sol-x86
   1374 0.55500 ARRAY      sgetest      r     06/15/2004 15:39:03     1 2
   1378 0.50617 PENDING    sgetest      r     06/15/2004 15:39:03     1 1
----------------------------------------------------------------------------
all.q@dt218-155                BIPC  0/20      0.36     sol-amd64
----------------------------------------------------------------------------
all.q@dt218-170                BIPC  2/40      0.00     sol-amd64
   1374 0.55500 ARRAY      sgetest      r     06/15/2004 15:39:03     1 3
   1378 0.50617 PENDING    sgetest      r     06/15/2004 15:39:03     1 3
----------------------------------------------------------------------------
all.q@dt218-32                 BIPC  3/4       0.01     sol-sparc
   1373 0.55500 SEQUENTIAL sgetest      r     06/15/2004 15:39:03     1
   1374 0.55500 ARRAY      sgetest      r     06/15/2004 15:39:03     1 4
   1378 0.50617 PENDING    sgetest      r     06/15/2004 15:39:03     1 4
----------------------------------------------------------------------------
all.q@dt218-65                 BIPC  1/40      0.02     sol-sparc64
   1374 0.55500 ARRAY      sgetest      r     06/15/2004 15:39:03     1 1

############################################################################
 - PENDING JOBS - PENDING JOBS - PENDING JOBS - PENDING JOBS - PENDING JOBS
############################################################################
   1376 0.55500 ERROR      sgetest      Eqw   06/15/2004 15:38:56     1
   1377 0.00000 HOLD       sgetest      hqw   06/15/2004 15:38:56     1


Pretty much like qstat -f.

The XML output is no better:

sgetest@dt218-130# qstat -explain E -xml
<?xml version='1.0'?>
<job_info  xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <queue_info>
    <Queue-List>
      <name>all.q@dt218-130</name>
      <qtype>BIPC</qtype>
      <slots_used>1</slots_used>
      <slots_total>20</slots_total>
      <load_avg>0.04000</load_avg>
      <arch>lx24-x86</arch>
      <job_list state="running">
        <JB_job_number>1378</JB_job_number>
        <JAT_prio>0.50617</JAT_prio>
        <JB_name>PENDING</JB_name>
        <JB_owner>sgetest</JB_owner>
        <state>r</state>
        <JAT_start_time>06/15/2004 15:39:03</JAT_start_time>
        <slots>1</slots>
        <tasks>2</tasks>
      </job_list>
    </Queue-List>
....

<job_info>
    <job_list state="pending">
      <JB_job_number>1376</JB_job_number>
      <JAT_prio>0.55500</JAT_prio>
      <JB_name>ERROR</JB_name>
      <JB_owner>sgetest</JB_owner>
      <state>Eqw</state>
      <JB_submission_time>06/15/2004 15:38:56</JB_submission_time>
      <slots>1</slots>
    </job_list>
    <job_list state="pending">
      <JB_job_number>1377</JB_job_number>
      <JAT_prio>0.00000</JAT_prio>
      <JB_name>HOLD</JB_name>
      <JB_owner>sgetest</JB_owner>
      <state>hqw</state>
      <JB_submission_time>06/15/2004 15:38:56</JB_submission_time>
      <slots>1</slots>
    </job_list>
  </job_info>
</job_info>


But the help flag says

sgetest@dt218-130#  qstat -help
SGE 6.0u4
usage: qstat [options]
        [-ext]                            view additional attributes
        [-explain a|c|A|E]                show reason for c(onfiguration
amiguous), a(larm), suspend A(larm), E(rror) state

   ------- Additional comments from roland Thu Nov 16 01:04:17 -0700 2006 -------
The comments section is incorrect because it mixes job error with queue error.
The "qstat -qs E" switch is a queue filter and shows all queues in error state
AND all pending jobs. The "qstat -f -qs E" should print the same output as
"qstat -qs E". This is not the case, it prints nothing.

My suspicion is qstat -f recognize no queues are selected and then print's no
output. This is wrong because it has to print the pending jobs.

   ------- Additional comments from roland Thu Nov 16 01:07:37 -0700 2006 -------
The last comment is wrong (belongs to issue 2073)

   ------- Additional comments from roland Thu Nov 16 01:08:51 -0700 2006 -------
qstat is not broken. The '-explain' switch shows only the state of a queue
instance. It's correctly documented in the man page:
-explain a|A|c|E
          'c' displays the reason for the configuration ambiguous
          state of a queue instance. 'a' shows the reason for the
          alarm  state.  Suspend  alarm  state  reasons  will  be
          displayed  by  'A'. 'E' displays the reason for a queue
          instance error state.

In the mentioned example a job is in error state. The reason for this error can
be found in the 'qstat -j <jobid' output.

The -help output should be improved.
#379 fixed IZ2102: Interpret $TASK_ID also for non-array jobs in -o / -e Dave Love <d.love@…> reuti
Description

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

        Issue #:      2102             Platform:     All           Reporter: reuti (reuti)
       Component:     gridengine          OS:        All
     Subcomponent:    kernel           Version:      6.0u8            CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     andreas
          URL:
       * Summary:     Interpret $TASK_ID also for non-array jobs in -o / -e
   Status whiteboard:
      Attachments:

     Issue 2102 blocks:
   Votes for issue 2102:


   Opened: Tue Sep 26 02:45:00 -0700 2006 
------------------------


Some automatic processing would be easier to implement, if also non-array jobs would have a task id
set in their filenames (-o / -e), which could be 0. The assembly of the filenames seems to happen in
"execd/get_path.c":

          if (ja_task_id) {
             if (!strncmp(t, "$TASK_ID", sizeof("$TASK_ID") - 1)) {
                sprintf(exp_path, "%s" sge_u32, exp_path, ja_task_id);
                s = t + sizeof("$TASK_ID") - 1;
             }
          }

by removing the ja_task_id test and use just the 0. So the RFE would be to interpret $TASK_ID always in
-o / -e. Maybe keeping the default name without an additional .0 at the end, would allow users to
decide whether non-array jobs should have such an extension or not. If they want it, the simply have to
request: -o '$JOB_NAME.o$JOB_ID.$TASK_ID' (well, the po/pe output will be joint with o/e this way,
which you can't prevent).
#414 fixed IZ2217: daemos/common/procfs.c failed to compile Dave Love <d.love@…> nova
Description

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

        Issue #:      2217             Platform:     PC       Reporter: nova (nova)
       Component:     gridengine          OS:        Linux
     Subcomponent:    build            Version:      6.0u10      CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     andreas
          URL:
       * Summary:     daemos/common/procfs.c failed to compile
   Status whiteboard:
      Attachments:
                      Date/filename:                                   Description:                    Submitted by:
                      Tue Sep 25 07:59:00 -0700 2007: procfs-diffs.txt patch with sysconf (text/plain) olesen

     Issue 2217 blocks:
   Votes for issue 2217:


   Opened: Tue Mar 20 10:28:00 -0700 2007 
------------------------


Compilation of procfs.c fails with the error about an undefined symbol "HZ".
It's on the openSUSE 10.2 x86_64 Linux with 2.6.18.8 kernel.

As I could found out, the problem is in the included <sys/param.h> header, which
in turn includes asm/params.h from kernel source. Apparently, the "HZ"
definition there has been changed in the kernel version <=2.6.18. One need to
#define __KERNEL__ now to obtain it, which can bring some side effects I think.
And it seems that to convert jiffies to seconds in procfs.c one should use
"USER_HZ", not "HZ".

I think the workaround is to use HZ=sysconf(_SC_CLK_TCK) (from <unistd.h>), or
function like jiffies_to_*() from <linux/jiffies.h>. Don't know though if this
is portable.

   ------- Additional comments from olesen Tue Sep 25 07:59:40 -0700 2007 -------
Created an attachment (id=121)
patch with sysconf

   ------- Additional comments from olesen Tue Sep 25 08:10:30 -0700 2007 -------
I just ran into this compile issue as well and needed to find the cause (qucikly).
From man page, it would look like the sysconf(3) is really the right thing to do
(ie, POSIX).

The following mini program yields '100' on SuSE 9.2 (2.6.8-24) and on SuSE 10.2.
This is identical to the HZ define.

If this same functionality is available in the older 2.4 kernels, sysconf()
could be used throughout.

#include <stdio.h>
#include <unistd.h>
int main()
{
    printf("sysconf(_SC_CLK_TCK) = %ld\n", sysconf(_SC_CLK_TCK));
    return 0;
}
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Note: See TracQuery for help on using queries.