An EVENT:UNIXCMD fails with the following message if the user in the login object is a different one than started the Linux/Unix agent.
U00010038 Runtime error: Could not create data sequence 'FILETRANSFER'. Status: '0000001820', return code: '0000000000'.
The following messages can be seen in the messages window:
U00010038 Runtime error: Could not create data sequence 'FILETRANSFER'. Status: '0000001820', return code: '0000000000'.
U00029003 Cannot open file 'EAADIICG.TXT', error code '2', error description: 'No such file or directory'.
U00011000 'REPORT' (RunID: '0001517004') could not be started on 'LINUX_AGENT'. See next message.
U00011003 Job 'EVENT.UNIXCMD' (RunID '0001517003') on Host 'LINUX_AGENT' aborted (return code='0001'). Remote ID=1436
The Linux/Unix agent has the following entries in its log file:
/opt/automic/agent/temp/JAADIICH.TXT.sh: line 23: /home/support/EAADIICG.TXT: Permission denied
rm: cannot remove '/home/support/EAADIICG.TXT': Permission denied
U02000015 Periodical job test started.
U02000482 Process '1436' for Run-Id '1517003', ended with exit code: '1'. Possible error description: 'General error.'.
U02000009 Job 'EVENT.UNIXCMD' with RunID '1517003' ended with return code '1'.
U02001026 Job 'EVENT.UNIXCMD' with RunID '1517003' has been removed from the job table.
U00029000 Report '1517004' for file 'EAADIICG.TXT' has been started.
U00029003 Cannot open file 'EAADIICG.TXT', error code '2', error description: 'No such file or directory'.
U00045014 Exception 'java.nio.file.NoSuchFileException: "Failed to open file: 'EAADIICG.TXT', errno: 2 (No such file or directory)"' at 'com.automic.os.process.unix.ErrnoException.checkForException():72'.
U00029002 Report '1517004' ended abnormally.
Agent Java Unix 21.0.x and 24.x
DE171612
Update to a fix version listed below or a newer version if available.
Fix version:
Component(s): Agent Java Unix
Automation.Engine 21.0.15 - Available
Automation.Engine 24.4.1 HF2 - Available
Automation.Engine 24.4.2 - Available
Public Title: PREP_PROCESS UNIXCMD not setting correct environments
Public Description: A problem has been fixed where Jobs that started with a specific user Login did not set the correct environment variables, such as "HOME".