Opened 14 years ago

Last modified 9 years ago

#307 new defect

IZ1926: no info messages in execd messages file

Reported by: crei Owned by:
Priority: normal Milestone:
Component: sge Version: 6.0
Severity: Keywords: AIX execution
Cc:

Description

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

        Issue #:      1926             Platform:     All      Reporter: crei (crei)
       Component:     gridengine          OS:        AIX
     Subcomponent:    execution        Version:      6.0         CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    pollinger (pollinger)
      QA Contact:     pollinger
          URL:
       * Summary:     no info messages in execd messages file
   Status whiteboard:
      Attachments:

     Issue 1926 blocks:
   Votes for issue 1926:


   Opened: Mon Nov 28 07:11:00 -0700 2005 
------------------------


The execd running on aix51 (denethor) doesn't report any
info messages after startup. There is no startup/shutdown
message. Message logging is set to info.

11/15/2005 15:32:13|execd|denethor|W|can't get load values
11/15/2005 15:36:38|execd|denethor|W|can't get load values
11/15/2005 15:56:26|execd|denethor|W|can't get load values

This bug is existing since GE 6.0:
06/29/2004 12:19:25|execd|denethor|W|can't get load values
06/29/2004 14:19:43|execd|denethor|W|can't get load values
06/29/2004 16:19:59|execd|denethor|W|can't get load values

   ------- Additional comments from crei Thu Dec 1 03:44:03 -0700 2005 -------
This seems to be a file permission problem

after installation the permissions of the execd messages file are:
-rw-r--r--   1 root     system           59 Dec 01 10:59 messages

when I change the permissions to

-rw-rw-rw-   1 root     system           59 Dec 01 10:59 messages

and restart the execd, the messages are written as expected.

Change History (0)

Note: See TracTickets for help on using tickets.