Unix Java Agent does not set HOME variable for jobs when started with systemd in v24
Article ID: 411134
Updated On:
Products
Issue/Introduction
Post upgrade from v21 to v24, customers have reported that when the Unix Java Agent is started using systemd, the HOME environment variable is not set for the user defined within the LOGIN object. In this scenario, systemd is being initiated by the root user, which results in the agent not inheriting the expected environment variable configuration.
This behavior is new to v24, as in v21 the HOME variable was automatically populated with the correct home directory path of the LOGIN object’s user. The problem does not occur when the agent is started directly from the command line, where the HOME variable is correctly set.
As a result, jobs that depend on the HOME environment variable may fail or behave unexpectedly when the agent is launched via systemd, while functioning normally when started manually from the command line.
Environment
Release: 24.4.x
Component: Unix Java Agent
Cause
DE176024
Resolution
Workaround:
Hardcoding the HOME variable in the systemd service configuration (for example, Environment=HOME=%h) is a workaround to ensure the variable is available when the agent is started via systemd.
Solution:
Update to a fix version listed below or a newer version if available.
Fix version:
Component(s): Agent Unix
Automation.Engine 24.4.2 HF1 - Available
Automation.Engine 24.4.3 - Planned release December 2025
Additional Information
Public Description: Agent Unix: job environment is not set properly for new Jobs, environment variables are not adapted properly if they are not inherited from parent process
Feedback
