Automic Workload Automation

  • Private Community
 View Only

  • 1.  Automic Linux/Solaris Agent Temp Log Ownership Issue After Upgrade 24.4.4 HF2

    Posted 20 days ago

    I'm facing a strange issue with Automic agents running on Linux/Solaris.

    Normally, we have been setting the SUID bit (s-bit) and root ownership on the ucxjlx6 file for many years without any issues. This has been our standard configuration.

    After upgrading to Agent 24.4.4 HF2, we noticed that the temporary log files created by the agent are now owned by root. As a result, we are unable to read these logs with the expected agent user permissions.

    With earlier agent versions, under the same configuration and permission model (SUID bit (s-bit) and root ownership ), the temporary log files were owned by the Automic agent user, and we did not experience this issue.

    It seems that something may have changed in this 24.4.4 HF2 version regarding log file creation or ownership handling.

    Has anyone else encountered this behavior after upgrading to 24.4.4 HF2? If so, were you able to identify the root cause or find a workaround/solution?

    Any insights would be greatly appreciated. Thanks!



    ------------------------------
    Olgun Onur Ozmen
    https://www.linkedin.com/in/olgunonurozmen/
    ------------------------------


  • 2.  RE: Automic Linux/Solaris Agent Temp Log Ownership Issue After Upgrade 24.4.4 HF2

    Posted 19 days ago

    Hello,
    we dont have this behaviour.
    That what i know is, if you start your servicemanager with root privileges the logs of servicemanager and agents are owned by root.




  • 3.  RE: Automic Linux/Solaris Agent Temp Log Ownership Issue After Upgrade 24.4.4 HF2

    Posted 19 days ago

    Dear Olgun,

    please look at the agent process. Does it run under the user root? If it does, that's why the log files are owned by root.

    These are some scenarios I can imagine why this happened:

    • at least with Version 24 the agent needs to run with java. As far as I can remember, the upgrade to a java based agent version was not possible with CAU, so you might have installed the agent manually or with a script, at some point running with root privileges. Perhaps the last step in that procedure was to start the agent (without restarting or triggering the servicemanager) and that was done by root?
    • check your systemctl script and the owner of the servicemanager files. The servicemanager binaries should be owned by your automic user for the agent to run under that user.


    ------------------------------
    Regards, Nicole
    ------------------------------