Linux Agent not executing FileEvent objects

Document ID : KB000087463
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
U2003041 Invalid 'access' call, file name '/iface/AT1/FDWH/in/305/', Error code: ('13' - 'Permission denied')

After an upgrade of a Linux Agent from version 8 to version 10.0.7.392 the FileEvent objects are no longer executed.

Error Indication

The 'technical user' has no permissions on specific folders.
 
U2003041 Invalid 'access' call, file name '/iface/AT1/FDWH/in/305/', Error code: ('13' - 'Permission denied') 
Environment:
OS Version: N/A
Cause:
Root Cause: The handling of process user IDs of the Unix Agent changed in order to enable the Agent to handle user context switches more powerfully.
Resolution:
The following changes are recommended to overcome this problem.

n the ini-file of the affected agent, set the following parameter: 

[MISC] 
SwitchToEffUser=yes 

 
Then restart the Agent.

This parameter isn't in the documentation yet, but as the name of the parameter suggests, it causes the job to use effective user rights for the job. Another way to alleviate the issue is to set the user rights for all directories, from root to the affected directory, the rights drwxrwxr--.

Handling process user IDs for the Unix Agent changed in order to enable the Agent to handle user context switches more powerfully. The Agent obtained real user root privileges in addition to effective user root privileges. For that reason, the Service Manager also must be started with root privileges which in turn caused a series of problems when the ServiceManager did not find a valid LD_LIBRARY_PATH or LIBPATH for the Service Manager and the components it started.

This method of handling user privileges has been changed as follows:

The Unix Agent no longer needs to obtain root privileges for the real user of its process. The Agents real user now is the start user (V8 behavior). As a consequence, the Sevice Manager for Unix no longer needs to be started with root user privileges to be able to terminate the Unix Agent.

As a result, the installation procedure for the Unix Agent is simpler and similar to the installation method of V8 Unix Agents.

Resource

Also check out following post on Automic Community:

 

Fix Status: No Fix

Fix Version(s):
N/A
Additional Information:
Workaround :
N/A