AutoSys Workload Automation

Expand all | Collapse all

Autosys Event_Demon log file permission issue

Jump to Best Answer
  • 1.  Autosys Event_Demon log file permission issue

    Posted 05-30-2016 06:11 AM


    We are running Autosys 4.5 instance on Linux machine

    We see that event_demon log has been created with incorrect permissions.

     

    No read permission for the other(s)/group.

     

    -rw-------

    The above read/write is only for the persons logging as autosys ID

     

    On normal cases, it should be:

     

    -rw-r--r--

     

    We are seeing this issue from recent times.

     

    Kindly help.



  • 2.  Re: Autosys Event_Demon log file permission issue

    Posted 05-31-2016 09:49 AM

    I suspect this would be related to the umask setting for the user starting the event_demon.

     

    For example, perhaps when you start as root you get 0600 but when you start using autosys (or some other) user you get 0644. Or vice versa.



  • 3.  Re: Autosys Event_Demon log file permission issue

    Posted 05-31-2016 10:34 AM

    Mark,

     

    Thanks for your reply.

    But our Autosys id is having 0002 as the umask value.

    Also not for all instances we get this issue and we recently started seeing this in couple of instances.

    Always the Autosys instance will be started under "Autosys" id only.

     

    Do you know how can be prevent this?

     

    Thanks in advance.



  • 4.  Re: Autosys Event_Demon log file permission issue

    Posted 05-31-2016 12:44 PM

    I assume you mean 0022 for your autosys id. Since this recently started, it suggests that something changed. Has the mount point changed at all? What does 'mount' reflect for the log location?



  • 5.  Re: Autosys Event_Demon log file permission issue

    Posted 06-01-2016 01:25 AM

    Hi Mark,

     

    Thanks for your response.

    umask value for Autosys ID is 0002 and not 0022 for the issue server.

    We don't know if mount point has been changed. The file system is mounted on "Root" currently.

    Another instance resolved on it own when it created a new file after 00:00 AM after a couple of days.

    But still this is been a problem



  • 6.  Re: Autosys Event_Demon log file permission issue
    Best Answer

    Posted 06-01-2016 11:39 AM

    I did see some reports of similar behavior in some old 4.5.x cases. In a couple cases it occurred following an OS update.

    In each case the problem resolved itself after a midnight rollover (as you described for one instance) or it was resolved following a restart at the next maintenance.

    As a precaution, check your eventor script to make sure it has not been modified.

    You should find the following lines within:

     

    touch $outfile

    chmod 644 $outfile

     

    At the next EP restart ensure that the out directory and log files are at the expected permissions prior to restart.

    Correct as needed.



  • 7.  Re: Autosys Event_Demon log file permission issue

    Community Manager
    Posted 05-31-2016 10:33 AM

    Vignesh, did Mark's suggestion help you? Can you come back and let us know? Thanks!



  • 8.  Re: Autosys Event_Demon log file permission issue

    Posted 05-31-2016 10:35 AM

    Hi Lenn,

     

    Just explained more about this with the umask value for our "Autosys" id

    Also requested help on how can we prevent the issue and what's the solution



  • 9.  Re: Autosys Event_Demon log file permission issue

    Broadcom Employee
    Posted 06-13-2016 02:42 AM

    Hi Vignesh

    A few more explanantions about umask setting

    Default umask value for any Unix/Linux file is 666

    I would suggest to set umask 022 in /etc/auto.profile which is normally executed by the autosys userid

    By setting umask 022, permissions of the newly created files will be 644

     

    0110 0110 0110

    0000 0010 0010

    ---------------------

    0110 0100 0100

    6        4      4

     

    Otherwise you can also trace the event_demon process with an strace command like: strace -f -o /tmp/event_demon.trace -p <PID of event_demon process>

     

    Regards

    Jean Paul