Custom Query (431 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (16 - 18 of 431)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Ticket Resolution Summary Owner Reporter
#45 fixed IZ270: Make it possible not checking for binaries at install Dave Love <d.love@…> andy
Description

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

        Issue #:      270              Platform:     All           Reporter: andy (andy)
       Component:     gridengine          OS:        All
     Subcomponent:    install          Version:      5.3              CC:    None defined
        Status:       NEW              Priority:     P5
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    dom (dom)
      QA Contact:     dom
          URL:
       * Summary:     Make it possible not checking for binaries at install
   Status whiteboard:
      Attachments:

     Issue 270 blocks:
   Votes for issue 270:


   Opened: Tue May 28 01:33:00 -0700 2002 
------------------------


It should be possible to issue qmaster
installation without checking for the presensce of
all binaries (e.g a switch "-nobincheck")


Verification: If someone builds SGE without
support for all binaries (e.g. qmon) qmaster
installation will fail.

   ------- Additional comments from andy Tue Jun 15 06:38:58 -0700 2004 -------
reassigning
#64 fixed IZ358: Kerberos credentials are not being deleted on execution host svdavidson
Description

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

        Issue #:      358              Platform:     All      Reporter: svdavidson (svdavidson)
       Component:     gridengine          OS:        All
     Subcomponent:    execution        Version:      5.3         CC:    None defined
        Status:       REOPENED         Priority:     P4
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    svdavidson (svdavidson)
      QA Contact:     pollinger
          URL:
       * Summary:     Kerberos credentials are not being deleted on execution host
   Status whiteboard:
      Attachments:

     Issue 358 blocks:
   Votes for issue 358:


   Opened: Thu Aug 15 13:57:00 -0700 2002 
------------------------


While running some Kerberos cross-realm
authentication tests, I noticed that the Kerberos
forwarded credentials are not being deleted at the
end of the job. I ran the debug and found that the
delete_credentials() function is being called
properly, but the wrong credentials cache name is
being stored in KRB5CCNAME to pass to the
delete_cred security sub-program.  The name should
be FILE:/tmp/krb5cc_sge_<jobid>, but the name
being passed is FILE:/tmp/krb5cc_qmaster_<jobid>,
which is the name of the credenials cache used on
the qmaster host.  I plan on fixing this in the
5.3 branch and the main development trunk.

   ------- Additional comments from andreas Fri Mar 5 08:09:01 -0700 2004 -------
won't be fixed for 6.0 beta

   ------- Additional comments from andreas Mon Mar 29 04:53:02 -0700 2004 -------
Reopened.

   ------- Additional comments from sgrell Tue Dec 6 07:59:54 -0700 2005 -------
Changed the subcomponent.

Stephan
#85 fixed IZ483: reporting of reason for job abort fy
Description

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

        Issue #:      483              Platform:     All           Reporter: fy (fy)
       Component:     gridengine          OS:        All
     Subcomponent:    execution        Version:      5.3p2            CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     pollinger
          URL:
       * Summary:     reporting of reason for job abort
   Status whiteboard:
      Attachments:

     Issue 483 blocks:
   Votes for issue 483:


   Opened: Wed Feb 5 08:11:00 -0700 2003 
------------------------


When a job exceeds one of the resource limits, say
h_rt, the job is killed with SIGKILL, however,
there is no clear indication as to why the job was
killed. None of the files in $SGE_JOB_SPOOL_DIR
provide any added information, so writing an
epilog does not help. The best we can do is guess
from the failed code (=100), and
end_time-start_time.

The enhancment being asked for is some kind of
reason as to why the job was killed, e.g.
(reason=limit_exceeded, limit=h_rt).

   ------- Additional comments from andreas Fri Apr 15 06:56:13 -0700 2005 -------
HOWTOFIX:
In case a job was terminated due to limit exeeded a new SSTATE_* such as
SSTATE_LIMIT_EXCEEDED is needed. Each time sge_execd initiates job termination
a flag must be set with that job. This will sge_execd to report
SSTATE_LIMIT_EXCEEDED for those jobs/tasks.

   ------- Additional comments from andreas Mon Jul 25 02:15:10 -0700 2005 -------
Changed execd logging in Maintrunk from Info to Warning to improve diagnosics.
Further improvements seem possible. Added related comments to
daemons/execd/execd_signal_queue.c

   ------- Additional comments from andreas Mon Aug 8 04:16:35 -0700 2005 -------
See issue 1743 for a reasonable 6.0 based workaround and an RFE how to generally
improve job diagnostics based oo job life-cycle information available in
reporting(5).

   ------- Additional comments from sgrell Mon Dec 12 03:04:05 -0700 2005 -------
Changed the subcomponent.

Stephan
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Note: See TracQuery for help on using queries.