A JOBF fails when a symlink is not accessible
Article ID: 278907
Updated On:
Products
Issue/Introduction
An FT job tries to resolve a symlink that doesn't correspond to the filter defined in the FT jobs and fails if the Agent's user doesn't have permission to the folder in the link.
This fails even if FT_linkfiles=0 is set in the Agent's ini-file.
The issue happens independent of setting root or set-UID on the Agent's executable
Reproduction:
- Create the following files in a folder called /tmp/case/source/ on a Linux server:
-rw-rw-r--. 1 sup sup 0 Aug 23 14:47 logfile.txt
drwx------. 2 root root 35 Aug 23 14:50 root_folder
lrwxrwxrwx. 1 root root 33 Aug 23 14:53 xxx.txt -> root_folder/file_from_root_folder
- Create an FT job with the source file filter: /tmp/case/source/log*
- Start the FT job
It is expected that only file 'logfile.txt' transferred
However, the FT fails with the following error:
8/24/2023 02:35:06 PM U00011005 File transfer 'JOBF.CASE' (RunID '0002439015') ended abnormally.
8/24/2023 02:35:06 PM U00063014 Failed to read directory '/tmp/case/source'. Error: 'boost::filesystem::status: Permission denied [system:13]: '/tmp/case/source/xxx.txt''.
If the folder is accessible by user 'sup' the FT works.
Environment
OS: Unix/Linux
Cause
AE-33343
Resolution
Update to a fix version listed below or a newer version if available.
Fix version:
Component(s): Agent Unix
Automation.Engine 21.0.10 - Available
Additional Information
Defect Desc: A problem has been fixed where the Unix Agent did not process the ini file setting "ft_Linkfiles", and Filetransfers ended abnormally with "permission denied" because the Agent tried to access files that should not be accessed.
Feedback
